Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Nov 1996 12:45:10 -0500
From:      "Steve Sims" <SimsS@IBM.Net>
To:        "Christoph Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
Cc:        <questions@FreeBSD.org>
Subject:   Re: iijppp - cannot ping host after connect
Message-ID:  <199611202032.UAA49598@smtp-gw01.ny.us.ibm.net>

next in thread | raw e-mail | index | archive | help
Thanks, Chris, for your input and feedback.  I'll try to play with it a
little and see if I can get the dial-on-demand ironed out.  This has been one
of the lowest priorities in the world for me, since the only things I do with
that (9.6 - ugh) serial line on that platform is ntpdate once in a while and
cvsup maybe a couple of times a month.

The box in question on my end is a be-all, catch-all system for a dozen or so
folks in my immediate workgroup; Samba, DNS, Web development, Telnet access,
tcpdump, code development and sandbox.  (Basically, it's a
data-center-in-a-box(tm).)  I can't bounce it as much as I'd like to get the
dial-on-demand ironed out, but I'll do so as time permits.  

Who knows, I may even resort to running `gated` or something just to sort out
the routing problems. 

The handbook section and FAQ are very dicey regarding iij-ppp; the source
remains my most valuable reference.  While the published documents are nice
from a casual users' perspective, (and, in fact, do a nice job of getting
newbies up and connected) they seem to come up somewhere short of
'definitive' for more sophisticated roles such as the application I have:
running dynamic dial-out in a static-routed, high-availability,
multi-interface role.  (Then I complicate it by using RFC-1597 addresses on
the local net side.)

Anyway - nice to hear the ideas of someone with about the same level of
expertise as I have on iij-ppp.

...sjs...
----------
From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>
To: SimsS@Infi.Net
Subject: Re: iijppp - cannot ping host after connect
Date: Wednesday, November 20, 1996 10:17 AM

> Christoph Kukulies has written....
> 
> > > When I try and ping 205.205.70.175 (my host) nothing happens.  It seems
> > > this is pretty straight forward, at least it was the last time I had
FBSD
> > > 2.01 installed on my system
> > 
> > > Also I don't have a lan connection so the only ifconfig entry I have is
> for
> > > the loopback.
> > > And, I don't run routed or gated.
> > > 
> > Do you have an (in /etc/ppp/ppp.conf):
> > 
> > your-link:
> > set openmode active
> > 
> > 
> > And in /etc/ppp/ppp.linkup:
> > 
> > your-link:
> > delete ALL
> > add 0 0 HISADDR
> 
> ... and this leads me to wonder....
> What is the significance of the 'delete ALL' line referred to? 

I took that from another config - maybe it's superfluous. I believe it's
needed
when running pppd.

> 
> I've got a dozen or so STATIC routes pointing between a pair of local
> ethernets (They're static because they're in different networks and don't
> EVEN ask about the routing protocols on the local side ;-).  I have NO
> default route when ppp is down.  Gateway-ing is on in the kernel so I can
> route between locally-connected nets.
> 
> As a result, I've not used the 'delete ALL' directive in ppp.linkup, but I
do
> use the add 0 0 HISADDR.  This works quite well as long as I start ppp from
> the command line.  But dial-on-demand doesn't work as seamlessly as it
> should.  If I add the 'delete ALL' line, would this nuke the local static
> routes I've so carefully crafted?  I suspect it would.

I haven't used ppp dial on demand yet.

> 
> In short, what I'm asking is:  How can one get iij-ppp to 
>  - dial on demand
>  - link up serially between "unknown-in-advance" IP's

This seems to work for me when I dial manually from ppp>


>  - Add an appropriate gateway to the ISP

This is done by negotiation over ppp protocol.


>  - Preserve existing routing table information on the local side
> (It's the last bullet that has me stumped.)

I believe ppp only affects the tun(x) interface. Not other routes.

> 
> ...sjs...
> 

I'm still in the course of learning.


--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611202032.UAA49598>