IPv6 broken beyond pfSense after 2.5 upgrade

[stepheng]

@jknott Yes, I know that the WAN address is usually separate from the LAN address on IPV6. I've attached a screen shot here (with a little bit of obscuration)

I think that this shows that I'm getting a real WAN IPv6 (that address matches the address that my ISP advised me of as my IPv6 /64 that would be my WAN address) and the LAN ipV6 address is in my /48 that is allocated and is correct (again corresponding to the /48 as advised by my ISP).

Somehow the RA / DHCPv6 / SLAAC stuff is not running now like before ....

[JKnott]

@stepheng

Please show the Interface > WAN & LAN settings. You might also include Router Advertisements page.

[stepheng]

@jknott Here goes. These are all presumably as they were set up when running 2.4.5p1. I've not changed anything since.

WAN settings

LAN settings (I actually have two ports bridged - I know that this is frowned upon, but I don't need the speed and although I have a switch that I could use the extra box and plug would make me unpopular at home)

Router Advertisements

[JKnott]

@stepheng

The only thing I've noticed is, on the RA page, I'm using unmanaged, but you're using assisted. However, I don't know if that would cause the problem. Can you upload a packet capture, showing ICMP6?

[stepheng]

@jknott yes, I’ll do that, but it may have to wait until tomorrow morning (UK time) as I have some jobs and a Zoom conference to see to. I had thought I might have to do a packet capture and see what is going on.

[stepheng]

@jknott I am seeing Neighbour Solicitation messages from computers but not seeing any responses to these ICMP messages. It looks to me as if the radvd daemon or the dhcpv6 daemon isn't responding (actually I'm at the limits of my IPv6 knowledge - I'm fairly good on IPv4 having been using computers since before networking but IPv6 is still a little more magical to me!). I have checked that radvd is apparently running (shows up in a ps aux output).

[stepheng]

@jknott Just another follow up to the above. It is definitely the whole NDP/RA exchanges that are just not happening to allocate IPV6 addresses. I've confirmed this by manually configuring IPV6 on a couple of my machines (adding in the IPV6 address of the pfSense router, an IPV6 address in my address range and prefix for the machine) and then the individual machines passes the appropriate tests on sites like test-ipv6 and ipv6-test just as before my update from 2.4.5p1. I can route IPV6 between the machines and on the internet correctly. Something is just not happening to enable the "chatter" to make the address/router negotiation work, but which happened perfectly previously.

[JKnott]

@stepheng

I don't know what would be causing that. IPv6 works fine for me with 2.5.

[stepheng]

@jknott I'm at a loss at this point. Doing a packet capture of ICMP v6 packets on my LAN I can see a steady chatter of Neighbour Solicitation/Neighbour Advertisement packets being used to determine link layer addresses, but absolutely no router solicitation or router advertisement messages.

I've also tried changing the RA settings to Unmanaged and to SLAAC with no change.

As I said pfSense is operating with IPv6 and commands on clients such as "host google.com" will return IPv6 addresses as well as IPv4.

All a mystery!

[JKnott]

@stepheng

Try reinstalling pfsense. Backup your config first, then see what happens after the reinstall, but before restoring the config.

[tadao]

@stepheng To me, after upgrading to 2.5.0, it doesn't let me use LAN with IPv6 with SLACC, if RADVD is activated. It only permits SLACC on LAN if RADVD is set to Disabled.

[stepheng]

@jknott I will do that, but it will have to wait for a couple of days until I'm on my own in the house and don't have any pressing deadlines.

I know that in theory it only takes 15 minutes to do a reinstall, but you never know what may not quite work. I'll get my old Ubiquity Edgerouter out as well in case I need to use it (I think it still has a working configuration).

[stepheng]

@tadao That is very interesting, but also to my limited understanding, somewhat puzzling. As I said, I'm not really as expert on IPv6 as I would like, but I'd be surprised that turning RADVD off would work (except with manually assigned clients - and that works for me in any case, but is a bit impractical for phones and mobile devices and besides the whole point of RA/DHCPv6 is to do all this stuff automagically). However, I did try it and got no joy. I have tried all of the setting in the RA tab. As @JKnott says, I think a re-install is needed in my case which I will try in a day or two when I have some quiet time on my own.

[stepheng]

@stepheng SOLVED!

I didn't need to re-install pfSense.

I noticed that poking around in the command line with "ps" that although I was seeing the radvd process, the only dhcp6 process that I was seeing was the dhcp6c which was being used on my pppoe0 connection to obtain my WAN IPv6 address.

I went back to the LAN / DHCPv6 Server page and made a trivial alteration (added an NTP server) and resaved the page. This obviously caused the DHCPv6 server to kick into action again. I can now see a "/usr/local/sbin/dhcpd -6 " process running (as well as the normal dhcpd process for IPv4), and also a "/usr/local/sbin/dhcpleases6" process.

All the expected ICMPvs messages for RA, RS, NS, NA are now being seen on the LAN and all devices that previously had IPv6 addresses are getting them. "test-ipv6.com" gives me my score of 10/10 again.

I was able to return the LAN / DHCPv6 Server page back to exactly the same configuration as before without any strange behaviour happening (i.e. removed the NTP server again).

I assume that for some reason during the upgrade process the dhcpv6 process didn't get started or failed. It might be interesting to see if with my configuration it starts properly when the system is rebooted - and I might try that tomorrow as that is something that can be done in a couple of minutes without risk.

Thanks for the help from @JKnott and @tadao. I must confess that I think I need to understand more about IPv6. Now that it is working I've captured some packets in Wireshark so I can study them and hopefully further my knowledge.

[ebcdic]

I have a similar problem. My ISP is also Zen, and it was working perfectly in 2.4.5p1. I'm using an SG-1100.

It appears that IPv6 comes up normally, but after a few seconds the LAN interfaces lose their IPv6 addresses. This can be reproduced by disconnecting and reconnecting the WAN in Status / Interfaces.

The DHCP logs shows that dhcp6c receives a prefix, adds addresses to the LAN interfaces, then removes them:

log.txt

[yon 0]

@ebcdic

https://redmine.pfsense.org/issues/11365

[ebcdic]

The "restarting" in the log indicates that dhcp6c is getting a sighup, but from where?

[ebcdic]

@yon-0 You seem to be talking about a completely different problem. Our ISP delegates a /48 to us, as is normal, and the LAN interfaces use a /64 subnet.

[JKnott]

@ebcdic

Are you trying to configure the WAN interface for a /48? Or allowing DHCPv6-PD to do it? What happens if you select a smaller prefix. For example, I get a /56 from my ISP, but can select a smaller one.

[ebcdic]

@jknott I'm not sure I understand you. There is no problem with the WAN interface; the router has an IPv6 connection to the outside world and can connect happily to external sites. The problem is that the LAN interfaces lose their addresses after a few seconds, apparently because dhcp6c does a restart, so clients cannot make (non-local) IPv6 connections.

[JKnott]

@ebcdic

Sorry, I wasn't quite sure what you were saying. However, what happens if you select a smaller prefix? On the WAN page, you can choose in the DHCPv6 Prefix Delegation size box. Do you have the same problem if you select a /49? /56? etc.

[ebcdic]

@jknott Changing it to /49 didn't seem to change anything. After changing it to /56 it didn't work at all - dhcp6c seemed to exit. Change back to /48 and it's the same as before: LANs get addresses then lose them a few seconds later.

[mrsunfire]

After my WAN was down for some minutes IPv6 doesn't come up anymore. I'm getting my prefix and every device gets an IPv6 address but the gateway keeps pending. Of course I use a monitor IP but it's not working. Only solution is to reboot the whole pfSense. This is unacceptable and I can't believe that this major fault wasn't discovered in the BETA builds.

Any ETA for a fix? How do I downgrade back to 2.4.5_p1?

[mrsunfire]

@johnpoz With 2.5.0 I see with Multi WAN setup that sometimes I don't get a prefix after interface down/up. DHCP log is showing "unexpected interface"

Mar 1 16:50:09	dhcp6c	22055	unexpected interface (15)
Mar 1 16:50:09	dhcp6c	18058	reset a timer on pppoe0, state=SOLICIT, timeo=151, retrans=109128
Mar 1 16:50:09	dhcp6c	18058	send solicit to ff02::1:2%pppoe0
Mar 1 16:50:09	dhcp6c	18058	set IA_PD
Mar 1 16:50:09	dhcp6c	18058	set IA_PD prefix
Mar 1 16:50:09	dhcp6c	18058	set option request (len 4)
Mar 1 16:50:09	dhcp6c	18058	set elapsed time (len 2)
Mar 1 16:50:09	dhcp6c	18058	set identity association
Mar 1 16:50:09	dhcp6c	18058	set client ID (len 10)
Mar 1 16:50:09	dhcp6c	18058	Sending Solicit

I do have to kill the dhcpd6 with "killall -9 dhcp6c" and apply interface to get it back working.

[mrsunfire]

Still no ETA for fixing this major bug that makes IPv6 unusable?

[Derelict]

Moved that other, non-related discussion to its own thread.

Most of the IPv6 work I see being done for 2.5.1 can be tracked here:

https://redmine.pfsense.org/issues/11454

Overall progress of everything being done for 2.5.1 here:

https://redmine.pfsense.org/projects/pfsense/issues?page=1&query_id=172

And here:

https://redmine.pfsense.org/projects/pfsense/issues?query_id=179

There are snapshots to try if you want to test it in your environment but it is still "In Progress."

[yon 0]

@derelict
ipv6 static routing rules do not work, when I setup 240e::/20 via wan dhcpv6 interface, but
it still via frr bgp other upstream. and I had try
setup static routing in frr still not work.
pf2.4.5 version normal work, I am using pf 2.6
not work for this.

[Derelict]

@yon-0 You are going to have to be more descriptive as to exactly what you are doing. If you are using bleeding-edge development versions and are having problems, you should be bringing up problems in the development forum, not here.

https://forum.netgate.com/category/84/2-6-development-snapshots

[fragged]

I'm now on 2.5.1-RC trying to get IPv6 to work. It looks like we're getting close, but I'm now having an issue with the interfaces going up and down in a loop if I try to enable IPv6 on WAN.

Config is WAN:
DHCPv6, /56, send prefix hint

LAN, vlan1,vlan2,vlan3 all set to track interface.

With the latest snapshot and change cca31114b0ac041e41865c586d587558f82979d6 from github I'm getting a gateway all the way on my PC on LAN, but the interfaces keep resetting on a loop on pfSense.

Spoiler

Mar 22 17:11:39 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:39 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:37 check_reload_status 700 Reloading filter
Mar 22 17:11:37 check_reload_status 700 updating dyndns opt1
Mar 22 17:11:36 check_reload_status 700 Reloading filter
Mar 22 17:11:36 check_reload_status 700 updating dyndns opt3
Mar 22 17:11:36 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:36 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:36 php-fpm 69246 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425896] unbound[88636:0] error: bind: address already in use [1616425896] unbound[88636:0] fatal error: could not open ports'
Mar 22 17:11:35 php-fpm 74596 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425895] unbound[17921:0] error: bind: address already in use [1616425895] unbound[17921:0] fatal error: could not open ports'
Mar 22 17:11:35 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:35 check_reload_status 700 Reloading filter
Mar 22 17:11:35 check_reload_status 700 updating dyndns opt2
Mar 22 17:11:34 check_reload_status 700 Reloading filter
Mar 22 17:11:34 check_reload_status 700 updating dyndns lan
Mar 22 17:11:33 php-fpm 28703 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425893] unbound[24925:0] error: bind: address already in use [1616425893] unbound[24925:0] fatal error: could not open ports'
Mar 22 17:11:30 php-fpm 29377 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:11:30 php-fpm 69246 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:11:30 check_reload_status 700 Restarting ipsec tunnels
Mar 22 17:11:30 php-fpm 28703 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:11:30 check_reload_status 700 Restarting ipsec tunnels
Mar 22 17:11:30 php-fpm 74596 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:11:30 php-fpm 74596 /rc.linkup: HOTPLUG: Configuring interface opt3
Mar 22 17:11:30 php-fpm 74596 /rc.linkup: DEVD Ethernet attached event for opt3
Mar 22 17:11:30 php-fpm 28703 /rc.linkup: HOTPLUG: Configuring interface opt2
Mar 22 17:11:30 php-fpm 28703 /rc.linkup: DEVD Ethernet attached event for opt2
Mar 22 17:11:30 php-fpm 69246 /rc.linkup: HOTPLUG: Configuring interface opt1
Mar 22 17:11:30 php-fpm 69246 /rc.linkup: DEVD Ethernet attached event for opt1
Mar 22 17:11:30 php-fpm 29377 /rc.linkup: HOTPLUG: Configuring interface lan
Mar 22 17:11:30 php-fpm 29377 /rc.linkup: DEVD Ethernet attached event for lan
Mar 22 17:11:29 check_reload_status 700 Linkup starting em1.200
Mar 22 17:11:29 check_reload_status 700 Linkup starting em1.101
Mar 22 17:11:29 check_reload_status 700 Linkup starting em1.100
Mar 22 17:11:29 kernel em1.200: link state changed to UP
Mar 22 17:11:29 kernel em1.101: link state changed to UP
Mar 22 17:11:29 kernel em1.100: link state changed to UP
Mar 22 17:11:29 kernel em1: link state changed to UP
Mar 22 17:11:29 check_reload_status 700 Linkup starting em1
Mar 22 17:11:26 check_reload_status 700 Reloading filter
Mar 22 17:11:26 check_reload_status 700 Reloading filter
Mar 22 17:11:26 php-fpm 39491 /rc.linkup: DEVD Ethernet detached event for opt3
Mar 22 17:11:26 php-fpm 74596 /rc.linkup: DEVD Ethernet detached event for opt2
Mar 22 17:11:26 php-fpm 28703 /rc.linkup: DEVD Ethernet detached event for opt1
Mar 22 17:11:26 php-fpm 69246 /rc.linkup: DEVD Ethernet detached event for lan
Mar 22 17:11:25 check_reload_status 700 Linkup starting em1.200
Mar 22 17:11:25 check_reload_status 700 Linkup starting em1.101
Mar 22 17:11:25 check_reload_status 700 Linkup starting em1.100
Mar 22 17:11:25 check_reload_status 700 Linkup starting em1
Mar 22 17:11:25 kernel em1.200: link state changed to DOWN
Mar 22 17:11:25 kernel em1.101: link state changed to DOWN
Mar 22 17:11:25 kernel em1.100: link state changed to DOWN
Mar 22 17:11:25 kernel em1: link state changed to DOWN
Mar 22 17:11:25 php 85589 [pfBlockerNG] filterlog daemon started
Mar 22 17:11:25 tail_pfb 85065 [pfBlockerNG] Firewall Filter Service started
Mar 22 17:11:25 lighttpd_pfb 83328 [pfBlockerNG] DNSBL Webserver started
Mar 22 17:11:25 php_pfb 82575 [pfBlockerNG] filterlog daemon stopped
Mar 22 17:11:25 tail_pfb 82531 [pfBlockerNG] Firewall Filter Service stopped
Mar 22 17:11:25 lighttpd_pfb 81336 [pfBlockerNG] DNSBL Webserver stopped
Mar 22 17:11:24 php-fpm 670 /rc.start_packages: Skipping STARTing packages process because previous/another instance is already running
Mar 22 17:11:23 php-fpm 74596 /rc.start_packages: Skipping STARTing packages process because previous/another instance is already running
Mar 22 17:11:23 ladvd 25994 ladvd 1.1.2 running
Mar 22 17:11:23 check_reload_status 700 Starting packages
Mar 22 17:11:23 php-fpm 28703 /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 10.10.14.1 - Restarting packages.
Mar 22 17:11:23 php-fpm 28703 /rc.newwanip: rc.newwanip called with empty interface.
Mar 22 17:11:23 php-fpm 28703 /rc.newwanip: rc.newwanip: on (IP address: 10.10.14.1) (interface: []) (real interface: ovpns2).
Mar 22 17:11:23 php-fpm 28703 /rc.newwanip: rc.newwanip: Info: starting on ovpns2.
Mar 22 17:11:23 php-fpm 29377 /rc.start_packages: Restarting/Starting all packages.
Mar 22 17:11:22 check_reload_status 700 Starting packages
Mar 22 17:11:22 php-fpm 39491 /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 10.10.13.1 - Restarting packages.
Mar 22 17:11:22 check_reload_status 700 Reloading filter
Mar 22 17:11:22 php-fpm 39491 /rc.newwanip: rc.newwanip called with empty interface.
Mar 22 17:11:22 php-fpm 39491 /rc.newwanip: rc.newwanip: on (IP address: 10.10.13.1) (interface: []) (real interface: ovpns1).
Mar 22 17:11:22 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:22 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:22 php-fpm 39491 /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
Mar 22 17:11:22 check_reload_status 700 rc.newwanip starting ovpns2
Mar 22 17:11:22 check_reload_status 700 Starting packages
Mar 22 17:11:22 php-fpm 74596 /rc.newwanipv6: pfSense package system has detected an IP change or dynamic WAN reconnection - 2111:14xx:3183:2a2d::1 -> 2111:14xx:3183:2a33::1 - Restarting packages.
Mar 22 17:11:22 php-fpm 74596 /rc.newwanipv6: Creating rrd update script
Mar 22 17:11:22 kernel ovpns2: link state changed to UP
Mar 22 17:11:22 php-fpm 74596 OpenVPN PID written: 31365
Mar 22 17:11:22 kernel ovpns2: link state changed to DOWN
Mar 22 17:11:22 php-fpm 74596 OpenVPN terminate old pid: 33830
Mar 22 17:11:21 check_reload_status 700 rc.newwanip starting ovpns1
Mar 22 17:11:21 kernel ovpns1: link state changed to UP
Mar 22 17:11:21 check_reload_status 700 Reloading filter
Mar 22 17:11:21 php-fpm 74596 OpenVPN PID written: 88755
Mar 22 17:11:21 check_reload_status 700 Reloading filter
Mar 22 17:11:21 kernel ovpns1: link state changed to DOWN
Mar 22 17:11:21 php-fpm 74596 OpenVPN terminate old pid: 77669
Mar 22 17:11:21 php-fpm 74596 /rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
Mar 22 17:11:20 php-fpm 74596 /rc.newwanipv6: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Mar 22 17:11:17 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:16 php-fpm 670 /rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Mar 22 17:11:16 php-fpm 74596 /rc.newwanipv6: The command '/sbin/ifconfig em0 inet6 2111:14xx:3183:2a2d::1 delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
Mar 22 17:11:16 check_reload_status 700 Reloading filter
Mar 22 17:11:16 php-fpm 74596 /rc.newwanipv6: Gateway, NONE AVAILABLE
Mar 22 17:11:15 php-fpm 69246 /interfaces.php: Creating rrd update script
Mar 22 17:11:15 check_reload_status 700 Reloading filter
Mar 22 17:11:13 check_reload_status 700 updating dyndns wan
Mar 22 17:11:12 php-fpm 74596 /rc.newwanipv6: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425872] unbound[21998:0] error: bind: address already in use [1616425872] unbound[21998:0] fatal error: could not open ports'
Mar 22 17:11:11 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:11 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:09 check_reload_status 700 Reloading filter
Mar 22 17:11:09 php-fpm 28703 /rc.newwanip: rc.newwanip: on (IP address: 84.253.242.158) (interface: WAN[wan]) (real interface: em0).
Mar 22 17:11:09 php-fpm 28703 /rc.newwanip: rc.newwanip: Info: starting on em0.
Mar 22 17:11:08 check_reload_status 700 Restarting ipsec tunnels
Mar 22 17:11:08 php-fpm 69246 /interfaces.php: Gateway, NONE AVAILABLE
Mar 22 17:11:08 check_reload_status 700 rc.newwanip starting em0
Mar 22 17:11:07 php-fpm 69246 /interfaces.php: Shutting down Router Advertisment daemon cleanly
Mar 22 17:11:00 check_reload_status 700 Reloading filter
Mar 22 17:11:00 check_reload_status 700 updating dyndns opt1
Mar 22 17:11:00 check_reload_status 700 Syncing firewall
Mar 22 17:11:00 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:11:00 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:10:59 check_reload_status 700 Reloading filter
Mar 22 17:10:59 check_reload_status 700 updating dyndns opt2
Mar 22 17:10:59 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:10:59 kernel config_aqm Unable to configure flowset, flowset busy!
Mar 22 17:10:58 check_reload_status 700 Reloading filter
Mar 22 17:10:58 check_reload_status 700 updating dyndns lan
Mar 22 17:10:57 check_reload_status 700 Reloading filter
Mar 22 17:10:57 check_reload_status 700 updating dyndns opt3
Mar 22 17:10:56 php-fpm 74596 /rc.newwanipv6: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425856] unbound[43451:0] error: bind: address already in use [1616425856] unbound[43451:0] fatal error: could not open ports'
Mar 22 17:10:56 php-fpm 29377 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425856] unbound[21722:0] error: bind: address already in use [1616425856] unbound[21722:0] fatal error: could not open ports'
Mar 22 17:10:56 php-fpm 36283 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425856] unbound[19055:0] error: bind: address already in use [1616425856] unbound[19055:0] fatal error: could not open ports'
Mar 22 17:10:56 php-fpm 39491 /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1616425856] unbound[844:0] error: bind: address already in use [1616425856] unbound[844:0] fatal error: could not open ports'
Mar 22 17:10:54 php-fpm 74596 /rc.newwanipv6: rc.newwanipv6: on (IP address: 2111:14xx:3183:2a33::1) (interface: wan) (real interface: em0).
Mar 22 17:10:54 php-fpm 74596 /rc.newwanipv6: rc.newwanipv6: Info: starting on em0.
Mar 22 17:10:53 php-fpm 36283 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:10:53 php-fpm 670 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:10:53 check_reload_status 700 Restarting ipsec tunnels
Mar 22 17:10:53 php-fpm 39491 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:10:53 check_reload_status 700 Restarting ipsec tunnels
Mar 22 17:10:53 php-fpm 29377 /rc.linkup: Gateway, NONE AVAILABLE
Mar 22 17:10:53 php-fpm 28703 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan].
Mar 22 17:10:53 php-fpm 28703 /rc.newwanipv6: rc.newwanipv6: Info: starting on em0.
Mar 22 17:10:53 php-fpm 28703 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan].
Mar 22 17:10:53 php-fpm 28703 /rc.newwanipv6: rc.newwanipv6: Info: starting on em0.
Mar 22 17:10:53 php-fpm 670 /rc.linkup: HOTPLUG: Configuring interface opt3
Mar 22 17:10:53 php-fpm 670 /rc.linkup: DEVD Ethernet attached event for opt3
Mar 22 17:10:53 php-fpm 36283 /rc.linkup: HOTPLUG: Configuring interface opt2
Mar 22 17:10:53 php-fpm 36283 /rc.linkup: DEVD Ethernet attached event for opt2
Mar 22 17:10:53 php-fpm 29377 /rc.linkup: HOTPLUG: Configuring interface opt1
Mar 22 17:10:53 php-fpm 29377 /rc.linkup: DEVD Ethernet attached event for opt1
Mar 22 17:10:53 php-fpm 39491 /rc.linkup: HOTPLUG: Configuring interface lan
Mar 22 17:10:53 php-fpm 39491 /rc.linkup: DEVD Ethernet attached event for lan
Mar 22 17:10:52 check_reload_status 700 Linkup starting em1.200
Mar 22 17:10:52 check_reload_status 700 Linkup starting em1.101
Mar 22 17:10:52 check_reload_status 700 Linkup starting em1.100
Mar 22 17:10:52 kernel em1.200: link state changed to UP
Mar 22 17:10:52 kernel em1.101: link state changed to UP
Mar 22 17:10:52 kernel em1.100: link state changed to UP
Mar 22 17:10:52 kernel em1: link state changed to UP
Mar 22 17:10:52 check_reload_status 700 Linkup starting em1

[Tzvia]

@fragged I don't know if you've tested the IPV6 gateway with gateway monitoring OFF or set with a monitoring address (such as google.com or their IPV6 DNS for example)- it's a known issue with 2.5 and at least some ISPs. So a quick test of that would be just go into SYSTEM/ROUTING and turn IPV6 gateway monitoring OFF to see what happens. You can then try supplying a monitoring IP and turning it on if it works.
I was lucky in that IPV6 didn't work if monitoring was ON with my previous ISP so I already had it off. I didn't bother to turn it on when I switched ISPs, so didn't have that problem when I upgraded to 2.5. I have since enabled it with google's IPV6 as the monitoring IP. So it's worth a try if you haven't tried that yet.

[tomahhunt]

I felt for sure this was the problem I was having.
But I have struggled in a seemingly identical way.

I am on 2.5.0 (also now running the 2.5.1-RC but seems the same)
I tried disabling the gateway monitor as noted above.

I have PPPoE WAN which requests a 48 prefix from my ISP. (Giganet in the UK)
Tried other prefix sizes and various option on the WAN side i.e. prefix hints only request prefix etc.

My Wan has a proper IPv4 and IPv6 IP.
I can always ping ipv6.google.com from the router ping page.

However My LAN which is set to track interface WAN never gets an IPv6 IP assigned to it.

Consequently I can never get any ipv6 assignements to my LAN.

Any debug hints?

Cheers,

Tom