IPv6 Roll Out

Afrigirl said:
Yes, Ipv6 is active for all Openserve clients.
Please share a screenshot of your settings, I will check if we can get someone with UniFi Dream Machine to test for us.
Click to expand...

Here you go.

Then I thought the issue is maybe that it needs to enabled LAN side to "activate" but even that didn't help.

While the Auto mode for LAN greys out and seems to select SLAAC I assume that not actually happening in the background because even if I override it with Manual and DHCPv6 there is no joy.
 

Attachments

  • Screenshot 2024-04-29 at 12.01.17.png
    Screenshot 2024-04-29 at 12.01.17.png
    86.1 KB · Views: 36
  • Screenshot 2024-04-29 at 12.03.37.png
    Screenshot 2024-04-29 at 12.03.37.png
    49.9 KB · Views: 35
SauRoNZA said:
Here you go.

Then I thought the issue is maybe that it needs to enabled LAN side to "activate" but even that didn't help.

While the Auto mode for LAN greys out and seems to select SLAAC I assume that not actually happening in the background because even if I override it with Manual and DHCPv6 there is no joy.
Click to expand...
Please try and set the prefix to /64
 
SauRoNZA said:
Well somewhere between that change and upgrading to UniFiOS 4.03 I'm finally getting an IPv6 address.

Now to make Adguard work with it. :)

Thanks for your help!
Click to expand...
I am glad to hear that.
 
SauRoNZA said:
Well somewhere between that change and upgrading to UniFiOS 4.03 I'm finally getting an IPv6 address.

Now to make Adguard work with it. :)

Thanks for your help!
Click to expand...
Biggest challenge of that will be, decided by the fact whether you run adguardhome inside a docker container or not. The challenging part, its making docker play ball.

If you running it as an addon with Home Assistant....eh you might be out of luck.
 
Tinuva said:
Biggest challenge of that will be, decided by the fact whether you run adguardhome inside a docker container or not. The challenging part, its making docker play ball.

If you running it as an addon with Home Assistant....eh you might be out of luck.
Click to expand...

Works just fine as the add-on in Home Assistant as it runs it at host level by the looks of it.

Just pointed it to the IPv6 address of Home Assistant and off it went. The real pain is needing to go add the IPv6 of every client now.

Bigger problem for me is that I have no idea what I'm doing with the DHCP range and how I would go about splitting it up if I want to do it across VLANS.

I just used the Default Start ::2 and Stop ::7d1 with no real clue what that actually means but I assume it's a massive range consuming the entire /64.
 
SauRoNZA said:
Works just fine as the add-on in Home Assistant as it runs it at host level by the looks of it.

Just pointed it to the IPv6 address of Home Assistant and off it went. The real pain is needing to go add the IPv6 of every client now.

Bigger problem for me is that I have no idea what I'm doing with the DHCP range and how I would go about splitting it up if I want to do it across VLANS.

I just used the Default Start ::2 and Stop ::7d1 with no real clue what that actually means but I assume it's a massive range consuming the entire /64.
Click to expand...
Oh I see yeah addons are in host most. Nice.

As for the ranges over VLANs. You want a /64 per vlan really. Since you have dhcp, maybe not. But in my case, with a mikrotik router, it doesn't do dhcp on ipv6 to hosts, only to other routers.

So I have to use RADVD / IPV6->ND. This mean, each host configure their own ip address.
1x ipv6 ip using EUI-64, which uses the mac address with the /64 prefix.
1x ipv6 that is anonymous and change with reboots.

Also, a /64 doesn't end at ::7d1 but you more than welcome to limit it to that if you want, but its actually a whole lot more.

For example, fd00::/64
Start at fd00:0000:0000:0000:0000:0000:0000:0000
ends at fd00:0000:0000:0000:ffff:ffff:ffff:ffff
With this example, you can see a network card's mac address fits in there. Although it goes through the EUI-64 algorithm which changes it slightly.

I use fd00 to keep a static range across my home network, and all internal traffic use this range. I don't nat it either to go out publicly. Each device also sets up my ISPs prefix. The OS then use the public ip for internet and the fd00 for private stuff. That also allows me a much stricter firewall rules for the internet vs lan between my vlans.
 
Tinuva said:
Oh I see yeah addons are in host most. Nice.

As for the ranges over VLANs. You want a /64 per vlan really. Since you have dhcp, maybe not. But in my case, with a mikrotik router, it doesn't do dhcp on ipv6 to hosts, only to other routers.

So I have to use RADVD / IPV6->ND. This mean, each host configure their own ip address.
1x ipv6 ip using EUI-64, which uses the mac address with the /64 prefix.
1x ipv6 that is anonymous and change with reboots.

Also, a /64 doesn't end at ::7d1 but you more than welcome to limit it to that if you want, but its actually a whole lot more.

For example, fd00::/64
Start at fd00:0000:0000:0000:0000:0000:0000:0000
ends at fd00:0000:0000:0000:ffff:ffff:ffff:ffff
With this example, you can see a network card's mac address fits in there. Although it goes through the EUI-64 algorithm which changes it slightly.

I use fd00 to keep a static range across my home network, and all internal traffic use this range. I don't nat it either to go out publicly. Each device also sets up my ISPs prefix. The OS then use the public ip for internet and the fd00 for private stuff. That also allows me a much stricter firewall rules for the internet vs lan between my vlans.
Click to expand...

So if I wanted like conventional /24 size networks how could I break the /64 IPV6 into say 4 VLANs using Ubiquiti’s syntax to define the range?

Even a subnet calculator didn’t help and it’s been way too long since I touched a Hexadecimal/binary bible to make sense of it.

Also why does it seem like some devices get 2 or even 3 IPs while others get just one?

I am 100% n00b with this and actually wondering if I need IPv6 locally at all, but then I still need to use NAT I presume which is part of the reason I’m trying to make the switch.
 
SauRoNZA said:
So if I wanted like conventional /24 size networks how could I break the /64 IPV6 into say 4 VLANs using Ubiquiti’s syntax to define the range?

Even a subnet calculator didn’t help and it’s been way too long since I touched a Hexadecimal/binary bible to make sense of it.

Also why does it seem like some devices get 2 or even 3 IPs while others get just one?
Click to expand...
No you dont want to break up the /64. You rather want to get a /60 or /62 from Afrihost, then have 2 or more /64 ranges. a whole /64 per vlan. Basically, the /64 is in ipv6 what your /24 in ipv4 is. Not exactly but see it like that.

As for 2 or 3:
1x EUI-64 ip, stay static
1x anonymous ip, change every reboot.
3rd is mabye the link local you see
 
Last edited:
Tinuva said:
No you dont want to break up the /64. You rather want to get a /60 or /62 from Afrihost, then have 2 or more /64 ranges. a whole /64 per vlan.

As for 2 or 3:
1x EUI-64 ip, stay static
1x anonymous ip, change every reboot.
3rd is mabye the link local you see
Click to expand...

Well I don’t even need that many full /24 equivalents.

How many IP’s can I get out of the /64 total?
 
SauRoNZA said:
Well I don’t even need that many full /24 equivalents.

How many IP’s can I get out of the /64 total?
Click to expand...
Its not about how many ips you can get in it, its about the fact that a mac address fits into a /64 and that is what it was designed around. If you make it smaller, you going to run into issues I cant even imagine.
 
Gambit said:
There are 18 446 744 073 709 551 616 IPv6 addresses in a /64 subnet. Going to need to add a lot of IOT devices to your smart home to use all that up.
Click to expand...

Yeah so how do I break it down into reasonable chunks?

Say a 100 at a time?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X