F5F Stay Refreshed Power Users Networks Issue with pfSense webUI in VLAN 50

Issue with pfSense webUI in VLAN 50

Issue with pfSense webUI in VLAN 50

Pages (2): 1 2 Next
M
MonkeyOnTheCar
Junior Member
2
09-18-2020, 03:46 PM
#1
I have set up my PFSense box with a guest VLAN on ID 50, and everything functions properly. I receive a DHCP lease at 10.0.1.1/24, which is standard for a LAN. The issue lies in trying to restrict access to the web UI from my guest network (10.0.1.1/24). I have created the following rules: the blue squiggle blocks internet access, and the destination alias points to 10.0.0.1 and 10.0.1.1. The problem persists because the top rule completely blocks internet access, preventing even basic searches like google.com.
M
MonkeyOnTheCar
09-18-2020, 03:46 PM #1

I have set up my PFSense box with a guest VLAN on ID 50, and everything functions properly. I receive a DHCP lease at 10.0.1.1/24, which is standard for a LAN. The issue lies in trying to restrict access to the web UI from my guest network (10.0.1.1/24). I have created the following rules: the blue squiggle blocks internet access, and the destination alias points to 10.0.0.1 and 10.0.1.1. The problem persists because the top rule completely blocks internet access, preventing even basic searches like google.com.

X
XaVaTaR
Member
77
09-20-2020, 12:39 AM
#2
The alias pfsensewebuiacess corresponds to a different name across systems. It requires redefinition since it matches all traffic.
X
XaVaTaR
09-20-2020, 12:39 AM #2

The alias pfsensewebuiacess corresponds to a different name across systems. It requires redefinition since it matches all traffic.

_
_Alphaaa_
Junior Member
10
09-23-2020, 02:36 PM
#3
The IP addresses are 10.0.0.1 and 10.0.1.1
_
_Alphaaa_
09-23-2020, 02:36 PM #3

The IP addresses are 10.0.0.1 and 10.0.1.1

M
MyNameTim5581
Member
196
09-23-2020, 04:31 PM
#4
Adjust the rule to restrict the web UI access exclusively to the IP address 10.0.1.1 on port 443.
M
MyNameTim5581
09-23-2020, 04:31 PM #4

Adjust the rule to restrict the web UI access exclusively to the IP address 10.0.1.1 on port 443.

B
borzsony
Junior Member
49
09-23-2020, 06:13 PM
#5
Pfsense supports self aliases but it's recommended to use them for $if_ip instead of modifying the web UI address directly.
B
borzsony
09-23-2020, 06:13 PM #5

Pfsense supports self aliases but it's recommended to use them for $if_ip instead of modifying the web UI address directly.

D
dogymann245
Member
112
10-15-2020, 05:30 AM
#6
It seems my explanation got a bit confusing. You mentioned changing the destination to 10.0.1.1 and port 443, but the issue persists. Could you clarify what you were trying to do? It looks like there might be some misconfiguration or misunderstanding.
D
dogymann245
10-15-2020, 05:30 AM #6

It seems my explanation got a bit confusing. You mentioned changing the destination to 10.0.1.1 and port 443, but the issue persists. Could you clarify what you were trying to do? It looks like there might be some misconfiguration or misunderstanding.

M
Mikeahl
Member
196
10-16-2020, 02:45 AM
#7
Yes, we have a pass rule in place.
M
Mikeahl
10-16-2020, 02:45 AM #7

Yes, we have a pass rule in place.

T
TheTivekas
Member
194
10-18-2020, 12:26 AM
#8
Sure, you seem uncertain.
T
TheTivekas
10-18-2020, 12:26 AM #8

Sure, you seem uncertain.

G
GreenLightFabi
Senior Member
696
10-24-2020, 04:34 AM
#9
All guidelines you possess are shown in the image for the guest network. At the end of the list, there is an "allow all to all" rule, which you can apply generally.
G
GreenLightFabi
10-24-2020, 04:34 AM #9

All guidelines you possess are shown in the image for the guest network. At the end of the list, there is an "allow all to all" rule, which you can apply generally.

Z
zarross
Junior Member
40
10-29-2020, 03:29 AM
#10
Check pf activity through the console using the pflog interface. For example, tcpdump -n -e -ttt -i pflog0 followed by grep helps filter data. Review the pf rules and their output with commands like pfctl -vvsr to see rule numbers and troubleshoot issues. A common challenge is converting these outputs to match the GUI display, so enable logging on all rules for clarity.
Z
zarross
10-29-2020, 03:29 AM #10

Check pf activity through the console using the pflog interface. For example, tcpdump -n -e -ttt -i pflog0 followed by grep helps filter data. Review the pf rules and their output with commands like pfctl -vvsr to see rule numbers and troubleshoot issues. A common challenge is converting these outputs to match the GUI display, so enable logging on all rules for clarity.

Pages (2): 1 2 Next