Web GUI LAN not accessible
-
I have configured the LAN interface and WAN interface on my virtual instance of pfsense, however when i try access the GUI login screen i am getting the following error:
This site can’t be reached
172.16.0.1 took too long to respond.Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
Check your internet connection.I need assistance to resolve this error?
-
@Tafy said in Web GUI LAN not accessible:
I need assistance to resolve this error?
Sorry, we can't come over to check, so you will have to communicate a bit more.
You still have the (most important) console access.
And do not forget to mention ALL VM settings, as there impact is huge .... (like : do the same setup and a bare bone system, and all will be ok). You did use one one those https://docs.netgate.com/pfsense/en/latest/virtualization/index.html right ? -
I have a virtual instance of pfsense running in Hyper V on Windows Server 2016, i have created a LAN virtual switch as private and WAN virtual switch as external. When i type the LAN ip address i cannot access the WEB GUI.
-
@Tafy said in Web GUI LAN not accessible:
When i type the LAN ip address i cannot access the WEB GUI.
That's it for the details ?
The console access says what ?
Your ipconfig /all says what ?The Internet is still accessible ? (shouldn't, because if so, your interface you use on for Windows as "LAN" isn't the pfSense LAN)
-
I have realized that the issue could possible be creation of virtual switches in Hyper V for the LAN and WAN.
Ifconfig shows ip address assigned for the hn0 (WAN) and hn1 (LAN).
I can successfully ping the WAN ip address from the ping host menu on the console and i can successfully ping the LAN ip address with the ping host.
However i cannot ping any other nodes on the LAN and i cannot launch the WEB GUI via the url of the LAN. -
@Tafy Both LAN and WAN v-switches should be created as External if you want to access pfSense from your LAN. Private will only allow VM-VM connections (not even to the host).
-
@provels said in Web GUI LAN not accessible:
Both LAN and WAN v-switches should be created as External if you
https://docs.netgate.com/pfsense/en/latest/virtualization/virtualizing-pfsense-with-hyper-v.html says not the same thing.
WAN should be External.
LAN is setup as Private on that page ... and if recall well, that is how I run pfSense @home using a Windows 10 Pro .... -
Depends on the network architecture. If it's a workstation VM on the same host as pfS VM, it (Private) would work. But not for Inet access for anything downstream on the LAN, not even the host. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/create-a-virtual-switch-for-hyper-v-virtual-machines
