From owner-freebsd-questions Fri Jul 26 00:19:18 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04331 for questions-outgoing; Fri, 26 Jul 1996 00:19:18 -0700 (PDT) Received: from pino.ngonet.be (pino.ngonet.be [193.190.166.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA04323 for ; Fri, 26 Jul 1996 00:19:14 -0700 (PDT) Received: from koekiemonster.ngonet.be (tommie.ngonet.be [193.190.166.2]) by pino.ngonet.be (8.7.5/8.6.9) with SMTP id IAA19789; Fri, 26 Jul 1996 08:14:14 +0200 Message-ID: <31F87099.6C62@ngonet.be> Date: Fri, 26 Jul 1996 09:15:37 +0200 From: Gunter Loos Reply-To: Gunter.Loos@ngonet.be Organization: NgoNet Brussels Belgium X-Mailer: Mozilla 3.0b4Gold (Win95; I) MIME-Version: 1.0 To: Charlie ROOT CC: Wes Side Story , Gunter.Loos@ngonet.be, questions@freebsd.org Subject: Re: user PPP server problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charlie ROOT wrote: > > > On bootup you should also see something about ipforwarding=yes. No, you shouldn't. It depends on wether you _want_ to forward IP packets between interfaces. I for one do not, I want to tunnel all my ppp traffic through the proxies... > > My /etc/ppp/options file (and the /etc/ppp/ppp.conf, for user ppp as > a server) both have the line proxyarp in them. Mine does too. options, I mean. > > Then in /etc/rc.local I've got: > > # put your local stuff here > /usr/sbin/arp -s 36.33.0.75 00:20:af:be:eb:e0 pub Huh? Why set it static? proxyarp does work, you know. > > and I have routed -q running. This is on the machine running as the If you want to route. > server (my office machine). The IP address in the above is not the > IP address of the office machine, but the IP address that I use for > my home machine, i.e., the client, but the ethernet card number is > the number of the card in the server. I think if you do this the > IP address on the client machine and the IP address of the server > have to be on the same network segment (if that is the proper term), > i.e., in this case both the home and office machines are on 36.33. > If you had another client machine with an IP address you could have > a second arp -s statement. (My understanding is that the arp -s > statement causes the ethernet card to grab incoming packets addressed > to, in this case, 36.33.0.75, and route them in accordance with the > routing tables, but that may be incorrect.) > > The alternative and perhaps more standard approach is to assign > another IP address to the ppp interface on the server machine. I do think it's more of a standard way of working, afaik. Gul. -- . .__ . |Nationaal Centrum voor OntwikkelingsSamenwerking vzw, NgoNet _| _ [ __ | |Voice Gunter.Loos@+32 2 5392620 Fax +32 2 5391343 (_](/, [_./(_|| |mailto:gul@ngonet.be "You are all weirdos." - Sam the Eagle ----MijnEigenWoordenNietVanIemandAnders - MyOwnExpressionsNotSomeoneElses----