Hi, On Jun 06 17:46:35, j...@kerhand.co.uk wrote: > On Sat, Jun 06, 2020 at 05:56:56PM +0200, Jan Stary wrote: > > This is current/amd64 on an APU2. > > The egress is XDSL pppoe(4) over vlan(4) over em(4), > > as is the case with many European dialup telecoms. > > > > The connection itself works just fine (after some mss woes), > > but it takes some time to get assigned and IP address at startup. > > > > $ cat /etc/hostname.pppoe0 > > inet 0.0.0.0 255.255.255.255 NONE pppoedev vlan0 \ > > authproto 'pap' authname 'X' authkey 'PASS' up > > dest 0.0.0.1 > > inet6 eui64 > > !/sbin/route add default 0.0.0.1 > > !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 > > > > As per pppoe(4), the 0.0.0.0 and 0.0.0.1 get changed > > to my actual address (fixed) and the other end, respectively; > > routes get established, etc. > > > > My problem is that the delay is long enough > > to make some of the the early daemons choke: > > > > starting network > > add net default: gateway 0.0.0.1 > > add net default: gateway fe80::%pppoe0 > > starting early daemons: syslogd pflogd nsd(failed) unbound ntpd. > > > > nsd seems to get fixed using "ip-transparent: yes"; > > ntpd eventualy synchronizes after some "DNS lookup tempfail"s; > > but unbound spams /var/log/daemon with thousands of lines of > > > > unbound: [2895:0] notice: sendto failed: Permission denied > > unbound: [2895:0] notice: remote address is 178.17.0.12 port 53 > > > > as it tries in vain to contact its forwarders > > (or the root servers, if I don't specify forwarders). > > > > Eventually, it all falls into place, but is there a way > > to make the boot sequence wait for the pppoe IP address > > get assigned before moving on? I appended a lame > > > > !while ! ifconfig pppoe0 | grep -F 185.63.96.79; do date ; sleep 1; done > > > > to /etc/hostname.pppoe0, resulting in > > > > starting network > > add net default: gateway 0.0.0.1 > > add net default: gateway fe80::%pppoe0 > > Sat Jun 6 17:41:19 CEST 2020 > > Sat Jun 6 17:41:21 CEST 2020 > > [...] > > Sat Jun 6 17:42:53 CEST 2020 > > Sat Jun 6 17:42:54 CEST 2020 > > inet 185.63.96.79 --> 10.11.5.146 netmask 0xffffffff > > starting early daemons: syslogd pflogd nsd unbound ntpd. > > > > (The date is there purely for debug of course; > > it shows it took about a minute and a half this time.) > > > > Are people having the same problem? > > Are you doing something about the late ifconfig? > > > > Jan > > > > hi. > > although i haven't used pppoe for a little while, i definitely had the > same issue when i did (uk provider). i think i bugged another developer > to look at it (mpi?) but we never got far in working out a solution. > > sthen provided a workaround though: sth like "ifconfig pppoe0 down" in > /etc/rc.shutdown. i guess it's worth a shot...
thank you for the tip. I just tried that, but it didn't make a difference. Is the aim to let the ISP know that the iface is down, so that it gets set up afresh on boot, as opposed to waiting for some PPP keep-alive timeout? Jan
