[Solved] Ds-lite auto-created interface is shutting down

After restarting my router I'm not able to reconnect to IPv4 via dslite tunnel.

The router connects sucessfully to IPv6 via pppoe and dynamically creates the dslite-pppoe interface.
However, the dslite-pppoe never comes up succesfully.

From the logs I can see an infinite loop of

Thu Aug 10 15:42:25 2023 daemon.notice netifd: Interface 'DSL_6_4' is now down
Thu Aug 10 15:42:25 2023 daemon.notice netifd: Interface 'DSL_6_4' is setting up now
Thu Aug 10 15:42:34 2023 daemon.notice netifd: Interface 'DSL_6_4' is now down
Thu Aug 10 15:42:34 2023 daemon.notice netifd: Interface 'DSL_6_4' is setting up now
Thu Aug 10 15:42:43 2023 daemon.notice netifd: Interface 'DSL_6_4' is now down
Thu Aug 10 15:42:43 2023 daemon.notice netifd: Interface 'DSL_6_4' is setting up now
Thu Aug 10 15:42:53 2023 daemon.notice netifd: Interface 'DSL_6_4' is now down
Thu Aug 10 15:42:53 2023 daemon.notice netifd: Interface 'DSL_6_4' is setting up now
Thu Aug 10 15:43:02 2023 daemon.notice netifd: Interface 'DSL_6_4' is now down
Thu Aug 10 15:43:02 2023 daemon.notice netifd: Interface 'DSL_6_4' is setting up now

I already tried a tcpdump on the DSL interface to check whether the AFTR-adress is being advertised and it is.

Is there any way to debug this?

My network config:

config interface 'DSL'               
        option device 'eth0.7'    
        option ipv6 'auto'    
        option ip6ifaceid 'eui64'
        option peerdns '0'
        option proto 'pppoe' 

Edit:
I found out that the dslite script fails when trying to resolve the peer address.
remoteip6=$(resolveip -6 "$peeraddr")
At the same time a warning is issued by dnsmasq:

Thu Aug 10 16:21:22 2023 daemon.warn dnsmasq[1]: Maximum number of concurrent DNS queries reached (max: 150)

Edit2:
That was indeed the key. For some reason the peerdns '0' option made it to my config, which seems to have had no harm until eventually I rebooted my system. Setting it to the (default) '1' value resolves my problem.

1 Like