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

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

Unoptanio

@Gertjan
Good morning, excuse me , in the openvpn log section I find these IP addresses unknown to me that are trying something.

Do I have to worry?
What I can do?

Gertjan

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

Do I have to worry?

Noop.
Example : you have a phone, and a SIM card. So you have a phone number.
Is is a surprise that very body on earth can call you right now ? Of course not. That's the way it should work.
( although there are people that actually want to use world's public phone network but not want to be called by any one .... or drive on the public road, and not want to encounter other people with their cars - you understand what I mean )

Before, they had this perfect WAN firewall rule set :

Yep, that is right : no rules !!
The default firewall behaviour is : drop everything that comes in.
And if you had this one not checked :

then you aren't even aware that there are actually incoming connection all the time.
Like something pressing on your doorbell, and even trying if the front door is open .... They try without stopping.

Now that your pfSense has a process that is actually listening on the WAN interface, (port 1194, protocol UDP), you suddenly can see them .....
Nothing changed. You just became aware of this aspect. It was always there already.

So nothing to worry about. It's part of becoming more "aware". Just keep on doing this ^;)

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

What I can do?

Although I should not advising anybody to stop securing is infrastructure, I can tell you this :
I do nothing.
I have this rule :

like you.
And if some one manages to 'pass along' the OpenVPN (the process listing) then I kneel down and will say : "I'm honoured to meet you". OpenVPN-server as of today, hasn't been broken yet.
When the entire planet went into a lock down and home working became the new thing, every company was implementing a OpenVPN access.
And noop ..... OpenVPN wasn't broken ....

So : again : let them have it.

You can, of course, do something about it.

Stupid, but valid example :

You saw the Source (IP) is a start which means : all the IPv4, so from 0.0.0.0 to 255.255.255.255.
You can change that.
Put an alias in place !
And set this alias to the IPv4 of your phone or device you use to connect to your OpenVPN server.

Now only you - your device - can connect to your OpenVPN.
And nobody else.

You'll find out quickly that you can't control what IPv4 your device is using while running around in your country.
So : note down the IPv4 - and call home, and have the alias used in the OpenVPN set to this IPv4.
Now you can connect again, using any IP.
And no one else.

You'll say : hey, that's tedious ! Of course it is. So, automate it !
Example use some dyndns client on your phone or PC. When it conects to the Internet, it will update your "your-device.dydns.org" so it point to your device.

On the pfSense side of things, decalre an URL/IP as "your-device.dydns.org". pgSEne will no refresh the IP of this your-device.dydns.org every 5 minutes or so (check this !).

So, your device gets an IPv4 - it will update it, and max 5 minutes later, the pfSense alias is 'resolved' and you can 'OpenVPN' into your pfSense as only that IP is now valid.

Btw : I just invented this procedure, I never actually tested and used it.