* Jürgen Mell wrote on Tue, Jun 05, 2001 at 11:54 +0200:
Unfortunately something must have changed from SuSE 6.3 to 7.1: If there is no 'defaultroute' statement in /etc/ppp/options.ippp0, a previuosly set default route (from /etc/route.conf) will be deleted
SuSE's ip-down script does this by ifconfig $INTERFACE down ; ifconfig $INTERFACE up which clears all routes through $INTERFACE. SuSE's ip-up just sets a default route to the device ($INTERFACE) what's going up - and doesn't cares if you specified a default route in /etc/route.conf or not. ip-up/down dont even read route.conf.
- at least sometimes (I could not reproduce the conditions when and why the route was deleted.) This resulted in the first connection to our ISP to work correctly
Yep, this sounds like such a ip-up/down problem: first works, but second not. That's why I patched that thing and integrated full route.conf support to it. If you have more that a single ipppX device and/or a route different from exactly a defaultroute through that single device, you cannot use SuSE's ip-up (at least up to SuSE 7.0, haven't checked 7.1). It will simply not work.
but afterwords (we have a dial-up line to the ISP) I got lots of Martian packets due to the missing route. I fixed this with a '-defaultroute' statement in /etc/ppp/options.ippp0 and now everything is fine,
Yep, if you use SuSE's ip-up script, it sets a deaultroute hardcoded without any checking. If you configured ipppd to set up a route too - maybe a changed default value - you might get such results. By that, IIRC, SuSEs ip-up script dont reports such errors (correct: it reports it via STDOUT/STDERR which are closed since the script has no controlling terminal).
as the route set from /etc/route.conf stays active.
Not from route.conf. You can make a simple test: remove (comment out) the default route from route.conf (when offline) and give a "isdnctrl dial ippp0". I expect you will have a defaultroute through ippp0. After all, I would suggest to let ipppd set the defaultroute, and not ip-up since ipppd is a lot more clever at this. But you cannot use SuSEs version of ip-up for this - since it doesn't read route.conf at all IIRC. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.