From owner-freebsd-questions Mon Feb 25 10:12:26 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 336B737B417 for ; Mon, 25 Feb 2002 10:12:23 -0800 (PST) Received: (qmail 42537 invoked from network); 25 Feb 2002 18:19:40 -0000 Received: from unknown (HELO proxy.pt.com) (151.201.71.209) by mail.the-i-pa.com with SMTP; 25 Feb 2002 18:19:40 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Bill Moran Organization: Potential Technology To: jshenry@comp.uark.edu, "Seth Henry" , freebsd-questions@freebsd.org Subject: Re: problems setting up gateway/bridge Date: Mon, 25 Feb 2002 13:11:09 -0500 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <02022513110903.00731@proxy.pt.com> Content-Transfer-Encoding: 8bit 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 On Monday 25 February 2002 11:48, Seth Henry wrote: > Hello everyone, > I am having problems bridging the gap between my PPP connected laptop and > my LAN. I have an older Compaq 486 laptop running FreeBSD 4.3-REL attached > to my FreeBSD server, running FreeBSD 4.4-REL, via a serial cable using > slattach. This connection works well, and I have used it to window xterms > to the laptop. > > Presently, the serial links are: > 192.168.0.10 (server / serial) > 192.168.0.11 (laptop) > > The LAN is configured as > 192.168.1.1 (server / LAN - hard coded) > 192.168.1.254 (router/DHCP server) > 192.168.1.(2-4) (local LAN connected workstations - DHCP) > > I can ping 192.168.0.10 and 192.168.1.1 from the laptop, but not beyond. > Pinging the router results in "no route to host". Can you ping (for example) 192.168.1.2 from the laptop? > The local configuration on the laptop indicates that 192.168.0.10 (the > server) should be the default gateway. What does "netstat -r" on the server give you? You may also need to add route statements to your "router/DHCP server" > I have tried using sysctl to modify the bridging configuration, but sysctrl > returns an error when I use the command as listed in the MAN pages. (the > parameter doesn't seem to exist when I use sysctl -a) I did change > 'net.inet.ip.forwarding' to 1. I don't think you want to bridge in this instance anyway. -- Bill Moran Potential Technology technical services http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message