Excellent. Is there a way to access the device over USB port via serial adapter or something??Yes, you missed reading the specs before buying it.
But this doesn't connect to serial console? It is only for running routeros devices?Sure, there is the WOOBM:
https://www.youtube.com/watch?v=2yWrUQ_woKQ
Could you please provide me the with the thread link? I can't find it.Do not work on v7, see other topic about that.
Could you please provide me the with the thread link? I can't find it.
Backup for what? For have serial port onsite or use remotely the serial port?This said, 5009 is a great device, but without serial I can't implement it anywhere as there is no backup access.
Backup for what? For have serial port onsite or use remotely the serial port?This said, 5009 is a great device, but without serial I can't implement it anywhere as there is no backup access.
Thanks, there might be issues, but on my HAPac2 it does work well with v7, just tested it, could connect via WOOBM:Do not work on v7, see other topic about that.
[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
I get where your coming from – want to get in if the router is FUBAR...Is there a way to access the device over USB port via serial adapter or something??
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.I got a reply re connectivity -> USB-serial-nullmodemcable-serial-usb contraption should work no problems.
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.As for woobm I am still not sure if that is console connection or terminal connection.
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.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.
Not sure about TTL boards. What benefit do they bring? I need a robust solution that I will use once or never and that will always work.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.I got a reply re connectivity -> USB-serial-nullmodemcable-serial-usb contraption should work no problems.
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.As for woobm I am still not sure if that is console connection or terminal connection.
So it's USB serial console terminal with WEB UI.
Yes, it is better, but I am not happy.Probably there are some stuff lost in translation.
1. You CAN use serial<>usb adapters to connect to your RouterOS, IF: that adapter is properly recognized and configured under RouterOS and if RouterOS is functional.
2. You CAN'T use serial<>usb adapters as a debug port (if RouterOS crashed for some reason and it doesn't boot): RouterBOOT has disabled serial console output on the devices that have no serial port from the factory and it's not configured to output to some random USB device anyway.
Better?
I support that. Even if going to the board directly if there are headers there, that would be a viable option to recover router that died. Or make header ourselves. The current way is kind of no go.Let's make a request for MikroTik to make that setting an option? Something that can be flipped the same way other RouterBOOT settings can?
Exactly what I did. I decided to put 5009 as a core router in my LAN, and 4011 I salvaged last month exactly thru serial console connection will be used for testing.Any router that might be designed for use as a test bed or lab environment should be designed with a serial port.
The fact that the RB5009 wasn't baffles me. Initially, it looked attractive till I saw the serial port wasn't there..
Just get a RB4011 instead..
-tp