Definitely needs a bit more detail. Creating a bridge without choosing VLAN filtering and just putting physical interfaces in is like creating a switch that allows all traffic through However VLAN's are quite complex on mikrotik and is worth explaining, along with split-horizon and VLAN filtering and how those affect things The way i've always mentally envisioned VLAN's in the mikrotik world is that the physical port represents a bundle of wires, each of those wires in a VLAN. Normally you're just joining the entire bundle together at once (eth2 and eth3) via some form of connection box (the bridge) that joins every wire to its matching partner. All VLAN's flow by default and behave as expected However when you create a VLAN interface on a port, its like you've cut open the outer insulation and pulled 1 of the wires out. It's now no longer part of that bundle and does not flow traffic until its connected somewhere. It can infact be connected to a different wire in a different bundle, (i.e. putting eth2.10 and ether3.30 into another bridge will seamless bridge VLAN10 on ether2 to VLAN30 on ether3). And if you ever need to intercept one of the wires without breaking its connection, then you instead create a VLAN interface on the bridge. This is how you would i.e. give the router/switch an IP address in that VLAN. Since if you instead created ether2.10 and put an IP there, then you've broken that wire out of the bundle and it will only work on the ether2 side, not ether3
Bridging is so much easier than VLAN on Mikrotik especially on the RB2011 that has two different switch chips that do VLAN differently. However, it has limited use in networks with multiple network devices.
I am a self-taught hobbyist. I have an RB5009UG+S+IN with 9 ports: - If I assign port 4 to a Bridge can I assign the same port to a second Bridge, or is it "used up"? - Can I think of VLANs as if they were a subset of Bridges? I would love to test these questions at home without taking down my network. Could I create a separate "lab" network by configuring a new Bridge with its own set of WAN and LAN ports? Would it be isolated from the primary network?
Thank you, it’d be amazing if you build on this basic concept and start impending vlans and adding wireless interfaces etc Because realistically people start right then mess up the config once start implementing slightly more complex settings Cheers
1:08 Right here is where you lost me. What is “the bridge”? Is that the collection (or a subset) of the physical interfaces on a networking device? So on my inexpensive, unmanaged 5-port switch that I purchased from the local office supply store, is “the bridge” the 5 ports?
Definitely too basic. But it good you specified about making 2 bridge and their potential consequence. I've seen a lot of people use multiple bridge and have individual vlan tag port an bridge those back into a bring instead of vlan filtering.
a position, a staff, appears in the list of my interfaces marked with a letter R: running then type: < loopback> and a number next to it: Actual MTU 65536 RX: = 0 Tx Packet=0; and so on the other data all zero there is no traffic. what can I do should I delete this line? maybe in the past I created it and was unable to create a bridge. the current configuration is the default configuration. Wireless interface and Ethernet (except WAN port) are part of the LAN bridge; The rest is as per default configuration.. I need to convey as much signal from the hAPax3 router on a port where I receive streaming (of my Hifi) to enjoy music. I was thinking of hooking up to their "server" to get a direct signal. How should I configure my Mikrotik hAPax3 router?
Good video for beginners, I just think that is time we start to introduce IPV6 on this concepts as switching and bridging are much more simple and efficient in IPV6.
good start... but you can/could diffidently expend on the subject for at least 10/15 minutes and not loose my interest.... or do a daily 10 minute "coffee break" networking series.... your group does a good job of presenting not only the configuration but more importantly "Why".......
Guys, Bridges deserve more episodes!
this video was just right! to the point and exactly what I needed without addressing other aspects of configuration. many thanks
It is basics, can you please go more detail on how to use the rules on the bridges, there are none on the internet.. may thanks…❤
Good explanation.
Definitely needs a bit more detail. Creating a bridge without choosing VLAN filtering and just putting physical interfaces in is like creating a switch that allows all traffic through
However VLAN's are quite complex on mikrotik and is worth explaining, along with split-horizon and VLAN filtering and how those affect things
The way i've always mentally envisioned VLAN's in the mikrotik world is that the physical port represents a bundle of wires, each of those wires in a VLAN. Normally you're just joining the entire bundle together at once (eth2 and eth3) via some form of connection box (the bridge) that joins every wire to its matching partner. All VLAN's flow by default and behave as expected
However when you create a VLAN interface on a port, its like you've cut open the outer insulation and pulled 1 of the wires out. It's now no longer part of that bundle and does not flow traffic until its connected somewhere. It can infact be connected to a different wire in a different bundle, (i.e. putting eth2.10 and ether3.30 into another bridge will seamless bridge VLAN10 on ether2 to VLAN30 on ether3). And if you ever need to intercept one of the wires without breaking its connection, then you instead create a VLAN interface on the bridge. This is how you would i.e. give the router/switch an IP address in that VLAN. Since if you instead created ether2.10 and put an IP there, then you've broken that wire out of the bundle and it will only work on the ether2 side, not ether3
VLAN is a different "object" and should be its own "method" or "function", no need to add complexity to a simple function of adding a bridge
Basic and complicated. A beginner wouldn't know why he would really need to do that.
finally bridging series, good start.
Bridging is so much easier than VLAN on Mikrotik especially on the RB2011 that has two different switch chips that do VLAN differently. However, it has limited use in networks with multiple network devices.
I am a self-taught hobbyist. I have an RB5009UG+S+IN with 9 ports:
- If I assign port 4 to a Bridge can I assign the same port to a second Bridge, or is it "used up"?
- Can I think of VLANs as if they were a subset of Bridges?
I would love to test these questions at home without taking down my network. Could I create a separate "lab" network by configuring a new Bridge with its own set of WAN and LAN ports? Would it be isolated from the primary network?
• Too basic info
• I am one of your fans ❤
• Please, continue on this topic, especially in the bridge filter rules😊
@mikrotik Why it's called bridge and not switch?
Bridge is basically a logical switch, a switch does it functions on hardware, a bride does it using CPU
@@gabrielpb Hmmm but the first bridge on mikrotik is hardware offloaded so finally it's a switch
It used to be called a switch with a master port. But I think people found that confusing.
@@Morteell yeah, that's a feature you can use, but not all the Mikrotik devices have that feature, not all have the Switch chip inside
Just rename the bridge to ‘switch’. I do that on all bridges with hardware offloading.
Thank you, it’d be amazing if you build on this basic concept and start impending vlans and adding wireless interfaces etc
Because realistically people start right then mess up the config once start implementing slightly more complex settings
Cheers
1:08 Right here is where you lost me. What is “the bridge”? Is that the collection (or a subset) of the physical interfaces on a networking device?
So on my inexpensive, unmanaged 5-port switch that I purchased from the local office supply store, is “the bridge” the 5 ports?
Good video.
PVID is where my confusion comes in when on the same bridge.
Definitely too basic. But it good you specified about making 2 bridge and their potential consequence. I've seen a lot of people use multiple bridge and have individual vlan tag port an bridge those back into a bring instead of vlan filtering.
Too informative
I find it odd you described how a hub and switch work without mentioning them properly, or once using the term hub.
What's that little white box on the top shelf, right most?
Video en español por favor. Saludos
a position, a staff, appears in the list of my interfaces
marked with a letter R: running then type: < loopback>
and a number next to it: Actual MTU 65536
RX: = 0 Tx Packet=0; and so on the other data all zero there is no traffic.
what can I do should I delete this line?
maybe in the past I created it and was unable to create a bridge.
the current configuration is the default configuration.
Wireless interface and Ethernet (except WAN port) are part of the LAN bridge; The rest is as per default configuration..
I need to convey as much signal from the hAPax3 router
on a port where I receive streaming (of my Hifi) to enjoy music. I was thinking of hooking up to their "server" to get a direct signal. How should I configure my Mikrotik hAPax3 router?
It is a loopback interface. It is built in. You can't delete it, just ignore it.
@@mikrotik thank you very much.
Good begining, but please go deep on that topic.
Thank you sir although nothing new 😇
Good video for beginners, I just think that is time we start to introduce IPV6 on this concepts as switching and bridging are much more simple and efficient in IPV6.
good start... but you can/could diffidently expend on the subject for at least 10/15 minutes and not loose my interest.... or do a daily 10 minute "coffee break" networking series.... your group does a good job of presenting not only the configuration but more importantly "Why".......
Too basic! We need a solution to switch stacking.