Internode Native IPv6, No Address?
-
I've tried statically assigning an address to the LAN interface, but it's still not working. For some reason the LAN link-local address is stuck on fe80::1:1, which I'm pretty sure shouldn't be the case. I can get an IPv6 ping out from the WAN interface (which actually appears to be the dynamic /64 upon closer inspection), that's about all that I can make work properly.
RA is also giving me headaches, but I'd say I'm better off crossing that bridge when I come to it.
-
Well I get a dynamic /64 on my WAN interface as well, once the dynamic address is assigned it seems to use that to route my /56 that's static on the LAN interface.
-
My settings are as follows for DHCP6 on the WAN interface, can you confirm that yours are the same?
Use IPv4 connectivity as parent interface: Yes
Request only a IPv6 prefix: Yes
DHCPv6 Prefix Delegation size: None
Send IPv6 prefix hint: No -
I have DHCPv6 Prefix Delegation size set to 56
-
I also notice I have a WAN V6 address of fe80::20c:29ff:fe65:5f35%em1
-
My WAN v6 address is fe80::225:90ff:fe91:d2e6%em0, which seems more or less correct. This "track interface" thing on the LAN interface should Just Work
, but instead it's driving me mental. It gives me an option for inputting a hexadecimal prefix ID between 0 and ff, but I have no idea what it should be set to. Maybe I need to go down the static configuration route after all. -
Sigh, I just tested it for shit n giggles, its not working anymore either grown
-
What address are you getting for your IPv6 gateway? I'm seeing fe80::224:14ff:fe9a:9700, which seems a bit suspect.
-
What I got in my last post. fe80::225:90ff:fe91:d2e6%em0
-
dhcp6c[52181]: client6_recvadvert: XID mismatch
Now this on restart.
Honestly I am lost now, it was working.
-
Same boat. Had it working yesterday, but no go today. Maybe it's on Node's end? Although I can't see any advisories which would suggest that. I might give support a call tomorrow.
-
@ingenieurmt:
My WAN v6 address is fe80::225:90ff:fe91:d2e6%em0, which seems more or less correct.
These are link-local addresses -> definitely NOT correct.
-
Looking over my logs, I have a feeling something's gone wrong on the nodes end.
It was not link local in the past.
-
I haven't called support yet, but in the meantime I thought I'd try disabling IPv6 in the Node CP, and will enable it again later tonight… might kick something on their end into working differently.
-
As silly as it sounds, try changing your MAC,
-
Tried setting it all up again today… still doesn't work 100%. I can use Diagnostics > Ping to google.com using IPv6, and get replies... but nothing on the LAN side can access remote IPv6 addresses.
Toje, are you seeing entries like these in your System Log?
php: rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable' php: rc.newwanip: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable'IPv6 Destination Gateway Flags Refs Use Mtu Netif Expire default fe80::224:14ff:fe9a:9810%pppoe0 UGS 0 2146 1492 pppoe0Similar to another thread here.
Edit: Seems to be working now, for some reason. ??? ;D
The settings I'm using:
WAN:
-
IPv6 Configuration Type: DHCP6
-
Use IPv4 connectivity as parent interface: Ticked
-
Request only a IPv6 prefix: Ticked
-
DHCPv6 Prefix Delegation size: 64
-
Send IPv6 prefix hint: Ticked
LAN:
-
IPv6 Configuration Type: Static IPv6
-
IPv6 address: 2001:44b8:xxx:yyyy:: (/64)
DHCP:
-
Enable DHCPv6 server on LAN interface: Un-ticked
-
Router Advertisements: Assisted (though I think it should be Unmanaged.. but I'll just leave it as is for the minute ;))
… and a few WAN and LAN firewall rules.
Edit 2: ugh, borked again, without any changes made.
-
-
@ingenieurmt:
Request only a IPv6 prefix: Yes
DHCPv6 Prefix Delegation size: NoneThat seems a bit odd; the first option says you only want a delegated prefix, but the second option says you don't want a prefix. Why do you think you want the first one, anyway?
-
The settings I'm using:
WAN:
-
IPv6 Configuration Type: DHCP6
-
Request only a IPv6 prefix: Ticked
-
DHCPv6 Prefix Delegation size: 64
-
Send IPv6 prefix hint: Ticked
LAN:
- IPv6 Configuration Type: Static IPv6
That, too, seems odd: You're requesting prefix delegation, but then you're not actually using the prefix information obtained via DHCP-PD but instead configure your prefix statically. Also, I thought the delegated prefix was supposed to be a /56, not a /64?!
-
-
That, too, seems odd: You're requesting prefix delegation, but then you're not actually using the prefix information obtained via DHCP-PD but instead configure your prefix statically.
Not too sure what you're saying… any chance you could elaborate?
Also, I thought the delegated prefix was supposed to be a /56, not a /64?!
Your delegated static /56 IPv6 prefix for your LAN is: 2001:44b8:xxx:yyyy
- Your existing IPv4 address (if static) and any existing framed route(s)
- A dynamic /64 IPv6 prefix for your PPP session
- A static /56 IPv6 prefix for your LAN (if you are using a router with Prefix Delegation)
That's what's shown in the Node control panel. My interpretation of that is 64 is used on the WAN's "DHCPv6 Prefix Delegation size" drop-down, and 56 is used for the LAN's "IPv6 address" (although Logs > System > Routing then has entries saying "radvd[79545]: prefix length should be 64 for em0", so I just set it to 64 there as well).
Edit: em0 is the LAN interface.
-
I have the same Setup Rezin,
Razzfazz I set it up with the idea my WAN is the Internode side of the network and my LAN is my side, so like on a normal lan-lan router there are two different IP's