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

LAN set to Track IPv6 Interface WAN but no global IPv6 address on LAN #1506

Closed
borisneubert opened this issue Mar 25, 2017 · 8 comments
Closed
Assignees
Labels
bug Production bug
Milestone

Comments

@borisneubert
Copy link

I had this working once in 17.1.1. I am now on 17.1.3.

Details:

Configuration in web interface is
WAN interface: Basic, Directly send SOLICIT, DHCPv6 Prefix Delegation size 64, Send IPv6 prefix hint
LAN interface: Track IPv6 Interface WAN, IPv6 Prefix ID 0

WAN interface gets 64bit prefix from upstream stateless DHCPv6 server:
inet6 2a02:908:xxx:xxx:xxx:xxx:xxx:f83 prefixlen 64 autoconf

LAN interface only has link-local address:
inet6 fe80::1:1%em0 prefixlen 64 scopeid 0x1

LAN interface does not get an IPv6 address from the delegated prefix.

The following reports may or may not be related:
https://forum.opnsense.org/index.php?topic=4774.msg18598#msg18598
https://forum.opnsense.org/index.php?topic=4404.msg16570#msg16570

@Taomyn
Copy link

Taomyn commented Apr 4, 2017

I'm seeing the same with 17.1.4 although this is the first time I have tried IPv6 - I have a WAN interface that gets it's IPv6 address from my ISP without issue (same as borisneubert but I have delegation set to /56), and two internal interfaces LAN and Guest_LAN, both set to track WAN, each with different IDs, and neither ever gets an IPv6 address.

@cvbkf
Copy link

cvbkf commented Apr 6, 2017

Same problem here.
Sometimes it works, but if the OPNSense is rebooted, or the wan connection was offline weirdest things are happening. E.g.: WAN Interface gets no or a new prefix, LAN stays on the old prefix, resulting in massive connection issues for the clients

17.1.4 here, Vodafone cable connection

@borisneubert
Copy link
Author

Updated to 17.1.6 today. No change in behavior. Here ist the routing.log after enabling IPv6 on WAN and LAN and setting LAN to track WAN. igb1 is LAN.

May  4 21:39:07 opnsense radvd[67667]: version 1.15 started
May  4 21:39:07 opnsense radvd[67667]: no auto-selected prefix on interface igb1, disabling advertisements
May  4 21:39:07 opnsense radvd[68032]: sendmsg: Can't assign requested address
May  4 21:39:17 opnsense radvd[68032]: Exiting, sigterm or sigint received.
May  4 21:39:17 opnsense radvd[68032]: sending stop adverts
May  4 21:39:17 opnsense radvd[68032]: removing /var/run/radvd.pid
May  4 21:39:17 opnsense radvd[33496]: version 1.15 started
May  4 21:39:17 opnsense radvd[33496]: no auto-selected prefix on interface igb1, disabling advertisements

@fichtner
Copy link
Member

fichtner commented May 4, 2017

I'd love to help but I don't have access to such setups and we can exclude a general issue in radvd as it hasn't been updated in all of 17.1. SSH access would likely help to advance this if no fixes or config settings are proposed.

@borisneubert
Copy link
Author

User Space in Forum got it working but there is no obvious difference to my setup. You mean ssh access to my opnsense box? Is TeamViewer access to my Linux desktop with Firefox and terminal session running on opnsense an option?

@fichtner
Copy link
Member

fichtner commented May 5, 2017

@borisneubert that would work... can you drop me a mail for coordination franco@opnsense.org thanks!

@fichtner fichtner self-assigned this May 5, 2017
@fichtner fichtner added the bug Production bug label May 5, 2017
@fichtner fichtner added this to the 17.7 milestone May 5, 2017
@Taomyn
Copy link

Taomyn commented May 6, 2017

I thought I would add my findings from today that I posted to the forums:

I've made some progress having looked at another thread here about IPv6 but I'm still a little stumped.

If I set the WAN to the following as per the other thread:

IPv6 Configuration Type: DHCPv6
Configuration Mode: Basic
Use IPv4 connectivity: yes
Request only a IPv6 prefix: yes
Directly send SOLICIT: yes
DHCPv6 Prefix Delegation size: 56
Send IPv6 prefix hint: yes

With this both my LAN interfaces get an IPv6 address, although I discovered that an ID of "0" does not work even though that's what the help-hint says, so I set them to "1" and "2".

However, the WAN no longer has an IPv6 address. Tweaking the WAN settings in any way I either end up with no IPv6 addresses, or just the WAN gets an IPv6 and neither LAN gets one. Even after waiting several minutes or rebooting the firewall.

I did see this in the system log when the WAN did not get an address:

May 6 14:38:26 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
May 6 14:38:25 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for WAN[wan]
May 6 14:38:24 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
May 6 14:38:23 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for WAN[wan]

So in the end, I currently have IPv6 addresses or the LAN interfaces but nothing on the WAN interface. Any idea how I can sort that out?

@fichtner
Copy link
Member

Lots of progress here. Should be fixed. :)

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

No branches or pull requests

4 participants