Multiple OpenVPN clients non-functional
-
Do you see how the tunnel addresses are in 10.35.0.X/?? for both ovpnc1 and ovpnc2? That certainly could be part of the problem, depending on the netmasks involved. It looks like they are using net30 which should be OK.
You also have 8.8.8.8 and 8.8.4.4 apparently assigned to the OpenVPN gateways and those change. That could also be part of the problem, depending on what is set to use those DNS server addresses, including the firewall itself.
I don't know what those routes for the 104.223.91 addresses are, but they are also host routes assigned to individual OpenVPN clients.
You do realize that you have to completely stop and start an OpenVPN client after assigning an interface to it, right?
Not sure what you're doing wrong…
If I …. all connections time out.
What, exactly, does that mean. All connections from where? To where? What find of connection? Do DNS lookups work? pings? is it just web browsing? Everything? Have you sent any traceroutes? where do they stop? Sorry but this is going to require some sleuthing.
-
Do you see how the tunnel addresses are in 10.35.0.X/?? for both ovpnc1 and ovpnc2? That certainly could be part of the problem, depending on the netmasks involved. It looks like they are using net30 which should be OK.
You also have 8.8.8.8 and 8.8.4.4 apparently assigned to the OpenVPN gateways and those change. That could also be part of the problem, depending on what is set to use those DNS server addresses, including the firewall itself.
I don't know what those routes for the 104.223.91 addresses are, but they are also host routes assigned to individual OpenVPN clients.
You do realize that you have to completely stop and start an OpenVPN client after assigning an interface to it, right?
Not sure what you're doing wrong…
If I …. all connections time out.
What, exactly, does that mean. All connections from where? To where? What find of connection? Do DNS lookups work? pings? is it just web browsing? Everything? Have you sent any traceroutes? where do they stop? Sorry but this is going to require some sleuthing.
I stop the clients before changing or assigning the interface, yes. As for timing out, I can't ping any addresses I've tried, DNS lookups fail (If I clear my local DNS cache), traceroutes timeout at every hop.
I've removed all clients, interfaces, and gateways and setup most of these things from scratch again to try and simplify things and remove the other "junk" that was a result of me testing. Here are my routes now (issue still exists)
Client 1 (working)
Client 2 (timeouts)
-
What are your policy routing rules that send traffic over the openvpn circuits?
-
What are your policy routing rules that send traffic over the openvpn circuits?
The first two rules are evaluated first to allow certain devices or sites to use the WAN gateway instead of the VPN. This is mostly due to certain services restricting or blocking access. These work as expected.
The highlighted rule is the VPN rule, it should be a catch-all.
The next two rules are to try and prevent torrents from leaking over my WAN if for some reason the VPN is down.
The final rule is the WAN catch-all for IPv4.
When I try and use my 2nd VPN client I just go into the highlighted rule and switch it to the gateway for the 2nd VPN client for testing purpose. I can switch the interfaces for each client around in the OpenVPN config and the first one will always work and the 2nd not, regardless of interface & gateway.
-
Sorry. I know that would work if I tried to duplicate it. No idea what you're doing wrong. But you're doing something wrong somewhere.
-
Sorry. I know that would work if I tried to duplicate it. No idea what you're doing wrong. But you're doing something wrong somewhere.
I've checked and referenced to the point where I'm going crazy, and others on here don't seem to know at this point either as my setup looks correct.
100% sure there isn't a bug in PFSense specific to my setup? By process of elimination how much is left? Any way I can try and diagnose this further to rule out additional items, or rule in others? Multiple VPN connections is a must-have for me, so I'm at a loss here…
Edit: Could this have anything to do with the difficult I have with assigning an interface to the OpenVPN client? When I try it would always tell me:
An IPv4 protocol was selected, but the selected interface has no IPv4 address.
Which always seemed like a catch-22 since it can't have an IPv4 address till I start the OpenVPN client up. This can be found on https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/vpn_openvpn_server.php#L277 .
-
You don't put an address on an OpenVPN assigned interface. They get Enable checked, a name, then None / None selected there. That's it.
I have never seen that message when assigning an interface. What, exactly, are you doing when it happens?
-
You don't put an address on an OpenVPN assigned interface. They get Enable checked, a name, then None / None selected there. That's it.
I have never seen that message when assigning an interface. What, exactly, are you doing when it happens?
I get this error when creating or editing the OpenVPN client when I have an interface like the one below selected. I can just create a new client, enter any random gibberish into it and select an interface and that error will pop up. I get around it by commenting out that line of code.
Here is an example OpenVPN client: (not embedded because long) http://i.imgur.com/znt5J08.png
Interface is setup with none/none:
-
Aha. I knew it had to be something.
The interface you select there is not the assigned interface, it is the interface used to establish the VPN connection - usually WAN. Or maybe a gateway group if you are running multi-wan and you want it to switch if your tier 1 fails.
So all of your OpenVPN client configurations will have WAN selected there because that is the interface used to ESTABLISH the VPN connection.
-
Good catch Derelict.. Glad that is settled…
-
Aha. I knew it had to be something.
The interface you select there is not the assigned interface, it is the interface used to establish the VPN connection - usually WAN. Or maybe a gateway group if you are running multi-wan and you want it to switch if your tier 1 fails.
So all of your OpenVPN client configurations will have WAN selected there because that is the interface used to ESTABLISH the VPN connection.
Sorry for being dull, but I'm gonna parrot what you said to make sure I understand.
The WAN interface is used to establish the VPN connection, so regardless of what interface I have selected there (unless I have multi-wan) it will use the WAN interface?
If that's the case, how do I set up routing rules for the VPN clients if they will all use the WAN interface? Do I always select WAN in my OpenVPN client setup?
-
You have to specify a real interface there. In the example you posted to imgur, when your firewall needs to connect to xxx.vpnaccess.com on server port xxxx it will use the interface specified there to source from for the TUNNEL PACKETS - the Outer tunnel packets. It has nothing to do with what traffic is sent through the tunnel itself. It has to be a real interface. What you have there is nonsense.
Create all three OpenVPN clients. Tell them all to use the WAN interface.
Go into Interfaces > (assign). Assign an interface to each ovpncx instance.
Edit each interface, enable it, name it, leave the IPv4 and IPv6 configurations as None.
Make sure you bounce each OpenVPN as this is a required step after initial interface assignment. Another Edit/Save with no changes of each OpenVPN client will do this, as will a Stop/Start of each service in Status > Services.
Make sure outbound NAT is set for each new interface so traffic leaving that interface gets source translated to that particular tunnel address.
You can then policy route whatever traffic you want over each OpenVPN at any time using the policy routing rules on the source network interface. You will have three OpenVPN gateways to choose from. One on each assigned interface.
-
You have to specify a real interface there. In the example you posted to imgur, when your firewall needs to connect to xxx.vpnaccess.com on server port xxxx it will use the interface specified there to source from for the TUNNEL PACKETS - the Outer tunnel packets. It has nothing to do with what traffic is sent through the tunnel itself. It has to be a real interface. What you have there is nonsense.
Create all three OpenVPN clients. Tell them all to use the WAN interface.
Go into Interfaces > (assign). Assign an interface to each ovpncx instance.
Edit each interface, enable it, name it, leave the IPv4 and IPv6 configurations as None.
Make sure you bounce each OpenVPN as this is a required step after initial interface assignment. Another Edit/Save with no changes of each OpenVPN client will do this, as will a Stop/Start of each service in Status > Services.
Make sure outbound NAT is set for each new interface so traffic leaving that interface gets source translated to that particular tunnel address.
You can then policy route whatever traffic you want over each OpenVPN at any time using the policy routing rules on the source network interface. You will have three OpenVPN gateways to choose from. One on each assigned interface.
And we're working!
Thanks a ton for sticking with me and helping me sort this out.
-
Excellent to hear. Glad it's working.
-
It is absolutely NOT possible to run 2 concurrent OpenVPN clients in 2.4.
Absolute nonsense.
-
It is absolutely NOT possible to run 2 concurrent OpenVPN clients in 2.4.
Absolute nonsense.
Great answer! At least wirh AirVPN this does not. I changed nothing configuration wise, just updated and nothing is working anymore. Then did everything from scratch, not working. I configured 20 times minimum 2 concurrent VPN on AirVPN with 2.x. No problems, never.
And as said there are always hard ifconfig errors coming up, change just a simple setting in Routing of one VPNM and both go down (a monitoring IP for instance).
What do you want to tell me with this significant sentence?If you can help help otherwise why bother?
When I was testing 2.4 I was getting ifconfig errors too. But, obviously it works for some people.
I've always had Don't Pull Routes and Don't Add/Remove Routes enabled for my OVPN clients.
The networks for the different VPNs I used did not overlap.
Anyway, I went back to 2.3.x and am happy in the meantime. Hopefully this will get figured out because I've seen several other people with the same problem.
-
It is absolutely NOT possible to run 2 concurrent OpenVPN clients in 2.4.
Absolute nonsense.
Great answer! At least wirh AirVPN this does not. I changed nothing configuration wise, just updated and nothing is working anymore. Then did everything from scratch, not working. I configured 20 times minimum 2 concurrent VPN on AirVPN with 2.x. No problems, never.
And as said there are always hard ifconfig errors coming up, change just a simple setting in Routing of one VPNM and both go down (a monitoring IP for instance).
What do you want to tell me with this significant sentence?If you can help help otherwise why bother?
When I was testing 2.4 I was getting ifconfig errors too. But, obviously it works for some people.
I've always had Don't Pull Routes and Don't Add/Remove Routes enabled for my OVPN clients.
The networks for the different VPNs I used did not overlap.
Anyway, I went back to 2.3.x and am happy in the meantime. Hopefully this will get figured out because I've seen several other people with the same problem.
Don't pull routes should be standard, yes. That was not the problem. If you had monitoring IPs in your Routing try to to remove them and just leave it blank. That did it for me. In pfsense 2.3.x this was no problem at all but in 2.4.1 it seems to. So no monitoring IPs and everything is working as expected now.
Thank you for your answer.
Cheers
-
It is absolutely NOT possible to run 2 concurrent OpenVPN clients in 2.4.
Absolute nonsense.
Great answer! At least wirh AirVPN this does not. I changed nothing configuration wise, just updated and nothing is working anymore. Then did everything from scratch, not working. I configured 20 times minimum 2 concurrent VPN on AirVPN with 2.x. No problems, never.
And as said there are always hard ifconfig errors coming up, change just a simple setting in Routing of one VPNM and both go down (a monitoring IP for instance).
What do you want to tell me with this significant sentence?If you can help help otherwise why bother?
When I was testing 2.4 I was getting ifconfig errors too. But, obviously it works for some people.
I've always had Don't Pull Routes and Don't Add/Remove Routes enabled for my OVPN clients.
The networks for the different VPNs I used did not overlap.
Anyway, I went back to 2.3.x and am happy in the meantime. Hopefully this will get figured out because I've seen several other people with the same problem.
Don't pull routes should be standard, yes. That was not the problem. If you had monitoring IPs in your Routing try to to remove them and just leave it blank. That did it for me. In pfsense 2.3.x this was no problem at all but in 2.4.1 it seems to. So no monitoring IPs and everything is working as expected now.
Thank you for your answer.
Cheers
Oh, is that it? Thanks for that tip. Yes, I do edit the IP for gateway monitoring as I like to see the RTT to the other side of the tunnel. Stinks that won't work in 2.4.
-
Same with me or like i did. Deleting it solved ALL the problems there were with the gateways, the ifconfig problems and everything else.
In a second :(
