networking

3604 readers

1 users here now

Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.

founded 3 years ago

MODERATORS

manifex@sh.itjust.works

Update on Frontier IPv6 (wetshav.ing)

submitted 5 months ago by walden@wetshav.ing to c/networking@sh.itjust.works

1 comments fedilink hide all child comments

I made this post 3 months ago: https://sh.itjust.works/post/50242033

@stevetech@aussie.zone was super helpful in checking that my Mikrotik configuration was set up correctly. There's a mess of IPv6 information out there for Mikrotik and it's confusing for a mid-nerd like myself.

Anyway, I checked the other day and boom, I had a prefix assigned by my ISP (Frontier).

Unfortunately Frontier has decided to give out /64 prefixes. The downside to that is you can't use SLAAC inside your LAN to do subnetting (guest networks, VLANs, etc).

So my next step is to learn about DHCPv6 to manage things inside my LAN.

There are comments on other forums that are hopeful that since Verizon bought Frontier, they'll eventually switch to handing out /56 prefixes.

you are viewing a single comment's thread
view the rest of the comments

[–] SteveTech@aussie.zone 2 points 5 months ago* (last edited 5 months ago)

Wow, thanks for the update!

Edit: You can possibly look into NPT if you want to use SLAAC on your LAN, it's like NAT but for your prefix, so the connection is still somewhat end to end.

Although one thing to note, fd00::/8 is allocated to be used as a private address, however most browsers will prioritise IPv4 over these ULA addresses. You can pick your own prefix from the unallocated addresses, which is kinda sketchy but then browsers trust it.