I just (finally) received RB5009, and I see no serial port? Am I missing something?
Yes, you missed reading the specs before buying it.
Excellent. Is there a way to access the device over USB port via serial adapter or something??
Sure, there is the WOOBM:
https://www.youtube.com/watch?v=2yWrUQ_woKQ
Do not work on v7, see other topic about that.
But this doesn’t connect to serial console? It is only for running routeros devices?
Could you please provide me the with the thread link? I can't find it.
This said, 5009 is a great device, but without serial I can't implement it anywhere as there is no backup access.
try to write WOOBM v7 on Search… and press ener…
Backup for what? For have serial port onsite or use remotely the serial port?
Backup for what? For have serial port onsite or use remotely the serial port?
[/quote]
Backup for when routeros is broken so I can fix it tru console.
Thanks, there might be issues, but on my HAPac2 it does work well with v7, just tested it, could connect via WOOBM:
[admin@ut-r1] /system/routerboard> print
routerboard: yes
board-name: hAP ac^2
model: RBD52G-5HacD2HnD
serial-number: E5780F4848A2
firmware-type: ipq4000L
factory-firmware: 6.45.9
current-firmware: 7.8beta2
upgrade-firmware: 7.8beta2
Must be 5009 then, as hAP ac3 ROS V7 is no problem.


What firmware have your WOOBM? (on bottom of the settings page)
I put my WOOBM already away, but I know I have installed the file: woobmfw_211105.bin
That file is still on my laptop…
I hope on more recent version that fix the issue…
I get where your coming from – want to get in if the router is FUBAR…
But winbox’s MAC-address / layer2 access is a godsend to avoid needing a serial port to access the router if you’re at the physical router. If you enable RoMON, Layer2 access get extended to other routers using an alternative switching plane.
I don’t have any handy, but I’d image a USB to serial adapter work if it showed up under /port… Then it could be assigned to console in /system/console – before you’d needed for an “emergency”. Just plugging in the serial-to-USB is likely going to do nothing since RouterOS wants you to assign the port to some service, of which console is one possibility.
My version v1.1.
Once had a problem on hAP ac2 , with the already defined system/console. Deleting console solved the problem.
EDIT: with some luck and fail-safe RouterOS design
.
https://wiki.mikrotik.com/wiki/Serial_Port_Usage
“as RouterOS will recreate the console after the next reboot when you really remove it.”
“When rebooting a RouterBoard the bootloader (RouterBOOT) will always use the serial console (serial0 on RouterBoards) to send out some startup messages and offer access to the RouterBOOT menu.”
I got a reply re connectivity → USB-serial-nullmodemcable-serial-usb contraption should work no problems.
I just ordered another usb adapter I know works fine and I tested over USB connection.
As for woobm I am still not sure if that is console connection or terminal connection.
What I do on “important” RB5009 is to sacrifice ether8 for mgmt port. I make it not part of the main bridge nor part of the LAN interface group and bind a static ip directly to ether8, allow winbox/webui/ssh on it. So if I mess up bridge settings or FW rules in a way not even MAC access is working, I can connect an Ethernet cable to ether 8.
But as long as RB5009 is still booting, MAC access usually works also for worst config mishaps.
And there is always safe mode which should be activated before changing bridge/IP/FW settings.
It can be made even easier from two USB to TTL boards (super cheap from China, <$1, just get FTDI chips as they are least problematic), connect RX->TX, TX->RX, GND->GND and it’s done. Easiest OOB management from one Mikrotik to another.
WOOBM contains ESP8266 MCU for dealing with wifi/serving web pages and USB to UART module so it appears as USB serial device/adapter on Mikrotik.
So it’s USB serial console terminal with WEB UI.
I usually just enable mac access and be done with it. Password is humongous, so if someone breaks it, well - they have my permisson to wreak havoc
what bothers me the most is not having ability to access the actual terminal console, because that thing saved my ass not once. A month ago I had dead 4011, as in completely dead. Corrupted ssd storage. And I fixed it thru boot sector force over serial. It worked! So no serial is a deal-breaker for me. But it is not a big deal, as if I understand correctly USB is just an implementation of serial port, but I will have to test that + there is an other option of using serial adapters.