i use the regular pfsense 1 year + but only using ipv4 without issue. only recently when added ipv6 then i started having this freeze issue at least once a month or 2-3 month roughly, when before i never had this issue
o like this? well hopefully customer support will be enuff. i rather not call the technician over. is it true there is such warranty if u use ur own networking gear like router? technician claim should i decide to use my own router like the pfsense, if it resulted in tmnut account getting stuck/frozen again, then he claims warranty expire. But how does that work? it's not like i am flashing third party firmware onto the default tmnut router which i am not using. i keep the default router so i can use that to relogin because it should work, because by their logic, at that point i am using their own gear/setup so it should connect to the internet, so then they can't blame pfsense for why i cannot connect .

But he claims that for whatever reason, pfsense is causing the account login to get stuck (this part we can at least agree), there is no opinion why or any effort to troubleshoot this apparently (although i saw to fix this issue, he had to reset the tmnut password for isp    ) This part we disagree, because since the issue seems to be on their end why my isp relogin seems to get stuck for whatever reason, they can't just simply deny to solve this issue (i assume password reset or whatever it is like they did for u but didn't what exactly?) under the basis u decide to connect using pfsense that gets it stuck yet again, can they? 

i alrdy switch config to an old working one which only connects to ipv4 (but no ipv6), so hope i won't get this issue again, but i can't be completely certain until i've tested this for a while 
mine got lost ages ago. had to pay to get issued a new one 

that void warranty thing sounds like BS, probably dont want you to simply mess around and call them over for something so "simple".

technician saw my network rack, but don't know what a nas is.... (probly didn't even know what a server rack switch is either from the looks of it as well)    that's why hard to take seriously. i'm not a full fledged expert but even i know enuff    i also thought it was bs....

so if they refuse fix internet, can i refuse pay my bill? 

to uncomplicate during troubleshoot, i even just connect the modem to standard unifi router (this is very easy to do so wasn't a bother, just removed 2 ethernet cables and rewire accordingly), and hook direct to desktop pc, so can illustrate the networking in network rack has no relevance at that point, if the internet isn't functional.

the part i agreed with somewhat, was that perhaps something with the pfsense config was probly causing some issue during reconnect which made the unifi account frozen/stuck which results in unsuccessful login, even if u switch back to default tmnut router to do so.

but i never heard before u can void warranty using ur own gear?    (i never even said i was going to reflash their tmnut router. maybe he got confused?)

also tried to get me to rewire all the cabling to use default tmnut router fulltime right then and there, but i declined citing i will do later, but i later put back own my pfsense router after first using a working config i had no issue with for many years    internet confirmed working again no issue for now 

though i still haven't figured out why the isp relog is stuck/frozen 
but like u mentioned, seemed like they can fix on their end without sending anyone over. how come they don't train their technician to diagnose and troubleshoot this issue? save everyone time 

...

Better do not enable IPv6 on unifi before 2024/2025...
Routing not optimized for 50-60% connection.

did u check out this thread?

https://forum.lowyat.net/topic/2978208/+1340
seems there rely might be something up with tmnuts ipv6 implementation 
anyway right now i'm using old pfsense config when i only had ipv4 only setup. so far haven't had any internet issue. but it's only been a month... so that hardly says much. i'll report back next year or if i have an issue occur for it before then.
https://forum.lowyat.net/index.php?showtopic=5285577&
but at some point not many years from now, we probly need this ipv6 sorted out    but for now using just only ipv4 seems to be ok.

i run speedtest i still max out on my subscribed speed. latency is roughly same so basically not rely much diff when using ipv6 afaik. also since i use vpns, it's even more of a reason not to use it.

There's 2 ways to solve this:

1* reduce IPv6 DHCP leasetime to say 3 mins or lower in your router(troublesome)

2* TM assign static-prefix(best option)

i have not seen it. but maybe this is the culprit?
my machine got fried so I am havent been using OPN for a while 
did you see if recent PF updates made any changes in the ipv6 department?

DHCP (IPv6)
Fixed: DHCPv6 Server should not offer configuration options for unsupported PPPoE Server interfaces #12277

Dynamic DNS

Fixed: RFC 2136 Dynamic DNS client uses IPv6 alias VIP instead of Track IPv6 address for AAAA records #11816

Gateways

Fixed: Default IPv4 gateway may be set to IPv6 gateway value in certain cases #12282

IPv6 Router Advertisements (RADVD)
Fixed: radvd only responds to the first Router Solicitation received after each multicast Router Advertisement #10304

Fixed: “Default preferred lifetime” router advertisement validation check uses incorrect variable #12159

Fixed: IPv6 RA DNSSL lifetime is too short, not compliant with RFC 8106 #12173

Fixed: Default IPv6 router advertisement intervals and lifetime are too low #12280

Fixed: “Default preferred lifetime” field for IPv6 RA does not have input validation #12439

Fixed: IPv6 interface prefix change not reflected in RADVD configuration #12604

Fixed: Router Advertisement DNS search domain from one interface may unintentionally be used by other interfaces #12626

for pf news, there is this

https://www.youtube.com/watch?v=cDgF6UoyThQ
pfsense is adding features to their subscription pf plus release, while keeping the open source pfsense community version at a slower update track.

makes me wonder about if i should start moving to opnsense yet or not? but i'm not too familiar with it. is it better than pfsense? 

also recently pfsense added a tailscale package for pfsense which is nice. also it already has useful packages like pfblocker, and even suricata which i'm not sure opnsense has or not.

for ipv6 news in pfsense i'm not sure  but this is the changelog
https://docs.netgate.com/pfsense/en/latest/...ases/index.html

hi there.

still learning and trying to understand ipv6 in opnsense
what prefix delegation size to use by the way?

64. be wary though, i suspect it’s TM screwing up some ipv6 settings. if after reconnection/reboot you get no internet. you need to call TM to get it solved.

just to confirm, setting strictly to ipv4 only, and omitting the ipv6 settings, the connection remains stable and i don't experience any lock out/issue when reconnecting back to tmnut.

long term no good, since will need to figure out how to get ipv6 working in pfsense to work with tmnut without this issue 
so what is your situation like? did you figure out the working ipv6 settings for your opnsense? or do you still have this frozen internet and having to call up tmnut each time to unstuck it? 
or does anyone else who uses pfsense have a working setting for this?  :confused:

i didn’t bother anymore and stick to using ipv4.
or you can connect ipv6 and hope you have 100% uptime never drop connections then it will work

too risky. too troublesome if a problem occur 

at one point, i thought maybe it's due to me using vlan in my pfsense config (for guest wifi and iot). but based on your result doesn't seem to be that  so i could only narrow this down to something related to the ipv6 configuration on pfsense side, or something on isp side that doesn't play nicely with pfsense?

o well.. i'll visit back this thread in 1-2 years and hope someone has a solution by then    using ipv4 only reliably for now on latest community edition pfsense    i max out on the subscriber dl/ul speed, and latency is low for gaming, so not really much else to complain unless maybe if torrent peer strictly use ipv6 then doesn't that mean i cannot download from those users? other than that i don't think there is a big issue, until a few more years from now if they force everyone to use ipv6 eventually

too risky. too troublesome if a problem occur 

at one point, i thought maybe it's due to me using vlan in my pfsense config (for guest wifi and iot). but based on your result doesn't seem to be that  so i could only narrow this down to something related to the ipv6 configuration on pfsense side, or something on isp side that doesn't play nicely with pfsense?

o well.. i'll visit back this thread in 1-2 years and hope someone has a solution by then    using ipv4 only reliably for now on latest community edition pfsense    i max out on the subscriber dl/ul speed, and latency is low for gaming, so not really much else to complain unless maybe if torrent peer strictly use ipv6 then doesn't that mean i cannot download from those users? other than that i don't think there is a big issue, until a few more years from now if they force everyone to use ipv6 eventually

wonder if it’s feasible to call them and send a technician over every time it happens.
if > 24h downtime, claim rm50 rebate.
perhaps if done often enough with enough volume they’ll do something about it

for your pfsense there's this.
https://docs.netgate.com/pfsense/en/latest/...igure-ipv6.html



how's yours configured with regards to this option?

After much try and error and research, I've managed to get pfSense to work with UniFi's IPv6 allocation. For a bit of a background, I'm running the latest release of pfSense i.e. 2.2.1 and also I got this to work with my office's UniFi which is on Biz 10.

I'd just like to share my settings here to benefit those who might want to get IPv6 to work for their pfSense box.

1. Under "System -> Advanced -> Networking", make sure "Allow IPv6" is checked. Then go to "Interfaces", click on "WAN". Under IPv6 Configuration Type, choose "DHCP6". MTU should be 1492.

2. Under DHCP6 client configuration section, put a tick mark on "Request a IPv6 prefix/information through the IPv4 connectivity link". In the drop down list for DHCPv6 Prefix Delegation size, choose "56". (I have no idea why this is the case, but the allocated subnet for both the PPPoE and LAN are actually 64. I've tried choosing 64 here, but it doesn't work. Maybe 56 is for a Biz account. If 56 doesn't work for you, try choosing 64 especially if you're on home UniFi account.)

Also, put a tick mark for "Send an IPv6 prefix hint to indicate the desired prefix size for delegation". Click on "Save".

3. Now, go to "Interfaces", click on "LAN". Under IPv6 Configuration Type, choose "Track Interface". Type 1492 for MTU.

4. Under Track IPv6 Interface section, ensure IPv6 Interface "WAN" is selected and as for IPv6 Prefix ID, just type 0 (zero) here.

5. Under Private networks section, ensure "Block Bogons networks" is unchecked. Then, click "Save".

6. Finally, I've read that IPv6 requires ICMP to work. So under Firewall -> Rules, I've also created a rule to allow ICMP IPv6 traffic for both WAN and LAN.

I'm not entirely certain what the security implications are with the above settings to the firewall, so please be forewarned.

With the above settings, I'm able to get IPv6 addresses for PPPoE and LAN interfaces for pfSense and also devices connected to the LAN. Hope this helps those who are using pfSense.

[attachmentid=4391721]
[attachmentid=4391722]

Dear TM IPv6 Implementor,

IMHO, i've successfully run TM_IPv6 on pfSense and managed to get it working SLAAC mode and DHCPv6 mode (one mode at a time - not both). (Streamyx ADSL 8Mbps here - PPPoE)

After relentless hour of searching, calling here and there (esp TM guys) and the results is very good. I'm able to replicate the case if needed but to pfSense users/IPv6 Implementor please do read on.

Findings:

1. Only works in pfSense 2.2 . Currently i'm on BETA specifically pfSense-LiveCD-2.2-BETA-i386-20141017-1129

2. Set your WAN to DHCPv6 , Tick Request IPv6 via IPv4 connectivity, Tick Request Prefix no IP Address , Select 64 as for the size and last Tick the box third .Of course you'll need to setup your PPPoE Username and Password.

3. Go to LAN and as usual set your IPv4 LAN IP and for IPv6, Pick DHCPv6 here. Tick the first and the third box only and set 64 too.

4. You may want to adjust your DNS Server at System -> General Setup accordingly.

As soon as all the configuration in place and you have your internet connectivity, please head on to Status -> Interfaces . Your pfSense LAN interface should pickup the PD (Prefix Delegation IP) and you can set your PC/Netbook/Notebook "statically" using the information. Below are the example:

PD Info
pfSense IPV6 "LAN" IP -  2001:4411:7a4::1:1
YOUR PC IPv6 "LAN" IP - 2001:4411:7a4::1:fdc0:c0d3
Subnet - 64
Gateway -  2001:4411:7a4::1:1

EDITED: The IPv6 Address will change once you reboot your pfSense and you'll have to manually assign the address again. So do watch out.

Another caveat to look for, as far as i'm testing, i do suffer MTU problem (certain website lag and unable to accesss) and i haven't lowered yet the MTU. You should try to lower your MTU at 1432 as per suggested on previous post and test it out. YMMV

As always, pfSense 2.2 is still in BETA mode and i can't wait for RELEASE version of 2.2
If anyone wishes to look at my config and screenshot, please state it here and i'll try my best to upload somewhere.

P/S: the "LAN" IPv6 is actually Globally Routed IP - WAN IPv6 so to speak . I'm trying to differentiate the terms so that hopefully you might grasp the idea. Please do pardon me for any confusion.



credit: Thanks to asellus for answering some of my question earlier on.

Regards

This much I know for Home Unifi broadband, TM IPv6 assign /64 dynamic-prefix so when you reconnect or reboot router, you get new prefix but your devices still using old prefix address and when you try to access say youtube or any IPv6 sites the page just loading..

There's 2 ways to solve this:

1* reduce IPv6 DHCP leasetime to say 3 mins or lower in your router(troublesome)

2* TM assign static-prefix(best option)

If many customers bomb TM requesting to change from dynamic-prefix to static-prefix then maybe have hope :>

for me slaac workout of the box using dlink router
my suggestion is get ipv6 try using automatic or slaac
Prefix delegation: enabled
DNS address try using cloudflare or google

IPV6 lan delegated using SLAAC+ Stateless DHCP

Switch to Auto prefix delegation

Then use SLAAC+stateless for best compatibility


The reason why I suggest use SLAAC+stateless is because Android devices (incl chromebook) not compatible with DHCPv6

When possible, do not use Auto default settings because may cause possible compatibility problems

i pretty much just copied as much as i could from your own setting
https://forum.lowyat.net/topic/5204701

yes but i brought that up because i don’t find that option in OPNsense to drop prefix.
by default can you check if yours is enabled or disabled?

yes but i brought that up because i don’t find that option in OPNsense to drop prefix.
by default can you check if yours is enabled or disabled?