Bug #7816
closed
IPv6 breaks on reboot
0%
Description
My setup:
2.4.0-RC (amd64) (custom hardware)
built on Fri Aug 25 18:40:44 CDT 2017
FreeBSD 11.0-RELEASE-p12
net.link.bridge.pfil_bridge = 1
LAN Interface (bridge) IPv6 config: Track Interface (WAN IPv6 which is 6rd tunnel from ISP)
Altibox (Norway) IPv6RD ISP settings:
IPv4 BR address: 213.167.115.92
IPv4 Prefix: 0
IPv6 Prefix: 2a01:79c::
IPv6 Prefix Length: 30
IPv6 DNS: 2a01:798:0:8012::4
After a reboot I experience the following issues:
ping6 ipv6.google.com fails from both the firewall's WAN and its bridge LAN clients (SLAAC configured, different OS' and devices). I have also tried a different setup with a SLAAC+DHCPv6 configuration, but that did not help fix this issue.
When I do a WAN interface restart (disable, then enable) everything runs fine and I can ping6 from both the firewall and its LAN (bridge) side clients with a 10/10 score on any ipv6 tests.
Can I provide you with any logs to help solve this issue?
Files
| Interface WAN.JPG (67 KB) Interface WAN.JPG | WAN Status interface | ||
| ipv6 google ping.JPG (34.3 KB) ipv6 google ping.JPG | IPv6 Google ping6 |
Updated by Paal Andreas Lindsetmo over 6 years ago
- File Interface WAN.JPG Interface WAN.JPG added
- File ipv6 google ping.JPG ipv6 google ping.JPG added
Paal Andreas Lindsetmo wrote:
My setup:
2.4.0-RC (amd64) (custom hardware)
built on Fri Aug 25 18:40:44 CDT 2017
FreeBSD 11.0-RELEASE-p12net.link.bridge.pfil_bridge = 1
LAN Interface (bridge) IPv6 config: Track Interface (WAN IPv6 which is 6rd tunnel from ISP)Altibox (Norway) IPv6RD ISP settings:
IPv4 BR address: 213.167.115.92
IPv4 Prefix: 0
IPv6 Prefix: 2a01:79c::
IPv6 Prefix Length: 30
IPv6 DNS: 2a01:798:0:8012::4After a reboot I experience the following issues:
ping6 ipv6.google.com fails from both the firewall's WAN and its bridge LAN clients (SLAAC configured, different OS' and devices). I have also tried a different setup with a SLAAC+DHCPv6 configuration, but that did not help fix this issue.
When I do a WAN interface restart (disable, then enable) everything runs fine and I can ping6 from both the firewall and its LAN (bridge) side clients with a 10/10 score on any ipv6 tests.
Can I provide you with any logs to help solve this issue?
Updated by Jim Pingle over 6 years ago
- Status changed from New to Duplicate
- Target version deleted (
Future)
Looks the same as #3965 -- bridges are setup too late for them to be used as a track interface at boot time.
Updated by Paal Andreas Lindsetmo over 6 years ago
Hey, and thanks for the swift reply.
What about the fact that the firewall's WAN interface is unable to ping6 ipv6.google.com, would the bridge issue explain that?
Have a good weekend.