Date: Sun, 16 Jun 2002 14:30:36 -0400 From: "Scott M. Nolde" <scott@smnolde.com> To: glbj@verizon.net Cc: Freebsd-questions@freebsd.org Subject: Re: getway forwarding and interface questions Message-ID: <20020616143036.C42599@smnolde.com> In-Reply-To: <20020616155144.JTFR25251.out018.verizon.net@out018>; from glbj@verizon.net on Sun, Jun 16, 2002 at 10:51:44AM -0500 References: <20020616155144.JTFR25251.out018.verizon.net@out018>
next in thread | previous in thread | raw e-mail | index | archive | help
glbj@verizon.net(glbj@verizon.net)@2002.06.16 10:51:44 +0000: > I've managed to get the FreeBSD box to talk to MSN over this God-awful arescom modem/gateway/router they supply. However, I can't get the F-BSD box to fdorward packets from the windoze machine. I can ping from windows to F-bsd and from F-bsd to windoze. The setup that worked so successfully with Verizon in NJ was: > > one ethernet interface "rl0" > all machines on 192.168.123.xx > running PPoE > gateway enabled > > This obviously doesn't work here. The new setup first tried was: > > One ethernet card "rl0" with 192.168.1.2 netmask 255.255.255.252 bound to it > > 192.168.123.xx aliased on rl0 > gateway enabled > NO PPPoE since the arescom does that part > > result: packets are not forwarded but F-BSD has access to the Net. > > I decided to try using two Ethernet interfaces. When the second one was installed F-BSD found rl0 as usual, but then came up with rlphy0 for the second card. I've never seen or heard of rlphy0 before. Could that be a conflict with the first card? > > Help !!!!!! > > Oh... > And thanks for past assistance. Look into using ipfw+natd or ipf+ipnat to do the routing. http://www.mostgraveconcern.com/freebsd/ipfw.html is a good start. Google for ipnat help. -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020616143036.C42599>