Think of the bridge as a switch. You add ports (to the bridge) that you want to be part of your switch. \
So you can have untagged traffic on ether5 and ether7 send data to vlan20 on ether1 and vlan20 on ether9. You put all of those in a bridge. You cannot add a bridge to a bridge. I suggest a diagram that shows what's on this device and where the IPs are and maybe their routes. It could help to clear up what you are trying to do. Matthew Jenkins SmarterBroadband m...@sbbinc.net 530.272.4000 On 07/01/2014 04:32 PM, Josh Reynolds wrote: > So I need to make two bridges then? > > 1 for the lan interface and wan side vlan, and 1 that bridges that > bridge with the eoip tunnel? > > That doesn't seem right. > > On 07/01/2014 02:58 PM, Faisal Imtiaz wrote: >> If you keep these rules in mind, you will be able to sort out the confusion >> ... >> >> MT are routers.. >> Each Physical Port is an interface. >> Vlan is tied to a Port (as such ports are Trunk Ports), and each >> VLAN/Port Combination is an virtual interface. >> If you want to make Two Interfaces talk to each others as one then you need >> to create a Bridge and put in the physical or virtual interface, in that >> bridge. >> >> >> ------- >> e.g. if you define a vlan 20 on port 2 and define a vlan 20 on port 3, each >> of these two are independent virtual interfaces... i.e. vlan20/pt2 will not >> talk to vlan20/pt3...(but you can route between then as if they were two >> separate ports) >> >> If you want both of these vlan20's to be the same network, then you need to >> create a bridge called brvlan20, and put the two vlan20 in it. >> >> Hope it makes sense ? >> -------- >> >> Any time you use a bridge to connect (virtual interface or physical >> interfaces) together, then all IP services need to be assigned to the >> Bridge, so that they are visible on all interfaces in the bridge group. >> >> -------- >> >> BTW, a bridge is also a virtual interface, not tied to any port.... it is >> commonly used in this manner as a loopback interface.. (you can assign a >> /32, i.e. single ip to such an interface) >> >> >> ============================ >> >> Hope this helps ... >> >> >> Regards. >> >> >> Faisal Imtiaz >> Snappy Internet & Telecom >> 7266 SW 48 Street >> Miami, FL 33155 >> Tel: 305 663 5518 x 232 >> >> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net >> >> ----- Original Message ----- >>> From: "Josh Reynolds" <j...@spitwspots.com> >>> To: wireless@wispa.org, a...@afmug.com >>> Sent: Tuesday, July 1, 2014 5:25:51 PM >>> Subject: [WISPA] mikrotik - bridge - van - eoip questions >>> >>> So, new question. >>> >>> Special project. >>> >>> "cpe" Router has a management ip >>> "cpe" Router has a separate vlan piped to it as well >>> >>> I had lan -> bridged -> vlan, with vlan assigned to wan interface. This >>> gave me a layer2 tunnel. My problem here, is that I don't have much real >>> visibility or testing capability over the separate vlan. >>> >>> So I'd like to create an EOIP tunnel between the devices over the >>> separate vlan, but I'm running into issues figuring out what goes where. >>> >>> So you've got a lan interface, wan interface, vlan that sits on the wan, >>> eoip tunnel, and a bridge or two, and another ip that goes on the vlan >>> or eoip tunnel for them to communicate over the vlan. >>> >>> Soooooo: >>> >>> Create vlan >>> assign vlan to wan interface >>> create eoip tunnel >>> assign ip address to vlan interface ? >>> bridge ( lan, vlan, eoip tunnel) ? >>> >>> >>> -- >>> >>> Josh Reynolds >>> >>> Chief Information Officer >>> SPITwSPOTS >>> >>> _______________________________________________ >>> Wireless mailing list >>> Wireless@wispa.org >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >> _______________________________________________ >> Wireless mailing list >> Wireless@wispa.org >> http://lists.wispa.org/mailman/listinfo/wireless _______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
