You are here: Home » Switching. I will use two switches for this: I will configure an You can do it like this:. Explained As Simple As Possible. Full Access to our Lessons. More Lessons Added Every Week! You may cancel your monthly membership at any time. That would have required me to crawl around behind shelves and under desks to figure out which cable needed to be pulled, moved and put back later.
I defined a shared port eth with a gateway of That gave me two interfaces on the single physical interface, with each one asking a different DHCP server for an IP address. I plugged a cable between the Primus LAN port and the switch that normally handles my local network of I confirmed that I could ping both my Linksys router at Then I connected my browser to I thought you might be interested in at least one practical application for one of the Linux labs we did.
The only ports that should be able to exchange mix of tagged and untagged frames should be trunks and tunnel endpoints e. You're referring to the VLAN traversal attack? The behavior I described in the comment above certainly isn't necessary, and I understand that it isn't possible on most platforms.
Agree regarding the native VLANs; was just checking if I wasn't missing some valid use case when the behaviour above was desired. Interesting post Chris. I know from the dim and distant past that accepting untagged frames as belonging to a native VLAN was useful if you had a hub inbetween two switches or swithc and router as in your post , which would still allow a host connected to the hub to communicate on a particular VLAN despite the hub not having any idea about them.
What was more useful than that was to throw the hub in the bin and replace it with a switch. Hey Matt, Yeah, accepting untagged frames on a tagging interface is useful for all kinds of reasons nearly every wall jack in an environment with IP telephony does this , but I'm less clear on the usefulness of accepting both tagged and untagged frames into the same VLAN.
I did some fiddling around with router-on-a-stick configurations recently and found some native VLAN behavior that took me by surprise. The topology for these experiments is quite simple, just one router, one switch, and a single The initial configuration of the switch looks like:.
And the initial configuration of the router looks like:. So, nothing too interesting going on here. The devices can ping each other on each of their three IP interfaces. On the switch we'll do:. Both configurations leave us with full connectivity on all three subnets, with the So, what's the difference between them?
0コメント