your issue here, we're
going to need to see evidence that shifts the finger of blame
back towards the FreeBSD networking code and away from your home
network where it is currently pointing.
cheers,
--
Matthew Hudson
___
freebsd-net@freebsd.org
is problem
from a different external network?
Actually, I just realized that you've provided enough information for me
to run this test myself which I've now done. I ran the following test;
i=0; while true; do ((i++)); echo $i; curl http://stbgo.org > /dev/null;
don
e chances that your ISP's support staff can
resolve the problem. Many times even if they know that a problem
exists they may not know how to resolve it... having tcpdumps handy
makes it easier for them to show the problem to someone else (say
the firewall/loadbalancer vendor) who can tell them how to fix it.
I know this from experience, I work at a company that makes
loadbalancers. ;)
Hope that helps,
--
Matthew Hudson
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hello everybody,
I believe I may have stumbled across a bug in the arp program and
the reproduction is simple (and should be easy to verify) so I'll
just jump to the point.
This is on 6.1-RELEASE-p3 i386
I discovered this while trying to create proxy-arp entries for a
subnet of a network I was
