I have 18.06.01 installed on my R7800 for the past few weeks. On 2 occasions I have completely lost access to wifi, no ssid broadcast etc... and I've completely lost the ability to access the LUCI web interface.
The first time this happened, I was able to reset and get my wifi working again. But this 2nd time, I'm completely stuck, I've tried rebooting a couple of times but still no Wifi/Luci. I can ssh in and access the cli, but I'm totally stuck here now.
slh, I can still ssh to the cli so I'm hoping that I don't need to recover in that way since it's not bricked.
lleachii, Thanks, that did work. I was just hoping to fix it without having to reset everything. I've had this happen twice already, so I feel like this is just going to be a monthly thing and I wanted to figure out just exactly what's breaking. I'm new to openwrt but I do need this to be moderately reliable =)
Thanks again, maybe someone else will know something and chime in...
Yes, I couldn't connect to luci through the wired connection. I tried restarting the httpd service but that didn't help either. I had to execute firstboot to get luci ane wifi working again.
Hello,
My laptop also lost contact to LuCI after installing OpenWRT on my R7800.
My steps:
R7800 original (Stock V1.0.3.92).
I installed the 'factory' version 24.10.1 (verified hash) and
followed this to get 'AP' behavior:
After this, I checked/ticked the wan port in br-lan to include it (in 'Devices' -- needed the extra port) and
enabled wireless ..11b/g/n without configuring.
At 'save' Luci seemed to crash, blank screen in the browser.
Restarted the R7800
At that point Ipconfig showed correct IP (from DHCP ISP router), gateway and DNS.
Internet worked and there was an added Wifi 'OpenWRT' (open).
So it seemed not reaching Luci was the only issue.
Restarted the R7800 with reset, (white blinking) fixed IP4 on my HP Elitebook (192.168.1.100 - it got 169.254.239.40 from the R7800) and then connecting to 192.168.1.1 in Firefox on W10 shows a blank screen with a link:
LuCi - Lua Configuration Interface (192.168.1.1/cgi-bin/luci/), but this times out when clicked.
I am able to ping 192.168.1.1 (<1ms)
When restarting the R7800 without 'reset' it seems to boot to a continuous white light, but still only the Luci link and pinging times out ('unreachable').
I am new to OpenWRT and limited in Linux, but tried to connect via Tftpd64-4.64 (connection rejected) and PuTTY (v0.83, port 22, timed out)
My newbie questions:
How can I establish an SSH-client terminal connection to the R7800 to view files and try these 'firstboot' and 'reboot' commands? What SSH-client? What settings (in detail)? (maybe a link to a general introduction in SSH?)
How can I install the ..sysupgrade or ..uImage version through Tftp from W10 (software? settings?) and is this safe, or can I 'brick' my R7800 completely?
Any other topics to link to, covering this issue in more detail?
I hope to execute the 'Recovery process' as described by hnyman in nov 2016 here:
Contemporary Windows versions seem to ship with OpenSSH by default, so using ssh should work, but PuTTY is also fine. SSH is just a remote shell protocol, 'any' ssh client available on your OS should work.
Forget about uImage/ initramfs quickly (those are only useful if you have serial console access), or you will brick your device. Only the sysupgrade image matters for upgrading OpenWrt, either via luci or over ssh via the sysupgrade tool (e.g. sysupgrade -n /tmp/openwrt-24.10.1-ipq806x-generic-netgear_r7800-squashfs-sysupgrade.bin; -n do not save configuration over reflash).
.
The factory image is the one to take whenever the OEM firmware is in charge, so either for the first time flashing XOR for push-button tftp recovery (and/ or nmrpflash).
Keep in mind that your local browser might cause interesting side effects as well, so deleting cookies and/ or using an incognito window might help as well.
Thanks all for the pointers. Another basic question: What is the SSH password for user 'admin'? While connecting with LuCI I did not set any password.
I am now in Fail-save mode (10/s orange blinking led), with disabled Windows Defender, but when starting an SSH session for user 'admin' there is a request for a password and nothing seems to work (and I cannot find this in this forum). TIA.
Thanks! That helped. In my 'network' file 'wan' was added (by LuCi) as port under device 'br-lan', but also still present as device under interfaces 'wan' and 'wan6'. I will follow this up in the 'Bridged AP' thread mentioned earlier.
Short update: After removing the "list ports 'wan'"-line from the 'br-lan' device in the file 'network', the connection to LuCI is back, so this previous double assignment of 'wan' seems connected to the not starting of the LuCI web-interface. I learned a lot; again many thanks for the help!