Aggravating as all get out when a business product which is CAPABLE of doing normal network switching decides to do things differently. I can understand maybe Cisco doing this or Juniper because they have the clout to change things. But D-Link? Really guys, why must you try to change how port trunking or vlan tagging works?
I'm configuring the network at my school with vlans, and it works great on the wireless, but wired connections... SHEESH. Short of it all is I did it wrong the first time. Had to go find someone else asking the same question on D-Link's support documents to find the correct answer.
With these switches you have Untagged, Tagged, and Not a Member settings for each port.
"Not member": This port is not a member of the VLAN.
"Tagged": The packets have already a VLAN-tag, i.e. they are tagged by the network device connected to this port.
"Untagged":
The packets at this port have no VLAN-tags, so the incoming packets are
tagged by the switch and the outgoing packets are untagged by the
switch.
Which means you have to instead select the port and REMOVE all the OTHER vlans from the port instead of just add the vlan to the port you wish it to be a member of. That's bass-ackwards. So for the rest of the day my network is not working the way it was designed to work and I have to go AFTER work to fix it. GRR!!!
For more context see here: VLANS - Tagged, untagged, what do they all mean?
No comments:
Post a Comment