OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2

Gertjan

When I connect my iPhone using the OpenVPN app, it obtains a 192.168.3.2 (192.168.3.1/24 being the OpenVPN IPv4 network) :

From a PC on my LAN (192.168.1.1/24 ) I can ping my iPhone on 192.168.3.2.

highc

@gertjan

Thx, so this confirms that routing is broken here since the update.

I just googled the command for showing the routing table, and it seems that there is something missing for the OpenVPN net 10.0.10.0/24:

 netstat -r
Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            p3e9bf55d.dip0.t-i UGS      pppoe0
10.0.11.0/24       link#16            U        ovpns2
10.0.11.1          link#16            UHS         lo0
10.8.0.0/24        gateway            UGS       lagg0
10.9.0.0/24        gateway            UGS       lagg0
p3e9bf55d.dip0.t-i link#14            UH       pppoe0
p5b17515d.dip0.t-i link#14            UHS         lo0
localhost          link#6             UH          lo0
192.168.1.0/24     link#9             U         lagg0
firewall           link#9             UHS         lo0
192.168.2.0/24     gateway            UGS       lagg0
192.168.3.0/24     link#10            U      lagg0.30
192.168.3.1        link#10            UHS         lo0
192.168.4.0/24     link#3             U          igb0
192.168.4.2        link#3             UHS         lo0
192.168.5.0/24     link#11            U      lagg0.50
192.168.5.1        link#11            UHS         lo0
192.168.6.0/24     link#12            U      lagg0.60
192.168.6.1        link#12            UHS         lo0
192.168.7.0/24     link#13            U      lagg0.70
192.168.7.1        link#13            UHS         lo0

Would you happen to know how to fix this?

Gertjan

@highc said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

Would you happen to know how to fix this?

Undo whatever you did, related to routing ?
( honstly, I don't know how to 'read' a routing table to see what needs to be done where ).

My IPv4 routing table is pretty straight forward :

As I'm using :
a upstream ISP router using 192.168.10.1 - pfSense WAN is 192.168.1.3
pfPblockerNG uses 10.10.10.1
I consider my routes 'simple'.

You can clearly see 192.168.3.0 being the "OpenVPN" interface.

What you could do :
Take a know, recent ( !! - as it needs to be OpenVPN 2.5.2, that is the openVPN version, not the pfSense version that happens to be the same right now ) Youtube Video (example : Lawrence ?) and use that to make a working connection.
When it works, add you own changes 'up until it fails'. Then you know what the issue is.

highc

@gertjan said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

Undo whatever you did, related to routing ?

Just to be clear: The only thing I did, was upgrade vom 2.4.5p1. It worked there. Since them, I'm trying to get back to the state I had with 2.4.5p1.

Gertjan

@highc

The (a) OpenVPN setup probably needs some changes as many Open-VPN parameters changed when shifted from 2.4.x to 2.5.y.

I advise you to read what you mentioned :

@highc said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

(as available from here.

There is a big :

section.

Don't forget to export a newer opvn file for the clients.

highc

@gertjan
Ok, I did not just point to that section, but I actually read it ("of course, I'm tempted to say"). It might be that ...

Linux-specific features

    - VRF support
    - Netlink integration (OpenVPN no longer needs to execute ifconfig/route or ip commands)

... the netlink part is related to my problem. But there is no config option on this in pfSense. Neither would I know how to debug that part in pfSense. I'm happy to execute commands, but it would be great, if someone with a bit of background knowledge of how this works in pfSense could help me.

And as I said above, I did recreate the client config, exported it, and imported it again into the client. Doesn't work. I could redo the whole thing now for the third again and hope for a different outcome this time. But that sounds like a very desperate approach.

There are, by the way, open bug reports for OpenVPN related to pushing routes (e.g., here and here). But whether or not that is related to my problem where I can't even ping the OpenVPN client itself from pfSense, I don't know.

Gertjan

@highc

You entered this :

push "route 192.168.1.0 255.255.255.0"
 push "route 192.168.2.0 255.255.255.0"
 push "route 192.168.2.0 255.255.255.0"
 push "route 192.168.3.0 255.255.255.0"

?

( and why a leading space the last 3 lines ?)

johnpoz

@highc said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

something missing for the OpenVPN net 10.0.10.0/24:

You would not push the tunnel network you setup.. These should be in the routing table of pfsense, if openvpn is running.

example I use 10.0.8/24 and 10.0.200.248/29 in my tunnel networks.

routing table on pfsense shows these..

There really is little reason to use push route, networks you want your clients to get to should be listed in the local networks of your vpn

When not using the force gateway parameter

Notice if I disable the vpn instance, that route is no longer listed in pfsense for that tunnel network.

Gertjan

@johnpoz said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

You would not push the tunnel network you setup.

Did I miss that ?
He isn't pushing "10.0.10.0 255.255.255.0" (right ?)

As I have a

server 192.168.3.0 255.255.255.0

because my tunnel is 192.168.3.0/24

@highc has

server 10.0.10.0 255.255.255.0

as 10.0.10.0 is is tunnel.

highc

Ok, thanks. I've now configured the VPN to route all IPv4 traffic via the VPN. That works. Will leave it at that.

johnpoz

@gertjan said in OpenVPN Connection to iOS not working since update from 2.4.5p1 to 2.5.2:

He isn't pushing "10.0.10.0 255.255.255.0" (right ?)

No he isn't pushing it - but you wouldn't need too.. The problem I saw with his configuration was that pfsense showed no route for his tunnel.

So something glitched or his instance wasn't actually running as I showed. If the instance is running there should be routes on pfsense for that tunnel network. See where I tuned off my instance and the route went away.

My point about pushing as well - is there is really no reason to have to add those. As long as you list them as local networks they are auto pushed.. You don't need to add them to the options box, etc.