Date: Fri, 11 May 2001 16:54:32 -0700 From: Sean Chittenden <sean-freebsd-stable@chittenden.org> To: Terry Lambert <tlambert@primenet.com> Cc: freebsd-net@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: FreeBSD breaks sockets two ways... Message-ID: <20010511165432.A67648@rand.tgd.net> In-Reply-To: <200105112343.QAA04578@usr08.primenet.com>; from "tlambert@primenet.com" on Fri, May 11, 2001 at = 11:43:00PM References: <200105112343.QAA04578@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Are you sure it's failing to allocate the port? I had a similar problem in trying to connect to a service, but found out that aliasing an IP didn't add the arp entry in the routing table (local connections were failing). If I added the arp entry by hand, everything was happy (is IP aliasing a part of the scneario you're describing?). arp -s a.b.c.d 00:60:08:aa:aa:aa pub arp -s a.b.c.e 00:60:08:aa:aa:ab pub A tad annoying, but it seems to work (yeah, I know about the ethers file, but I refuse to use it). -sc On Fri, May 11, 2001 at 11:43:00PM +0000, Terry Lambert wrote: > I have run into two issues, that I find really, really annoying. This > is in FreeBSD 4.3 and 5.x. Bot machines are on a local (non-switched) > segment (it works the same with a switch, but taking that out proves > it is not the switch causing the problem). > > > Primus > ------ > > The first is that when you create a socket, and bind it to a > specific local IP address, and then connect, it fails to > allocate an automatic port private to the socket; specifically: -- Sean Chittenden [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden <sean@chittenden.org> iEYEARECAAYFAjr8e7cACgkQn09c7x7d+q2tuQCaA6PwZyW5IG33AgevgaN+n5so pZkAnRjax8S0kGKdusPUWJ1/dv9si1FN =tJcl -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010511165432.A67648>