tun-mtu size & embedded_packet_size_error
Posted: Wed Apr 09, 2014 8:21 pm
I'm encountering a problem staying connected to my VPN from my iOS device and searching hasn't turned up very much in the way of help. I'm hoping someone here might have some insight.
In iOS(7), I am able to connect to my VPN via the OpenVPN app; it connects, I have an IP address, I can even ping the device over the VPN from the VPN server.
But as soon as I try and access something (specifically an internal web server) on the VPN, the connection drops and I get an "embedded_packet_size_error" in my app.
It looks like the problem is with the tun-mtu setting.
On my server, I have a tun-mtu value of 6000. Of course I have this same value in my client configuration files and it works great with my Linux and OSX machines. On my iOS7 devices, however, looking through the log output, it appears as though it's using a tun-mtu value of 1500. At first I thought maybe I forgot to update the config on my iOS device, so I re-uploaded the config & keys, but I'm still getting the same number in the logs for the tun-mtu value.
Any ideas why this might be happening?
I can post my server & client configs if needed. I'm using the TCP protocol and the tun device (obvs).
TIA!
In iOS(7), I am able to connect to my VPN via the OpenVPN app; it connects, I have an IP address, I can even ping the device over the VPN from the VPN server.
But as soon as I try and access something (specifically an internal web server) on the VPN, the connection drops and I get an "embedded_packet_size_error" in my app.
It looks like the problem is with the tun-mtu setting.
On my server, I have a tun-mtu value of 6000. Of course I have this same value in my client configuration files and it works great with my Linux and OSX machines. On my iOS7 devices, however, looking through the log output, it appears as though it's using a tun-mtu value of 1500. At first I thought maybe I forgot to update the config on my iOS device, so I re-uploaded the config & keys, but I'm still getting the same number in the logs for the tun-mtu value.
Any ideas why this might be happening?
I can post my server & client configs if needed. I'm using the TCP protocol and the tun device (obvs).
TIA!