Unable to connect between lan1 and lan2
-
Hi, my lan setup:
Area 1: Lan1
IP: 192.168.50.100/24
GW: 192.168.50.1Area 2: Lan2
IP: 192.168.60.50/24
GW: 192.168.60.1I am able to ping all subnet areas within Area 1 from Area 1, and all subnet areas within Area 2 from Area 2.
I can ping all networks (including those in Area 1 and Area 2) from the pfSense diagnostic page.I can ping www.google.com from either side. However, I am unable to ping from a PC in Area 1 to Area 2, or vice versa.
I have switched off my firewalls for testing purposes only, and I have an 'any to any' rule enabled on both LANs.Am I missing anything, any suggestion welcome.
-
@sutha
Consider that your computers run a system firewall, which by default blocks access from outside of their local subnet.
So you might have to allow access on the destination devices or disable its firewall. -
@viragomann Sorry for any misinterpretation. I have disabled the firewall on my Windows system.
Firewall image below here:
-
@sutha Do all devices use pfSense as their gateway?
Rules allow protocol * or ICMP not just TCP? (Picture?)
https://docs.netgate.com/pfsense/en/latest/troubleshooting/connectivity.html#firewall-rules
-
@sutha Policy routing can also be a reason for this.. Be nice to actually see your rules, screenshot. And do you have any rules in floating?
If your forcing traffic out your wan or vpn via a policy route, then no you wouldn't actually be able to get to your other networks.
-
@SteveITS Hi Steve, for test pupose I have open the rule for any(source=any, destination=any)
-
@johnpoz Are you saying, I'm unable to communicate with my second lan when I have a vpn connection. I don't have any floating rule.
-
@sutha only if you are policy routing out it..
If your doing that, then you would have to create rules to allow to get to your other networks before you force it out the vpn gateway.
https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html#bypassing-policy-routing
-
@johnpozYes, my policy is routing out. However, only certain IPs are affected, which are not included in the routing rule at all. Before activating this second LAN on my pfSense, I had a working site-to-site VPN. Now, with the addition of a second area, I aim to connect only specific computers to this network. Therefore, I equipped PCs with two network cards, one for connecting to Area 1 (192.168.50.0/24) and another for connecting to the other network (192.168.60.0/24). My LAN rule already allows any-to-any traffic, and I replicated this same rule for the newly created LAN2 as well.
However, I am able to connect from my pfSense web interface to both LAN and subnets, but not from a local PC. -
@sutha said in Unable to connect between lan1 and lan2:
@SteveITS Hi Steve, for test pupose I have open the rule for any(source=any, destination=any)
The protocol…show us a screen cap.
-
equipped PCs with two network cards, one for connecting to Area 1 (192.168.50.0/24) and another for connecting to the other network (192.168.60.0/24).
If a PC has two networks traffic for them would not go through pfSense, the gateway.
If that’s not the case they presumably don’t have two gateways and static routes so the reply is going out the wrong network.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/asymmetric-routing.htmlIf you unplug the “other” network from a few so they each have one network does it work?
-
@sutha said in Unable to connect between lan1 and lan2:
herefore, I equipped PCs with two network cards, one for connecting to Area 1 (192.168.50.0/24) and another for connecting to the other network (192.168.60.0/24)
That is horrible solution.. And you have now created asymmetrical traffic flow..
And if "both" your devices have interfaces in both networks.. Why would the traffic even flow through pfsense.. The traffic would go out the interface connected to the network the IP is on.
-
@SteveITS
Lan1
Lan2
-
@sutha They have to flow through pfsense, because they are connected on pfsense lan 1 and lan 2 port.
-
@sutha said in Unable to connect between lan1 and lan2:
They have to flow through pfsense, because they are connected on pfsense lan 1 and lan 2 port.
That is NOT what you stated..
I equipped PCs with two network cards, one for connecting to Area 1 (192.168.50.0/24) and another for connecting to the other network (192.168.60.0/24)
-
@johnpoz Yes, because of the gateway. I have mentioned above, I'm using 2 different gateway.
-
@sutha said in Unable to connect between lan1 and lan2:
I'm using 2 different gateway.
Doesn't work that way..
There is no reason to send traffic to a gateway if the IP is on the network your attached too..
If I have an IP in network 192.168.50.0/24 and I want to talk to 192.168.50.X why would I send traffic to a gateway.. Gateways are for getting off a specific network.
I would suggest you disable the 2nd interface on each machine... So you have machine A in only lan 1, and machine B only on lan 2..
-
@johnpoz You're right, but I'd like to go to the second lan which is 192.168.60.X.
I don't know, if there's a way to communicate without the second card to this ip range. I'm happy to remove my card. -
@sutha That is what pfsense is there for - it is the router, it routes traffic between 192.168.50 and 192.168.60..
-
@johnpoz Yes, this what I want. After creation of lan2, I didn’t get any internet access and I couldn’t ping from pfsense web interface either but after I created an any rule. It was fine, only I’m unable to connect from local pc.
