pfSense

Either this issue or something similar happens when you change anything on the WAN interface settings page and hit apply.

Seeing the same issue with recent snapshots (second week of April) on my Comcast home connection.

Have installed ..

2.1-BETA1 (amd64)
built on Thu May 9 07:06:51 EDT 2013

... will need 4 days uptime to validate the fix (the dhcp-pd lease time).

Connectivity now persists through the DHCPv6 renewal process, radvd stays up.

Sadly, the connection is still not usable: Every time a refresh occurs (which is approximately every 15 minutes for me, the ISP is Deutsche Telekom) the state table seems to be dropped, regardless of whether or not the prefix has actually changed. This causes all TCP connections on the clients (including IPv4, which should not be affected) to time out.

Not a good fix. Behavior is the same. At the expiration of the 4 day lease, the LAN and WAN IPv6 addressing does not renew and is removed. This is on Comcast.

Similar results here, also on Comcast: The LAN interface eventually loses its IPV6 address, and radvd disappears from the list under services->status.

I have been testing with m0n0wall (1.8.1b540) and it does not have this problem. Perhaps the teams can collaborate to determine what is being done differently and that could be used for a fix to pfSense.

Can you test again with latest snapshots and see if this is fixed?

This seems to have been working fine for me on Comcast Home for the past few snapshots that I've tried. After > 8 days uptime and at least one renew, IPv6 connectivity continued to work on both the WAN and the LAN side.

Just updated to June 24 release (details below) and IPv6 connectivity -still - does not work. Am on Comcast service and can get IPv6 address if connect computer (mac) directly to cable modem (ZOOM 5341J) - http://www.zoomtel.com/products/5341J.html

2.1-RC0 (i386)
built on Mon Jun 24 02:46:42 EDT 2013
FreeBSD 8.3-RELEASE-p8

Robert Guerra wrote:

Just updated to June 24 release (details below) and IPv6 connectivity -still - does not work. Am on Comcast service and can get IPv6 address if connect computer (mac) directly to cable modem (ZOOM 5341J) - http://www.zoomtel.com/products/5341J.html

That seems unrelated to this particular issue (--> renew), though?!

For the very first time, I have been able to go over 4 days without loosing IPv6 addressing. This is very positive, but I would need to run longer before calling it fixed. Currently on ...

2.1-RC0 (amd64)
built on Mon Jun 24 04:05:41 EDT 2013

Glad to report that the firmware update I just installed (details below) seems to work.

Will continue to monitor the status to make sure IPv6 address is not lost after 4 days.

2.1-RC0 (i386) 
built on Thu Jul 4 03:04:00 EDT 2013 
FreeBSD 8.3-RELEASE-p8

IPv6 connectivity appears to survive the 4-day mark (renew) for me at this point. However, I am seeing an issue where temporary loss of upstream connectivity by the cable modem results dhcp6c quitting and never getting restarted, so pfSense loses IPv6 until the next reboot.

More details in this forum post .

At this point, I am no longer seeing any problems.

1) DHCP-PD IPv6 addressing has survived multiple renewals.

2) The IPv6 address survives loss of cable modem connectivity (I have restarted the CM multiple times)

Thanks!

The IPv6 address may survive the loss of connectivity to the cable modem (i.e., from pfSense's point of view, link goes down and back up). However, what myself and others are still seeing is that it does not survive loss of upstream connectivity (i.e., cable modem stays up, but cannot talk to ISP).

A forum thread with more details is here .

Should this issue be re-opened, or should we file a separate ticket for this?