From owner-freebsd-arch Fri May 11 16:54:44 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.tgd.net (rand.tgd.net [64.81.67.117]) by hub.freebsd.org (Postfix) with SMTP id B879637B43F for ; Fri, 11 May 2001 16:54:38 -0700 (PDT) (envelope-from sean@mailhost.tgd.net) Received: (qmail 67706 invoked by uid 1001); 11 May 2001 23:54:32 -0000 Date: Fri, 11 May 2001 16:54:32 -0700 From: Sean Chittenden To: Terry Lambert Cc: freebsd-net@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: FreeBSD breaks sockets two ways... Message-ID: <20010511165432.A67648@rand.tgd.net> References: <200105112343.QAA04578@usr08.primenet.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <200105112343.QAA04578@usr08.primenet.com>; from "tlambert@primenet.com" on Fri, May 11, 2001 at = 11:43:00PM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ X-All-your-base: are belong to us. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). >=20 >=20 > Primus > ------ >=20 > 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: --=20 Sean Chittenden --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden iEYEARECAAYFAjr8e7cACgkQn09c7x7d+q2tuQCaA6PwZyW5IG33AgevgaN+n5so pZkAnRjax8S0kGKdusPUWJ1/dv9si1FN =tJcl -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message