Windows 10 using 2 Ethernet Connections, trying to connect to a Site to Site tunnel.
-
Hello everyone, I am somewhat new when it comes to PFSense but have been learning more and more. I ran into an issue recently.
My Windows 10 computer has a MOBO with 2 ethernet ports. I use both, one goes into my PFSense for my personal LAN, and the other goes into my homes Modem/Router for the homes LAN.
I recently set up a site to site wireguard connection using this video to connect to my friends LAN. I also have a personal server running arch linux and nextcloud etc. connected to PFSense which has no problem pinging my friends LAN or the transit network.
However my Windows 10 computer can not ping my friends LAN but can ping the transit tunnel. Ex: Can't connect to friends LAN (10.69..) but can connect to transit network set up for his side (10.100..).
The interesting part though is that when I disable my home LAN ethernet port (only PFSense port enabled now), I can suddenly ping my friends LAN, and can still ping his transit, but when I enable my home LAN again (both eth ports enabled) I can only ping the transit.
I am curious if this is a Windows 10 network priority problem, but if it was then how come I can ping the transit? It would block both no?
Wondering what I can do to keep both eth ports enabled and be able to connect to his LAN without having to constantly enable/disable my home eth port on pc.
For understanding, my friend doesn't have the issue because he does disable/enable his eth ports depending on his needs.
-
Check the Windows routing table. You need to have a route to 10.69.x.x via the local pfSense IP.
There is likely already a route to 10.100.x.x there.
Neither of you should have to disconnect anything if you have the right local routes in place.
Steve
-
@stephenw10 You sir are a brilliant man, I added a route to the routing table and that seems to have fixed it. Thank you so much!
-
No worries.
-
This post is deleted! -
This post is deleted! -
S stephenw10 locked this topic on