From owner-freebsd-questions Tue Sep 12 14:11: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by hub.freebsd.org (Postfix) with ESMTP id 4C93E37B422 for ; Tue, 12 Sep 2000 14:10:45 -0700 (PDT) Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by cactus.fi.uba.ar (8.9.3/8.9.3) with ESMTP id SAA99555; Tue, 12 Sep 2000 18:08:30 -0300 (ART) (envelope-from fgleiser@cactus.fi.uba.ar) Date: Tue, 12 Sep 2000 18:08:29 -0300 (ART) From: Fernando Gleiser To: JP Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Dual homed host routing problem In-Reply-To: <200009122019.WAA00706@pig.bigmama.xx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000, JP wrote: > > > What happens is that from both the gateway machine and all hosts on the > 192.168.118 network, I am able to access the ed1 interface, but > anything beyond the ed1 (other computers connected to that subnet, a > router that sits there, etc) are unreachable. But they are not totally > unreachable, the traffic seems to get to the 172... address, but does > not get routed back. I say that because the message returned is "host Maybe the hosts on the 172... network don't have a route to the 192.168.. network, or the route is wrong . So, when you ping from a machine on the 192.168 net to a host on the 172 the following happens: 1- The 192 hosts sends the packet to the freebsd box acting as a router. 2- the fbsd box forwards it to the destination host. 3- The destination host does'nt have a route back to to the 192 network, so it simply drops the response packet. It would be very useful if you post the routing tables of: a) a host on each network. and b) the dual homed bsd box. > is down" after only about 10 seconds but if i for example attempt to > ping a host that really does not exist, telnet will wait for many > minutes then the eventual message is "Unable to connect to remote > host". Additionally, I see the traffic hit the nics/router on the > other side (the lights flash). > > I also see now after trying Steve van den Akker's suggestion to use the > "cheat sheet" that natd is reporting "failed to write packet back (host > is down). > > Any ideas what I am doing wrong? > > Regards, > > Patrick > > > On Mon, Sep 11, 2000 at 11:33:49PM +0200, JP (J. Patrick Russell) wrote: > > > HELP! I'm trying to setup a dual homed host with two ethernet devices. Only > > > one device seems to be forwarding. ed1 never seems to fully forward, I have > > > switched the card out with another type (rl0), but the behavior was identical > > > -- only interface ed0 worked. ed1 is recognized and the cards do not seem to > > > conflict: > > > > > > dmesg relevant output: > > > > > > ed0: port 0x6000-0x601f irq 11 at device > > > 12.0 on pci0 > > > ed0: address 52:54:00:da:22:0c, type NE2000 (16 bit) > > > ed1: port 0x6100-0x611f irq 10 at device > > > 14.0 on pci0 > > > ed1: address 52:54:00:da:21:6d, type NE2000 (16 bit) > > > > > > and ed1 is automatically added to the routing table: > > > > > > Internet: > > > Destination Gateway Flags Netif Expire > > > default 172.16.1.2 UGSc ed1 > > > 127.0.0.1 127.0.0.1 UH lo0 > > > 172.16.1/24 link#2 UC ed1 => > > > 172.16.1.2 link#2 UHLW ed1 => > > > 172.16.1.3 52:54:0:da:21:6d UHLW lo0 > > > 192.168.118 link#1 UC ed0 => > > > 192.168.118.1 52:54:0:da:22:c UHLW lo0 > > > 192.168.118.2 0:e0:4c:66:77:3d UHLW ed0 750 > > > > > > getting to the ed1 interface from the ed0 subnet works, but nothing gets > > > forwarded beyond the nic. > > > gateway_enable="YES" is set in rc.conf, and sysctl is set so > > > net.inet.ip.forwarding=1 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message