From owner-freebsd-isp Mon Aug 6 16: 2:15 2001 Delivered-To: freebsd-isp@freebsd.org Received: from inet03.citec.qld.gov.au (inet03.citec.qld.gov.au [203.5.10.10]) by hub.freebsd.org (Postfix) with ESMTP id 0F7A837B401 for ; Mon, 6 Aug 2001 16:02:10 -0700 (PDT) (envelope-from sgcccdc@citec.qld.gov.au) Received: by inet03.citec.qld.gov.au; id JAA15952; Tue, 7 Aug 2001 09:01:59 +1000 (EST) Received: from citecub.citec.qld.gov.au( 131.242.4.98) by inet03.citec.qld.gov.au via smap (V2.0) id xma013569; Tue, 7 Aug 01 09:00:34 +1000 Received: from guru.citec.qld.gov.au by citecub.citec.qld.gov.au (SMI-8.6/SMI-SVR4) id JAA07401; Tue, 7 Aug 2001 09:00:25 +1000 Received: from localhost (sgcccdc@localhost) by guru.citec.qld.gov.au (8.9.3/8.9.3) with ESMTP id JAA02813; Tue, 7 Aug 2001 09:00:24 +1000 (EST) (envelope-from sgcccdc@citec.qld.gov.au) X-Authentication-Warning: guru.citec.qld.gov.au: sgcccdc owned process doing -bs Date: Tue, 7 Aug 2001 09:00:24 +1000 (EST) From: Colin Campbell To: alexus Cc: Subject: Re: another ip as alias on NIC doesn't work properly In-Reply-To: <01a201c11e98$7ecab280$0d00a8c0@alexus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am assuming you still have your original problems. 1) Why do you not see traffic from the alias? I am guessing that your irc server is bound to all addresses. When a UNIX system receives a packet for any address on the system it will accept it on the interface the packet came in on. All return packets will go out with that IP address. For example suupose you had xl0 = 192.168.1.1 xl1 = 10.0.0.1 If machine 10.0.0.2 sent a packet to 192.168.1.1, the machine would accept it on interface xl1 and all packets would come out with source of 10.0.0.1 despite being directed to 192.168.1.1. On some systems you can actually prevent this behaviour. ie if 10.0.0.2 sent to 192.168.1.1 you'd get back a "no route to host" or something similar. 2) The routes you queried are all host routes. If you "man netstat" you would have seen that the "UHLW" means H RTF_HOST Host entry (net otherwise) L RTF_LLINFO Valid protocol to link address translation U RTF_UP Route usable W RTF_WASCLONED Route was generated as a result of cloning Freebsd installs a host route for all local hosts. At least I think that's what happens. :-) Colin -- Colin Campbell Unix Support/Postmaster/Hostmaster CITEC +61 7 3006 4710 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message