From owner-freebsd-hackers Mon Oct 5 02:18:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08126 for freebsd-hackers-outgoing; Mon, 5 Oct 1998 02:18:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08101 for ; Mon, 5 Oct 1998 02:18:30 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id EAA17906 for hackers@freebsd.org; Mon, 5 Oct 1998 04:18:07 -0500 (CDT) From: Joe Greco Message-Id: <199810050918.EAA17906@aurora.sol.net> Subject: A "feature request", maybe...? To: hackers@FreeBSD.ORG Date: Mon, 5 Oct 1998 04:18:07 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if anyone else thought this is an interesting idea. 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. The source isn't always available. :-( How hard would it be to add a sysctl that "changed" any normally- INADDR_ANY socket to instead to bind to some specified IP address? I can see some potential uses on things like firewalls, too... ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message