Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access

Unoptanio

RESOLVED!!!!!!

I've gone crazy.

Enabling this item now works. I can access the internet (browser, email, etc) on the remote client pc while they are also connected in VPN with Remote Desktop

Unoptanio

@viragomann

Tested by checking the public ip.
On the remote client pc, the internet goes out with the local connection of the pc and not with that of the remote OpenVpn tunnel.

Do you know if it is possible to get it out with the remote VPN tunnel connection?

IPCONFIG in client pc:

viragomann

@Unoptanio
Go into the OpenVPN server settings and add a check at "Redirect gateway".

However, this also needs an outbound NAT rule on WAN for the source of the tunnel network. If you went through the wirzard, pfSense might have add it automatically, otherwise set outbound NAT back to hybrid mode and add the rule manually as you had it before.

Unoptanio

@viragomann

Unoptanio

@Unoptanio

if i check redirect ipv4 gateway then disappear ipv4 local network

viragomann

@Unoptanio said in Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access:

if i check redirect ipv4 gateway then disappear ipv4 local network

Yes, this is not needed anymore in this case.
It pushes the route for the local networks to the clients. Redirect gateway pushes the default route, i.e. any traffic is routed over the VPN.

Unoptanio

@viragomann

great thanks it works. Tested now.
with this change the internet use the remote tunnel

Unoptanio

@Unoptanio

The crucial setting that didn't make the internet work on the local pc but only the VPN was this

Unoptanio

@Unoptanio

Performance:

Test speed under remote server openvpn on firewall pfsense: (1Gb optical fiber)

Test speed in remote pc client with OPEN VPN ON with internet routed on the remote server .......shouldn't it go faster?

Test speed in remote pc client with OPEN VPN OFF with internet on local PC

Gertjan

@Unoptanio

I propose : replace these :

with

where 192.168.3.1 is your tunnel IP, 10.10.94.1

If you unbound settings are default, you're good :

(All includes my OpenVPN server called SVPN)

as unbound also listens on 10.10.94.1, the OpenVPN server IP on the pfSense side.

Why ? Now you can use local URL/host names like server.XXXXpfSense.homa.arpa to join a RDP session on "server" on your LAN.
8.8.8.8 and others don't know anything about your local devices ;)

Unoptanio

@Gertjan

HI,
that's what I've been trying to do for the last few hours. but at the moment I haven't succeeded yet.
I would like to use the computer name in RDP sessions instead
of the IP address

RDP session using PC NAME not work.

RDP session using ip address of PC work OK.

i changed the pfsense config like you saids:

Unoptanio

@Gertjan

I find this in "services", "DNS RESOLVER?"

I have not added the OPENVPN server in the interfaces.

and consequently does not appear in the DNS resolver list.

slu

@Unoptanio
dou you have set firewall rules for the OpenVPN connection?

Unoptanio

@slu
the openvpn wizard entered them automatically

slu

@Unoptanio said in Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access:

the openvpn wizard entered them automatically

no I mean internet access from your VPN client over the VPN into WAN.
That was your question, or?

Gertjan

@Unoptanio

Observe :

As soon as you connect, the right number will raise.
The left number will show the number of open states, so bigger then 0.

This means traffic comes in ....
Do you see the same ?
To hit your perfect OpenVPN server Firewall rules :

as these are all pass rules (for me : IPv4 and Ipv6) traffic can get everywhere.
Take note : the counter in front of the rules : do they go up ?

If you were connecting to some device on LAN, then the traffic would get routed out to the LAN interface, and then it really try to reach that device ....
Suspense : will this device (its firewall ?) accept this traffic

You can do a packet capturing on the LAN interface, as you know the destination IP, and destination port, and protocol used (UDP ?)
Do you see it ?

Unoptanio

@Gertjan

latest updates and tests:
I added a specific OPEN_VPN interface that I didn't have before

here the numbers turn, there is traffic when there are rdp sessions

The problem:
RDP work only with IP address of the pc
if i use PC name not working

Gertjan

@Unoptanio said in Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access:

I added a specific OPEN_VPN interface that I didn't have before

This Open_VPN is assigned to the OpenVPN server instance ?

Like this (my OpenVPN server ) :

?

Then you have probably an issue.
RDP is mostly, if not all, UDP based. Your firewall rule only permits IPv4-TCP and blocks IPv4-UDP.

As proposed : time to do some : Diagnostics > Packet Capture

Btw : read also : Cannot connect with RDP via openVPN for some out of the box thinking ;)

Unoptanio

This post is deleted!

Unoptanio

@Gertjan said in Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access:

s unbound also listens on 10.10.94.1, the OpenVPN server IP on the pfSense side.

Why ? Now

@Gertjan said in Pfsesne 2.7.0 OpenVPN Client connected, RDP Work OK BUT no internet access:

Why ? Now you can use local URL/host names like server.XXXXpfSense.homa.arpa to join a RDP session on "server" on your LAN.
8.8.8.8 and others don't know anything about your local devices ;)

I finally found it. it's about DNS resolver at the bottom

you need to add the hostnames in the override section of the DNS resolver.
This way you can access RDP using hostname.domain

Tried it works