IPv6 static address over pppoe - interface only gets configured after "restarting" it

Hello there,

My ISP (KPN business in the Netherlands) provides ipv4 and ipv6 internet connectivity over pppoe. The pppoe interface gets assigned a public ipv4 address, as well as remote and local link-local ipv6-addresses. My local address changes every time.

The ISP routes a fixed /56 prefix over this connection, which I have to configure manually. I did this by creating a new interface, assigning the first address of the prefix to that interface, and setting the prefix as the ip6prefix. I did not configure a IPv6 gateway for the interface, as the local address changes every time I reconnect. Instead, I added a static default route via the pppoe interface (without specifying the address of the next hop).

The configuration works - however, the interface will not configure itself properly upon a reboot. It will not assign its ::1 address, nor the prefix - even though it is configured to be brought up on boot. When I restart the interface manually (by pressing "restart" in luci), it will configure itself and will work properly.

Any ideas what I can do to make the interface configure itself properly on reboot? Relevant configs/logs below.

Thanks much,

Rien

My relevant openwrt network configuration is as follows:

> 
> config interface 'WAN_KPN'
>         option proto 'pppoe'
>         option device 'eth3'
>         option username 'internet'
>         option password 'internet'
>         option mtu '1500'
>         option metric '1'
>         option ipv6 'auto'
> 
> config interface 'WAN_KPN_6'
>         option device 'pppoe-WAN_KPN'
>         option proto 'static'
>         option ip6prefix '2a02:22a0:XXXX:XXXX::/56'
>         list ip6addr '2a02:22a0:XXXX:XXXX::1'
>         option defaultroute '0'
>         option metric '0'
>         option force_link '0'
> 
> ...
> 
> config route6
>         option interface 'WAN_KPN'
>         option target '::/0'

The system log shows:

Sat Oct  8 11:28:49 2022 daemon.info pppd[3884]: Renamed interface ppp0 to pppoe-WAN_KPN
Sat Oct  8 11:28:49 2022 daemon.info pppd[3884]: Using interface pppoe-WAN_KPN
Sat Oct  8 11:28:49 2022 daemon.notice pppd[3884]: Connect: pppoe-WAN_KPN <--> eth3
Sat Oct  8 11:28:49 2022 daemon.notice netifd: Interface 'WAN_KPN_6' is enabled
Sat Oct  8 11:28:49 2022 daemon.notice netifd: Network device 'pppoe-WAN_KPN' link is up
Sat Oct  8 11:28:49 2022 daemon.notice netifd: Interface 'WAN_KPN_6' has link connectivity
Sat Oct  8 11:28:49 2022 daemon.notice netifd: Interface 'WAN_KPN_6' is setting up now
Sat Oct  8 11:28:49 2022 daemon.notice netifd: Interface 'WAN_KPN_6' is now up
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: read /etc/hosts - 4 addresses
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: read /tmp/hosts/dhcp.cfg01411c.3700 - 11 addresses
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: read /tmp/hosts/odhcpd - 0 addresses
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: read /tmp/hosts/dhcp.cfg01411c - 11 addresses
Sat Oct  8 11:28:50 2022 user.notice firewall: Reloading firewall due to ifup of WAN_KPN_6 (pppoe-WAN_KPN)
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: PAP authentication succeeded
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: peer from calling number 70:6D:15:EB:03:45 authorized
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: local  LL address fe80::a0a4:c5be:789c:d28b
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: remote LL address fe80::726d:15ff:feeb:0340
Sat Oct  8 11:28:50 2022 daemon.notice netifd: Interface 'WAN_KPN' is now up
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: local  IP address 92.68.XXX.XXX
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: remote IP address 212.121.121.183
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: primary   DNS address 213.144.235.1
Sat Oct  8 11:28:50 2022 daemon.notice pppd[3884]: secondary DNS address 213.144.235.2
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain test
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain onion
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain localhost
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain local
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain invalid
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain bind
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using only locally-known addresses for domain local.guto.nl
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using nameserver 213.144.235.1#53
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using nameserver 213.144.235.2#53
Sat Oct  8 11:28:50 2022 daemon.info dnsmasq[2502]: using nameserver 192.168.8.1#53
Sat Oct  8 11:28:50 2022 daemon.notice netifd: Interface 'WAN_KPN_6' is now down
Sat Oct  8 11:28:50 2022 daemon.notice netifd: Interface 'WAN_KPN_6' has link connectivity loss
Sat Oct  8 11:28:50 2022 user.notice firewall: Reloading firewall due to ifup of WAN_KPN (pppoe-WAN_KPN)
Sat Oct  8 11:28:50 2022 user.notice firewall: Reloading firewall due to ifupdate of WAN_KPN (pppoe-WAN_KPN)

Whops - solved.

option ipv6 '1' instead of 'auto'

Sorry for bothering :slight_smile:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.