LAN with multiple subnets
-
It might have something to do with the finicky-ness of the internet links down here, at least one of the times this ocurred i had reconfigured the main switch therefore causing pfSense to mark all gateways as down.
Attached are the VM config, where each WAN has a vlan and it's interface, the interface tab and the route tab.
Network config is:
VMCluster -> bladecenter stacked switch - > main switch (in trunk mode, ESXi deals with untagging the vlans)
WAN1-4 -> main switch (with the ports correctly set as general, untagged and the corresponding vlan id)Like i said, it works. it just so happens that for some reason it suddenly wants to route thru the LANGW. nothing in the logs saying why or how it does that (at least not after a reboot)
-
What is the interface address and subnet mask configured on pfSense LAN?
-
10.222.254.251 /16, in the old non-subnetted range.
-
What else do you have anywhere that starts with 10.222 ?? besides the switch at 10.222.255.254
No idea why you have that on a /16 but it's your network.
-
It's a /16 because i was young and stupid at the time (might be stupid still…) and didn't know anything about networking, vlans, subnets and didn't have hardware that supported it. The separate ranges are for each lab and it's people to be able to configure PXE, BOOTP, DHCP, and all the other multicast stuff they might want without crashing the rest of the network.
The stuff still on the 10.222.0.0/16 are some of the labs that i haven't been able to move to VLANs yet and one of the DCs that is awaiting new licenses for a migration.
-
So everything's working now and the issue is why, as you say, pfSense uses LANGW as the default gateway right?
Did you do something silly like make a failover gateway group with WAN and LANGW as members?
-
No, only the real WAN GWs are included in the gateway groups. i have 3 with different tiers for different needs (adsl for the visitors, cablemodem for users, best one for the servers, etc)
-
Well, pfSense doesn't just arbitrarily route out LAN so I guess I don't know what to tell you.
-
Damm, i hoped i had something misconfigured. Well, i'll try to delve deeper and see if it happens again.
Thanks! -
You might but I have no idea where to tell you to look next. Grep WANGW in /tmp/rules.debug and see if it's somewhere it shouldn't be. Take a good, long look at what's really happening next time it blows up. At least get a copy of Diagnostics > Routes.
