Unable to connect between lan1 and lan2
-
@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.
-
@sutha Firewall rules control access between networks (as packets arrive at an interface). One NIC on each PC and routing through pfSense would simplify everything and it will work that way.
Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
Upvote đź‘Ť helpful posts! -
@SteveITS Thanks Steve, but any suggestions how?
I have open all possible blocking via any rule and disabled my system firewall. -
@SteveITS so you removed the 2nd interface from these devices?
And from device in A, you try and ping IP address of device in network B?
Can you ping pfsense IP address on network B? Does that work?
You have this
So 50.100 can ping pfsense IP 60.1 but can not ping 60.50?
And you have any any rules on both lan 1 and lan 2 interfaces of pfsense.. No policy routing out any gateways on pfsense. No GW actually set on lan 1 or 2 interface in pfsense?
If you can ping 60.1 from 50.100, but can not ping 60.50 - this screams firewall on 60.50..
Sniff on pfsense 60.1 interface while you ping from 50.100 device to 60.50.. So you see pfsense send the ping request to 60.50? If you do and you get no response that is 60.50 not answering, or not using pfsense 60.1 as its gateway.
example... Here is me pinging from my Pc on 192.168.9.100 to an IP in one of my other network 192.168.3.10, now doing a packet capture on my pfsense 192.168.3 interface you can see the traffic sent on to 192.168.3.10 from 192.168.9.100
If you see this but no response - that SCREAMS firewall on the destination IP device... or its not using pfsense as its gateway, or its mask is wrong and thinks the source IP is on its own network, so it doesn't send traffic back to pfsense, etc.
