Set up mixed IPv4 and IPv6 traffic?
-
@pfguy2018 said in Set up mixed IPv4 and IPv6 traffic?:
I am told that the set top boxes can connect to one's own wifi access points even if the router is in bridge mode, but I don't know what things have to be in place to allow this to happen.
I have mine connected via Ethernet, as I already had it at every point I have a TV.
-
@jknott said in Set up mixed IPv4 and IPv6 traffic?:
I have mine connected via Ethernet, as I already had it at every point I have a TV.
Is your ethernet connection to an IPV4 network, or IPV6?
-
@pfguy2018 said in Set up mixed IPv4 and IPv6 traffic?:
Is your ethernet connection to an IPV4 network, or IPV6?
Both. I've been running IPv6 for almost 11 years and 5 of those as provided by Rogers. My entire network is dual stack and everything that supports IPv6 uses it. However, for a while, my guest WiFi was IPv4 only, due to my TP-Link AP not handling VLANs properly. So, my Rogers TV boxes are connected to my main LAN, where they work fine.
BTW, what sort of bandwidth are you getting from Rogers. I have 500/10 and a friend on Bell fibre gets 500/500. I suspect the increase in bandwidth has something to do with IPTV, though I don't know what.
-
@jknott
I am on 1000/30 with Rogers, and I do actually get that bandwidth. I have not taken the plunge on Ignite yet. Before I can do so, I would have to swap out my switches and access points to ensure that IPv6 can be used. I am getting a headache just thinking about it. -
Switches and APs should not see or care about IPv6 other than their own management, which doesn't have to be v6. They are layer 2 devices (mostly
)Steve
-
@stephenw10
Looks like I have a lot to learn about this. How can a switch or access point pass IPv6 traffic if it only has IPv4 in all its settings? -
Because settings on a (layer2) switch or access point that include any sort of IP would only apply to the management interface.
You could connect two Ethernet cables through a switch and pass, for example, 50 IPv4 subnets between them. The switch may only have an IP for management in one of them but still passes all subnets, it doesn't care what the IPv4 traffic is.
In fact it will pass anything at layer 2, doesn't have to be IP at all could be IPX or Appletalk.
So it will pass IPv6.
https://en.wikipedia.org/wiki/List_of_network_protocols_(OSI_model)#Layer_3_(Network_Layer)Steve
-
Switches and access points should have no problem at all with IPv6, as they are supposed to pass all Ethernet frames. Many years ago, switches were used to pass IPX and many other frame types. The only thing is some gear might be IPv4 only on the management interface. As I mentioned, I've been running IPv6 for almost 11 years. The only thing that absolutely has to hand IPv6 is the router and pfsense does that very well.
-
@jknott @stephenw10
Like I said, I guess I have a lot to learn. I am still not clear on how vlans work with IPv6 if the switch/APs don't see IPv6 (how does the equipment know which vlan to place the traffic in? Just based on the tag? Does the tag work with both v4 and v6?). I will have to do some reading/learning about this. -
They work exactly as they do with IPv4. You're confusing layers. Ethernet is layer 2 and IP, both 4 & 6 (and IPX) are layer 3. VLANs are an extension of Ethernet and so belong at layer 2 (some say 2.5). In every Ethernet frame, the first significant bytes are the 2 in the Ethertype/Length field. This is what determines what the frame contains. If it is 1500 or below, it is an 802.3 frame and the value refers to the payload size. Otherwise, it's a DIX II frame and the number refers to the data type, including IPv4, IPv6 and much more. So, normally a frame would have the Ethertype for IPv4 or IPv6. But if it's for a VLAN, it would have the Ethertype for VLANs, followed by 2 bytes for the VLAN ID and then followed by the original IP Ethertype, etc. So, for a VLAN, there are 4 bytes added, which the switch uses to sort according to VLAN.
-
@jknott
Thank you for the extremely detailed explanation. I am going to read and re-read that a few times until I grasp all the concepts you outlined. I think what you are saying though is that if pfSense passes IPv6 traffic on to a vlan, it will stay on that vlan throughout my networking equipment (switches, APs) even if that equipment does not explicitly have settings for IPv6? -
@pfguy2018 said in Set up mixed IPv4 and IPv6 traffic?:
I think what you are saying though is that if pfSense passes IPv6 traffic on to a vlan, it will stay on that vlan throughout my networking equipment (switches, APs) even if that equipment does not explicitly have settings for IPv6?
Yep. As mentioned above, the only equipment where that would be a factor is routers. Switches and APs are transparent to the layer 3 packet type.
-
@jknott
So as long as pfSense is set up to accept and process IPV6, I don't need to change anything in my switches or APs or vlans? Whichever vlan the cable boxes get added to (either by ethernet connection to an untagged port belonging to the desired vlan on a switch or by joining a wireless network associated with that vlan), things will just work? -
Think of VLANs as though they were physically separate. If you can do something with plain switches and APs, you can do it with a VLAN. What VLANs allow you to do is run those logically separate networks over one physical network and then separate the traffic. For example, in offices, VoIP phones and computers often share the same connection, with the phone on a VLAN. This allows the phones to have priority over the computer data, as VLANs enable priority through switches, etc.. Another example is guest WiFi, so you can use the same APs, but keep then separate from the main LAN traffic. I have that here.
Bear in mind the VLANs must be configured on pfsense, switches and APs and the VLAN ID must match on each device.
-
@jknott
Right. I already have the vlans configured and running on all equipment. I am just confirming that nothing will need to be adjusted to accommodate IPV6 traffic on those vlans (except for at the pfSense end of things). -
Yep.
-
@jknott
So much easier than I would have thought. Thanks! -
One thing to bear in mind is that each interface has to use a different prefix ID. With a /56 from Rogers, your choices are 0 to ff. You also have to specify you want a /56, though you could get a smaller one if you want.
-
@jknott Good to know. I appreciate all your help so far. Once (if) I decide to proceed with this, I might have to come back to get more assistance...
