*BSD News Article 99345


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.cc.swin.edu.au!news.rmit.EDU.AU!news.unimelb.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news.mira.net.au!pumpkin.pangea.ca!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!howland.erols.net!ix.netcom.com!netcom.com.nojunkemailplease.com!not-for-email
From: nobody@not.for.email (Timothy J. Lee)
Subject: User ppp (iijppp) and routing (more)
Message-ID: <timleeED39pF.6r8@netcom.com>
Sender: timlee@netcom13.netcom.com
Reply-To: see-signature-for-email-address---ads-not-welcome
Date: Thu, 10 Jul 1997 05:53:39 GMT
Lines: 48
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:44196

Dialing in with ppp, I get:

% netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire
10.0.0.2           10.0.0.2           UH          0       13       lo0
127.0.0.1          127.0.0.1          UH          0        4       lo0
xxx.xxx.xxx.57     xxx.xxx.xxx.82     UH          0        8      tun0 
% ping xxx.xxx.xxx.82
PING xxx.xxx.xxx.82 (xxx.xxx.xxx.82): 56 data bytes
ping: sendto: No route to host
ping: wrote xxx.xxx.xxx.82 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote xxx.xxx.xxx.82 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote xxx.xxx.xxx.82 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote xxx.xxx.xxx.82 64 chars, ret=-1
^C
--- xxx.xxx.xxx.82 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

xxx.xxx.xxx.57 is the SunOS 4.1.3 machine with pppd on the other end.
xxx.xxx.xxx.82 is the IP address assigned to the FreeBSD 2.2.1 machine
running ppp (iijppp).

In the $HOME/.ppp.conf file, I have the following:

set ifaddr 10.0.0.2/0 xxx.xxx.xxx.57/0 255.255.255.0

The modem connection appears to be successful, but the routing seems
to not work.  Adding a default route of xxx.xxx.xxx.57 (either by doing
"route add default xxx.xxx.xxx.57" from a shell or by doing "add 0 0
HISADDR" from the ppp prompt) simply causes routing to be even more
messed up (since it is trying to use xxx.xxx.xxx.57 as the default
router, but it cannot even get to xxx.xxx.xxx.82).

Adding a route to xxx.xxx.xxx.82 through 10.0.0.2 (e.g. by doing a
"route add xxx.xxx.xxx.82 10.0.0.2" from a shell) works to get ping
to work on xxx.xxx.xxx.82, but not xxx.xxx.xxx.57.

-- 
------------------------------------------------------------------------
Timothy J. Lee                                                   timlee@
Unsolicited bulk or commercial email is not welcome.             netcom.com
No warranty of any kind is provided with this message.