Unable to connect between lan1 and lan2
-
@johnpoz This is my result:
Something is not right.
After sniffing with packet capture, I'm able to capture packets between pfsense only.
My pfsense is on 192.168.50.1, I'll get traffic captured if I send anything to this ip.
Packet capture:
These are my ping result from lan1:
If try my lan2 network, nothing happend.Pfsense:
18:17:41.297565 IP 192.168.50.100 > 192.168.50.1: ICMP echo request, id 1, seq 114, length 40
18:17:41.297603 IP 192.168.50.1 > 192.168.50.100: ICMP echo reply, id 1, seq 114, length 40
18:17:42.316326 IP 192.168.50.100 > 192.168.50.1: ICMP echo request, id 1, seq 115, length 40
18:17:42.316343 IP 192.168.50.1 > 192.168.50.100: ICMP echo reply, id 1, seq 115, length 40
18:17:43.332647 IP 192.168.50.100 > 192.168.50.1: ICMP echo request, id 1, seq 116, length 40
18:17:43.332661 IP 192.168.50.1 > 192.168.50.100: ICMP echo reply, id 1, seq 116, length 40
18:17:44.345138 IP 192.168.50.100 > 192.168.50.1: ICMP echo request, id 1, seq 117, length 40
18:17:44.345153 IP 192.168.50.1 > 192.168.50.100: ICMP echo reply, id 1, seq 117, length 40ISP:
18:17:53.333221 IP 192.168.50.100 > 192.168.1.1: ICMP echo request, id 1, seq 118, length 40
18:17:53.333890 IP 192.168.1.1 > 192.168.50.100: ICMP echo reply, id 1, seq 118, length 40
18:17:54.346585 IP 192.168.50.100 > 192.168.1.1: ICMP echo request, id 1, seq 119, length 40
18:17:54.347073 IP 192.168.1.1 > 192.168.50.100: ICMP echo reply, id 1, seq 119, length 40
18:17:55.362542 IP 192.168.50.100 > 192.168.1.1: ICMP echo request, id 1, seq 120, length 40
18:17:55.363027 IP 192.168.1.1 > 192.168.50.100: ICMP echo reply, id 1, seq 120, length 40
18:17:56.375135 IP 192.168.50.100 > 192.168.1.1: ICMP echo request, id 1, seq 121, length 40
18:17:56.375467 IP 192.168.1.1 > 192.168.50.100: ICMP echo reply, id 1, seq 121, length 40Google:
18:18:28.443341 IP 192.168.50.100 > 142.250.187.195: ICMP echo request, id 1, seq 126, length 40
18:18:28.445510 IP 142.250.187.195 > 192.168.50.100: ICMP echo reply, id 1, seq 126, length 40
18:18:29.459627 IP 192.168.50.100 > 142.250.187.195: ICMP echo request, id 1, seq 127, length 40
18:18:29.461912 IP 142.250.187.195 > 192.168.50.100: ICMP echo reply, id 1, seq 127, length 40
18:18:30.478792 IP 192.168.50.100 > 142.250.187.195: ICMP echo request, id 1, seq 128, length 40
18:18:30.481679 IP 142.250.187.195 > 192.168.50.100: ICMP echo reply, id 1, seq 128, length 40
18:18:31.498252 IP 192.168.50.100 > 142.250.187.195: ICMP echo request, id 1, seq 129, length 40
18:18:31.501290 IP 142.250.187.195 > 192.168.50.100: ICMP echo reply, id 1, seq 129, length 40
18:20:27.374903 IP 192.168.50.100 > 192.168.50.1: ICMP 192.168.50.100 udp port 52048 unreachable, length 286 -
@sutha These all ping belongs to lan1 port, even if I try to ping another pc on the same network. I'll get a ping result on command prompt but nothing will be captured.
Lan2 port got nothing captured. -
If you are trying to ping something on LAN2 from 192.168.50.100 and it doesn't appear in that capture then the client is not sending it to the gateway.
It would only do that if it has a bad route to that subnet. So if it has the wrong subnet mask. Or if it is still dual homed with a second IP in that subnet.
What error is shown on on the host when it fails?
-
@sutha So sniffing on the lan interface, this is where the 192.168.50.x box is and pfsense is IP is 192.168.50.1 and you ping 192.168.60.50 and you get nothing?
Lets see the output of your ipconfig /all
You sure you turned off this boxes 192.168.60 interface you said it had, or did you just remove the gateway from the interface?
-
@johnpoz Sorry for the late reply. I'll try to disable my tunnel tomorrow and let you know the outcome.
-
@sutha said in Unable to connect between lan1 and lan2:
I'll try to disable my tunnel tomorrow
tunnel? No freaking wonder your not seeing anything.. Its going out your vpn.. uggghhhh - you have wasted everyones time not stating that in post 1..
-
@johnpoz Actually, that's not true. When I trace the ping, only the tunnel IP goes through the tunnel. Everything else showing the local system ip with the message unreachable.
-
@sutha dude turn off your vpn client on this box and your issues will go away!!
A vpn client will route traffic not set to the local network out the vpn.. So yeah trying to go to 192.168.60 vs 192.168.50 will go your vpn client tunnel... Pfsense can not route traffic its never seeing.. Ie your sniff on your lan not showing any traffic when trying to go to 192.168.60 because its being routed out your tunnel
-
@johnpoz Does this mean I'm unable to create another interface for my local system as I was planning now?
My scenario:
A tunnel exists: site-to-site VPN connection.
I'd like to have another area for locally separated traffic. I don't want, as I mentioned earlier, Area 2 to communicate with Area 1, but I have users in Area 1 who need to access Area 2.
Do you think this is possible?
-
@sutha if you want a site to site tunnel - create that on pfsense..
Yes you can filter traffic that pfsense routes.. If you want client X to be able to get to vlan Y, you can allow that, if you want client A not to go to vlan Y from vlan X you can block them..
-
@johnpoz Yes, that's what I'm looking for. Currently, I have disabled two of the rules, and after reboot, my system suddenly went offline. I need to go to my office to see what happened. Once I have my system back online, I can provide you with some more details.
-
@sutha So, now I have removed all the rules and disabled the tunnel as well. I've also removed the lan1 and lan2 rules. Currently, I have no internet access and no connectivity to any system. Since I have no internet, I enabled an 'any' rule on lan1, and now I can see there is internet access for lan1 PCs. However, I still have no internet access on lan2. Therefore, I repeated the same steps I took for lan1 on lan2, and now I have internet access on both interfaces.
I'm now able to ping from 192.168.50.100 to 192.168.50.1, and when I enter this IP:192.168.50.1 in my browser, it took me to the pfSense web configurator. However, when I attempted to ping a pc on lan2, it failed. I moved to over to lan2 pc and did the ping to an ip 192.168.60.1 and it was successful. Furthermore, I tried to access the pfSense web configurator from lan2 using the IP 192.168.60.1, and it successfully redirected me to the web configurator.
At this point, I don't have any rules other than these two. Anyone got any idea what is blocking here, I have disabled my windows own firewall tatally on both system.
-
@sutha Realistically there’s only a handful of things it can be:
- Incorrect subnet mask on pfSense or PC
- Incorrect gateway on either PC
- firewall on either PC
- firewall rule on pfSense
If it was a VLAN, VLAN/switch config.
-
It's almost certainly not a gateway problem since hosts on both LANs can reach the internet.
It could be a subnet mask problem if hosts are configured statically. If they use DHCP it probably isn't since you cannot configure conflicting subnets in pfSense.
If any hosts still have two NICs or additional IPs in both subnet they will be unable to connect to the other subnet.
Try to ping 192.168.60.1 (the pfSense interface address) from a host in the 192.168.50.X subnet. If that works then routing and firewall rules are fine and it's almost certainly the hosts themselves blocking the traffic.
-
@stephenw10 I was talking in general and wasn’t clear. Low on coffee. :)
-
@sutha said in Unable to connect between lan1 and lan2:
. Anyone got any idea what is blocking here
Now do the sniff.. When you ping a 60.x IP from a 50.x device.. Do you see the traffic get to pfsense?
And like to see the output of ipconfig /all from a device.. This will validate your mask is no messed up. And for good measure output of route print..
-
@SteveITS This is my network and interface setting.
PC on Lan1:
PC on Lan2:
Interface Lan1:
Interface Lan2:
-
@stephenw10 I'm able to ping from lan1 IP:192.168.50.100 to lan2 ip: 192.168.60.1 and from lan2 ip: 192.168.60.50 to lan1 ip:192.168.50.1.
Works fine, but I'm unable to ping any other local pc. Example:
from 192.168.50.100 to 192.168.60.50, not working.
from 192.168.60.50 to 192.168.50.100, not working as well. -
@sutha And you could have 14 other interfaces.. On this machine and 3 different vpn interfaces.. How about a simple ipconfig /all output and a route print..
$ ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : i9-win Primary Dns Suffix . . . . . . . : home.arpa Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : home.arpa Ethernet adapter Local: Connection-specific DNS Suffix . : home.arpa Description . . . . . . . . . . . : Killer E2600 Gigabit Ethernet Controller Physical Address. . . . . . . . . : B0-4F-13-0B-FD-16 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.9.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, March 15, 2024 11:21:05 PM Lease Expires . . . . . . . . . . : Thursday, March 21, 2024 11:21:05 PM Default Gateway . . . . . . . . . : 192.168.9.253 DHCP Server . . . . . . . . . . . : 192.168.9.253 DNS Servers . . . . . . . . . . . : 192.168.3.10 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Nas-San: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek USB 2.5GbE Family Controller Physical Address. . . . . . . . . : A0-CE-C8-CC-57-DE DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.10.9(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Ethernet adapter vEthernet (WSL): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 00-15-5D-2F-73-DB DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::41b8:afee:a2a0:27e2%25(Preferred) IPv4 Address. . . . . . . . . . . : 172.29.64.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled$ route print =========================================================================== Interface List 15...b0 4f 13 0b fd 16 ......Killer E2600 Gigabit Ethernet Controller 1...........................Software Loopback Interface 1 7...a0 ce c8 cc 57 de ......Realtek USB 2.5GbE Family Controller 25...00 15 5d 2f 73 db ......Hyper-V Virtual Ethernet Adapter =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.9.253 192.168.9.100 40 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 172.29.64.0 255.255.240.0 On-link 172.29.64.1 5256 172.29.64.1 255.255.255.255 On-link 172.29.64.1 5256 172.29.79.255 255.255.255.255 On-link 172.29.64.1 5256 192.168.9.0 255.255.255.0 On-link 192.168.9.100 276 192.168.9.100 255.255.255.255 On-link 192.168.9.100 276 192.168.9.255 255.255.255.255 On-link 192.168.9.100 276 192.168.10.0 255.255.255.0 On-link 192.168.10.9 556 192.168.10.9 255.255.255.255 On-link 192.168.10.9 556 192.168.10.255 255.255.255.255 On-link 192.168.10.9 556 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 192.168.9.100 276 224.0.0.0 240.0.0.0 On-link 192.168.10.9 556 224.0.0.0 240.0.0.0 On-link 172.29.64.1 5256 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 192.168.9.100 276 255.255.255.255 255.255.255.255 On-link 192.168.10.9 556 255.255.255.255 255.255.255.255 On-link 172.29.64.1 5256 =========================================================================== Persistent Routes: NoneHow about the 30 seconds it takes to do a packet capture? To validate traffic is actually going to pfsense and not some vpn tunnel you have that failed to mention..
-
@sutha said in Unable to connect between lan1 and lan2:
Works fine, but I'm unable to ping any other local pc. Example:
If you can ping pfsense 192.168.60.1 from your 50.x device but not some other 60.x this SCREAMS!!!! firewall on the 60.x device..
Again simple packet captures that take all of 30 seconds will finally prove to you its your device and not pfsense..
