How to access web GUI when internet goes down?
-
Unlikely. Even with no battery it should only lose time when the machine is powered off.
If it crashes in software there should be a crash report generated. If the hardware simply stops responding with nothing logged that's usually a hardware issue.
Steve
-
@pfew said in How to access web GUI when internet goes down?:
The LAN port is the internal NIC of the Dell Wyse because I was having trouble with the LAN port when set up on the QNAP card. Not sure if that's related to this issue.
I suspect if you had issues with the card as a LAN interface it is having the same issues as your WAN interface.
-
@stephenw10 this is the last error message I got before it crashed again this morning
Sep 14 07:52:57 php-fpm 373 /rc.newwanipv6: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1663163577] unbound[27214:0] error: bind: address already in use [1663163577] unbound[27214:0] fatal error: could not open ports'
-
@stephenw10 "Ctrl + t" does work on the console. I was also able to reboot using the console this time.
I unplugged the wifi router and plugged my computer directly into the LAN port during outage. I was unable to ping 192.168.1.1 and the web gui was not working
-
@pfew Do you have a switch that can do VLANing? I would remove the QNAP NIC and see if VLANing the WAN to the LAN interface and setting a shared port config resolves your reboots.
-
@rcoleman-netgate I do not own a switch that can do VLAN.
-
Ok, if you were able to reboot from the console can I assume the console was fully functioning?
If so were you able to see what IP addresses were shown for the interfaces?
Or try any other tests like pinging out to 8.8.8.8 from the firewall itself?
You need to try to pin down what's actually failing here. That Unbound error usually only means it tried to start twice and shouldn't cause a problem. Certainly it wouldn't prevent you connecting to the firewall LAN by IP address.
Steve
-
@stephenw10 another incident happened today. The console was fully functional, and I was able to ping out to 8.8.8.8
My thought is that the built in NIC I was using for LAN was a RealTek NIC, and I've heard that RealTek NICs cause problems. I decided to reset to factory settings and use the ports of the QNAP card for both WAN and LAN. This time it set up correctly.
-
Mmm, Realtek NICs certainly can stop passing traffic like that. You would normally see a watchdog error from the driver in the logs though.
Steve
-
@pfew said in How to access web GUI when internet goes down?:
https://www.amazon.com/QNAP-QXG-2G2T-I225-2-5GbE-4-Speed-Network/dp/B0923FL2K3/ref=psdc_13983711_t3_B08FB83C1H
This card (NIC - QNAP-QXG-2G2T-I225-2-5GbE-4-Speed-Network) is based on an Intel i255-LM Chipset. that offers some different speed options | 10/100/1000/2500 MBit/s
It can be that the negotiation is not working well or proper out of the box!I'm guessing a monitor must be connected at bootup.
Would be the best to copy and paste us here the output
using the code (</>) option shown above if you are text writing and answering. -
I wanted to give an update. My internet has not been interrupted for 25 days using the QNAP card for both WAN and LAN.
I have not tested a crash yet by unplugging the WAN port but eventually I'll get around to trying that.
