IPv6 No Gateway after 2.5 upgrade

g.shaffer

I noticed that both /tmp/em0_routerv6 and /tmp/em0_defaultgwv6 were empty while the ipv4 versions had the valid router addresses in them. Both of these are set in the script /var/etc/rtsold_em0_script.sh which is built by the script /etc/inc/interfaces.inc. It looks like the parameter is not being passed to the script. I modified the routine in interfaces.inc that builds the resold_em0_script (search for "rtsoldscript") to set a hard coded value for both these files and my IPv6 gateway started working! Routing, firewall rules, Policy Based Routing, etc, all work!

My mods:

#echo $2 > /tmp/em0_routerv6
echo "fe80::X:X:X:X" > /tmp/em0_routerv6
#echo $2 > /tmp/em0_defaultgwv6
echo "fe80::X:X:X:X" > /tmp/em0_defaultgwv6

After I made the mods, I "saved" the WAN interface again without making any changes. Hope this helps someone until a real fix is pushed out.

g.shaffer

@g-shaffer

UPDATE:

Here is a diff of my changes to /etc/inc/interfaces.inc

interfaces.inc.diff

mrsunfire

@g-shaffer Worked for me, thank you!

pete

@mrsunfire - thank you. It is working for me here.

randyshoopman

I'm also seeing this issue.

@g-shaffer What are you setting as the "hard coded value"? The Link Local IPv6 address of the WAN?

g.shaffer

@randyshoopman I got it by looking for the "receive advertise from ..." in the dhcpd.log, but you should be able to use the default IPv6 route address (minus the %interface) listed in the default route table (Diagnostics -> Routes).

randyshoopman

@g-shaffer I don't seem to have any log entries in my dhcp.log with that exact text. In any case the default route has an fe80 link local address. I will try that -- thanks

MarcO42

@g-shaffer Hi, I did this change with the result that I got a static IPv6 address to monitor.
Btw. This can slo be done here -> System - Routing - Gateways - Edit WAN_DHCP6 -> Monitor IP

But now come the strange part: After I realised that I can do this also in the configuration I revert the change to

        $rtsoldscript .= "# This shell script launches dhcp6c and configured gateways for this interface.\n";
        $rtsoldscript .= "echo $2 > {$g['tmp_path']}/{$wanif}_routerV6\n";
        $rtsoldscript .= "echo $2 > {$g['tmp_path']}/{$wanif}_defaultgwv6\n";
        $rtsoldscript .= "/usr/bin/logger -t rtsold \"Received RA specifying route \$2 for interface {$interface}({$wanif})\"\n";

It works. I can not explin why but it works :)
Cheers
Marco

pete

@marco42

Putting the local link address as an IP6 monitoring address is the first thing I did to originally "fix" the issue.

This time around went back to putting in the google IP6 address as a monitoring address for IP6:

1 - 2001:4860:4860::8888
2 - 2001:4860:4860::8844

This Google DNS monitoring address is what I was using for PFSense 2.4.x

That and went to diagnostics / routes / IP6 routes and took the local interface FE80 address minus the %em1 and used it in the diff file.

I wanted to just leave it alone for time bean as it is working and everytime I play with this I lose my IP6 connectivity.

On the second WAN failover interface which is using a CPE to T-Mobile I tested it with my Laptop and do get an IP6 address just fine. When I connect it to PFSense and set it to IP6 dhcp I do not get an address. I am not sure how to figure this out so went back to connecting to the LAN interface and using that as a WAN interface for my failover.

That and not relating to OP I noticed I lost my IPSec and OpenVPN stuff. Fixed the OpenVPN stuff yesterday and confirmed that it is working. Haven't fixed IPSec VPN yet though.

MarcO42

@pete
To be clear: I reverted my changes in the /etc/inc/interfaces.inc to the code above and didn't use the monitoring funktion from System/Routing/Gateways and after a reconect I can see the the Gateway have now the correct entry. :)

pete

@marco42

Ahhh....thank you Marco.

So where did you get the IP6 gateway address and where did you install it?

Do you have the temp files /tmp/em0_routerv6 and /tmp/em0_defaultgwv6 with the IP6 gateway address before you removed the diff changes?

Today did a new 2.5 build on my PFSense hot spare box. IP6 worked out of the box. Have to test OpenVPN and IPSec VPN on it first.

Will drop this box in to place after configuring add ons the rebuild the updated machine from scratch.

Using monitoring function here because primary WAN is cable and secondary WAN is a T-Mobile LTE CPE.

MarcO42

@pete
Hi,
the IP6 is set like the IP4. After a reconnect its there. (Like magic ;) )
And yes, I had these files (named on my side with pppoe) before.
I double checked it right now and I think I found somthing strange.
I have the old file already in place but please take a look:

[2.5.0-RELEASE]/root: ls -al /tmp/pppoe_r*
-rw-r--r--  1 root  wheel  14 Mar  3 03:50 /tmp/pppoe0_router
-rw-r--r--  1 root  wheel   1 Mar  3 03:50 /tmp/pppoe0_routerV6
-rw-r--r--  1 root  wheel  26 Mar  3 03:50 /tmp/pppoe0_routerv6

Then I checked my script and I saw that I made a mistake that fixed my issue:

        $rtsoldscript .= "echo $2 > {$g['tmp_path']}/{$wanif}_routerV6\n";

I think that in the original script create this file (**_routerv6*) with emptiy content.
Maybe the function file_put_contents() is afterwards not able to recreate or fill the file with content?

After I chnaged it to a file named _routerV6 with an upper V another prozess created the correct file.

So my solution for me is now this:

        $rtsoldscript .= "# echo $2 > {$g['tmp_path']}/{$wanif}_routerv6\n";

Cheers

SteveITS

@marco42 I figured I'd just check for you as we have one on 21.02 and others on 2.4.5. I found interesting results from "ls -l /tmp/mvneta*" (the interface on SG-2100):

21.02:
-rw-r--r-- 1 root wheel 12 Feb 27 00:37 /tmp/mvneta0_defaultgw
-rw-r--r-- 1 root wheel 1 Feb 27 00:37 /tmp/mvneta0_defaultgwv6
-rw-r--r-- 1 root wheel 0 Feb 27 00:37 /tmp/mvneta0_dhcp6_complete
-rw-r--r-- 1 root wheel 0 Feb 27 00:37 /tmp/mvneta0_error_output
-rw-r--r-- 1 root wheel 244 Feb 27 00:37 /tmp/mvneta0_output
-rw-r--r-- 1 root wheel 13 Feb 27 00:37 /tmp/mvneta0_router
-rw-r--r-- 1 root wheel 1 Feb 27 00:37 /tmp/mvneta0_routerv6

2.4.5p1:
-rw-r--r-- 1 root wheel 9 Feb 19 00:22 /tmp/mvneta0_defaultgw
-rw-r--r-- 1 root wheel 26 Feb 15 15:28 /tmp/mvneta0_defaultgwv6
-rw-r--r-- 1 root wheel 0 Feb 19 00:24 /tmp/mvneta0_error_output
-rw-r--r-- 1 root wheel 577 Feb 19 00:25 /tmp/mvneta0_output
-rw-r--r-- 1 root wheel 10 Feb 19 00:25 /tmp/mvneta0_router

On BOTH, Status/Gateways shows "WAN_DHCP6 (default)" as Pending and IPv6 is working. So perhaps the Pending status is not new in 2.5? Note 2.4.5 does not have "mvneta0_routerv6" either.

MarcO42

@teamits said in IPv6 No Gateway after 2.5 upgrade:

21.02:
-rw-r--r-- 1 root wheel 1 Feb 27 00:37 /tmp/mvneta0_routerv6

Hi Steve,
your file have a size of 1 Bytes. It looks like that this is the same issue like my. Are you able to edit /etc/inc/interfaces.inc and change line 5145 like I did to validate if my fix works?
Cheers

pete

@marco42

Thank you @marco42.

Here made the mistake of removing all IP6 related temp files and GUID file to start from scratch on the IP6 configuration file.

Then reconfigured IP6 on the WAN / LAN pieces. Doing this and nothing else showed IP6 pending and working IP6 internet and empty temp files. Edited the temp files to show the local IP6 gateway and all appears fine. Later on edited the diff file with the IP6 local gateway address and that is what is showing in the gateway dashboard section.

Today bringing up test hot swap box with new V2.5 on it to see what happens and if IP6 works.

SteveITS

@marco42 I noticed that. But IPv6 is working for both these routers...can ping from the router or PCs behind it. The router has a default route for IPv6 in Diagnostics/Routes, just no gateway shown in Status/Interfaces. These are two locations and two ISPs (AT&T and Comcast).

chicaneau

@marco42 Hey I'm new to this bug, but I thought i could provide some input

I have attempted your fix on lines 5145 and 5146 with no success. It is not creating the v6 files in /tmp but it does seem to update the script @ /var/etc/rtsold_em0_script.sh

If i manually create those 2 files em0_routerv6 and em0_defaultgwv6 then the gateway shows in the front-end on both the dashboard and the gateway status screen. instead of 'dynamic' and '~' respectively. This however doesnt seem to apply to the firewall rules or whatever else is wrong, i assume something has to restart... i did 'reapply filters' on the firewall but this didnt help. I also 'saved' my WAN interface and this didnt help either. In fact it deleted the 2 em0_* files.

My RA setting is on unmanaged and i have dhcpv6 disabled. This is how I had it setup on 2.4.5 where it worked perfectly. My clients are not receiving an ipv6 address.

I also noticed that on a cold boot that my WAN/LAN interfaces have no ipv6 address at all. They only receive an address after i either save the WAN interface screen or release/renew the WAN address in interface status.

Im happy to try any suggestions, cheers

g.shaffer

@chicaneau

If your WAN is not set to DHCP6, what is it set to (e.g. Static)?
My WAN interface is set to DHCP6 with "Use IPv4 connectivity...", "Send IPv6 prefix hint", "Debug" and "Do not allowPD/Address..." checked. "Do not wait for a RA" is not checked.

chicaneau

@g-shaffer Ahh sorry, i should have been clear. My WAN type is DHCP6. My LAN DCHP6 server is turned off. under Services -> DHCPv6 Server & RA -> DHCPv6 Server.

Under WAN i have.

config type = "DHCP6", Send IPv6 prefix hint = ticked, Do not wait for a RA= ticked, Do not allow PD/Address release = unticked.

Under Router Advertisements i have Router mode = "unmanaged" and everything else blank/default

These are the exact settings i have on 2.4.5 which worked perfectly from cold boot with no issues.

chicaneau

@chicaneau EDIT: it appears the script started working after i unset the ipv6 type in the WAN config and set it to DHCP6 again. I also only set my DHCPv6 Prefix Delegation size to 56 (as per isp recommendation) and left all else unticked in the ipv6 settings.

I still have no ipv6 connectivity from any windows devices. ping6 in the pfsense shell is working for external addresses

the ipv6 gateway now shows online and shows the gateway ipv6 address instead of "~"