From owner-freebsd-questions Fri Jun 7 12:39:41 2002 Delivered-To: freebsd-questions@freebsd.org Received: from priv-edtnes09-hme0.telusplanet.net (mtaout.telus.net [199.185.220.235]) by hub.freebsd.org (Postfix) with ESMTP id 5710137B400 for ; Fri, 7 Jun 2002 12:39:36 -0700 (PDT) Received: from box.ici.net ([161.184.25.32]) by priv-edtnes09-hme0.telusplanet.net (InterMail vM.5.01.04.01 201-253-122-122-101-20011014) with SMTP id <20020607193934.IJKG7991.priv-edtnes09-hme0.telusplanet.net@box.ici.net>; Fri, 7 Jun 2002 13:39:34 -0600 Date: Sat, 8 Jun 2002 12:10:14 -0600 From: James Earl To: Bill Moran Cc: freebsd-questions@FreeBSD.org Subject: Re: PPP dial-in to LAN Message-Id: <20020608121014.2494e6ff.kim-james@telusplanet.net> In-Reply-To: <3D00E31C.8030805@potentialtech.com> References: <20020608101527.0f67ca1d.kim-james@telusplanet.net> <3D00E31C.8030805@potentialtech.com> X-Mailer: Sylpheed version 0.7.6 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Thanks for the information, it works perfectly now! I can see where I went wrong with my thinking. I realize now that it doesn't make much sense to have the same 192.168.1.1 ip assigned to both rl0 and tun0! Thanks again for your time! On Fri, 07 Jun 2002 12:45:16 -0400 Bill Moran wrote: > James Earl wrote: > > I've set up a FreeBSD 4.5 (192.168.1.1) server which I dial-in to > > from my home FreeBSD 4.6 (192.168.1.4) machine. I've become stumped > > in that I can't communicate with the rest of the LAN which is on the > > same subnet. I have tried setting up the server as a gateway, but I > > don't think it should have to be, right? > > No, you either need a gateway or a bridge. The network traffic isn't > going to "magically" traverse the machine, FreeBSD has to be told to > forward it. > You don't describe your network in much detail, so I'll tell you a good > way to do it and you can either learn from this or duplicate it exactly. > > The gateway should have something like this (hypothetically) > NIC to internal network IP=192.168.1.1, netmask 255.255.255.0 > Modem IP=192.168.2.1, netmask 255.255.255.0 > Make sure gateway service is turned on > > Your home machine (assuming there's no home network, only a modem) > Modem IP=192.168.2.2, netmask 255.255.255.0 > Set 192.168.2.1 as your default gateway > You should now be able to reach any computer your dial-in server > can reach. > > If you've got a home network and another default gateway (such as > your ISP) it gets just a little more complicated. In that case, > your routing table should look something like this: > > default your.isps.gateways.IP > 192.168.2.1 192.168.2.2 > 192.168.1 192.168.2.1 > > You may have to add routing statements manually to accomplish this. > You may also have routes to your home network (if you have one), > just make sure none of the ip/netmasks overlap or conflict. > > > The other thing I should mention, is that originally I set up the > > Dial-in Service on a WinNT machine and had the exact same problem, > > except now I could get from the WinNT machine to the FreeBSD machine > > (and the rest of the LAN)! > > I don't understand what you're describing here. But if you had the > same problem, it's like that you've made a similar configuration > mistake on both the NT and the BSD machine. > > > This kinda makes me think it may be my settings on my home machine, > > but I have no idea what to do different. It would seem to me that > > if I'm on the same subnet, and I can ping 192.168.1.1, I should be > > able to ping 192.168.1.2? > > Not automatically. Use "netstat -rn" to see how your routes are set > up, if you don't have a route to those other machines, you'll not get > to them. > > -- > Bill Moran > Potential Technology > http://www.potentialtech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message