Unable to access pfSense2 on one VLAN
-
I do have 2 HW pfSense with multiple VLANs configured. CARP enabled.
VLAN Number is (almost) always the third octet, CARP is (almost) always the .1
Physical IP is (almost) always .254 for the first pfSense, .253 for the secondPer example:
VLAN 253 = 192.168.253.1 CARP, 192.168.253.253 pfSense2, 192.168.253.254 pfSense1
VLAN 254 = 192.168.254.1 CARP, 192.168.254.253 pfSense2, 192.168.254.254 pfSense1I can connect from VLAN 253 to WebGUI on VLAN 253 CARP, VLAN 253 pfSense2 IP and VLAN 253 pfSense1 IP fine.
I can connect from VLAN 253 to WebGUI on VLAN 254 CARP and VLAN 254 pfSense1 IP fine.I cannot connect from VLAN 253 to WebGUI on VLAN 254 pfSense2 (https://192.168.254.253:441). Page is blank white. HTTPS certificate is correct.
As described above access to https://192.168.253.253:441, which is the same pfSense, works just fine. Only that VLAN is not okay.
VLAN254 is my default LAN interface with the Anti-Lockout Rule, so Firewall is okay. The page does open and a white page is shown with a HTTPS certificate, so it should not be a firewall problem.Sometimes the access itself works, but the WebGUI is not displayed completely and is loading forever.
See attachment.
![Bildschirmfoto 2016-04-19 um 16.06.48.png](/public/imported_attachments/1/Bildschirmfoto 2016-04-19 um 16.06.48.png)
![Bildschirmfoto 2016-04-19 um 16.06.48.png_thumb](/public/imported_attachments/1/Bildschirmfoto 2016-04-19 um 16.06.48.png_thumb) -
After Update to 2.3.1 no change.
-
push
-
Still having the problem, now I have some logs
See attached file.
Tried the workaround in https://redmine.pfsense.org/issues/6862 - did not work
![Bildschirmfoto 2017-03-13 um 11.35.16.png](/public/imported_attachments/1/Bildschirmfoto 2017-03-13 um 11.35.16.png)
![Bildschirmfoto 2017-03-13 um 11.35.16.png_thumb](/public/imported_attachments/1/Bildschirmfoto 2017-03-13 um 11.35.16.png_thumb)