Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 prefix tracking on WAN broken on 19.1.1 #3240

Closed
klada opened this issue Feb 16, 2019 · 4 comments
Closed

IPv6 prefix tracking on WAN broken on 19.1.1 #3240

klada opened this issue Feb 16, 2019 · 4 comments
Labels
support Community support

Comments

@klada
Copy link

klada commented Feb 16, 2019

Describe the bug

I have a FTTH connection from Deutsche Telekom. They use PPPoE and DHCPv6 for IPv6 connectivity. I am getting a dynamic /56 prefix from them. I have split the prefix across multiple interfaces using prefix tracking on WAN interface.

Whenever a new prefix is assigned to me (e.g. after a PPP reconnect) the new prefix is not picked up by the tracking interfaces (LAN and GUEST in my case). This breaks IPv6 connectivity on these interfaces, causing massive timeouts for all IPv6-enabled clients on the networks.

The WAN interface itself (pppoe0) picks up the new prefix, so the firewall can ping IPv6 addresses on the internet even after a PPPoE reconnect.

To Reproduce

  1. Configure WAN interface with PPPoE and DHCPv6 (request /56 prefix, use IPv4 connectivity)
  2. Configure interface tracking for IPv6 on LAN interface
  3. The LAN interface gets a subnet from the assigned prefix
  4. Power cycle the FTTH modem (to force reconnection)
  5. The WAN interface gets a new IPv6 address and a new prefix, the LAN interface keeps the old prefix
  6. The new IPv6 prefix is only picked up the the LAN interface after a reboot

Expected behavior

The new IPv6 prefix should be picked up by all interfaces after it changes on the WAN interface.

Environment
Software version used and hardware type if relevant.
e.g.:

OPNsense 19.1.1-amd64
Network Intel® I210-AT
APU2C4

@marjohn56
Copy link
Member

Have you enabled a sticky ipv6 DUID in Interfaces:Settings?

Click on the 'Insert existing DUID' and then save. Then try reproducing.

@fichtner fichtner added the support Community support label Feb 18, 2019
@klada
Copy link
Author

klada commented Feb 18, 2019

Thanks for the input.

Unfortunately I am still getting a dynamic prefix, even if the DUID the OPNsense DHCPv6 client sends out to my ISP stays the same. This is (unfortunately) common practice among ISPs.

I was however able to resolve the issue. It turns out that the "Prevent release" option is required for Deutsche Telekom IPv6. Kinda weird.

Anyway, I am sorry for spamming the issue tracker → closing.

@klada klada closed this as completed Feb 18, 2019
@marjohn56
Copy link
Member

That's quite normal to use prevent release, I assumed you already had that selected.

@fichtner
Copy link
Member

No worries, thanks for posting the solution. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

3 participants