>>>>> "chris" == chris gray <ep71@bcs.org.uk> writes:

> kiffer# ppp
> kiffer# May 17 20:10:59 kiffer pppd[201]: pppd 2.3.0 started by root, uid 0
> May 17 20:11:26 kiffer pppd[201]: Connect: ppp0 <--> /dev/mdm02
> May 17 20:11:27 kiffer pppd[201]: local  IP address 193.74.13.34
> May 17 20:11:27 kiffer pppd[201]: remote IP address 193.74.13.33
> May 17 20:11:27 kiffer routed[73]: Send sendto(ppp0, 193.74.13.33.520): 
>   Network is down
> May 17 20:11:27 kiffer routed[73]: Send sendto(ppp0, 193.74.13.33.520): 
>   Network is down

Aah, I remember, 'routed' was the bad guy in my scenario! It always
tries something with the new appearing PPP route, in the worst case it
turns the interface (ppp0) off!! Here is an example for that:

May 17 23:09:14 pcwork1 routed[146]: Send sendto(ppp0,
  192.11.100.124.520): Network is down
May 17 23:09:14 pcwork1 pppd[29439]: local  IP address 192.11.100.143
May 17 23:09:14 pcwork1 pppd[29439]: remote IP address 192.11.100.124
May 17 23:09:14 pcwork1 routed[146]: write(rt_sock) RTM_ADD
  192.11.100.124/32-->192.11.100.143  metric=0 flags=0:
May 17 23:09:14 pcwork1 routed[146]: ignore RTM_ADD without gateway
May 17 23:10:24 pcwork1 routed[146]: interface ppp0 to 192.11.100.124
  turned off
May 17 23:10:27 pcwork1 pppd[29439]: Connection terminated.

The most certain way to let the ppp connection untouched is turning
the 'routed' off: It's normaly useless on the connecting client (you
use the 'defaultroute' option?) On the other side I've usually enabled
the 'proxyarp' option to make the ppp client be a regular part of our
network.

When you look at 'man routed' '-h' should prohibit advertizing these
ppp connections, so that should be a way to get a working 'routed'
_and_ 'pppd'.

    chris> Hope this tells you something ...

Hope this helps you...

Markus.