Date: Thu, 21 Dec 1995 17:14:50 +0100 From: Poul-Henning Kamp <phk@critter.tfs.com> To: Nate Williams <nate@rocky.sri.MT.net> Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), hackers@freebsd.org, isp@freebsd.org Subject: Re: BSD networking code guru needed? Message-ID: <5392.819562490@critter.tfs.com> In-Reply-To: Your message of "Thu, 21 Dec 1995 09:10:36 MST." <199512211610.JAA02765@rocky.sri.MT.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I have seen the same kind of trouble with arp, ipfw and routed. > > > > Basically packets would go another way that what "netstat -rna" would > > make you think. > > > > Sometimes I could clear the trouble by zapping all arp-entries. > > That's what I've done, and it seems to work. > > > I stopped using routed and made static routes, and have had no > > problems since. > > Unfortunately, that's not a solution given that the boxes can exist on > the local ethernet and come in via PPP (portables are great fun). No, but it's probably something we can use as a data-point to find out what's going on. The thing I don't like is that packets get routed counter to what "netstat -rna" & "arp -a" reports. In my case packets were sent out a wrong interface even. So we are talking about some pointer which ends up pointing to the wrong arp-entry I think. Maybe that could be a/the hint. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5392.819562490>