From owner-freebsd-hackers Mon Oct 5 04:16:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22649 for freebsd-hackers-outgoing; Mon, 5 Oct 1998 04:16:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22644 for ; Mon, 5 Oct 1998 04:16:14 -0700 (PDT) (envelope-from fluffy@vszbr.cz) Received: from localhost (fluffy@localhost) by coredump.int.tele.dk (8.8.5/8.8.5) with SMTP id NAA08303 for ; Mon, 5 Oct 1998 13:15:46 +0200 X-Authentication-Warning: coredump.int.tele.dk: fluffy owned process doing -bs Date: Mon, 5 Oct 1998 13:15:46 +0200 (CEST) From: Fluffy -- The Other White Meat X-Sender: fluffy@coredump.int.tele.dk To: freebsd-hackers@FreeBSD.ORG Subject: Re: A "feature request", maybe...? In-Reply-To: <199810050918.EAA17906@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Oct 1998, Joe Greco wrote: > I'd like, in some instances, to be able to avoid the default UNIX IP > behaviour of grabbing the "closest interface" address when connecting > to a remote host with TCP (or UDP for that matter). There are some > times when I know a better address to use, but would rather not have > to modify lots and lots of userland code to specifically do a bind() > of the socket to the particular address that I'd really like to use. YES!!@! I was just wondering how I could do this painlessly this last week, as I prepared to move one of my machines seamlessly from one IP address to another, while still retaining limited compatibility with those laggards who haven't yet updated their configuration to use the new IP address. I'd use it. Barry Bouwsma (do not attempt to ajust your mailreader to reply by e-mail, none for me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message