Agreed. You have to carry a VLAN all the way through all devices for it to work on the same layer2 network.
It shouldn't be a problem for most devices to tag VLAN on a port or its own routed layer3 network. Then all of the switches and radios must trunk that VLAN all the way to the edge ports. You can't have an untagged port in multiple VLANs, it has to tag traffic on one VLAN only at the edge. So all of your services much attach to a VLAN aware device on a separate port, unless it also supports VLAN. -----Original Message----- From: Af [mailto:[email protected]] On Behalf Of Josh Reynolds Sent: Tuesday, January 26, 2016 4:58 PM To: [email protected] Subject: Re: [AFMUG] Router for VLANs Okay, bridging a VLAN is where you are going wrong. Bridging is ALWAYS going to send traffic to a low performance management CPU as opposed to some type of FastPath hardware offloaded implementation. You need to attach a network diagram, and explain what you are trying to do. On Tue, Jan 26, 2016 at 5:54 PM, Brett A Mansfield <[email protected]> wrote: > I'm looking for the best router available to handle Internet over VLANs that > doesn't peg the CPU. > > Currently I use a UBNT EdgeRouter Pro, but I cannot get more than 100Mb from > a bridged VLAN and that pegs the CPU to 100%. I get the same issue on CCRs. > > Thank you, > Brett A Mansfield
