That Netgear does appear to have support for VLANs, so either it was configured once upon a time, or it can optionally ignore tags, which wouldn't surprise me on a consumer or 'prosumer' switch. Enterprise switches tend to be far stricter about such things.The switch was a Netgear GS116Ev2. It has basic admin config but I never use them besides for update.
With these hints I seach a little deeper in the freebox config and I found that freebox server and player communicate via VLAN100 (tagged) and they also are visible via the standard LAN (untagged). the freebox player always gets its IP via the freebox server DHCP.
I am still not familiar to what I need to config on the switch, but I am closer to a solution. Is it possible to have a RJ45 port with both VLAN100 (tagged) and standard LAN (untagged) packets ?
Thanks for the link about the diagram, I will use it.
In Brocade syntax (this may be slightly different, I run 7k series with 8.0.95), and using ports 23 and 24 as the example:
Code:
conf t
int e 1/1/23
port-name Freebox Server
int e 1/1/24
port-name Freebox STB
vlan 100 name TV by port
tag e 1/1/23 e 1/1/24
end
wr me
For the TV equipment, you don't need to worry about untagged, since the only thing using these ports will be the TV equipment which is applying tags. If you were linking multiple switches and needed to pass multiple VLANs, you can tag one port in multiple VLANs to make a trunk.
Untagged VLANs are for when devices are not applying the tags themselves; then traffic entering the port gets tagged by the switch. In most cases you will not need to mix tagged and untagged traffic on a port. For a 6k series switch, if you needed to do so, there's a 'dual-mode' option or some such that I have no experience with as it stopped being a thing in v8.0.80 I believe.
Last edited: