Can't Access Webgui while hooked up to internet
-
@mercurynormanbates When you look at both the WAN NIC of your Sophos when connected to your modem and the modem NIC, are the link LEDs on for each NIC? For each NIC, one LED should be on solid and the other should flash when passing traffic.
-
@kom his NO CARRIER posting would say its not connected to anything or any lights. It sure not going to work if it has no carrier..
-
What makes Windows not pull a gateway or not set on like that? The rest looks like DHCP.
Already something with that IP on the system?There's enough confusion here for 3 threads!
I would connect to the pfSense console and test from there to avoid it.Steve
-
@stephenw10 said in Can't Access Webgui while hooked up to internet:
There's enough confusion here for 3 threads!
Agreed - another thing that seems "off" here - his pings to 192.168.1.1, 2 and 3ms response?? On a lan over a wire? That makes no sense - so is his client wireless?
-
Yeah, I'd guess there's another interface using that IP. But speculation...
-
This post is deleted! -
Does it not have a serial console? Much easier to copy/paste from.
The EFI shell is what the BIOS is booting to if it can't find anything else to boot from. Or you choose to boot to it. It shouldn't boot to that unless interrupted but it's not related to the WAN issue.
At the console menu hit option 8 to reach the shell and run:
ifconfig -a.Check the state of WAN. If it's connected to the modem it should at least show linked.
If it's not but there are link LEDs shown then check the other NICs, it might be connected to igb2 or igb3.
Steve
-
Thank you all for your help. I was able to get it working again and was able to get ProtonVPN on it without incident. I appreciate all of the troubleshooting help.
-
@mercurynormanbates Don't leave us hanging here. What did you do to get it working? What was the missing piece of the puzzle?
-
@kom So when I factory reset the router with pfsense on it, for some reason it reset the port assignment so that the port labeled WAN on the device was not the actual WAN port anymore. The LAN/WAN ports went from being assigned to ports igb1/2 to igb0/1. On top of that, the way the ports were numbered and labeled is not very intuitive (at least not to me)
It basically goes like this:
First port: labeled LAN, (igb1)
Second port: labeled WAN (but not WAN) is (igb2)
Third port: (ibg3)
Fourth port: actual WAN port on factory reset (igb0)So the "0" port is the 4th port and is, of course, not labeled WAN but became the WAN port upon factory reset.
I did not think igb0 referred to the 4th port or that the factory reset reassigned the ports. Once I finally figured that out, it was simple. Like I said, I am pretty much a noob, but there you have it. I was finally able to get pfsense up and running with the VPN, added wireless, etc after that. It's no wonder everyone was so stumped.
