pfSense

Tom, can you please test a new snapshot and confirm this fix? I can't replicate.

I'm still seeing this issue on the Apr 16 snapshot.

Actually, I think what I'm seeing may be a separate issue: In my case, radvd fails to start after a reboot (or possibly just after a firmware update? the two tend to coincide for me...); it does still show up under status -> services, so it's really only a minor annoyance.

I am also running into the issue still on the latest April 16th snapshot. Radvd is running when the firewall starts up, but on a DHCP6 renew from the cable provider, radvd does not restart. It also does not show up under services until after a restart.

The end result of this is that ipv6 wan connectivity lasts for about 2-4 days maximum.

Tom

This has been working for me with the past several snapshots I've tested.

I'm still seeing an issue with RADVD not restarting automatically after a dhcp renew from my internet provider (Comcast). I was using 2.1-BETA1 for the past month. I've updated to the build from Mon Jun 24 02:46:42 EDT 2013 today. However, now I am not even seeing RADVD in the list of services.

Just updated to the same snapshot, and radvd seems to have come up just fine for me. This is also on Comcast, so I wonder what's different about our setups... Different type of CMTS, maybe?

I've been updating a snapshot copy since December 2012 without a full rebuild. I'm wonder if I start with a fresh beta install if this would fix the issue.

I am still seeing this issue. I have turned off Track Interface for DHCP on my LAN Interface and ipv6 is now only turned on on the LAN. It does not appear that I am even reliably getting an IPV6 address on the WAN interface now. Apinger log is showing the following:

Jul 2 14:57:54 apinger: Starting Alarm Pinger, apinger(41577)
Jul 2 14:57:54 apinger: bind socket: Can't assign requested address

I am using this build:
2.1-RC0 (i386)
built on Tue Jul 2 05:48:25 EDT 2013

Tom M wrote:

I am still seeing this issue. I have turned off Track Interface for DHCP on my LAN Interface and ipv6 is now only turned on on the LAN. It does not appear that I am even reliably getting an IPV6 address on the WAN interface now. Apinger log is showing the following:

Jul 2 14:57:54 apinger: Starting Alarm Pinger, apinger(41577)
Jul 2 14:57:54 apinger: bind socket: Can't assign requested address

I am using this build:
2.1-RC0 (i386)
built on Tue Jul 2 05:48:25 EDT 2013

The logs for WAN show..
Jun 29 03:34:48 fw php: : DEVD Ethernet attached event for wan
Jun 29 03:34:48 fw php: : HOTPLUG: Configuring interface wan
Jun 29 03:34:48 fw php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf fxp1 > /tmp/fxp1_output 2> /tmp/fxp1_error_output' returned exit code '1', the output was ''
Jun 29 03:34:48 fw php: : Accept router advertisements on interface fxp1
Jun 29 03:34:49 fw php: : DEVD Ethernet detached event for wan
.....
Jul 3 08:22:46 dhcp6c³⁵³⁹⁸: dhcp6_ctl_authinit: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Jul 3 08:22:46 dhcp6c³⁵³⁹⁸: client6_init: failed initialize control message authentication
Jul 3 08:22:46 dhcp6c³⁵³⁹⁸: client6_init: skip opening control port
Jul 3 08:22:46 dhcp6c³⁵³⁹⁸: add_options: /var/etc/dhcp6c_wan.conf:3 IA_NA (0) is not defined
Jul 3 08:22:46 dhcp6c³⁵³⁹⁸: main: failed to parse configuration file

[2.1-RC0][admin@fw.subnothing.com]/var/etc(18): cat dhcp6c_wan.conf
interface fxp1 {
send ia-na 0; # request stateful address
send ia-na 0; # request stateful address
send ia-pd 0; # request prefix delegation
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_wan_script.sh"; # we'd like some nameservers please
};
id-assoc na 0 { };
id-assoc pd 0 {
};

Please test with latest gitsync or tomorrow snapshots.
There were some fixes doen related to this as well.