You are here

No access to MikroTik WLAN-Bridge SXTsq Lite5 after firmware upgrade

8 posts / 0 new
Last post
No access to MikroTik WLAN-Bridge SXTsq Lite5 after firmware upgrade
I have two MikroTik WLAN-Bridge SXTsq5nd Lite5.
I was able to upgrade one device with the firmware. I did the same with the second device (several times), but in the end I still can't access it with "localnode.local.mesh:8080".
Here are the steps I took:
Device: SXTsq5nd Lite5
Firmware: aredn- 
Rename this to "rb.elf" and upload with "pxesrv.exe".
Then make the update with this file: aredn-
It seems that the Lite5 did the reboot, but I can't get to it with localnode.
Does anyone have any ideas?
Any help will be greatly appreciated here.
73 de Mac, HB9EMS 
K6CCC's picture
Personally I NEVER use

Personally I NEVER use "localnode..." to get to any node.  If I have not set a node name on a new flash, I will ALWAYS use the IP address to get to the node.  To determine the IP address, open a command window (assuming a Windows computer here - linux has an equivalent), and type ipconfig [Return].  That will give something like this:


Windows IP Configuration

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :


The Default Gateway address is the node you got an IP address from.  Note that the sample above was NOT on an AREDN connected computer - hence the IP range and subnet.


kc8ufv's picture
While James's suggestion will

While Jim's suggestion will work, it's an extra step to take. I normally use the localnode.local.mesh when setting up new nodes, or if I don't know what node I'm on (multiple nodes connected situation). I always make sure to specify it as http://localnode.local.mesh, though. The firmware should recognize port 80, which is the standard port for HTTP traffic. I've seen some act finicky on the alternative port of 8080 if it didn't redirect there itself, which, by internet standards, is a non-privledged port, meaning it's intended for user level programs.

K6CCC's picture
I will stand by my statement
I will stand by my statement of using IP addresses.  In another forum thread, a user had a "bricked" USB-150.  Ultimately, he mailed it to me, and by using the IP address, I was quickly able to determine that the node was in the AREDN first boot state.  Did the first boot config and the node is working fine in all respects.
BTW Chrissy, I normally go by Jim, not my formal name James.
kc8ufv's picture
Sorry about that. Fixed.
Sorry about that. Fixed.
No IP address ...
Thank you very much for your help.
I'm going mad ...

The access point on the left in the picture works. The green LED next to the person symbol is lit.
The access point on the right of the picture is not working. The green LED next to the PC symbol is lit.
And I can't address it by IP address because it doesn't output an IP address on the PC.

What can I do?
73 de HB9EMS
Image Attachments: 
kc8ufv's picture
In that case, did you make it
In that case, did you make it to uploading the sysupgrade version? I think that sounds like it may have failed to load that fully, in which case starting the process over should resolve it. 
nc8q's picture
starting the process over should resolve it.

+1 with Chrissy kc8ufv.
Else, if the firmware load seems to fail,
try to ping the device at to see if the .elf (initramfs) or .bin is still loaded.
Else, try to ping the device at default RouterOS address.
Else, you may have faulty hardware.

73, Chuck


Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer