Odd LAN Addressing Issue
-
What subnet mask were you trying to use?
-
You mean 192.168.2.0 as the network right? Or were you assigning 192.168.2.0 as the interface address?
-
192.168.2.0/24
GW 192.168.2.1
Cant ping 8.8.8.8 nor 192.168.2.1 when connected if i switch it to another number besides 2 it works just fine, 2.X is not used anywhere else
-
So what is the exact IP address assigned to your LAN interface? 192.168.2.0? Why there is a gateway on the LAN?
Sorry, I still don't understand your network
-
OK!
I went to Interfaces>Opt 4
Choose Static IPv4
Entered 192.168.2.1 for the IP with /24 as the subnet.
No DHCP enabled.
If i connect with any static address 192.168.2.2-254 i cannot PING 8.8.8.8 nor 192.168.2.1
If i enable DHCP and let any device get its address 192.168.2.2-254 i still cannot PING 8.8.8.8 nor 192.168.2.1
If i switch the address to 192.168.3-anything other then 2 it works just fine.1
i can work around this by not choose 2, i am just curious why it doesnt like .2
-
Quite odd as you describe it :)
What are your NAT rules?
Can you paste the ipv4 part of netstat -nr? -
I went to Interfaces>Opt 4
And what are you firewall rules on this OPT interface? Since opt interfaces have no rules by default..
Also what are you Ips on all your other interfaces.. Sure you don't have say a 192.168.1.0/23 which would overlap your 192.168.2.0/24
Also as mentioned there really should not be a GW on a lan interface.
-
No gateway was chosen, first thing i learned when first starting out with PFSense, i love PFSense all around, i am referring to the IP entered in the box next to the subnet drop down box, if I switch it from 192.168.2.0/24 to lets say anything other then 2 such as 192.168.3.0/24 it works.
In the IP box next to the subnet drop down i entered 192.168.X.1 for this interface/network
192.168.2.X is not used anywhere else
As for rules i have just the normal ones to allow traffic from one subnet to another or to block one subnet from accessing these devices on this interface, i do not see however how a rule would not allow me to use 2.X but allow any other number 3.X, 4.X, 5.X, 88.X etc…
If it was a rule issue i would assume that i would not be able to use it regardless of the number and i would not be able to use the workaround of just switching to the next number up.
-
After looking through everything including logs and all configurations i figured it out
-
and what was it for the next guy reading this thread
