Hey Butch, Just got back to review this list ... thanks for the very useful post about letting the Mikrotiks participate in the trunking. Much appreciated!
Adam ----- Original Message ----- From: "Butch Evans" <but...@butchevans.com> To: "WISPA General List" <wireless@wispa.org> Sent: Saturday, June 13, 2009 2:14 PM Subject: Re: [WISPA] basic mikrotik question > On Sat, 2009-06-13 at 09:01 -0400, Adam Greene wrote: >> A while back we experimented with trunking VLANs over a Mikrotik >> backhaul, >> and *at the same time* putting the Mikrotiks themselves into a tagged >> 802.1q >> management VLAN. We had major problems with that. > > I just did this the other day. There are several possible scenarios that > you can do: > > 1. Straight passing of vlan tags (just simple layer2 bridge) where the > MT is not "participating" in any of the vlans. This is very easy, as > you said. > > 2. Passthrough of tagged traffic and the MT participates in one or more > vlans (management vlan for example). This, too, is fairly easy. > * Build the bridge to include the ports that will passthrough > traffic. > * Build a bridge to "host" the management vlan. > * Create a vlan on the passthrough bridge and add this vlan > interface to the "vlan host" bridge. DO NOT add the > management vlan as a port on the "passthrough bridge" > * managment IP address would be assigned to the "vlan host" > bridge > 3. VLAN termination with trunked port. Simply add vlan interfaces on > the physical interface. IP addresses for each vlan would be assigned to > the vlan interfaces themselves. The physical interface would then be > equivalent to a Cisco "trunk" port. Each vlan is a "routing interface" > in this scenario. > > 4. VLAN participation where multiple ports participate in the vlan. > This is a bit more complex type of configuration and describing steps to > create this would be too difficult to do here in a "generic" fasion. > > You can, of course, have combinations of all the above. The "trick" > with Mikrotik is a matter of creative use of bridges and vlans and > understanding traffic flow at layer 2. > > -- > ******************************************************************** > * Butch Evans * Professional Network Consultation* > * http://www.butchevans.com/ * Network Engineering * > * http://www.wispa.org/ * WISPA Board Member * > * http://blog.butchevans.com/ * Wired or Wireless Networks * > ******************************************************************** > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
