OPNsense Forum
Archive => 20.1 Legacy Series => Topic started by: jafinn on February 02, 2020, 01:19:52 am
-
I just spun up a fresh instance of 19.7 and IPv6RD worked. Upgraded to 20.1 and can't get an IP anymore. Anyone else got it working?
-
Hi there,
its up and running on my environment. Hard to say what the problem is at your end if you are not providing more details about your config
Br br
-
worked before the upgrade zero problems , Stopped working on the LAN side after so i can confirm it broke
-
It's kind of funny, people said the same thing about 19.1 -> 19.7 and here we are talking about 19.7 -> 20.1 with all the same patching in place since a year and literally no info beyond "it broke". I am not sure what to make of it honestly and it's not enough information to start looking.
Cheers,
Franco
-
lol I'm still searching to see why and if and when i find whats up I try to share
I have a feeling I got my breakage when I imported my backup. I'll have to reinstall a couple times to confirm this.
-
It's kind of funny, people said the same thing about 19.1 -> 19.7 and here we are talking about 19.7 -> 20.1 with all the same patching in place since a year and literally no info beyond "it broke". I am not sure what to make of it honestly and it's not enough information to start looking.
Cheers,
Franco
Just wanted to know if it was worth doing a re-install.
So, downloaded a new 20.1 ISO, did a fresh install. Went through the wizard and then added the IPv6RD details under the WAN interface.
Copy/paste from my ISP into OPNsense to avoid any typos.
IPv4 BR adresse: 213.167.115.92
IPv4 Prefix: 0
IPv6 Prefix: 2a01:79c::/30
In 19.7 it then gets an IPv6 address and I can ping6 2606:4700:4700::1111.
In 20.1 the LAN insterface gets an address but the WAN don't get an IPv6 address when looking at the interfaces widget or under interfaces > overview. I do however get an IPv6 in the console.. If I try to ping6 I get
# /sbin/ping6 -c '3' '2606:4700:4700::1111'
ping6: UDP connect: No route to host
In the logs there's no mention of wan interface, just that the lan interface gets an adress based on the external IPv4 and this
2020-02-03T10:29:54 opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
2020-02-03T10:29:54 opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to wan
Not sure what else I can provide for you, screenshots or logs?
Edit: Since it complains about no route, I guess it would make sense to include this
Proto Destination Gateway Flags Use MTU Netif Netif (name) Expire
ipv6 ::1 link#5 UH 0 16384 lo0
ipv6 2a01:79c:ceb9:2b78:: link#9 UHS 0 16384 lo0
ipv6 2a01:79c:ceb9:2b78::/64 link#2 U 36 1500 vtnet1 lan
ipv6 2a01:79c:ceb9:2b78::/62 link#9 U 0 1280 wan_stf
ipv6 2a01:79c:ceb9:2b78::1 link#2 UHS 0 16384 lo0
ipv6 fe80::%vtnet0/64 link#1 U 0 1500 vtnet0 wan
ipv6 fe80::28c4:fbff:fefd:3f37%vtnet0 link#1 UHS 0 16384 lo0
ipv6 fe80::%vtnet1/64 link#2 U 178 1500 vtnet1 lan
ipv6 fe80::547a:d1ff:fe2c:ec7a%vtnet1 link#2 UHS 0 16384 lo0
ipv6 fe80::%lo0/64 link#5 U 0 16384 lo0
ipv6 fe80::1%lo0 link#5 UHS 0 16384 lo0
-
ok I finally got my problem isolated to something with the saved backup.
I was using development and with the new updates I switched to production to do them.
Something about the old development backup and switching to production and using the old update is bad. I found that going to "Interfaces/Settings and then clearing the
DHCP unique identifier fixed the problem after a reboot.
Lots of reinstalling and testing to get this resolved for my system but all is well with just that one setting.
Figure the odds.
RADVD advertising and the dhcpv6 server on the lan side now works as it should.
-
This is what it shows i am running currently
Versions OPNsense 20.1-amd64
FreeBSD 11.2-RELEASE-p16-HBSD
OpenSSL 1.1.1d 10 Sep 2019
-
I am facing the same issue. But switching back to 19.7 did not help either ... not sure when it broke. I know IPv6 was working fine on my clients at some point in time.
My setup is like this: internet <--> FritzBox (get's /56 from telco provider) <--> OPNsense (requests /60) <--> LAN / OPT1.
I see the following in the logs:
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: restarting
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: Start address release
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: Sending Release
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: failed to remove an address on igb0: Can't assign requested address
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: remove an address 2a03:...:9bf6/64 on igb2
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: Received REPLY for RELEASE
Feb 11 00:57:25 OPNvirt dhcp6c[64003]: status code: success
Feb 11 00:57:25 OPNvirt dhcp6c: dhcp6c RELEASE on igb1 - running newipv6
Feb 11 00:57:25 OPNvirt opnsense: plugins_configure dhcp (,inet6)
Feb 11 00:57:25 OPNvirt opnsense: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6))
Feb 11 00:57:25 OPNvirt opnsense: /usr/local/etc/rc.newwanipv6: Warning! dhcpd_radvd_configure(auto) found no suitable IPv6 address on igb0
Feb 11 00:57:25 OPNvirt opnsense: /usr/local/etc/rc.newwanipv6: Warning! dhcpd_radvd_configure(auto) found no suitable IPv6 address on igb2
Feb 11 00:57:28 OPNvirt dhcp6c[64003]: Sending Solicit
Feb 11 00:57:28 OPNvirt dhcp6c[64003]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 11 00:57:29 OPNvirt dhcp6c[64003]: Sending Request
Feb 11 00:57:29 OPNvirt dhcp6c[64003]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 11 00:57:29 OPNvirt dhcp6c[64003]: Received REPLY for REQUEST
Feb 11 00:57:29 OPNvirt dhcp6c[64003]: add an address 2a03:......:9bf4/64 on igb0
Feb 11 00:57:29 OPNvirt dhcp6c[64003]: add an address 2a03:......:9bf6/64 on igb2
Feb 11 00:57:29 OPNvirt dhcp6c: dhcp6c REQUEST on igb1 - running newipv6
Feb 11 00:57:29 OPNvirt opnsense: plugins_configure dhcp (,inet6)
Feb 11 00:57:29 OPNvirt opnsense: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6))
In the dashboard I see the assigned addresses for LAN and OPT1 but WAN only shows the link local address although ifconfig reports the assigned address as
inet6 2a03:......:9bf5 prefixlen 64 autoconf
On the OPNsense I can ping6 all hosts ... but on the LAN side I can not. Any idea how to continue troubleshooting?
Some further infos about my config:
WAN interface:
IPv6 configuration type DHCPv6
Request only an IPv6 prefix yes
Prefix delegation size 60
Send IPv6 prefix hint yes
LAN/OPT1 interface:
Track interface WAN
IPv6 Prefix ID 0 / 1
-
Btw. ... I can ping6 the OPNsense from LAN and I can also ping the FritzBox from LAN ... wtf ... but the next step I can only ping from the OPNsense, not from LAN.
In the firewall logs I can see OK messages with
<IPv6 of LAN system> ipv6-icmp let out anything from firewall host itself
<IPv6 of LAN system> ipv6-icmp let out anything from firewall host itself
<IPv6 of WAN if on OPNsense> ipv6-icmp let out anything from firewall host itself (force gw)
<IPv6 of LAN system> ipv6-icmp let out anything from firewall host itself
<IPv6 of LAN system> ipv6-icmp let out anything from firewall host itself
-
Did you try what worked for me?
-
Did you try what worked for me?
Hi,
since I have two internal interfaces (LAN and OPT1) I need to specify an "IPv6 Prefix ID" (this is what you meant with unique identifier, right?). And changing it does not help either.
-
Did some network tracing on the FritzBox, both on the LAN and WAN side (of the FritzBox)
- ICMPv6 from the OPNsense box can be seen in both LAN and WAN trace on the FritzBox
- ICMPv6 from the client can only be seen in the LAN trace on the FritzBox
Does this mean there is something wrong on the FritzBox settings?
-
@Space, I couldn't help but notice that you don't mention 6rd at all. Which this topic is about.
-
Oh, my fault. I misread it and read PD, prefix delegation ...
@Admin: can you move my stuff to a new thread? Or even delete it, because I will check with AVM first ... maybe it broke during the firmware upgrade I did some time ago ... without noticing me ...
-
@Admin: can you move my stuff to a new thread? Or even delete it, because I will check with AVM first ... maybe it broke during the firmware upgrade I did some time ago ... without noticing me ...
Just to close my interruption: it's a known bug in FritzBox firmware starting version 7.10 ...
-
So i just tested this and it didn't work for me.
the wan_stf interface was created but not lined visibly anywhere in the GUI.
from the CLI i was able to see the wan_stf interface, but running ping6 google.com resulted in ping6: UDP connect: No route to host
adding the default route manually using route add -inet6 default -interface wan_stf temporarily fixes the issue, but none of the 6RD settings or status are visible in the interface.
tested on 20.1 and 20.1.1
went ahead and opened a github issue here: https://github.com/opnsense/core/issues/3903 (https://github.com/opnsense/core/issues/3903)