From owner-freebsd-questions Sun Jun 16 8:52: 7 2002 Delivered-To: freebsd-questions@freebsd.org Received: from out018.verizon.net (out018pub.verizon.net [206.46.170.96]) by hub.freebsd.org (Postfix) with ESMTP id 3447E37B421 for ; Sun, 16 Jun 2002 08:51:45 -0700 (PDT) Received: from out018 ([192.168.129.215]) by out018.verizon.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with SMTP id <20020616155144.JTFR25251.out018.verizon.net@out018> for ; Sun, 16 Jun 2002 10:51:44 -0500 From: To: Freebsd-questions@freebsd.org Subject: getway forwarding and interface questions Date: Sun, 16 Jun 2002 10:51:44 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20020616155144.JTFR25251.out018.verizon.net@out018> 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'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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message