ipv6 is down after restart WAN, won't back until reboot
-
Hi,
just hit an issue , whenever I restart WAN , then client-side IPv6 will be down , it won't back online until pfSense is rebooted, which is quite annoying
is there anyway I can bring IPv6 back up without reboot it ?
tried /usr/local/sbin/pfSctl -c 'interface reload lan' , but seems no luck.
Best regards,
-
So the WAN comes back up with a valid IPV6 address but LAN does not?
Does it come back with the same address?
WAN is set to DHCPv6 and LAN to track the WAN?
Steve
-
Hi,
I think it got something to do client side , I discover that if I disconnect then re-connect my Wi-FI , ipv6 seems back online then.
sorry for the trouble,
speaking of this , is there any I can force all connected devices to refresh their address ? like force them disconnect then reconnect but without them knowing it ?
Best regards,
-
With IPv6 and SLAAC, there's no need to force that. Router advertisements are sent out about every 15 seconds, which provide the addresses.
-
Hi,
@JKnott thanks , but where is this SLAAC setting ?
because on my case it seems not working , 1 minute after WAN restarted , still can't get ipv6 , unless disconnect and reconnect my Wi-Fi.
-
There is none that I'm aware of. It just happens as part of the protocol. Use Packet Capture or Wireshark and filter on ICMPv6. You should see those Router Advertisements. You mentioned WiFi, what about wired devices?
-
@JKnott said in ipv6 is down after restart WAN, won't back until reboot:
There is none that I'm aware of. It just happens as part of the protocol. Use Packet Capture or Wireshark and filter on ICMPv6. You should see those Router Advertisements. You mentioned WiFi, what about wired devices?
yeah ... thanks for the hint , wired devices still works , I got feeling might be something to do with my router that is on bridge mode for Wi-Fi....
-
@qtwrk
Since wired devices work, it's not a pfSense problem. IPv6 relies on multicasts for several functions. As I mentioned, RAs are used to provide address info. All a router does is send out the multicast with the appropriate info. About the only thing that could cause a problem would be bad info. However, that would affect all devices, not just WiFi.
