In your case you probably want to change the ifname to eth2.40 and remove the config interface ‘VLAN’ section and also the config interface ‘DSLite’ section. Restart the network (I usually reboot the node).
I don‘t understand how the removal of the DS-Lite config should fix the DS-Lite issue. The PPPoE connection via eth2.40 is working well together with IPv6.
I have removed VLAN and DSLite but nothing changed. I still have only the PPPoE on eth2.40 with IPv6 Address. No IPv4. I think without configuring Ds-Lite with the AFTR-Server the IPv4 will not work?
What is the output running from cli check_connection?
For comparison on my node it reads:
IPv4 Gateway: UNKNOWN
Pinging 217.31.205.50 … OK
Pinging 198.41.0.4 … OK
Pinging 199.7.83.42 … OK
Pinging 8.8.8.8 … OK
IPv4: OK
Pinging fe80::e2ac:f1ff:fe65:51ba%pppoe-wan … OK
IPv6 Gateway: OK
Pinging 2001:1488:0:3::2 … OK
Pinging 2001:500:3::42 … OK
Pinging 2001:500:2d::d … OK
Pinging 2606:2800:220:6d:26bf:1447:1097:aa7 … OK
IPv6: OK
Resolving api.turris.cz … OK
Resolving www.nic.cz … OK
Resolving c.root-servers.net … OK
DNS: OK
Resolving www.rhybar.cz … OK
DNSSEC: OK
right, so no ipv4 at all indeed, strange - it should work either way - with the automatic setting or the additional iface entry. Assuming the network is restarted (or the node rebooted) after changes committed to the network settings.
What is the output from cli of ip -d -h -s a s dev pppoe-wan?
And could check the log about netifdentries of this sort - potential errors?
netifd: Network device ‘pppoe-wan’ link is up
netifd: Interface ‘wan’ is now up
netifd: Network alias ‘pppoe-wan’ link is up
netifd: Interface ‘wan_6’ is enabled
netifd: Interface ‘wan_6’ has link connectivity
netifd: Interface ‘wan_6’ is setting up now
Nov 15 14:35:04 turris pppd[6742]: Plugin rp-pppoe.so loaded.
Nov 15 14:35:04 turris pppd[6742]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Nov 15 14:35:04 turris pppd[6742]: pppd 2.4.7 started by root, uid 0
Nov 15 14:35:05 turris kresd[3162]: [priming] cannot resolve ‘.’ NS, next priming query in 10 seconds
Nov 15 14:35:05 turris kernel: [ 62.884839] mvneta f1034000.ethernet eth2: Link is Down
Nov 15 14:35:06 turris netifd: Network device ‘eth2’ link is down
Nov 15 14:35:06 turris netifd: VLAN ‘eth2.40’ link is down
Nov 15 14:35:06 turris netifd: Interface ‘wan’ has link connectivity loss
Nov 15 14:35:08 turris netifd: Network device ‘eth2’ link is up
Nov 15 14:35:08 turris kernel: [ 64.951736] mvneta f1034000.ethernet eth2: Link is Up - 100Mbps/Full - flow control off
Nov 15 14:35:08 turris netifd: VLAN ‘eth2.40’ link is up
Nov 15 14:35:08 turris netifd: Interface ‘wan’ has link connectivity
Nov 15 14:35:08 turris netifd: Interface ‘wan’ is setting up now
ISP is providing dynamic IPv6 and IPv4 via DS-Lite.
What I don‘t understand -> How can it possible that your IPv4/DS-Lite is working without specifiyng the AFTR Server from the ISP which is used for tunneling IPv4?
Suppose that requires the ISP having it implemented (and correctly) in the first place. However, reading
To inform the B4 of the Address Family Transition Router’s (AFTR) location, a DNS [RFC1035] hostname may be used. Once this information is conveyed, the presence of the configuration indicating the AFTR’s location also informs a host to initiate Dual-Stack Lite (DS-Lite) service and become a softwire initiator.
wondering whether this being a DNS issue at your node somehow.
From the topic
Issues after upgrade to 4.0.1
I would infer that ds-lite worked as expected in the TOS3.x branch with the config stated in the initial post?
I had tried a similar config earlier but that caused some grievance in TOS3.x
Yes, under TOS 3.X my first config was working. Can I check somehow if my ISP is providing the AFTR_NAME via DHCPv6? If not, I guess there must be a way to configure it manually like I did it on TOS 3.X?
Note: To automatically configure ds-lite from dhcpv6 you need to create an interface with option auto 0 and put its name as the ‘iface_dslite’ parameter. In addition you also need to add its name to a suitable firewall zone in /etc/config/firewall
Do you have any additonal interfaces than wan configured?
Nothing WAN related, just the one WAN iface. netifd spawns WAN_6 (Virtual dynamic interface (DHCPv6 client)) and WAN_6_4 (Virtual dynamic interface (Dual-Stack Lite (RFC6333))) automatically on this node.
That is another way to go about it. In any case the firewall of course needs to be configured correctly to allow the necessary exchange of information with the ISP. Which might be the issue in your case.
Probably only by contacting the ISP support. I would know of a way to check it over the wire from the router.
I switched now back to 3.X since I was also not able configure it manually on 4.X.
If anyone has a running DS-Lite configuration with a manual setup of the interfaces it would be nice if could be posted here.
Since your ISP apprently furnished you with an IPv6 address (2001:a60:0:3::ffff) for their AFTR infrastructure, instead of a hostname on a FQDN, I would suspect that the ISP has not implemented RFC6334. My ISP furnished a hostname on a FQDN.
Perhaps you could try (play around) with this conf
Without any pointer from the node’s log it is sort of difficult to get to the bottom of it…
What happens when you disable ds-lite -> option ipv6 '0'?
Else (with *ds-lite) active, it might require some effort to debug the issue:
make sure the ISP’s AFTR node (2001:a60:0:3::ffff) is reachable/accessible
run a tcp/udp dump on the router, download the dump to a node with an app (e.g. wireshark) suitable for packet inspection (latest wireshark version comes also with remote ssh dump option)
use Foris Diagnostics and see whether the dumped information contains anything useful pertinent to the issue