Multi-LAN using VLAN's and Managed Switches, pfSense crashing.
-
I'm running pfSense 2.0. My configuration is as follows, I have my LAN link connected to some managed switches and have create a VLAN for each department in the building. I then set all ports that belonged to a specific department to untagged and the correct people were getting the correct IP's for their given departments. The configuration seems work good but crashes after about 6 hours and the only way to fix it is to reboot pfsense. When it crashes I loose all access to the box over WAN as well as LAN.
WAN (DHCP)
LAN (VLAN1) 192.168.1.1
LAN2 (VLAN2) 192.168.2.1
LAN3 (VLAN3) 192.168.3.1
LAN4 (VLAN4) 192.168.4.1
MGMT (VLAN4093) 10.10.10.1I have not yet had a chance to look at the logs as the box is in the process of being rebooted. Has anyone had issues with this type of setup?
-
Define "crashes", what does it show at the console?
-
It becomes unresponsive. I can no longer log into it via SSH, HTTP (WAN or LAN). Its sitting in a cabinet and I do not have a monitor connected to it at the moment. I'm going onsite tomorrow morning and will be taking a closer look. This is the first setup of this kind that I've done. I know that some of the old routers were disconnected although its possible that someone reconnected one and its feeding DHCP back into the network and I know that with standard routers it can cause similar symptoms. I'm hoping that's all it is as it will be very simple to find/fix.
-
Do you have NAT reflection disabled? Also, did you raise the state table size?
-
I can now access it via HTTP on the LAN.
@dreamslacker
Disable NAT Reflection for 1:1 NAT - DISABLED
Disable NAT Reflection for port forwards - DISABLED
Firewall Maximum Table Entries - DEFAULT (Left it Blank)
Firewall Maximum States - DEFAULT (Left it Blank)EDIT: Now that I am onsite here I found that the old router (connected to the same ISP) still had the static IP settings of the new router. Switched it to DHCP and I think our issue may have been resolved.