Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Oct 2002 09:55:30 +1000 (EST)
From:      Tony Maher <tonym@biolateral.com.au>
To:        stable@freebsd.org
Subject:   'losing' every second packet
Message-ID:  <200210022355.g92NtU1o029952@dt.home>

next in thread | raw e-mail | index | archive | help
Hello,

about 3-4 weeks ago my home firewall started to exhibit a strange
behaviour of losing what appears to be every second packet but _only_
after it has been running for more than 12 hrs (typically around the
24hr mark).  The only way to 'fix' it is to reboot.  Restarting firewall
rules does not help.

It was also about this time I modified my firewall to use squid and
started to run darkstat on both internal and external card. So I
initially  assumed it was something to do with that.  However I have
since turned off darkstat but the behaviour still remains.  I haven't
tried turning off squid yet but I doubt that it is the problem.

I also upgrade to 4-stable a few days ago (and started using ipfw2)
but the behaviour was similar. Had to reboot after about 24 hrs for the
first couple of days but yesterday had been running for more than 72 hrs
without problems but this morning (now that I am at work) it has
reappeared.  Cannot ssh to the firewall and ping shows 50% packet loss.
(FreeBSD gw 4.7-RC FreeBSD 4.7-RC #0: Wed Sep 25 06:10:10 EST 2002)

409 packets transmitted, 207 packets received, 49% packet loss
round-trip min/avg/max/stddev = 30.449/35.600/75.392/6.487 ms
(was also trying to ssh at the time so not 50% exactly)

Yesterday I also got confirmation from a colleague who runs a freebsd
firewall as well that he has similar problems (large packet loss
around 50%) in the same time-scale. He is unlikely to have modified
anything since we set it up. (He is away at present so I cannot get any
definitive answers about his setup. I do not think it has been upgraded
for several months, so it is probably release version 4.4).

We also run a freebsd firewall at work 4.4-STABLE that works perfectly
(uptime 220+ days).

What is in common is that our home firewalls are conected via cable
modem to optusnet.com.au (and the work firewall is on entirely
different network).  Also about 4 weeks ago optus changed their
charging policy to a 3Gb limit and maybe other changes to the
network?! Probes?!

Seems to be more than a coincidence.
Anybody else experiencing these problems?

The internal interface continues to work perfectly, and logging in and
checking logs and output from netstat and everything looks ok.

Just managed to login by running multiple concurrent ssh sessions
and rebooted. Works fine again.
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 31.681/40.618/50.807/6.888 ms

More details about configs etc available off-list but any ideas?

thanks
--
tonym

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210022355.g92NtU1o029952>