At 10:32 Uhr +0200 3.10.2003, Martin Husemann wrote:
>But, different to pppoe* interfaces (IIRC), ippp* interface default to "dial
>on demand" mode, i.e. have LINK1 set. Removing that should make them reconnect
>as aggressive as pppoe* interfaces do.
>
>At the time this defaults were established it seemed sensible, since (at least
>here) there were only flatrate DSL connections and mostly time charged ISDN
>connections. The situation has changed (again: here), but to change an
>established default requires some presure; and this is easily user
>configurable.

While we're on the issue of pppoe and ifwatchd... I noted that with a
-current kernel on 1.6.1 userland, ifwatchd gets an "extra round" of
up/down events during the daily disconnect [German Telekom]:

<snip="/var/log/messages">
Oct  1 14:49:53 pizza pppoe0[14420]: The pppoe0 link is going down (ip was
here 80.137.26.211 <> there 217.5.98.163
Oct  1 14:49:58 pizza pppoe0[9238]: The pppoe0 link is up, new ip here
0.0.0.0 <> there 0.0.0.1
Oct  1 14:50:00 pizza pppoe0[27997]: The pppoe0 link is going down (ip was
here 0.0.0.0 <> there 0.0.0.1
Oct  1 14:50:04 pizza pppoe0[12584]: The pppoe0 link is up, new ip here
80.137.23.219 <> there 217.5.98.163
</snip>

This is somewhat annoying because the ip-{up,down} scripts communicate the
ip address change to a nameserver, which then gets irritated by '0.0.0.?'
ip addresses.

Is this a mismatch between the 1.6.1 ifwatchd and -current kernel
interfaces, or a -current kernel issue?

	hauke

--
/~\  The ASCII Ribbon Campaign
\ /    No HTML/RTF in email
 X     No Word docs in email
/ \  Respect for open standards