Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Weaver]

[Ixel]

Private IPv6 addresses are easy to remember, public ones however aren't so easy.

My allocation for example is 2a0e:fd45:xxxx::/48 (where xxxx is just the masked out bit of nonsensical letters and numbers). IPv4 addresses are up to 12 numerical characters, excluding the dots, whereas the mentioned allocation is at least 12 hexadecimal characters (excluding the colons). I think it's already obvious why public IPv6 addresses might be harder to remember unless you're lucky enough to get something like 2a0e:fdfd:4345 or something easier to remember compared to a somewhat patternless allocation.

If I was to become an LIR member with RIPE however then I could request a /32, justification not required, and have more choice from the third segment (which I believe is considered an ISP level allocation, especially given how much a /32 can be split).

[Alex Atkin UK]

You have to remember Weaver, you're from a development background, you've trained your brain around remembering freaky hexadecimal values. :p

My memory has always been a weakness, I was in my 20s when I setup my first LAN so remembering 192.168.1 is second nature.  I rarely remember what my other clients are set as other than my gaming PC is 1 and my normal desktop is 2, server is 253 and router is 254.

There's also the complexity of which privacy scheme are you using on IPv6 and if you aren't, then your range depends on your ISP.

But most importantly, there's the fact IPv6 routing has inexplicably broken on my LAN right now and I have no clue why.  Spent a few hours yesterday trying to figure it out, I can ping from the server to the router, can ping the other way, but nothing will load.  A traceroute outright fails, pfSense is not sending the traffic onwards, something is borked.

[craigski]

One of the other LAN-local L2 name resolution protocols (I forget what Apple has used)

mDNS/Bonjour?

[XGS_Is_On]

What do other people do about IPv6 name resolution for non-server machines in practice?

Boring as it is I do nothing for them. If they aren't going to take inbound connections no point in name resolution. I don't actually track what servers use for IPv6 either as I use v4 for them for right now internally. Servers and other infrastructure do get nailed down addressing during setup. Servers have fixed MAC addresses so plenty of ways to handle it when the time comes. Clients using dynamic/randomised MAC addresses aren't going to be taking inbound connections so no need to worry about addressing them directly.

[Alex Atkin UK]

Boring as it is I do nothing for them. If they aren't going to take inbound connections no point in name resolution. I don't actually track what servers use for IPv6 either as I use v4 for them for right now internally. Servers and other infrastructure do get nailed down addressing during setup. Servers have fixed MAC addresses so plenty of ways to handle it when the time comes. Clients using dynamic/randomised MAC addresses aren't going to be taking inbound connections so no need to worry about addressing them directly.

Like I've said before, the exception to this rule seems to be Xbox which randomise their ID every reboot, highly frustrating.

For some bizarre reason they also expose manually entering an IPv4 address, but not IPv6.  In fact while trying to get IPv6 working again the Xbox was the worst client, it doesn't even show its getting an IP address though I know DHCPv6 IS working, its just actual traffic that isn't passing.

[XGS_Is_On]

Only have gaming PCs and PS5 so abstaining further from this.

[Alex Atkin UK]

So I removed and put back the IPv6 addess on the main LAN of pfSense and somehow its magically working again, even though that subnet is not actually used.

Weirder is clients on the V6 VLAN cannot ping the IP address of pfSense for that VLAN but can ping the main LAN IPv6 address.  I don't even have any rules on the main LAN allowing ICMP over V6 but do on the VLAN.

Oh well, its routing again at least.

[Chrysalis]

How do you enforce your VLAN tag? is it client side or switch side?

[Alex Atkin UK]

How do you enforce your VLAN tag? is it client side or switch side?

The Xbox is on that VLAN untagged via the switch config, my server and desktop (both Linux) has it tagged.  This way I just turn it on and off in the network manager when testing things.

The rest of the network isn't on that VLAN at all, except the WiFi which has a separate SSID for the dual-stack network, again in case I want to test it on different clients.

Frustrating the Xbox now says IPv6 is working but moans uPNP is not available and the NAT is strict - so what the heck is the point of IPv6 there if its using IPv4 for gaming traffic?  I thought the whole point was Microsoft was using Teredo for Xbox Live so it would work seamlessly when moving to IPv6.

[Ixel]

I wonder what the Xbox would do if there was no IPv4 support on the network?

[Alex Atkin UK]

I tried that before, it said no Internet connection.

So much for Microsoft being IPv6 pioneers.

[Weaver]

[Alex Atkin UK]

[Ixel]