VPN up Gateway up - No Internet
-
@vmac may try seeing how this plays out?
https://forum.netgate.com/topic/160257/lan-connection-drops-when-openvpn-client-connected/4
There are several apparently informed individuals helping this person out. The problem seems similar to yours.
-
@johnpoz @viragomann
Can either of you help here? -
@vmac
I don't know, how you've configured the DNS on the affected machines, but since your LAN rules don't allow DNS requests to internal servers, they can only access external ones, but must be configured to do so or you do some forwarding to an external server.
So check if you can resolve hostnames on a computer which belongs to the VPN_devices alias. -
@viragomann I'm confused what you are stating here.
Here is a copy of my current LAN rules. Doesn't the last rule allow access from any device on my LAN vLAN to any device?
Are you stating that I need to add another rule to allow DNS traffic?
-
@vmac
Yes, it does. But this rule will never be applied, since that one above matches to any traffic and directs it to the vpn gateway.Rules are processed from the top downwards. If one matches it is applied and other rules are ignored.
Still don’t know, how you do DNS resolution. But assumed it“s done by pfSense, add a pass rule to the top of the rule set for TCP/UDP, dest. „This Firewall“, port DNS. So this ruhe only is applied for DNS access to pfSense, all other traffic is still directed to the vpn.
-
@viragomann
I'm confused as to what you mean about the order. since VPN devices would only match specific devices. However, I made the change and still can't get any Internet when VPN connected:
To answer your other question, I have my pfSense resolving all DNS queries:
-
I'm starting to wonder if it has something to do with the Automatic Outbound NAT not working.
When I check the OpenVPN logs I see this noted:
When I go to Outbound NAT I don't see this interface in the "automatic" generated outbound.
Could this be the issue?
-
@vmac said in VPN up Gateway up - No Internet:
I'm confused as to what you mean about the order. since VPN devices would only match specific devices. However, I made the change and still can't get any Internet when VPN connected:
To answer your other question, I have my pfSense resolving all DNS queries:
The question is if your VPN devices are configured to resolve host names. If they are set to use pfSense you need this rule, otherwise DNS requests are directed to the VPN provider, while the destination address is pfSense and resolution fails.
Since the rule shows some matches I assume the devices are set to use pfSense for DNS resolution.@vmac said in VPN up Gateway up - No Internet:
I'm starting to wonder if it has something to do with the Automatic Outbound NAT not working.
When I check the OpenVPN logs I see this noted:When I go to Outbound NAT I don't see this interface in the "automatic" generated outbound.
I cannot find what's really wrong there. The virtual interface port is ovpnc3. This one you should have assigned to NordVPN in interfaces > assignments.
The only weird thing in the outbound NAT is in the automatically generated rules: 192.168.3.1/26 and 192.168.3.0/26. No idea where the .1 is from.
Your VPN devices may be in 192.168.1.0/24 and 192.168.3.0/24? However, the latter may not really be defined on your system, since it isn't shown in automatic rules.
-
@viragomann
Well I'm at a loss.Yes the devices are set to use pfSense for DNS.
That is correct ovpnc3 is assigned to NORDVPN.
I'm assuming this is where the 192.168.3.1 comes from Interfaces->IoT:
Yes I have some devices that I want to use the VPN that are in my IoT vLAN, and I have ones that are regular LAN vLAN that I want to use the VPN. The device that I'm testing right now is on the LAN vLAN and still can't hit the VPN. I just tried the IoT vLAN and same issue.
The really weird thing is nothing has been changed except me adding a traffic shaper. Before my config has worked for literally 2-3 years.
-
I just updated to 2.5.0 RC and have the same problem.
NordVPN used to work perfect, now I don't get internet through it. The interface comes up with an IP but when I look at the traffic graph I only see outgoing traffic (no incoming).
It was a straight upgrade, I made no changes to the pfSense config.
-
@sensecanuck could that be the problem? I've been using 2.5 beta since June/July due to an issue with miniupnp and my ps4s. Maybe something that was changed in November/December changed something?
-
@vmac could be.
This is the 3rd time I've tried upgrading to 2.5.0 and have always had this VPN issue. I just assumed it was on the to-be-fixed list but apparently it's something else since we're now into RCs.All three of my 2.5.0 attempts have been December or later.
-
@vmac said in VPN up Gateway up - No Internet:
I'm assuming this is where the 192.168.3.1 comes from Interfaces->IoT:
What I wanted to point out is that the outbound NAT shows these entries among other: 192.168.3.1/26, 192.168.3.0/26. But normally it only shows network address, 192.168.3.1/26 is none, but it's part of 192.168.3.0/26.
Post your routing table to get closer.Do a packet capture on the NortVPN interface, while you try to access something from a concerned device, to see if the packets are natted well.
-
My setup is almost identical to @vMAC (select VPN based on a IP alias group). The only difference I have is I don't use the DNS resolver (to avoid DNS leaks) - I forward all VPN alias group DNS traffic to the VPN's DNS server.
But same problem - was working perfect until the move to 2.5.0.
Noticed though my gateway shows as offline. I switched the monitor to 1.1.1.1 but no difference.
-
@sensecanuck I thought it typical to block and forward all dns traffic to the pfsense dns resolver to avoid dns leaks...
-
I didn't want to use the VPN DNS for all LAN clients, just the few selected to use VPN. So I manually forward all port 53 traffic on those clients to the VPN provider's DNS server.
-
@sensecanuck gotcha!
-
@sensecanuck I'm also feeling your pain.
Whether I upgrade or rebuild from scratch its the same result. Tried on 2 boxes (one a vlan setup and the other multiple nics).
Also made several attempts at this. I can get the gateway up but I can't get traffic to flow through it. It seemed to me like the firewall wouldn't direct traffic into it - though I haven't looked into it very deeply.
Watching this thread closely to see if anyone can shed light. -
@dilligaf You seem to be a step above me. My gateway won't even show up. I've changed every rule I can find, changed the monitor address to 1.1.1.1, no luck. I'm so fed up with this I'm about to try out an OPNsense install.
-
@sensecanuck I've have a very similar setup by the sounds and like you use cloudflare dns. And like you changed everything I could think of.
All sorts of different issues: I've had it running but only at about 120mb/s (I'm expecting 400+). I thought at that point it was just hardware acceleration. Backed up that config but when I restored it no traffic.
And had the gateway up but no traffic like you. I was mucking about with it late last night and can't repeat anything.
I'm looking to overhaul my network as a suitable and more powerful NUC type box has come into my possession. There's an issue there with 2.5 I don't understand and want to use PFSense on it as everything generally just works, but don't really want to put the effort in on 2.4.5.
And like you I'm testing OpnSense. Not getting the same VPN performance though. Generally 15-20% less. Beware of the NordVPN guide - do not follow the guide for dns prefetch suppork and prefetch dns key. It doesn't work!