Really like your video, liked and subbed... However, i will really appreciate it if you can answer how to convert or make an incoming LAN (eg; 192.168.1.20/24 without a VLAN ID) to a VLAN and add it to your trunk in mikrotik. The way of doing it in cisco seems easier and clear but not in mikrotik. Thanks for your swift and concise response and God bless.
Assuming you want to do this on a router, put the uplink interface in a bridge with the VLAN you want to trunk, e.g. ether1 - uplink [untagged], ether5 - trunk, ether5.10 [VLAN 10 tagged]: /interface bridge add name=br_10 /interface vlan add name=ether5.10 vlan-id=10 /interface bridge port add bridge=br_10 interface=ether1 /interface bridge port add bridge=br_10 interface=ether5.10 /ip address add interface=br_10 address=192.168.1.20/24 On a switch you'd simply put your uplink interface on untagged list and set the PVID to whatever you want it to be, e.g. 10: /interface bridge port bridge=bridge interface=ether1 pvid=10 /interface bridge port bridge=bridge interface=ether5 pvid=10 /interface bridge vlan add bridge=bridge vlan-ids=10 untagged=ether1 /interface bridge vlan add bridge=bridge vlan-ids=10 tagged=ether5
What seems to be evident from the presentation is that MikroTik seems to pass on all the troubleshooting to the user. If I were to buy it off the shelf I must make sure that I understand the internal details such as PVID, Master Interface, Bridging details etc... which remarkably should be hidden details for me rather than nitty gritty details that I must nitpick through. The switch should work off the shelf with a nice CLI that turns on these features automatically and must not lead a user down a fishbone diagram of consecutive steps of the feature NOT working and forcing the user to delve deeper in the nitty gritty of how to get it to work. Unfortunately the vendor seems to be exposing the user to a lot details that ought to be hidden. My 2 cents
Mmmm.. I really don't have a problem with this approach after all I'm the "Expert" who got the education and gets pay for it. Although I wish documentation wouldn't sucks as much as is right now. Anyways.. Mikrotik is not for consumers.. And is important to understand that.
Honestly, other than the mess of configuring VLAN on Mikrotik, I'm very much OK with this. I'd argue that the barrier to entry does hurt the "enterprise" readiness of Mikrotik hardware. As we get more standard hardware and *consistent* configuration options across devices, I'd wager that enterprise adoption will go up. For now, what I see is that SMBs who run on a tighter budget will choose something which is easier to use. In the world of enterprises with limited staff and resources, usability trumps features.
Awesome presentation idea. Not delivered by presenter. Had issues following him.
Can you give us a link to slides?
Some of these stories are so scary they should be said around a campfire.
Great presentation
Nice video
Итог ролика я вижу так: уволить Майка к чертям чтобы проблем не создавал!
I am having a hard time following the guy around !!! Rehearsal before a presentation may help him next time.
Really like your video, liked and subbed...
However, i will really appreciate it if you can answer how to convert or make an incoming LAN (eg; 192.168.1.20/24 without a VLAN ID) to a VLAN and add it to your trunk in mikrotik.
The way of doing it in cisco seems easier and clear but not in mikrotik.
Thanks for your swift and concise response and God bless.
Assuming you want to do this on a router, put the uplink interface in a bridge with the VLAN you want to trunk, e.g. ether1 - uplink [untagged], ether5 - trunk, ether5.10 [VLAN 10 tagged]:
/interface bridge add name=br_10
/interface vlan add name=ether5.10 vlan-id=10
/interface bridge port add bridge=br_10 interface=ether1
/interface bridge port add bridge=br_10 interface=ether5.10
/ip address add interface=br_10 address=192.168.1.20/24
On a switch you'd simply put your uplink interface on untagged list and set the PVID to whatever you want it to be, e.g. 10:
/interface bridge port bridge=bridge interface=ether1 pvid=10
/interface bridge port bridge=bridge interface=ether5 pvid=10
/interface bridge vlan add bridge=bridge vlan-ids=10 untagged=ether1
/interface bridge vlan add bridge=bridge vlan-ids=10 tagged=ether5
What seems to be evident from the presentation is that MikroTik seems to pass on all the troubleshooting to the user. If I were to buy it off the shelf I must make sure that I understand the internal details such as PVID, Master Interface, Bridging details etc... which remarkably should be hidden details for me rather than nitty gritty details that I must nitpick through. The switch should work off the shelf with a nice CLI that turns on these features automatically and must not lead a user down a fishbone diagram of consecutive steps of the feature NOT working and forcing the user to delve deeper in the nitty gritty of how to get it to work. Unfortunately the vendor seems to be exposing the user to a lot details that ought to be hidden. My 2 cents
Mmmm.. I really don't have a problem with this approach after all I'm the "Expert" who got the education and gets pay for it. Although I wish documentation wouldn't sucks as much as is right now.
Anyways.. Mikrotik is not for consumers.. And is important to understand that.
such learning barrier comes with the low cost...
you can get stuff that "does" that for you, but it also costs way more.
Sounds like you'd prefer ubiquiti. I prefer Mikrotik but to each their own.
Honestly, other than the mess of configuring VLAN on Mikrotik, I'm very much OK with this.
I'd argue that the barrier to entry does hurt the "enterprise" readiness of Mikrotik hardware. As we get more standard hardware and *consistent* configuration options across devices, I'd wager that enterprise adoption will go up. For now, what I see is that SMBs who run on a tighter budget will choose something which is easier to use.
In the world of enterprises with limited staff and resources, usability trumps features.
he`s a terrible story teller. Nevertheless, he well narrated that vlan topic.