@viragomann said in splitting a subnet, moving from LAN to WAN:
Yes, if they statically route the lower /25 to pfSense, that could be a reason. But why should they do that?
pfSense has just an IP in this subnet from their view and it would rather make sense to route the upper /25 to it, because this is behind of pfSense.
They might have an error in setting up the VLAN in vSphere.
It is routed correctly to the network port where the pfSense is attached, otherwise all my stuff wouldn't have worked for years.
But it's new and untested in the VMware environment. And it might be wrong. At least I don't have another idea right now.
I am looking forward to their reply.
As far as I understand things, even when the LAN interface in pfSense is configured in the upper /25, it won't hijack traffic going to an IP in /24. pfSense itself has a route to that upper /25 then, but this should must not affect routing in the larger /24 VLAN "above" ...
I even tried that yesterday: triggered a reboot of pfsense and pinged vm_new .180 all the time ... just to see if somehow things change while the pfsense is offline. It would have surprised me, but anyway ... I can only search in my range for now.
Maybe I overlook something, but so far @viragomann hasn't spotted a real misunderstanding, right? thx ...