Hello, I tried to configure my Mikrotik RBM33G device, and performed reset it with “No Default Configuration” and “No Backup” options. This caused the device do notrespond on address 192.168.88.1 anymore, and I can not reset it to initial configuration. Please help!
At the moment both blue and green leds of the device are lighted and central chip is very heating! I can not suggest what is happening
Thanks in advance,
Alex
It wont respond to its address 192.168.88.1 because there is no configuration anymore. So there is no such address.
Connect a computer to your ethernet port and login by mac.
Also you can return back to the configuration you were, the default one, by using the reset button on your device.
What command shall I type in linux command line? I tried “arp” command but it requires subnet mask which is unknown for mac-addresses…
It does not work – if I press the button on power-on, nothing happens. The chip of the routerboard is really hot and both leds (blue and green) are lightening. Small leds on LAN connector are alive and do blink as usual (when ethernet connector is on).
Just after resetting and rebooting only blue led were lightening, but after ~1 hour of power-on I had a look at the device – it was hot and both leds were lightening. What could happen?
Unplug power
hold reset button
apply power
wait until usr led starts blinking (about 5-10s)
release power.
Should be back to factory config.
Once more – it does not work at the moment.
It worked before but not now.
It should work…
No, unfortunately it is not responding. Just after reset it was in operation (but it did not allow to restore settings), but after 1 hour of standing by it has broken. I am not aware how it happened.
Now I’m looking for a way to upload firmware or any hardware jumper settings maybe… Unfortunately the documentation on jumpers is very poor.
Try Netinstall…
Zacharias,
Could you please do not quote full previous posts in your answers if there is no need for that.
Just use big button “Post replay”
You can try this tool on Linux/Mac: https://github.com/haakonnessjoen/MAC-Telnet
Why not to use Winbox with MAC address?
I will try now, today I bought RS-232 cable and now I will install windows in Virtual-box, then I will be able to try Winbox.
Because the OP asks about Linux command to connect using mac-telnet. Obviously he can run WinBox in a VirtualBox guest.
you can also run winbox under wine with mac-winbox working OK - can be a bit iffy but it does work. Sometimes you have to wait for the device to go to link-local address (wont detect the router while still searching for IP) or just set a static IP. Once connection ‘established’ on your linux box, winbox in wine should be able to see neighbor devices.
I’m in the same situation and can’t connect to 192.168.88.1. how can I connect via MAC (I mean where I find the MAC number).? (i use win 10)
I’m in this situation even though I used the reset button. if even this solution does not work Netinstall is the only solution left?
One technique I have used, as a linux user, to check if the router is alive when I lost configuration and the machines have ipv6 package active, is to plug an ethernet cable from my laptop to the router, ensure that the link is up on the linux side and
# use your eth interface name instead of eth1
$ sudo ip link set eth1 up
$ ping ff02::1%eth1
64 bytes from fe80::f8f8:5ac1:5ac8:31f8%eth1: icmp_seq=1 ttl=64 time=0.126 ms
64 bytes from fe80::b869:f4ff:fe89:9efb%eth1: icmp_seq=1 ttl=64 time=2.02 ms (DUP!)
^C
ff02::1 is the all-hosts ipv6 multicast address. You should receive at least two responses, one from the local host,
another from the router itself. More responses can come if the router has several bridged/switched interfaces.
Then your can try to log in using the local address from the DUP node:
ssh admin@fe80::b869:f4ff:fe89:9efb%eth1
...
and continue recovering the machine
I guess, maybe Software is totally erased (system and bootloader) OR maybe hardware is burned out.
Similar topic [Solved]Recover from “No Default Configuration” System Reset does not help.
Netinstall can be pretty fickle, if you have another device you know works, try see if you can get netinstall to recognise that instead.