I bought me a brand new CRS112-8G-4S-IN router wich i will use as a switch.
When i logged in with the 192.168.88.1 adress al went fine till i changed the adress to 192.168.1.5.
I did a soft reset, a hard reset, it doesn't matter the router is not responding.
Sure i can buy the console cable and try to connect, but i think that is not the way for now.
I have used Winbox, but even Winbox doesn't see the router.
The reset button has several options. This is mentioned in the guides.
Wit 5secs you make a soft reset wich don't erase the complete system. With 10 or 15 secs it will go in a Netloader menu. You can't ping the box, cause igmp pings get blocked, so Nmap is the tool to use here.
Right after my post i got a connection via lan.
I can conclude that it take a while before the box is fully started, wich i did.
Perhaps i must have more patiance...
Ehm, there is no "soft" or "hard" resets in MikroTik. When pressening the reset button, it will after 5secs enter regular reset mode, which completely resets the device to the factory defaults. After 10secs, it enters "CAPS" mode, which is essentially a mode for their wifi devices to be adopted into a capsman controller (and it bridges all ports, so it essentialy sets the device to bridge/switch all ports like an unmanaged one), and after 15 seconds, it will enter netboot, which will attempt to boot from the network in order to re-install the device from a second device in case the firmware/update/upgrade breaks. This last step is like formating the disk and installing it from scratch.
Read more on how and what each step does here:
To me, it sound like you are connected to either a port that is the wan port (ether1 usually) or it might be in SwOS (switch os) mode which i'm not sure how it usually appears to Winbox.
But what you wrote isn't precise.
Usually it means...
soft reset = simply reboot by software inside the os
hard reset = unplug the power and similar
factory reset = netinstall and/or follow reset button for reset config
("system reset configuration" do not do a real factory reset as intended...)
and you can do all.
is not netboot is etherboot
*
Neither.
That model does NOT support SwOS and does NOT have a default WAN configuration, being a switch...
And then the user has already wrote that he solved the problem... (just wait the slow device reboot after reset).
Only for the record, what I was referring to is the actual distinction in reset (NOT CAPS, NOT NETINSTALL) which is whether the primary or backup bootloader will be used at boot.
You press the reset button BEFORE[1] applying power= backup bootloader
OR:
You press the reset button IMMEDIATELY AFTER[2] applying power= primary bootloader
THEN:
Keep the reset button pushed UNTIL the led start flashing.
BOTH are the SAME reset (hard, as opposed to the soft one done via software, as rextended explained).
Anyway, all is well that ends well.
[1] this is the "easy" one
[2] this can be more difficult as the "immediately after" might be complicated as the "feedback" from the reset button is not very strong, and you may not press it fully in the short time allowed, so it is possible to "miss it"
Appreciate your help.
The reset procedure was confusing for a newbie like me meaning soft reset hard reset etc. It turns out that the reset button is a combi-button where you can make 3 (!) ways of resetting. Now i know Also i must have give the box some time to start up, wich i didn't.
I'm on Linux and you can't use Winbox, meaning you have to install Wine64 wich i did, and all working flawless now.
All ends well.
When i consult the documentation then there are 3(!) way's of resetting.
After 3 secs, after 5 secs, and after 10 secs. Why in the name of the Lord engineering came up with this? i don't know.
A soft reset isn't mentioned in the docs, but is a accepted term for making a reboot without losing configuration. Perhaps i must more clarify in this matter.
Nevertheless, the box is alive, and i thank everybody with suggestions or helping me out here.
Not really-really.
The (good ol') Winbox 3.x runs only on Windows (and WINE) but the new (arguably "better") Winbox 4.x runs on Linux (and even MacOs) natively.
The (good ol') "but I'm different" or "I use this other Os (implied, because it's so much better than Windows)" does not stand anymore.