[SOLVED] OpenVPN roadwarrior - cannot access home LAN computers
-
Okay, here you see only request to 192.168.1.2, but no responses from there.
That basically may have one of the two already mentioned reasons. Either pfSense isn't the default gateway on the destination device the device blocks the access.
Are you running the TP-Link in bridge mode?
-
Okay, here you see only request to 192.168.1.2, but no responses from there.
That basically may have one of the two already mentioned reasons. Either pfSense isn't the default gateway on the destination device the device blocks the access.
Are you running the TP-Link in bridge mode?
Refer to my ugly hand written topology…. pfsense is the default gateway.
TP Link is purely a switch now. everything is disabled. no DHCP, no NAT, no firewall, no wifi.
-
ekoo,
Have a look at this thread.
It could be that the TP-link is rejecting management from the OpenVPN subnet.
-
ekoo,
Have a look at this thread.
It could be that the TP-link is rejecting management from the OpenVPN subnet.
Hi biggsy,
its not just the TP-link. everything is not accessible.
Did i setup the openVPN remote access wrong? (thru the wizard)
if the intercommunication between 2 subnet is my problem, why is it that the phone (on 10.0.8.3) can access 192.168.1.1? and not 1.2 when its on the same subnet?
Correct me if i'm wrong: the point of a road warrior is that:
- I can be sitting at a hotel room 500miles away from home with my laptop,
- click on OpenVPN, and connect to pfsense at home,
- click on "Network" icon in Windows and see all my shared drives as if i'm sitting on my desktop at home.
yes? no?
-
Sorry, I misunderstood - reading that you couldn't access 192.168.1.2.
However, you can access 192.168.1.1 because it is on the firewall (the LAN interface IP) but you have to get past there to access 192.168.1.2
It could be that the TP-link is not replying because you are accessing from 10.0.8.x (see your PING).
Are you using the WAN port of the TP-link to connect to the LAN port of your pfSense?
-
You can try SNAT to resolve this.
Go to Firewall > NAT > Outbound. If the rule generation mode is set to Automatic, set it to Hybrid and save it.
Add a new rule:
interface: LAN
source: <the vpn="" tunnel="" subnet="">Let the other options add their defaults, enter a description and save the rule.</the> -
Sorry, I misunderstood - reading that you couldn't access 192.168.1.2.
However, you can access 192.168.1.1 because it is on the firewall (the LAN interface IP) but you have to get past there to access 192.168.1.2
It could be that the TP-link is not replying because you are accessing from 10.0.8.x (see your PING).
Are you using the WAN port of the TP-link to connect to the LAN port of your pfSense?
No, its not on the WAN port. its all connected on the LAN ports.
You can try SNAT to resolve this.
Go to Firewall > NAT > Outbound. If the rule generation mode is set to Automatic, set it to Hybrid and save it.
Add a new rule:
interface: LAN
source: <the vpn="" tunnel="" subnet="">Let the other options add their defaults, enter a description and save the rule.</the>This worked. Now I don't have to pay for Plex. =)
Thank you everyone for your help. -
Good to hear that.
Thanks for letting us know.
-
Thanks - sorted my problem 2
-
Thanks - solved my problem as well. I would have thought this was a pretty common configuration. An easier to find guide for newbies would be helpful.