MikroTik CLI: A Basic Introduction to It for New Users

[@batsirayimavunga3894]

You have definitely made the cli easier to navigate, thabks

[@brodie7838]

I love the rOS CLI. It helped me to understand that the structure of it follows the GUI, so if you can learn the GUI, you've effectively learned most of the CLI already. After that, the majority of rOS's learning curve boils down to understanding how Mikrotik implements different technologies in their platform, just like any other vendor.

[@kurtneytodman9360]

I did it the opposite way. I use to have winbox open to understand the structure of the CLI

[@brodie7838]

@@kurtneytodman9360 I do that too, it's a great help to have it that way.

[@drumaddict89]

thanks johnny i'll definitely show this video to my colleagues at work, which are completely new to MT great works as always - and it's just the beginning of the video ;)

[@TheTechCatalyst]

Coming from the Cisco world this was very helpful. Thanks!

[@IG2296]

Great, thank you. Many things now are clear

[@caezariidecastro4260]

Thank you so much Man, I started in Mikrotik GUI and switch to pfsense for GUI ease of use. Now adding back my Mikrotik CLI to my portfolio because there's a limitation on how you can control traffic in pfsense. Thank you!

[@mikkio5371]

Thank you soo much for these informative video

[@Anavllama]

Nice touch! Its halloween here on Monday. I reviewed the MT FORUM useful user article titled: "New User Pathway to Config Success", and specifically para M: "First Access Including Winbox" and noted that this video has already been added to the list. As a matter of fact, all the links in para M, connect to your youtube videos. Much thanks for this continuing series into demystifying ROS. I learned CLI the hard way trial and error. :-). It quickly became an important tool to have under one's belt, especially for rejigging parts of configs.

[@TheNetworkBerg]

Wow that's really cool, I wasn't even aware of the thread. Happy to see that a few of my videos can help out someone new 😁

[@theyogabios]

Thanks!

[@jakirbasha69]

Thanks sir From now on atleast i will try to do my config in cli

[@tobias2873]

Typically, Mikrotik devices allow serial access over USB. Plug a USB ttl device into an USB-A port on a MT device. At the other end convert serial back to USB with a ttl to USB converter. I've successfully tested this setup with Prolific and FTDI converters.

[@theyogabios]

this is great, thank you so much.

[@AdrianuX1985]

+1 Unless I'm mistaken, "swOS" still only allows configuration via HTTP, not HTTPS. Is there an unofficial project for automating "swOS"? Something like reverse engineering: HTTP --> PYTHON --> ANSIBLE

[@ahmadkakarr]

thanks

[@ChristopherMcAvaney]

Great video - qn - why is wlan1 in blue when you tab complete the interfaces when adding ports to the bridge?

[@TheNetworkBerg]

Because the interface is in a disabled state when doing a factory reset with no default configuration

[@ChristopherMcAvaney]

@@TheNetworkBerg ah so blue means disabled interface

[@s.m.shawon9931]

i want to change only the username and password of my pppoe-out interface by command line..anyone know the command line here ??

[@TheNetworkBerg]

You can use the set or edit function in the CLI to update that information. I first recommend doing a /print and then changing the value of the PPPoE-client interface that you want to update if you have multiple interfaces you could have item 0, item 1, item 2 etc. But for most cases it should just be 0 So you could use these two command: interface/pppoe-client/print interface/pppoe-client/set username=newusername password=newpassword 0 That should update your username and password for the PPPoE interface from the CLI :)

[@Botan109]

Thanks You cool Man. Is very usefull video for beginners. /export your-knows=import_in_mybrain.rsc :)