Can someone help me please? I can't access to pfsense web GUI.

javierrz

I'm new to working with pfSense and firewall OS in general. At first, I managed to install pfSense on a virtual machine in VMware, and I was able to access the GUI, but now I can't access it. I checked the LANs in VMware and the network configuration of the device I want to use to access the GUI several times, and they are correctly configured. The firewall is configured with an interface using DHCP that assigns an IP address to the device, and the device receives it correctly, but even so, it doesn't work.

I even decided to create another virtual machine to see if, by chance, it would work, following the same steps I took the first time when it worked, but nothing, it remains the same.

VMware Virtual Machine - Netgate Device ID: d5ee4f1f510621abfd4a

**** Welcome to pfSense 2.7.2-RELEASE (amd64) on pfSense ***

WAN (wan) -> em0 -> v4/DHCP4: 192.168.1.150/24
v6/DHCP6: 2a0c:5a80:3000:b900:20c:29ff:fe66:2f

LAN (lan) -> em1 -> v4: 192.168.1.1/24

OPT1 (opt1) -> em2 -> v4: 200.75.65.15/16

Windows:

Adaptador de Ethernet Ethernet1:

Sufijo DNS específico para la conexión. . : home.arpa
Descripción . . . . . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection #2
Dirección física. . . . . . . . . . . . . : 00-0C-29-18-D2-87
DHCP habilitado . . . . . . . . . . . . . : sí
Configuración automática habilitada . . . : sí
Vínculo: dirección IPv6 local. . . . . . : fe80::d81c:6998:2104:2404%8 (Preferido)
Dirección IPv4. . . . . . . . . . . . . . : 200.75.65.18 (Preferido)
Máscara de subred . . . . . . . . . . . . : 255.255.0.0
Concesión obtenida. . . . . . . . . . . . : lunes, 14 de abril de 2025 19:03:19
La concesión expira . . . . . . . . . . . : lunes, 14 de abril de 2025 21:03:18
Puerta de enlace predeterminada . . . . . : 200.75.65.15
Servidor DHCP . . . . . . . . . . . . . . : 200.75.65.15
IAID DHCPv6 . . . . . . . . . . . . . . . : 402656297
DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-2F-84-75-AA-00-0C-29-18-D2-7D
Servidores DNS. . . . . . . . . . . . . . : 200.75.65.15
NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitado

bmeeks

@javierrz said in Can someone help me please? I can't access to pfsense web GUI.:

WAN (wan) -> em0 -> v4/DHCP4: 192.168.1.150/24
v6/DHCP6: 2a0c:5a80:3000:b900:20c:29ff:fe66:2f

LAN (lan) -> em1 -> v4: 192.168.1.1/24

This is incorrect. Your WAN and LAN interfaces cannot reside in the same network. They must be in different subnets.

Second, your Windows machine will likely need to have a route added so that it knows where to find the pfSense VM. I see no 192.168.x.x addresses listed in your Windows machine's interface addresses.

javierrz

@bmeeks
I managed to get it to work following what you told me. I configured the LAN interface correctly, and it finally worked, and I added the route to Windows. However, I don't understand why it cannot be accessed from the other interface OPT1, which was the one I was trying to use to access the GUI despite having done "the same configuration".

bmeeks

@javierrz said in Can someone help me please? I can't access to pfsense web GUI.:

@bmeeks
I managed to get it to work following what you told me. I configured the LAN interface correctly, and it finally worked, and I added the route to Windows. However, I don't understand why it cannot be accessed from the other interface OPT1, which was the one I was trying to use to access the GUI despite having done "the same configuration".

In a default pfSense install, only the LAN interface gets the rule which allows all inbound traffic (including to the GUI interface). That's the anti-lockout rule. Optional interfaces such as OPT1, OPT2, etc., have zero rules applied to them and thus all inbound traffic is blocked unless a rule is created to allow it. Stated another way, only the LAN has some pre-configured rules applied to it out of the box that allow communication to the GUI and also allow any LAN host to access anything else. OPT1, OPT2, and similar interfaces are initialized with zero rules and thus all traffic is blocked on them until the admin creates the necessary rules for traffic to pass.

One other thing that looks strange to me is the unusually large subnet mask on that 200.75.x.x address. Are you sure that /16 is correct? If not correct on pfSense, it will cause communication issues. A subnet that large is going to have a huge broadcast domain.