From owner-freebsd-hackers Mon Feb 24 01:56:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11469 for hackers-outgoing; Mon, 24 Feb 1997 01:56:59 -0800 (PST) Received: from dawn.ww.net (root@ww.net [193.124.73.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11464 for ; Mon, 24 Feb 1997 01:56:43 -0800 (PST) Received: (from alexis@localhost) by dawn.ww.net (8.7.5/alexis 2.5) id MAA12893 for freebsd-hackers@freebsd.org; Mon, 24 Feb 1997 12:56:28 +0300 (MSK) Message-Id: <199702240956.MAA12893@dawn.ww.net> Subject: "black" interfaces list To: freebsd-hackers@freebsd.org Date: Mon, 24 Feb 1997 12:56:27 +0300 (MSK) From: Alexis Yushin Reply-To: alexis@ww.net (Alexis Yushin) X-Office-Phone: +380 65 2 26.1410 X-Home-Phone: +380 65 2 27.0747 X-NIC-Handle: AY23 X-RIPE-Handle: AY6-RIPE X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Imagine we have FreeBSD based ip router. There is a number of interfaces with different addresses, from different networks with different routing policy. (The boldest example is p2p interface with reserved addresses assigned for its ends) Now, the default behaviour is to originate packets with ip_src equal to the address of the interface the packets leave the system via. In case of reserved address such packets wont get anywhere, whilst packets originated from other systems (being routed) will find their destination just fine. The idea is very simple and I could be out of date on this issue, so please let me know if I am. So, we would have "black" list of interfaces for which packets should have another source ip address. Probably it could be built into the ifconfig mechanism. Comments? alexis -- I may be drunk but at least I'm not insane.