Internet > General Internet
IPv6 the selling point everyone missed.
Alex Atkin UK:
--- Quote from: Chrysalis on October 19, 2021, 07:38:51 PM ---What is recreating the UUID, pFSense? there should be an option there to make it only generated once, and then preserve across reboots.
--- End quote ---
I was of course referring to Xbox, not sure how that word got deleted.
Another bizarre issue is I installed Windows to test a used GPU I picked up off eBay (I got a crash on a game I was 99% sure was a Linux issue) on my Linux box that currently has the IPv6 VLAN on its port, and Windows got an IPv6 IP even though Home edition doesn't support VLANs. What's more confusing, it couldn't actually use it. So it seems it picked up DHCPv6 and router announcements, but actual normal traffic is not flowing. How and why is it doing that?
Of course I'd just move that box onto dual-stack but I kinda prefer how it is now, as I can keep IPv6 off on Linux and only turn it on when I want to, by having it on its own virtual NIC.
Chrysalis:
In my case my VLAN is assigned on my openwrt switch, I set it on the port, and windows itself has no VLAN tag on its packets. I dont know your LAN setup though.
In regards to the traffic flow does the IPv6 have a valid gateway configured on the windows home?
On my Series S, I couldnt get multiplayer gaming to work without native IPv6. For some reason the teredo tunnel just wouldnt work, and as soon as I enabled IPv6 on the VLAN, everything came to life.
Alex Atkin UK:
The point is in this scenario I didn't want IPv6, it was a temporary boot into Windows where I expected it to only respond to the untagged LAN.
On that machine in Linux I have the main IPv4 untagged and dual-stack on VLAN 6, with iIPv4 disabled on that adapter so it uses the main LAN for IPv4. This is so I could test IPv6 functionality, switch it on and off, without impacting IPv4.
The devices that are actually intended to use the IPv6 VLAN have it untagged on their switch ports so work as intended.
Its the fact VLAN 6 was somehow leaking into Windows that bothered me. I was able to get its IPv6 static IP and DNS server, which it shouldn't have. As I understand it DNS on IPv6 comes from RA, thus why I surmised its somehow seeing DHCPv6 and RA, but I think you may be right in that it possibly didn't get the gateway. But frankly, it shouldn't have gotten any of it.
How did it even get to DHCPv6 if Windows isn't tagging the outwards traffic so Windows should have been unable to talk to the router? I suppose theoretically it could have gotten the IP from RA alone, if pfSense broadcasts DHCPv6 Static Mappings over RA too, I don't really understand how IPv6 works in that respect. I didn't think you could do static IPs using RA and pfSense certainly makes no mention of it.
This is why I hate IPv6, its very poorly documented compared to IPv4.
Weaver:
About poor docs. There is a good Microsoft Press book about IPv6; of course it’s full of Windows stuff too and Microsoft-specifics, but it’s very well written as far as the protocols go. I will have to dig for the reference.
> even though Home edition doesn't support VLANs
I didn’t understand that bit. I’m sure you’re not sending out tagged PDUs from your switch or from your Windows-box’s NIC.
Could the leakage be a switch config problem? Is there any chance that an o/s is sending out tagged PDUs?
I’m not much help as I’ve never used DHCPv6. Nor VLANs much, apart from my modems which use VLAN mux/demuxing so they will fit into the limited number of ethernet ports on my FB2900 router. (Limited ethernet ports (three free) was an issue when I had four modems, but actually doesn't have to be now I only have three modems. I haven’t changed the topology though, because having my small mux/demux VLAN switch in between router and modems is another line of defence to hopefully protect the router from lightning strike. Together with the modems, the small mux switch would hopefully take a bullet first.)
Chrysalis:
I dont know Alex, I havent had any DHCPv6 allocations leaking from different VLAN's.
pfSense can have DHCP talk over RA, depending on how its configured in pfSense. If your VLAN's are configured in pfSense, you should see two separate VLAN configuration screens for DHCPv6 and RA. This might be easy to miss, as the second VLAN appears at top of configuration screen, and have to select it to configure for second VLAN.
I dont disagree that its more complicated than it needs to be. It seems the designers of IPv6 implemented things they felt should of been there from the off, and have used the new protocol as a reason to make these changes. Especially as we have different vendor's choosing which parts to support. Some have static UUID, some only dynamic, some can configure the behaviour, plus fragmented support for DHCPv6 or RA. These things may well be contributing to slow rollout of the technology from ISP's.
I am with Weaver that I think this particular problem you got might be a VLAN configuration issue. I remember when I first setup VLAN's on my network it was a learning game with mistakes made on the way to where I have got to now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version