On 2020-01-05, Tom Murphy <open...@pertho.net> wrote: > On 2020-01-03, jrmu <j...@ircnow.org> wrote: >> inet 0.0.0.0 255.255.255.255 NONE \ >> pppoedev cpsw0 authproto pap \ >> authname '12345...@isp.net' authkey 'abcd1234' up >> dest 0.0.0.1 >> #inet6 eui64 >> !/sbin/route add default -ifp pppoe0 0.0.0.1 >> #!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 > > I had major problems with using 'dest' in hostname.pppoe0. > I ended up having to do something like: > > inet 0.0.0.0 255.255.255.255 0.0.0.1 \ > pppoedev re0 authproto chap > authname '<USERNAME>' authkey '<PASSWORD>' > > etc.. > > For whatever reason, using 'inet 0.0.0.0 255.255.255.255 NONE \ > dest 0.0.0.1' would use this ifconfig command: > > ifconfig pppoe0 inet 0.0.0.0 netmask 255.255.255.255 pppoedev re0 authproto > chap
Yes, netstart processes hostname.if line-by-line and doesn't get to the "dest" bit until it's already configured the address on the interface (thus bringing it up automatically). It usually needs to be set earlier. Not sure if it's a race with the ISP bringing up IPCP or something else but "dest" either doesn't work reliably, or doesn't work at all. > Where as if you replaced the NONE with 0.0.0.1 and removed the 'dest 0.0.0.1' > line, it would > run: > > ifconfig pppoe0 inet 0.0.0.0 netmask 255.255.255.255 broadcast 0.0.0.1 > pppoedev re0 authproto chap > > And that seemed to make my connection work. I'm not sure why, but it had to > do something with my side > not accepting the peer's IP. This is what I have for v4+v6 with larger MTUs (which depends on ISP and your equipment) - omit the mtu lines if not wanted ... hostname.pppoe0: mtu 1500 inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap authname "someuser@zen" authkey "somepass" up inet6 eui64 inet6 autoconf -autoconfprivacy !/sbin/route add default -ifp pppoe0 0.0.0.1 !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 -priority 8 hostname.em1: mtu 1508 up
