Windows 10 box is getting an IPv6 address with DHCP, but not the gateway. Any tips?
After uninstall / reinstalling the nic driver - I get a a default gateway - but it’s not routing through
Here’s some more info:
I’m on ATT uVerse - so it’s 6RD
I can ping from the router to IPv6 address and such.
tracert -6 2001:4860:4860::8888
Tracing route to google-public-dns-a.google.com [2001:4860:4860::8888]
over a maximum of 30 hops:
1 Destination net unreachable.
Trace complete.
ifstatus wan 6
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 534,
"l3_device": "eth1",
"proto": "dhcpv6",
"device": "eth1",
"metric": 0,
"delegation": true,
"ipv4-address": [
],
"ipv6-address": [
{
"address": "2602:306:3275:a2d0:da58:d7ff:fe00:3838",
"mask": 64,
"preferred": 604483,
"valid": 2591683
}
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
{
"target": "2602:306:3275:a2d0::",
"mask": 64,
"nexthop": "::",
"metric": 256,
"valid": 2591683,
"source": "::\/0"
},
{
"target": "::",
"mask": 0,
"nexthop": "fe80::36ef:44ff:fe17:6ee9",
"metric": 512,
"valid": 1483,
"source": "2602:306:3275:a2d0:da58:d7ff:fe00:3838\/64"
}
],
"dns-server": [
],
"dns-search": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
]
},
"data": {
}
}
ifstatus lan
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 594,
"l3_device": "br-lan",
"proto": "static",
"device": "br-lan",
"updated": [
"addresses"
],
"metric": 0,
"delegation": true,
"ipv4-address": [
{
"address": "192.168.15.1",
"mask": 24
}
],
"ipv6-address": [
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
{
"address": "fdcc:85f7:26d3::",
"mask": 64
}
],
"route": [
],
"dns-server": [
],
"dns-search": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
]
},
"data": {
}
}
ip -6 route show
default from 2602:306:3275:a2d0::/64 via fe80::36ef:44ff:fe17:6ee9 dev eth1 proto static metric 512
2602:306:3275:a2d0::/64 dev eth1 proto static metric 256
fdcc:85f7:26d3::/64 dev br-lan proto static metric 1024
unreachable fdcc:85f7:26d3::/48 dev lo proto static metric 2147483647 error -113
fe80::/64 dev wlan0 proto kernel metric 256
fe80::/64 dev br-lan proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256After switching to 6rd and back to DHCPv6 (web interface crashed), so I rebooted and now it works sort of. I can ping the google dns ip, but http://ipv6-test.com/ says my IPv6 stuff fails.
Now I’m back to it not working (routing on to the network) after saving updates which removed the following:
network.wan6.ip4prefixlen
network.wan6.ip6prefix
network.wan6.ip6prefixlen
network.wan6.peeraddr.
OK. I manually set IPv6 stuff on my box, I can ping the router (lan and wan ip addresses), but i can’t ping the modem. TCP dump is showing this on ETH1:
22:37:27.119817 IP6 (hlim 127, next-header ICMPv6 (58) payload length: 40) fdcc:85f7:26d3::34f0:55c0:8fff:a2e8 > 2602:306:3275:a2d0::1: [icmp6 sum ok] ICMP6, echo request, seq 255
Now shouldn’t my internal IP translated to the public IPv6 address?
No I can’t get traffic from lan to wan, so I’ve switched to 6rd:
Remote 12.83.49.81
Prefix 2602:300::
IPv6 length 28
IPv4 length: 0
MTU: 1472
It comes back with an IP address ,and my box gets an address but, no data is received at all.
AT&T is pretty hostile to using IPv6 on your own router. What gateway device did AT&T give you? Pace 5268AC?
3800HGV-B
So if I do DHCPv6, I can ping from the router fine, so I have it in DHCPv6 now on the WAN side. So on the LAN side I have:
IPv6 Assignment length: 64
Router Advertisment Service: Server Mode
DHCPV6 Service: Server Mode
NDP-Proxy: Disabled
DHCPv6 Mode: stateless + stateful
Alway announce default router: checked
Announced DNS server: Googles…
Now I get an IP from the ULA, I get the DNS servers, but I don’t get a gateway that’s on the ULA, but the eth0’s link local address.
If I set my box to static ipv6 address, I can ping the lan interface fine, I can ping the WAN6 interface.
When I try to ping the modem the tcp dump looks like this on ETH1:
02:27:13.244603 IP6 (hlim 127, next-header ICMPv6 (58) payload length: 40) fde4:8dba:82e1::1584:27cc:b190:ad75 > 2602:306:3275:a2d0::1: [icmp6 sum ok] ICMP6, echo request, seq 783
No response back.
If I try to ping 2001:4860:4860::8888, TCP dump on ETH1 doesn’t show anything, but on ETH0:
02:29:36.808984 IP6 (hlim 128, next-header ICMPv6 (58) payload length: 40) fde4:8dba:82e1::1584:27cc:b190:ad75 > google-public-dns-a.google.com: [icmp6 sum ok] ICMP6, echo request, seq 791
02:29:36.809083 IP6 (flowlabel 0x9aeac, hlim 64, next-header ICMPv6 (58) payload length: 88) fde4:8dba:82e1::1 > fde4:8dba:82e1::1584:27cc:b190:ad75: [icmp6 sum ok] ICMP6, destination unreachable, unknown unreach code (5)
So damned frustrating.
Got it working:
https://forum.openwrt.org/viewtopic.php?pid=315621#p315621
Had to change up the dhcp config file.
That worked, till I added a fowarding rule then all heck broke lose and I had to revert the original DHCP config, which of course breaks IPv6 from working like it should. I thinking this is some sort of bug? Or am I just setting this up wrong?