From owner-freebsd-questions Tue Oct 8 8:23:38 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56DD637B401 for ; Tue, 8 Oct 2002 08:23:37 -0700 (PDT) Received: from goof.com (pcp02305702pcs.longhl01.md.comcast.net [68.52.164.8]) by mx1.FreeBSD.org (Postfix) with SMTP id B09BF43E6A for ; Tue, 8 Oct 2002 08:23:36 -0700 (PDT) (envelope-from jlido@goof.com) Received: (qmail 42713 invoked by uid 15016); 8 Oct 2002 15:23:35 -0000 Date: Tue, 8 Oct 2002 11:23:35 -0400 From: Jon-Erik Lido To: freebsd-questions@freebsd.org Subject: Routing Problem- interface to alias Message-ID: <20021008112335.A41704@goof.com> Mail-Followup-To: Jon-Erik Lido , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to something a little bizarre with routing, so I suppose it bears some explanation. I recently purchased one of those all-in-one firewall/NAT/ethernet switch/801.11b access point boxes for my home use. 802.11b security being what it is (useless), I'm planning on setting up IPSec for my WLAN for authentication and encryption. However, I haven't gotten that far yet. I've set up two subnets behind my firewall. One is 10.10.10.0/24 and is for the wired LAN. The other is 10.0.0.0/24 and is for the wireless LAN. I've got a FreeBSD box with a single NIC ethernetted to one of the ports on the firewall's switch. I'm planning to use it as my 10.0.0.0/24 to 10.10.10.0/24 gateway. Two subnets on one segment. So I have: ifconfig ed0 inet 10.10.10.1 netmask 0xffffff00 ifconfig ed0 inet 10.10.10.10 netmask 0xffffffff alias ifconfig ed0 inet 10.0.0.1 netmask 0xffffff00 alias The 10.10.10.10 is simply an alias I'm using since I'm running dnscache on 10.10.10.1 and tinydns on 10.10.10.10. I have IP forwarding compiled into the kernel and enabled. With my wireless laptop set to 10.0.0.50 using the 10.0.0.1 gateway as its default route I am able to ping 10.0.0.1, 10.10.10.1, but no other hosts on or off the LAN. traceroute from the laptop reveals a hop to 10.0.0.1 and then the packets are simply lost. 10.10.10.1's routing table looks like this (with 10.0.0.50 not connected): Destination Gateway Flags Refs Use Netif Expire default 10.10.10.254 UGSc 12 30 ed0 10/24 link#1 UC 0 0 ed0 10.10.10/24 link#1 UC 3 0 ed0 10.10.10.1 00:4f:49:0a:1e:85 UHLW 1 753 lo0 10.10.10.10 00:4f:49:0a:1e:85 UHLW 1 52 lo0 => 10.10.10.10/32 link#1 UC 1 0 ed0 10.10.10.254 00:30:f1:18:84:3c UHLW 13 25 ed0 1175 127.0.0.1 127.0.0.1 UH 0 0 lo0 Notice that the 10/24 subnet is listed, but not the 10.0.0.1 IP number. I'm sure what I'm trying to do is possible; the FreeBSD handbook section on routing even alludes to it. I just can't seem to get it to work. Any ideas? -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message