today i got my new dsl line from vodafone germany / providet by telekom ...
vodafone issues no real ipv4 adress .. i configured all thinks like described here in the help pages.
iam getting connection to the internet. so that seems to be fine. but i cannot use the real ipv6 adress - when iam going to ipv6 sites they say i not have a ipv6 adress:
but i want to connect to my home network via wireguard from the outside (smartphone) using ipv6.
iam getting the following information on the interfaces after the dsl line is estavlished. does this looks good? it seems that i get a local ipv4 adress and a public (?) ipv6 adress
Thanks for the hint. you are right - i waited longer now there is output. but it makes no real sense to me ... perhaps vodafone provides not a public connected ipv6 adress ... wired
i also tried dslite config but i deactivated it beacuase iam getting not just a ipv6 adress but also a local ipv4 adress from vodafone. so dslite makes no sense for me i think. here is the log:
Wed Oct 30 11:33:33 2024 daemon.info pppd[1777]: CHAP authentication succeeded: access accepted : vodafone-vdsl.komplett/xxxxxx
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: CHAP authentication succeeded
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: peer from calling number 3C:61:04:53:88:06 authorized
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: local LL address fe80::60ea:7e9b:9361:c651
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: remote LL address fe80::ded2:fcff:fe24:dd17
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: local IP address 192.0.0.1
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: remote IP address 88.72.0.1
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: primary DNS address 176.95.16.250
Wed Oct 30 11:33:33 2024 daemon.notice pppd[1777]: secondary DNS address 176.95.16.251
Wed Oct 30 11:33:34 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Oct 30 11:33:34 2024 daemon.notice netifd: Interface 'wan' is now up
This is strange since the ISP is giving you v6 configuration both inside and outside the tunnel. But the inside the tunnel is only a /56 prefix (which is good) but no direct IP. And outside the tunnel is a real mess with multiple IPs in different /64 prefixes but no larger routed prefix.
As a stopgap without knowing more about this ISP, try ip6class pppoe-wan on the LAN interface. This should (along with the default ip6assign 60 setting) give lan a /60 out of the /56 and allow LAN clients to route IPv6.
will this also makes me ping a public ipv6 adress in the internet from the openwrt router?
when i try this now it doesnt seems to work correctly - my assumption is, that vodafone disrupts the ipv6 connection ...
root@OpenWrt:~# ping 64:ff9b::40be:3fde
PING 64:ff9b::40be:3fde (64:ff9b::40be:3fde): 56 data bytes
^C
--- 64:ff9b::40be:3fde ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:~# traceroute 64:ff9b::40be:3fde
traceroute to 64:ff9b::40be:3fde (64:ff9b::40be:3fde), 30 hops max, 72 byte packets
1 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 0.055 ms 0.596 ms 0.423 ms
2 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 1.255 ms 5.045 ms 0.060 ms
3 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 29.959 ms 0.060 ms 7.725 ms
4 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 5.099 ms 12.639 ms 0.055 ms
5 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 5.125 ms 0.052 ms 0.053 ms
6 2a00:10:3f32:9c01:6a1:51ff:fe80:14cd (2a00:10:3f32:9c01:6a1:51ff:fe80:14cd) 0.056 ms 0.054 ms 0.054 ms
You could also try removing or disabling the stock wan6 section, which is making DHCP requests directly on eth0.2; outside the tunnel. Apparently something is answering them, perhaps with a lot of nonsense. A pppoe ISP usually has both IPv4 and IPv6 inside the tunnel.
No, IP6s that start with fe80 are link-local, they are not vaild on the Internet. You still don't have a public IPv6 (starts with 2 or 3), though there is a PD on wan_6. I don't have direct experience with pppoe but I think the pppoe driver is supposed to start up wan_6 and then obtain both an IP and a prefix from the ISP. (note that wan_6 is a completely different name than wan6.)
Kinda seems like it's working to me though, if you look at br-lan there in your screenshot there's a public ip right there. Though once you figure out your ip address troubles depending on what port you run the wireguard on you'll need to adjust the firewall settings to let it through, probably with a rule to allow UDP connection on the wireguard port.
... perhaps vodafone provides not a public connected ipv6 adress ... wired
