Hi Oliver, I had a similar problem with my application.
What is actually happening is that MRTG is designed with a 32-bit counter in mind. When it sees the count start again at 0, MRTG is assuming it reached the max ( 2^32-1 ) and then it wrapped around. What I can recommend is that you reduce the MaxBytes value to a number that is slightly higher than the max amount of traffic you expect to see between two MRTG samples, but a lot lower than the counter wrap-around value. Hope this helps. -- Hector Pier Programming Services Ltd. -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
