VLAN static IP doesn't work
-
I've got a problem never encountered before.
My Elastix box (CentOS Linux) is configured for 10.1.4.227 netmask 255.255.255.0 gw 10.1.4.254 and works just fine on the network.
On the pfSense box I have a VLAN 10.2.4.x with DHCP range of 100 - 200 in that subnet. My IP phones are picking up their addresses just fine and can ping within the subnet and outside too.
The 10.1.4.227 box can ping into the 10.2.4.x subnet without trouble.
… wait for it ...
Changing the Elastix box to 10.2.4.227 (note the subnet change) and now the box can ping anything other than itself. I changed the subnet on the box to 10.2.4.0 and the gateway to 10.2.4.254 (which is the pfSense VLAN router IP).
Setting the Elastix box to any other IP in the 10.2.4.x subnet and it still cannot get outside of itself.
I haven't configured VLANing on the Elastix box so it can't pick up a DHCP address from the VLAN yet.
But ... what's going on here?!
I'm not a newbie to networking and this one has me stumped. I can only figure it's got something to do with the DHCP server on the VLAN.
Thanks in advance,
Jason -
There are some details missing.
Changing the Elastix box to 10.2.4.227 (note the subnet change) and now the box can ping anything other than itself. I changed the subnet on the box to 10.2.4.0 and the gateway to 10.2.4.254 (which is the pfSense VLAN router IP).
You have a VLAN capable switch, pfSense connected to trunk port on the switch and the Elastix connected to a ?? port on the switch?
Setting the Elastix box to any other IP in the 10.2.4.x subnet and it still cannot get outside of itself.
The "still" in the above sentence implies it previously couldn't "get out of itself" which seems to contradict the earlier statement "now the box can ping anything other than itself".
I get the impression you might be trying to achieve some sort of isolation between the two subnets without a VLAN switch. Please clarify what you are wanting to accomplish with VLANs and what VLAN capable equipment you have (or expect to have).