> ./cfgmaker creates MaxBytes[myserver.com.2]: 1250000. Since I know this is
> a 100Mbps interface, I set my.cfg as:
> 
> Target[myserver.com.2]: 2:boogers@myserver.com
> MaxBytes[myserver.com.2]: 12500000

correct (for an 100Mbps interface) as 100Mbps == 12,5MBps == 12500000 Bps

> kilo[myserver.com.2]: 1024

Incorrect as kilo == 1000. It is only 1024 for memory and for disk space.
Disk space is often calculated as being kilo = 1024 and mega = 1000 kilo.

> Options[myserver.com.2]: absolute
> 
> Options[myserver.com.2]: gauge
> 

Both are not needed nor wanted in this case.

> No matter what I do, the math just don't work. MRTG reports (default)
> values as kB/s although I see data moving at rates in mB/s. In other words,
> data transfers which are observed at 4mB/s are plotted at 800 kB/s
> (approximate values).
> 
Depending on your linux version, there may be a bug in the implementation.
It used to count packets, and returned the number of packets multiplied
with the average number of bytes per packet.
This average is not calculated but fixed.
Suppose it is 300 bytes/packet on average (I do not know this) and you
are using mostly 1500 bytes/packet, this would match exactly:

800kB/s --> 800,000/300 packets per second.
800,000/300*1500 == 4,000,000 Bps == 4MB/s

Not sure, just a guess.

Regards,
Alex

--
* To unsubscribe from the mrtg mailing list, send a message with the
  subject: unsubscribe to mrtg-request@list.ee.ethz.ch
* The mailing list archive is at http://www.ee.ethz.ch/~slist/mrtg