Date: Tue, 1 Dec 1998 14:55:18 -0700 From: Nate Williams <nate@mt.sri.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Nate Williams <nate@mt.sri.com>, Luigi Rizzo <luigi@labinfo.iet.unipi.it>, hackers@FreeBSD.ORG Subject: Re: TCP bug Message-ID: <199812012155.OAA01489@mt.sri.com> In-Reply-To: <199812012153.NAA10746@apollo.backplane.com> References: <199812011811.LAA00104@mt.sri.com> <199812011619.RAA02622@labinfo.iet.unipi.it> <199812011834.LAA00343@mt.sri.com> <199812012153.NAA10746@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> :> > In trying to track down why some boxes in my network can't connect to > :> > certain WWW hosts, I determined that my FreeBSD is not routing the > :> > packets for some reason. It's receiving them, and the firewall code > :> > *thinks* it's passing them on, but tcpdump doesn't see these packets go > :> > out on the wire. .... > :Yep, no difference. It appears my router box is not passing packets > :through to the boxes on the internal ethernet. I stuck the firewall on > :that box just to see if the TCP stack was getting the incoming packets, > > I've noticed that FreeBSD doesn't always bind the local side of the > connection to the outgoing interface but instead binds the local side > of the connection to some other interface. ??? > > For example, if I have two interfaces and I telnet out, FreeBSD might > not use the outgoing interface's IP address for the local address and > instead might use the other interface's IP address. This is not the case here, because the machine who's packets are getting whacked has only one interface (the internel ethernet device). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812012155.OAA01489>