Hello,
I'm trying to install RouterOS on my device hEX S, however Netinstall fails to detect the router.
I tried both Windows and Linux w/o success based on this tutorial.
Can you please advise how to fix this issue?
THX
Re: Netinstall fails to detect router - cannot install RouterOS
The device is bricked, or you still can access the configuration?
Re: Netinstall fails to detect router - cannot install RouterOS
Well, I'm not sure if the device is bricked.
Actually, I don't think so because I can do this, means I can load OpemWRT's initramfs.
Using netinstall I get this:
This means, the client is identified, but netinstall fails to load the the *.npk package.
Actually, I don't think so because I can do this, means I can load OpemWRT's initramfs.
Using netinstall I get this:
Code: Select all
$ sudo ../netinstall -a 192.168.88.20 routeros-mmips-6.48.6.npk
Using server IP: 192.168.88.10
Starting PXE server
Waiting for RouterBOARD...
PXE client: 08:55:31:4C:B7:5C
PXE client: 08:55:31:4C:B7:5C
PXE client: 08:55:31:4C:B7:5C
Last edited by cmonty14 on Sun Apr 24, 2022 2:49 pm, edited 1 time in total.
Re: Netinstall fails to detect router - cannot install RouterOS
I guess the issue is that router expects DHCP.
There's a similar issue here.
So, I configured a DHCP server on my ethernet port connected to router's ethernet port 1.
The log of DHCP server shows:
Starting netinstall fails with error:
Any idea how to fix this?
There's a similar issue here.
So, I configured a DHCP server on my ethernet port connected to router's ethernet port 1.
The log of DHCP server shows:
Code: Select all
$ sudo dnsmasq -dd -C /etc/dnsmasq.conf
dnsmasq: gestartet, Version 2.86, DNS abgeschaltet
dnsmasq: Optionen bei Übersetzung: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, IP-Bereich 192.168.88.20 -- 192.168.88.100, Leasezeit 1d
dnsmasq-dhcp: 245898967 verfügbarer DHCP-Bereich: 192.168.88.20 - 192.168.88.100
dnsmasq-dhcp: 245898967 "Vendor class": MMipsBoot
dnsmasq-dhcp: 245898967 Marken: bootp, known, enp5s0
dnsmasq-dhcp: 245898967 BOOTP(enp5s0) 192.168.88.20 08:55:31:4c:b7:5c
dnsmasq-dhcp: 245898967 nächster Server: 192.168.88.10
dnsmasq-dhcp: 245898967 sent size: 4 option: 1 netmask 255.255.255.0
dnsmasq-dhcp: 245898967 sent size: 4 option: 28 broadcast 192.168.88.255
dnsmasq-dhcp: 245898967 sent size: 4 option: 3 router 192.168.88.10
dnsmasq-dhcp: 245898967 sent size: 6 option: 12 hostname iptime
Code: Select all
$ sudo ./netinstall -a 192.168.88.20 routeros-mmips-6.48.6.npk
Using server IP: 192.168.88.10
Starting PXE server
Waiting for RouterBOARD...
bind bootp failed: Address already in use
Last edited by cmonty14 on Sun Apr 24, 2022 4:59 pm, edited 1 time in total.
Re: Netinstall fails to detect router - cannot install RouterOS
Netinstall contains (striped down version of) dhcp/bootp server, so there should not be another such server running anywhere near netinstall "network".
Re: Netinstall fails to detect router - cannot install RouterOS
cmonty14,
I’ve never tried netinstall from Linux… only Windows 10 on an underpowered HP laptop. I never could get my RouterOS devices to reliably show up in netinstall until the day I put an inexpensive, unmanaged Ethernet switch between the laptop and the RouterOS device. Doing that keeps the laptop's Ethernet port up and active 100% of the time so it's ready to communicate with the RouterOS device the instant it enters etherboot mode. Now RouterOS devices show up in netinstall every time with ease.
You might give a network switch a try.
John L.
I’ve never tried netinstall from Linux… only Windows 10 on an underpowered HP laptop. I never could get my RouterOS devices to reliably show up in netinstall until the day I put an inexpensive, unmanaged Ethernet switch between the laptop and the RouterOS device. Doing that keeps the laptop's Ethernet port up and active 100% of the time so it's ready to communicate with the RouterOS device the instant it enters etherboot mode. Now RouterOS devices show up in netinstall every time with ease.
You might give a network switch a try.
John L.
Re: Netinstall fails to detect router - cannot install RouterOS
Try to have a direct cable connection between computer and device.
A trick which helps for some is to only use a dumb switch in between, nothing else connected.
Make sure all other network ports on that computer are disabled. Check, you'd be surprised what still will be active even though you think it's not working.
You may have to try several times before it works.
Using Windows I am having quite some problems recently as in: doesn't succeed at all anymore even though the device shows up (and funny enough, I was able to get it working in the past using that same win-laptop).
Using Linux (separate machine which normally would have been thrown away already for years...) it works almost first time right all the time (just did it again on hAP AC3).
A trick which helps for some is to only use a dumb switch in between, nothing else connected.
Make sure all other network ports on that computer are disabled. Check, you'd be surprised what still will be active even though you think it's not working.
You may have to try several times before it works.
Using Windows I am having quite some problems recently as in: doesn't succeed at all anymore even though the device shows up (and funny enough, I was able to get it working in the past using that same win-laptop).
Using Linux (separate machine which normally would have been thrown away already for years...) it works almost first time right all the time (just did it again on hAP AC3).
Re: Netinstall fails to detect router - cannot install RouterOS
Thanks for your advise.
However it's not working using
- a standard switch
- connecting ethernet port 1 of router to switch
- connecting ethernet port of Windows 10 laptop to switch
- starting netinstall version 6.40.9
- setting client IP address in "Net booting > Boot server enabled"
I struggle with the duration for pressing reset button, though.
Before starting up router I press the reset button for 5, 10, 15, 30 seconds.
But the router is not displayed in netinstall.
However it's not working using
- a standard switch
- connecting ethernet port 1 of router to switch
- connecting ethernet port of Windows 10 laptop to switch
- starting netinstall version 6.40.9
- setting client IP address in "Net booting > Boot server enabled"
I struggle with the duration for pressing reset button, though.
Before starting up router I press the reset button for 5, 10, 15, 30 seconds.
But the router is not displayed in netinstall.
Re: Netinstall fails to detect router - cannot install RouterOS
In case this helps…
I’m assuming you are following ALL other steps outlined in the Mikrotik wiki, then what I found worked best timing wise is to hold the reset button for an additional 5 seconds after the power LED goes out, then release it. The RouterOS device will appear in netinstall within a few seconds after that.
John L.
I’m assuming you are following ALL other steps outlined in the Mikrotik wiki, then what I found worked best timing wise is to hold the reset button for an additional 5 seconds after the power LED goes out, then release it. The RouterOS device will appear in netinstall within a few seconds after that.
John L.
Re: Netinstall fails to detect router - cannot install RouterOS [SOLVED]
Just keep pushing until it shows up.
Re: Netinstall fails to detect router - cannot install RouterOS
Issue is fixed.Just keep pushing until it shows up.
Obviously I didn't push reset button long enough.
Thanks for your support.
Re: Netinstall fails to detect router - cannot install RouterOS
Fixed it for yaObviously............... I didnt pay attention to the instructionsJust keep pushing until it shows up.
1 - Post #3, requested you read the link!! Para H.
H. NETINSTALL - should be used if any security concerns arise OR if your firmware version seems to be acting strangely or the firmware version is really old!!
Another way of getting your unit(s) up to date is to netinstall devices. I would say it's preferred because it also installs recent default configuration while upgrades convert running configuration. A few versions between your running ROS and current one brought some big changes and it is possible for upgrade process to fail to convert old config to new one. In addition, new default config makes much more secure setup in certain aspects. In other words, if you are many firmware versions behind, netinstall is the least painless way to get to the latest config and is more secure.
Sage tips/advice on NetInstall......
a. Regarding Etherboot for all devices, the most error-free method is - to press the reset button, keep it pressed, power on the device, and wait until the device shows up in the NetInstall window, then release the button. This holds true for the Audience as well.
b. Try to have a direct cable connection between computer and device (laptop to device for example).
c. A trick which helps for some is to only use a dumb switch in between, nothing else connected.
d. Also on THE COMPUTER being used to run netinstall, there may be issues if there are multiple NETWORK interfaces. If experiencing difficulties on the PC, it is best to ensure all other NETWORK interfaces are turned off.
Re: Netinstall fails to detect router - cannot install RouterOS
I have two identical revisions of hAP AC^2. One of them is detected by Netinstall, the other is not while using the same setup (Windows PC -> dumb switch -> hAP, other network interfaces temporarily disabled). Currently, both are running OpenWRT just fine (the devices boot up even after complete power cycling, ethernet and WiFi works) with the exception that one uses RouterBoot v6 to boot OpenWRT while the other uses v3 (most probably the factory backup bootloader because I never tried to install any ROS v3 package on any of them since they were working with ROS v6 and firmware auto-update was enabled). So I can't reinstall ROS. The strange thing is that I can boot the OpenWRT initramfs with pxesrv. Any ideas?
Re: Netinstall fails to detect router - cannot install RouterOS
If using OpenWRT or simular non Mikrotik OS, you may swithed the RouterBoot(Firmware) from BOOTP to DHCP.
And Netinstall doesn't support that.
You have to do like i have done in this thread.
viewtopic.php?p=1044565#p1044565
To switch back to BOOTP so you can use Netinstall program again.
And Netinstall doesn't support that.
You have to do like i have done in this thread.
viewtopic.php?p=1044565#p1044565
To switch back to BOOTP so you can use Netinstall program again.