An hour ago I succeeded to install OpenWrt on my Kimax BS-U35W.
When trying to change the static IP address to connect to my router, unfortunately I accidently touched the delete button of the br-lan interface.
I could not undo or reset this, no option.
So I powered off my BS-U35 and powered on again. But unfortunately I cannot connect to the device anymore.
Using the Reset button didn't help; looks like it does not work (?)
How can I fix this problem?
Any help is much appreciated.
You should be able to recover using failsafe mode. From there, you can either fix the mistake (re-add the interface), or simply reset to defaults. Keep in mind that you'll need to do this via ssh since the web server is not active in failsafe mode.
Thank you Peter for your reply.
I followed the link to 'Failsafe and Reset', and read the Failsafe section.
With a direct Lan cable from my PC to the BS-U35WF and setting a static IP on my PC I get a network connection to 192.168.1.1
First I tried in the terminal ssh root@192.168.1.1 with result: port 22: No route to host.
The doc says: Try LAN1 port first. But there is no explanation how to do that.
I searched on the internet and then I used ssh root@192.168.1.1 -p LAN1, with result: Bad port LAN1.
Can you tell me how I would do that?
Edit:
I also tried ssh root@192.168.1.1 -p enp3s0, result: Bad port enp3s0.
I also cannot ping to 192.168.1.1, result: host not reachable.
Thank you in advance.
You need to plug in your computer to port 1 of the router.
make sure that there are no other active network connections (your computer should have no other ethernet connections and wifi should be disabled; the router should have no other connections except the single ethernet and power).
Your computer's ethernet should be configured with a static IP 192.168.1.x where x is between 2-254, subnet mask 255.255.255.0.
Then verify that you've actually entered failsafe mode by looking at the LEDs on your device... one of them should be blinking rapidly (~10 times/sec) to indicate that failsafe is active.
At that point, you should be able to ping 192.168.1.1 and then ssh (ssh root@192.168.1.1).
First, my device is not a normal router.
It is a Kimax / Blueendless BS-U35WF external network drive with a sata board and a Wifi board in it.
The original firmware had kind of a router function in it.
This device is supported by OpenWrt and I installed the recent OpenWrt firmware and sysupgrade bin files on it.
The device has a Blue and a Red Led on it; blue (was) for the hard drive and red for the Wifi.
When I now power on the device then first goes the blue Led on. When the HDD is spinning up, both Leds start blinking - the Blue Led much faster than the Red Led.
A number of seconds later the Red Led stops blinking and the Blue Led becomes steady.
So I guess the device would be in Failsafe mode.
Then I connect the Lan cable from my PC (with static IP 192.168.1.143 and 255.255.255.0, gateway 192.168.1.1 and DNS 192.168.1.1) and I have a network connection.
But a ping to 192.168.1.1 still gives me: Destination host unreachable.
And ssh root@192.168.1.1 still gives: port 22: No route to host.
I don't understand what is wrong now.
Any more ideas what I can do?
No.... as I said earlier (and is also discussed in the failsafe wiki article), at least one LED should be blinking rapidly and continuously when it is in failsafe mode.
Did you follow the guide? Specifically, you need to apply power to the device (or flip the switch on) and then immediately start pressing the reset button. I recommend pressing and releasing repeatedly (quickly)... basically like button-mashing when playing a game.
@psherman,
I tried a few times with pushing immediately the Reset button.
One time with holding pushed in for 60 seconds, also with repeadedly pressing the Reset button on and off for 90 seconds; but and the end the Leds stop blinking.
So still no ping on 192.168.1.1
What can I try next?
I don't think there are any other buttons to press.
You may need to use serial at this point. Or, if the device has a TFTP recovery mode, you can reinstall the image that way.
Indeed, the device has no more buttons.
While there is ethernet connection, is there no other program that could access the device?
How can I determine if the device has a TFTP recovery mode?
About using a serial connection, the device has no serial port; I would have to create a serial port myself. However, I am not familiar with that.
I have searched already on the internet, but the problem (for me) is that de information is fragmented and summier and or not complete.
I really don't know what i can do best now; I am not a wizzkid (I am 74), so it's not easy for me).
Failsafe is the only way you can get OpenWrt to load with a known/default configuration (i.e. not the one that was accidentally messed up) without resorting to other methods like serial.
There is a serial port inside according to the device info page:
And it seems that the bootloader is uboot, so you can probably use tftp if required, but you'll probably need serial to get into the menu. You can try the generic debricking link.
@psherman,
thank you for the extra information.
The device also has a USB 3 port; is that maybe a possibility to use?
I doubt it, but you can try.
Okay, I don't know something about using the USB-port for that.
So I will first read about 'generic debricking' you mentioned.
Thank you so far for your help.
Hi, I'm getting back here with an update.
I ordered a Serial UART USB device (with FTDI chip) and I succeed to communicate with my BS-U35WF using Minicom.
I see Openwrt booting.
During this booting I see messages on the screen wirh:
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and [enter] to select the debug level
And 27 lines further:
Please press Enter to activate this console.
I tried all those options but no response; it just keeps booting.
The last line of the booting is: [153.136608] urngd: v1.0.2 started.
I don't know what that means.
Below that I entered 'firstboot', and 'reboot', but nothing happens.
Unfortunately, the Failsafe document on the Openwrt site doesn't give me information what I must do; not even what I should expect to see.
Can somebody tell me what I must do to enter commands for Openwrt?
If the input isn't working (from your keyboard to the device), that suggests a problem with the connection between the serial adapter on the host (the tx from that) and the rx pin on the OpenWrt device. It could also be voltage level related if -- make sure the output level of the serial adapter is correctly configured.
@psherman,
thank you for your info.
My serial device is set on 3.3 V, which is mentioned multiple times on forum(s).
I switched the RX and TX connection, but then nothing gets shown in Minicom; so the settings would be correct.
While I see the boot process on screen in Minicom, it looks to me that the serial device is working correct.
I just don't know in what state the connection is after Openwrt is 'ready' booting.
Am I then in the Openwrt console? Or what?
Do you know which command to use now?
Thank you in advance.
At this point, did you see your typing in the console? did you see any responses from the firstboot and reboot commands?
Hi psherman,
At this point, did you see your typing in the console?
When I set 'E'cho on in minicom then I see my typings in the console.
But that is probably the Minicom console, not the OpenWrt-console (?).
did you see any responses from the firstboot and reboot commands?
No, unfortunately not.
I tried multiple times power on the device and pushing the Reset button at different moments during the boot process, but I didn't see any changes in the Minicom console.
I made screenshots of the whole boot-process and uploaded them, see below.
(I can only upload one screenshot per post.)
