About 3 weeks ago i setup a R7800 (Netgear) with OpenWRT as a wireless accesspoint.
3 wifi networks 1 for LAN 1 for IoT and 1 for guests with seperated vlans.
This all worked great and then i left on a holiday. I came back an noticed there was no guests network anymore. So yesterday i tried to access the web gui on the IP 192.168.1.150 with no luck. Firefox just gives an error and so does Chrome. Also tried private windows and deleting cache etc. I have also explicitely tried https and http.
As we speak i am connected to the OpenWRT wifi network so i can still browse etc.The odd thing is that the router itself doesn't seem to have outside internet connection. I can't ping google dns for example.
The router is also accessible through SSH and i tried to restart the httpd service but this didnt help. As i am not fammilliar with the openwrt cli i am hoping someone would be willing to help me troubleshoot this as a hard reset would really be a last resort i don't want to do since setting this up took several hours.
ssh into it.... ( ssh root@x.x.x.x ) and run "ps -w"
look for uhttpd
run "netstat -na" look for port 80
a) is it there
b) what ip address is it on
c) what ip address are you on
if you can't ssh or ping.... try other physical ports on the router... including wan....... try all wifinetworks..... also try the default router ip and/or any other ip addresses you changed the router to.
as a last resort reset and when you set it up this time.... pay extra attention to the default / management / LAN "network"
if you really want to burn time.... you can try pre-tagging your ( client ) packets to a specific vlan..... my guess is that this is where something in what you did on the router is not quite as it should be...... a long shot but highlights all the things that are at play here.
Thank you! below is the output. There is nothing mentioned about httpd or port 80/443
is there anything from the cli i can do to make httpd listen to port 80 again?
Somebody might be able to troubleshoot that, if you would shows your actual config. The contents of /etc/config/network, firewall, dhcp, system.
you have alsotold nothing about your network topology. Is the router directly connected to internet? or is there some other router or routing modem between R7800 and internet.
Without facts it is really hard to say anything, as you have basically said just "it does not work".
Just a guess based on non-standard 192.168.1.150, "wireless accesspoint" and the failure above:
There is some other device between R7800 and internet, and that you have forgot to add proper netmask, DNS and gateway to R7800 settings. If that is true, you should follow the "dumb AP" advice.
config timeserver 'ntp'
option enabled '1'
option enable_server '0'
list server '0.openwrt.pool.ntp.org'
list server '1.openwrt.pool.ntp.org'
list server '2.openwrt.pool.ntp.org'
list server '3.openwrt.pool.ntp.org'
config led 'led_usb1'
option name 'USB 1'
option sysfs 'r7800:white:usb1'
option trigger 'usbport'
list port 'usb1-port1'
list port 'usb2-port1'
config led 'led_usb2'
option name 'USB 2'
option sysfs 'r7800:white:usb2'
option trigger 'usbport'
list port 'usb3-port1'
list port 'usb4-port1'
config led 'led_wan'
option name 'WAN'
option sysfs 'r7800:white:wan'
option trigger 'netdev'
option mode 'link tx rx'
option dev 'eth0'
config led 'led_esata'
Well, looks like I guessed right to some extent. The lan has no DNS server setting, so no wonder that the router itself can't ping google.com. You should set it pointing to your main router.
Thank you. The not being able to ping google was just something i tried but you're right that it makes sense.
I just resetted the Netgear since without the gui webinterface i figured my chances to fix this were slim to none as my knowledge of the cli is none. i wouldn't even know how to make the change you suggested.
DNS is provided on a pi-hole on a different server so i'll remember to set it up now using that.
What i find frustrating is that in my mind nothing changed and it worked perfectly before i left on holiday. I had 3 seperate WLANS all on 3 seperate VLANS provided by the edgerouter.
Lets hope when i finish setting it all up again (yes i am stupid for not making a backup of the config) it keeps working
the IP is again 192.168.1.150. I can ssh into the R7800 but the webinterface won't show up again. So basically the same problem as before (does this need a new thread?)
No idea what i am doing wrong. It's the very basic dump AP setup this time. I changed nothing to the vlans or anything else (yet)
here is the uhttpd process and parameters as listed in my ps w output. You can run a similar command to try and restart the web server.....
i'd suggest substituting the 0.0.0.0 to your internal address.
while you'll still need to get to the bottom of your issue.... there is a chance starting it manually might spit out some sort of error that will guide you to the root cause.....
I did several hard resets and got it setup now the way it used to (sort of) and i do notice that not every interface that is setup can be accessed through the GUI.
I have setup VLAN 1 on the WAN port (eth0) to connect to the edge router (because i need all 4 LAN ports) with IP 192.168.1.150 again. This i can´t access through the GUI. I have also setup a bridge for the wireless and VLAN 1 and this does provide access to the GUI.
Still not sure what i am doing wrong here but at least i now always have access on VLAN 10 (so far)
I got the same issue. I followed the Dumb AP Guide to set my R6220 (running OpenWrt 18.06.1) as an AP with the IP address 192.168.1.2 on LAN, and cannot access to LuCI anymore after configuration (SSH is still running well).
I run ps -w and found out that uhttpd is not running. I tried to run /usr/sbin/uhttpd -f -h /www -r 192.168.1.2 -x /cgi-bin -t 60 -T 30 -k 20 -A 1 -n 3 -N 100 -R -p 0.0.0.0:80, then the LuCI login page is accessable, but I can’t login using the correct password, with the “Invalid username and/or password!” message.
I got LUCI disabled right after I accidentally installed and then removed luci-ssl-nginx.
The snippets above partially help, but the thing that solved my problem, was dumb simple /etc/init.d/uhttpd --help and then /etc/init.d/uhttpd start.
option dns '192.168.1.4'