Are there many people using FreeBSD 6.x and Smokeping?

I asked this a while back but nobody seemed to have any input. Ever since 
moving from FreeBSD 5.3 to 6.0 (currently 6.1) I have been seeing artificial 
loss in smokeping that does not exist. It always shows up as two repeated 
intervals of 19/20 packets received (light blue) and never at the same time on 
any of the monitors. I think there is some sort of ICMP rate limiting or 
something else going on in the kernel but I have never been able to locate it. 
Users on the FreeBSD-Stable list didn't have any input either. You can clearly 
see on all of my graphs at the precise time I upgraded from 5.3 to 6.0 there is 
slight loss from that time forward. It makes the graphs that are logged for 
long periods of time look bad (always light blue) instead of mostly green which 
they should be (for my network anyway). I've done numerous tests with other 
tools to verify there is no packet loss from the same machine. I cannot 
reproduce the statistics I see with Smokeping using anything else. I'm
 hoping someone might have some input (other than use Linux). :)

If you need any more information about my setup, just ask. Almost all probes 
are Fping based and there are somewhere between 50 and 60 monitors setup. The 
server is a Dell 2650 with dual P4 Xeon 2.8GHz CPU's. MP kernel is enabled. I 
was toying with disabling MP to see if it was some sort of weird problem with 
multiple CPU's.

Any help or suggestions are appreciated! :)

-- 

Vinny Abello
Network Engineer
Server Management
[EMAIL PROTECTED]
(973)300-9211 x 125
(973)940-6125 (Direct)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN

"Courage is resistance to fear, mastery of fear - not absence of fear" -- Mark 
Twain

--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://lists.ee.ethz.ch/smokeping-users
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi

Reply via email to