I have a router running on time warner cable that does exactly the same thing.  Very annoying.

I keep forgetting to switch that one to HE.  Maybe tomorrow…

I wonder why any government would want to control what types of routers its citizens can use?

Only one thing comes to mind…

The one-size fits all solution of forcing a particular (usually crappy) router to be used is bad for many many people.

Its all there under the hood to make it happen I believe. The Web GUI needs to be updated/modify to allow the different IPv6 configurations to be generated.

I guess I'm confused by the "Only request a IPv6 prefix, don't request a IPv6 address" checkbox.

That setting is only available if DHCPv6 is selected as an interface type and there's no alternate way to set an IPv6 interface address.

You might do better asking this in the 2.2 snapshots forum under the Development category… or maybe a mod can move it there.

Solved:

System > Routing > Gateways > WAN_SLAAC >
Check  Disable Gateway Monitoring

Ipv6 all suddenly starts responding properly.

hi

Then get yourself a free tunnelbroker account at HE.net or equivalent and start using it!

I'm not experiencing this with TWC cable modems but I've heard of another user having a similar issue in another TWC market. The dhcp6c client has many options which I wish was changeable via the gui but you can change manually..

maybe these threads can help?

https://forum.pfsense.org/index.php?topic=76322.msg426945#msg426945
https://forum.pfsense.org/index.php?topic=73760.0

dhcp6c.conf man
https://www.freebsd.org/cgi/man.cgi?query=dhcp6c.conf&apropos=0&sektion=0&manpath=FreeBSD+Ports+8.4-RELEASE&arch=default&format=html

I posted an issue in regards to it a while back. Haven't heard anything yet

https://forum.pfsense.org/index.php?topic=77506.0

@hda:

Just use the /56 for configuring your IPv6 connection to world.

You can't just use an address from the delegated /56 for your WAN interface; the routing on the ISP side will be set up to route any traffic to the delegated /56 via an address in the (separate) prefix range assigned to the WAN.

Bumping this instead of starting a new thread.
This bug: https://redmine.pfsense.org/issues/1831

Now it says "Future" instead of 2.2. No news on this matter? Got CP working and then noticed DHCPv6 stopped working, somewhat frustrating. :)
Anyone got ideas for a workaround?

so since i probably can not make ipv6 for the client network work with my current setup i want to get ridd of the ISPs router (speedport w724v) completely and let pfsense handle everything solely (as it was before we switched to voip).

what i need is some sort of DECT base station that does VOIP or can "forward" VOIP to a asterisk (i'm not exactly sure how this would look like, voip is new to me)
are there all-in-one boxes that can do this and don't require to be the main router to the internet?  (so i just have to open the ports for it in the firewall/NAT)
i could also set up an VM with asterisk, but i somehow need the hardware to connect the phones via DECT and if the hardware has to be plugged in the server it has to work when on pci-passthrough on vmware esxi

i understand you.
its just for educational purposes and its easy since it dont require software on the clients.

Just to keep you updated… It works, today morning IPv6 was up and running, but there is one thing strange: The "Dynamic DNS" panel shows the wrong (old) IP in red. But I just saw, that there were some fixes for the upcoming 2.2, so I am relaxed.