Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

Unifi TMnet Streamyx/Unifi & IPv6, Now live!

views
     
Moogle Stiltzkin
post Nov 3 2022, 03:40 AM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
QUOTE(papyrous @ Nov 1 2022, 08:22 AM)
....
QUOTE(ansonlos @ Mar 30 2015, 11:48 AM)
....
just an update.

so i had some time so i tested ansonlos pfsense ipv6 settings, but it didn't quite work.

for verification i used

https://ipv6test.google.com/

https://test-ipv6.com/

https://ipv6-test.com/


and just in case i also did the following

- flush dns for windows and browser
https://www.freecodecamp.org/news/flushdns-...ns-command/#:~:

- disable/re-enable ethernet port on desktop pc

- reboot pc

- reboot pfsense router after applying all the settings



few things i noticed that varied from ansonlos setup guide

- have to add the ipv6 dns. for example, i use cloudflare so i had to add the ipv6 dns entries as well
https://1.1.1.1/dns/





- this part is what i am stuck at. yes in the guide it shows what to set for the lan interface. but what about for vlans? for example my pfsense has a few vlans setup e.g. for guest wifi, iots and etc. but it won't allow me to set track interface wan, because the lan interface is already using that. so what do you do for vlans you setup? all i could find was this on reddit. any help with this would be appreciated.



QUOTE
QUOTE
IPv6 splitting up a prefix on multiple VLANs
After having learned a ton here I am trying to break things further in interesting ways.

My provider gives me an IPv6 for the router and a 56 prefix. A while ago I've configured my LAN interface to track that and give out addresses to clients. That seems to work ok, I can reach IPv6 hosts and some of my traffic is IPv6.

Now I've figured I would extend that to my new VLANs, however I find it not to work. It was my expectation that I would track the WAN interface on each respective LAN interface and allocate a different prefix. That way I expected the LAN's to get separate-from-each-other IP addresses on the pfsense interfaces and network ranges for the other devices.

Doesn't work. The original LAN keeps that setup, any additional ones do not get any IPv6 address on the router.

What am I doing wrong? Is this not actually the correct approach?



jim-p-

If you get the allocation from DHCPv6 with prefix delegation, then setting the other local interfaces to track the WAN is correct, but you need to make sure each interface has a separate prefix ID set. If your ISP delegates you a /56 then you should be able to use prefix IDs 0-FF, just increase each new interface by 1. So LAN is prefix ID 0, the first vlan is 1, second VLAN is 2 and so on.

If it won't let you enter that, then double check your WAN DHCPv6 settings and make sure you have the correct DHCPv6 Prefix Delegation Size selected.


https://www.reddit.com/r/PFSENSE/comments/9...multiple_vlans/



in summary,

i notice in pfsense the ipv6 works. dnsipv6 seems to work too. but the reason why on client devices like desktop pc, mobile etc is not working, probably has something to do with the vlan interfaces not having the ipv6 enabled just yet. reason being the one i mentioned above. seeing as track interface wan won't allow it to be selected, then the other options are static ipv6, slaac, dhcpv6 ..... i am unsure what to put hmm.gif

This post has been edited by Moogle Stiltzkin: Nov 3 2022, 03:46 AM
Moogle Stiltzkin
post Nov 3 2022, 05:02 AM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
for troubleshoot,

in pfsense > ping

pinging to ipv6.google.com works fine.

in WAN in pfsense, the ipv6 is clearly shown both when testing dhcpv6 and slaac.


problem is for clients e.g. desktop etc, none of these are getting ipv6 to work. so there is something not configured correctly which is making this not work :/

https://test-ipv6.com/

https://ipv6test.google.com/

https://ipv6-test.com/



i double checked my dns setting which i followed lawrence, but i don't see any issue (i made sure to add the ipv6 dns of course)
https://www.youtube.com/watch?v=5mygS-TiT9c


anyway, anyone have any idea why not working sad.gif




found more useful info to help navigate this sweat.gif

IPv6 Basics on pfSense
https://www.youtube.com/watch?v=u4aZJpZJFeI






all i can think of right now is that my issue perhaps lies somewhere in client ipv6 delegation. probably either dhcpv6 server, or RA daemon.

QUOTE
Re: pfSense router - IPv6 client side problems
« Reply #7 on: December 12, 2013, 02:55:26 PM »
Quote from: lonevipr on December 12, 2013, 06:44:45 AM
QUOTE
All the guides say to enable DHCPv6 & set a valid IP range.

Clients can use either RA, DHCPv6, or a combination of the two. I think using just RA is the most common behaviour on the clients, which is why I was suggesting to focus on the router advertisement daemon, and not enable DHCPv6.

The error message you mentioned did suggest DHCPv6 was misconfigured. The error message might be harmless, I don't know for sure.

If you do enable both DHCPv6 and router advertisement on a segment, and both are properly configured, then that will support the widest range of clients. So if you are sure your DHCPv6 server is giving correct information to clients, then there is no point in turning it off.

Quote from: lonevipr on December 12, 2013, 06:44:45 AM
QUOTE
This is where i'm confused. If I was to shut off DHCPv6 how would clients get IPs?

Most systems would get their IPv6 address by using router advertisements and SLAAC. That part works without any DHCPv6 server. There is only a problem, if you need additional parameters to be configured. It is mainly DNS configuration, which would be a problem. Clients can get their own address using SLAAC and a DNS server address using DHCPv6. A DNS server address in the router advertisement is also possible, but was not in the first version and might not yet be supported by all clients. If you are running your own DNS cache, there is no problem in using IPv4 for communicating with that over your LAN, the DNS cache can still use both IPv4 and IPv6 for communicating with the rest of the world.


https://forums.he.net/index.php?topic=3050.0



i tried the guide shared earlier which didn't work for me. so i then tried with the dhcpv6 server enabled/disabled; tried a few RA Daemon options such as DHCP unmanaged, assisted

but nothing seems to work hmm.gif

This post has been edited by Moogle Stiltzkin: Nov 3 2022, 06:56 AM
Moogle Stiltzkin
post Nov 3 2022, 07:13 AM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
QUOTE
ok got ipv6 to work.

the setting that messed it up was prefix 56, i changed this to 64, NOW it works.

another thing i did was disable the dhcpv6 server, and just left it at assist for RA (i actually wanted to put stateless but i wasnt sure if it was unmanaged or dhcp stateless, so i went with assisted which uses either managed or stateless depending on what the client prefers)
well i got it to work, but then i tried to change back to slaac to see if i could get that to work. but then ipv6 no longer worked. so i tried to change back but it didn't work.

so i thought maybe either the avahi setting i had enabled was the issue, so i disabled that and soon after it worked. not sure if is a coincidence or whether this service really was the cause. either way it works now.

but what doesn't seem to work is android clients. but as long as desktop ipv6 works, i don't particularly care much smile.gif





QUOTE(ansonlos @ Oct 31 2022, 11:50 AM)
I have updated my post with screenshots of my latest IPv6 settings on pfSense CE 2.6.0. Hope it helps with those having IPv6 stability issues on pfSense.
*
QUOTE
QUOTE(asellus @ Feb 18 2021, 11:41 AM)

Did TM gives out /56 prefixes now?
*
QUOTE(rogue @ Feb 18 2021, 10:35 PM)
Only /64
*
QUOTE(asellus @ Feb 18 2021, 10:42 PM)
Oh, just played with a Unifi Biz 100MB account, and I found out it gives out /56 prefix.
*




QUOTE(rogue @ Aug 8 2022, 08:59 AM)
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 :>
*
QUOTE(rogue @ Aug 15 2022, 12:27 PM)
Thanks for the reply. Yes the RFC is for a workaround for ppl that familar with it. Yet you end up with a bunch of deprecated addresses in each host which shouldn't be there in the first place lol. On your router I think the 'secured' address is the most current one. On Windows, it will show up as 'preferred'.

With static prefix, you and the millions of Unifi/StreamyX users won't have this issue.

If you have many devices in your LAN address renumbering will become a nightmare with dynamic prefix. Same goes for VPN if you run one at home with IPv6.

I've highlighted this to TM and they will bring this up to their upper management for further discussion and reconsideration. Hopefully it goes through and they fix it for good.

*
bru, need to update your guide. for unifi home, seems the prefix is 64. for unifi busi they probably using 56


also not mentioned in the guide is for situations if you have multiple vlans. i already posted earlier the solution for that which was really simple. You still can use the track interface, just make sure the ipv6 prefix interface has a different number. WAN is default 0, then lan would be 1, then your vlans just change the numbers like 2, 3 and so on.

This post has been edited by Moogle Stiltzkin: Nov 3 2022, 08:17 AM
Moogle Stiltzkin
post Nov 3 2022, 10:15 PM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
just an update. android ipv6 does seem to work. but when i did the ipv6-test.com it says

native ipv6

slaac: no


but i'm using a vpn though, so not sure if that did anything for it. the other change i did was add the cloudflare dns for both ipv4 and ipv6

anyway it works on android
andrekua2
post Nov 4 2022, 12:17 AM

10k Club
********
All Stars
13,460 posts

Joined: Jan 2012


Hi.

I want to ask how to setup ipv6 on my tplink AC4000. The IPV6 page show fine but when did the test, it doesn't detect IPV6.

Is this not correct?

» Click to show Spoiler - click again to hide... «


This post has been edited by andrekua2: Nov 4 2022, 12:18 AM
papyrous
post Nov 4 2022, 09:07 AM

Getting Started
**
Junior Member
214 posts

Joined: May 2017
QUOTE(andrekua2 @ Nov 4 2022, 12:17 AM)
Hi.

I want to ask how to setup ipv6 on my tplink AC4000. The IPV6 page show fine but when did the test, it doesn't detect IPV6.

Is this not correct?

» Click to show Spoiler - click again to hide... «

*
try reboot+reconnect your clients. it looks fine.
Moogle Stiltzkin
post Nov 4 2022, 11:33 AM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
Just another update


ipv6 does now seem to work for android. before it didn't but when i checked later on it worked hmm.gif

few places i check on android device

- lan ipv6, works
- wan external ipv6, works
- https://ipv6-test.com (results show native ipv6 working, SLAAC no. Ipv6 supported yes.)


I updated ubiquiti unifi ap and so it rebooted. so i think this is why now it works properly. because i did not reboot the wireless ap earlier after having configured pfsense? that's all i can think of why it wasn't working before hmm.gif



my pfsense setting is the same

- WAN, dhcpv6 (settings like anhs posted but the change is prefix /64 )
- LAN ( track interface. the change is, for the other interfaces like vlans i setup for IOT, guest wifi etc, i had to add the prefix 1,2,3 and so on. Ans did not mention any of this in his settings, but this is what was required for those like myself using vlans)

- DHCPV6 server (disabled. not using this. honestly i'm confused why he opted not to configure this. all i know is that regardless of this disabled, ipv6 still works without it)

- RA (i'm using same like ANS posted, which is Assisted)




QUOTE
MikeV7896 Jun 3, 2016,

Unmanaged = SLAAC (StateLess Address Automatic Configuration)
Managed = DHCPv6
Assisted = SLAAC preferred, DHCPv6 available

If you set your RA to managed, but don't have a DHCPv6 server on your network (either from pfSense or another device on your network), then your devices won't get an IPv6 address.

Also, it should be noted that Android devices only use SLAAC for IPv6 addresses, so you need to either be in Unmanaged or Assisted mode. And Windows will only get an IPv6 address via SLAAC; it won't use RDNSS provided DNS servers. DHCPv6 is required for DNS servers under Windows.

https://forum.netgate.com/topic/100931/ra-r...-vs-unmanaged/2


under this guideline i'm not sure that my config is the best setup, but considering it works i'm content xd...


now remains to be seen if this ipv6 pfsense config can persistent without the issue some of us experienced before ^^; (that said, i did try rebooting pfsense, disconnect wan/reconnect and it was able to connect back to wan just fine without issue)


*update

further troubleshoot,

i don't know why but android ipv6 is not fully working. for example, https://ipv6test.google.com
when doing a quick check, one moment the ipv6 shows it's working. then test a minute or so later it's not working. and it's constantly fluctuating between working and not working. but when i try the same test on desktop pc (windows 11), it works fine all the time. So i'm unsure why it's like this for android, any ideas?

hmm.gif


*update

i notice though that when enable mullvad vpn app, ipv6 will consistently work. i setup mullvad to use cloudflare dns ipv4/ipv6 so i can only think that perhaps the dns setting on pfsense is somehow not working correctly or something for android hmm.gif just don't know how to fix without using my vpn app. but this issue seems restricted to android, doesn't seem to be affecting windows 11 desktop pc at all.


This post has been edited by Moogle Stiltzkin: Nov 4 2022, 12:55 PM
rogue
post Jan 16 2023, 03:45 AM

Getting Started
**
Junior Member
75 posts

Joined: Jun 2006
QUOTE(Moogle Stiltzkin @ Nov 4 2022, 11:33 AM)
Just another update
ipv6 does now seem to work for android. before it didn't but when i checked later on it worked  hmm.gif

few places i check on android device

- lan ipv6, works
- wan external ipv6, works
- https://ipv6-test.com  (results show native ipv6 working, SLAAC no. Ipv6 supported yes.)
I updated ubiquiti unifi ap and so it rebooted. so i think this is why now it works properly. because i did not reboot the wireless ap earlier after having configured pfsense? that's all i can think of why it wasn't working before  hmm.gif
my pfsense setting is the same

- WAN, dhcpv6 (settings like anhs posted but the change is prefix /64 )
- LAN ( track interface. the change is, for the other interfaces like vlans i setup for IOT, guest wifi etc, i had to add the prefix 1,2,3 and so on. Ans did not mention any of this in his settings, but this is what was required for those like myself using vlans)

- DHCPV6 server (disabled. not using this. honestly i'm confused why he opted not to configure this. all i know is that regardless of this disabled, ipv6 still works without it)

- RA (i'm using same like ANS posted, which is Assisted)
https://forum.netgate.com/topic/100931/ra-r...-vs-unmanaged/2
under this guideline i'm not sure that my config is the best setup, but considering it works i'm content xd...
now remains to be seen if this ipv6 pfsense config can persistent without the issue some of us experienced before ^^; (that said, i did try rebooting pfsense, disconnect wan/reconnect and it was able to connect back to wan just fine without issue)
*update

further troubleshoot,

i don't know why but android ipv6 is not fully working. for example, https://ipv6test.google.com
when doing a quick check, one moment the ipv6 shows it's working. then test a minute or so later it's not working. and it's constantly fluctuating between working and not working. but when i try the same test on desktop pc (windows 11), it works fine all the time. So i'm unsure why it's like this for android, any ideas?

hmm.gif
*update

i notice though that when enable mullvad vpn app, ipv6 will consistently work. i setup mullvad to use cloudflare dns ipv4/ipv6 so i can only think that perhaps the dns setting on pfsense is somehow not working correctly or something for android  hmm.gif  just don't know how to fix without using my vpn app. but this issue seems restricted to android, doesn't seem to be affecting windows 11 desktop pc at all.
*
My 2* cents with your setup and mine is I'm using dnsmasq and dnsmasq hands out IPv6 addresses and DNS information to LAN clients(PC, Android phone/tablet).

SLAAC = Stateless
DHCPv6 = Stateful

You could run both SLAAC + DHCPv6 or SLAAC + RDNSS so Windows gets IPv6 address from SLAAC and DNS information from DHCPv6 and Android phone/tablet get's IPv6 addresses/DNS information from SLAAC + RDNSS

This post has been edited by rogue: Jan 19 2023, 03:31 AM
Moogle Stiltzkin
post Sep 4 2025, 10:10 AM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
QUOTE(rogue @ Jan 16 2023, 03:45 AM)
My 2* cents with your setup and mine is I'm using dnsmasq and dnsmasq hands out IPv6 addresses and DNS information to LAN clients(PC, Android phone/tablet).

SLAAC = Stateless
DHCPv6 = Stateful

You could run both SLAAC + DHCPv6 or SLAAC + RDNSS so Windows gets IPv6 address from SLAAC and DNS information from DHCPv6 and Android phone/tablet get's IPv6 addresses/DNS information from SLAAC + RDNSS
*
my current settings work for android. just tested. in case others need help with their config.

these are my settings that work for desktop pc, but not for android
» Click to show Spoiler - click again to hide... «



Using latest pfsense 2.8.1-RC

user posted image


what was omitted from screenshot was the interface vlans. for unifi you need to set up the vlans to make sure internet works for unifi tmnut. so yeah... for the average user, pfsense is not that 1 click setup wizard like an off the shelf router like asus, where you can select your isp e.g. tmnut unif then i sets everything for you. For pfsense you have to MANUALLY set it all. But once you complete that, you don't have to bother again. It's worth it cause with pfsense you can use stuff like pfblocker among other privacy tweaks for dns.

user posted image

(pfblocker does not make you invulnerable. you still need to practise good networking hygiene like dont download dodgy stuff, surf weird sites etc.... but it does help block a lot of stuff trying to reach you. it's better protection than your standard router which lacks this type of function. If someone on your house hold has no clue about adblockers, then setting up pfblocker might help somewhat in that sense cause you are blocking it on their behalf on the router side and not client device)


the alternative is opnsense. i never tried it before though.


PS: on pfsense they now use keadhcp. seems stable enough, so i recommend enabling it. If you use pfblocker, you should also enable the python mode. If you don't you will encounter errors after switching to kea dhcp. Why? because you forgot to also switch to python mode. just a tip.


but i disgress. point is, something like pfsense or opnsense is good, but setting it up is hell especially for newbs like me. hopefully my settings helps others get ipv6 working on your pfsense smile.gif (not saying my settings is best, but it's what i found that worked for me. Desktop pc and also android)

This post has been edited by Moogle Stiltzkin: Sep 4 2025, 10:51 AM
papyrous
post Sep 5 2025, 12:52 PM

Getting Started
**
Junior Member
214 posts

Joined: May 2017
Opnsense moved to dnsmasq now with kea optional. i went with Opnsense because it has adguardhome integration, and with that regex style adblocking
Moogle Stiltzkin
post Oct 28 2025, 03:35 PM

Look at all my stars!!
*******
Senior Member
4,451 posts

Joined: Jan 2003
i noticed an odd issue for ipv6 using tmnut.

with my pfsense settings, ipv6 works for private lan.

but when i tried to use it for guest wifi vlan, it didn't work. in fact, the ipv6 settings i suspect was causing internet issues for my guest wifi using vlan30.

so my question, why does ipv6 work for private vlan but not for guest wifi vlan?

in the pfsense settings for ipv6, i basically copied the settings used for the lan settings and used for the wifi vlan. the only difference i set was the dhcp ipv4 range is different. everything else is basically the same.

so why then does ipv6 not work? any ideas?

Currently i had to go to

Pfsense > Services >Router Advertisement >GUESTNETWORK

QUOTE
Router Mode - change to disable

dns configuration - untick to disable


once i did that my internet on the guest wifi vlan for ipv4 started working properly. no ipv6 since that wasn't working and in fact it totally made internet not work at all for guest wifi.


PS: found this
https://www.hitoha.moe/mikrotik-ipv6-pppoe-...nifi-correctly/

hmm.gif

This post has been edited by Moogle Stiltzkin: Oct 28 2025, 03:50 PM
kwss
post Oct 28 2025, 03:44 PM

Regular
******
Senior Member
1,207 posts

Joined: Aug 2018
QUOTE(Moogle Stiltzkin @ Oct 28 2025, 03:35 PM)
i noticed an odd issue for ipv6 using tmnut.

with my pfsense settings, ipv6 works for private lan.

but when i tried to use it for guest wifi vlan, it didn't work. in fact, the ipv6 settings i suspect was causing internet issues for my guest wifi using vlan30.

so my question, why does ipv6 work for private vlan but not for guest wifi vlan?

in the pfsense settings for ipv6, i basically copied the settings used for the lan settings and used for the wifi vlan. the only difference i set was the dhcp ipv4 range is different. everything else is basically the same.

so why then does ipv6 not work? any ideas?

Currently i had to go to

Pfsense > Services >Router Advertisement >GUESTNETWORK
once i did that my internet on the guest wifi vlan for ipv4 started working properly. no ipv6 since that wasn't working and in fact it totally made internet not work at all for guest wifi.
*
You cannot use the same EUI64 index for 2 different subnet.
On Unifi Home, TM only give a single /64, so you cannot use a different index either.

Conclusion: You can only have one subnet using IPv6.
Why? Because stupid TM don't support BCOP-690.

69 Pages « < 67 68 69Top
 

Change to:
| Lo-Fi Version
0.0141sec    0.65    6 queries    GZIP Disabled
Time is now: 25th November 2025 - 06:35 PM