Anyone get IPv6 working after the fix?  Mine still not working.  IPv6pipe asked me to try another router.  I will do that tomorrow.

Just want to know anyone still having problems?

AKLWestie:

 

Anyone get IPv6 working after the fix?  Mine still not working.  IPv6pipe asked me to try another router.  I will do that tomorrow.

 

Just want to know anyone still having problems?

 

All working here but I haven't had to restart my router since the fix - and it's heavily used at the moment.  If you don't hear from anyone else I'll give it a reboot later tonight and let you know how it goes.

caminham:

 

AKLWestie:

 

Anyone get IPv6 working after the fix?  Mine still not working.  IPv6pipe asked me to try another router.  I will do that tomorrow.

 

Just want to know anyone still having problems?

 

 

All working here but I haven't had to restart my router since the fix - and it's heavily used at the moment.  If you don't hear from anyone else I'll give it a reboot later tonight and let you know how it goes.

 

That will be great.  For me, IPv6 worked fine when I was on VDSL.  It stopped working once I moved to UFB.  =-(  Even with the same router.

AKLWestie:

caminham:

AKLWestie:

Anyone get IPv6 working after the fix?  Mine still not working.  IPv6pipe asked me to try another router.  I will do that tomorrow.

Just want to know anyone still having problems?

All working here but I haven't had to restart my router since the fix - and it's heavily used at the moment.  If you don't hear from anyone else I'll give it a reboot later tonight and let you know how it goes.

That will be great.  For me, IPv6 worked fine when I was on VDSL.  It stopped working once I moved to UFB.  =-(  Even with the same router.

Works for me now.

Great to hear it's going for you @pesticles :)

For AKLWestie's line I can confirm v6 is enabled on our end. I'm currently following it up, as it's not clear where the source of the trouble lies at the moment.

On a related note @IPv6pipe, could you guys improve your comms when you're rebooting routers and whatnot?

Every time my net connection goes down I get paged, and again when it comes back up, so the other night when it went down at 3:30am, up at 3:45, down at 4:15 and up again at 4:30, I had a very bad nights sleep.

I get that this is not a commercial grade connection, but a little email in advance so I can configure a maintenance window in my Zabbix would be super awesome and appreciated.

Thanks.

I'll ensure your feedback is passed along.

A big thanks to @IPv6pipe to have my IPv6 connection fixed.

My connection has been moved from PPPoE to IPoE/DHCP this morning.  IPv6 starts working after the move.

Thanks a lot @IPv6pipe!

New release from PFsense 2.3.4 p1

Release notes include

• Fixed DHCPv6 to request a prefix delegation even if no interfaces are set to track6 #4544

might be worth a test by someone to see if now resolved

mentalinc:

 

New release from PFsense 2.3.4 p1

 

Release notes include

 

• Fixed DHCPv6 to request a prefix delegation even if no interfaces are set to track6 #4544

might be worth a test by someone to see if now resolved

 

Upgraded this morning.

I did succeed in getting an IPv6 address assigned to the LAN once, as I managed to do with earlier builds, but once again it does not persist after a reboot.

SirHumphreyAppleby:

 

mentalinc:

 

New release from PFsense 2.3.4 p1

 

Release notes include

 

• Fixed DHCPv6 to request a prefix delegation even if no interfaces are set to track6 #4544

might be worth a test by someone to see if now resolved

 

 

Upgraded this morning.

 

I did succeed in getting an IPv6 address assigned to the LAN once, as I managed to do with earlier builds, but once again it does not persist after a reboot.

 

I don't have pfsense, but I notice I have a better chance to get my router to work with IPv6 if I manually set the IPv6 DNS server to 2403:9800:c041:1000::a and 2403:9800:c041:1000::b

AKLWestie:

 

A big thanks to @IPv6pipe to have my IPv6 connection fixed.

 

Glad to hear it's all go now. :)

Success! pfSense is now working with Bigpipe!

I am able to connect to IPv6 on Bigpipe and to have that connection persist after reboots.

I am using using latest development branch for pfSense and IPoE.

The critical setting appear to be Do not wait for a RA. This didn't resolve the issue with earlier versions of pfSense, but it's possible the relevant change has been merged in the 2.3 branch, and may also work with PPPoE. IPv6 is very much a moving target on pfSense and OPNsense, so I still have no idea which of the many issues that presented with similar symptoms has been resolved. 2.4 does contain additional IPv6 fixes that have not been merged in to the latest 2.3 releases, and reports suggest it's quite stable.

My settings are as follows:

WAN

IPv6 Configuration Type: DHCP6 (note, this requires Bigpipe to enable IPoE on your connection)

Use IPv4 connectivity as parent interface

Request only an IPv6 prefix

DHCPv6 Prefix Delegation size: 60

Do not wait for a RA

LAN

IPv6 Configuration Type: Track Interface

IPv6 Interface: WAN

No additional firewall rules are required, Block private networks and loopback addresses and Block bogon networks do not need to be deselected on the WAN interface as some pfSense forum posts suggest. Both settings should be off on the LAN interface.