Openvpn as connected but not working on ipad

siulman

Hi,

I'm on vacation right now, far away from home, and need to access to some home files from my ipad.

The thing is the vpn session is well established but when I try to join some webservices using the private IP on my browser or even trying to connect on SSH to my server it's not working!!

I have an android smartphone and it's working great with the same profile...
I have tryed other profiles on the ipad but same issue...

Maybe it's from IOS 8.4 update I dont't know...I have been using it for one year...

I'm using openvpn access server

Can anybody helps please??

Envoyé de mon iPad en utilisant Tapatalk

jaka

iOS 8.4.1 same problem. I can connect to local web server, but not to any of the outside webpages. It was working well on iOS 8.4.

siulman

jaka wroteiOS 8.4.1 same problem. I can connect to local web server, but not to any of the outside webpages. It was working well on iOS 8.4.

Not the same issue...
I can't connect a local web server on the vpn server lan even if the session is up on the openvpn ipad client...

Envoyé de mon iPad en utilisant Tapatalk

Traffic

siulman wroteI can't connect a local web server on the vpn server lan even if the session is up on the openvpn ipad client...

What is your server LAN subnet ?

siulman

Traffic wrote
siulman wroteI can't connect a local web server on the vpn server lan even if the session is up on the openvpn ipad client...
What is your server LAN subnet ?

192.168.1.0/24

Envoyé de mon iPad en utilisant Tapatalk

Traffic

You should probably change it ..

NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.

You are advised to change your server LAN to a more unique RFC1918 compliant subnet. f.e 192.168.143.0/24

siulman

Traffic wroteYou should probably change it ..

NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.

You are advised to change your server LAN to a more unique RFC1918 compliant subnet. f.e 192.168.143.0/24

Thanks four your message.

I don't understand why this could be the problem...I mean....when connected to the VPN server, a new IP is assigned to the client (f.e 172.16.x.x depending on the server configuration).

Every packet sent from the client passes through the vpn tunel (except internet traffic if you configure it on the server) and is 'nated' from server.

192.168.0.1 (remote lan) --->> 172.16.0.1 (vpn network) -->> 192.168.1.110 (local lan)

No?

And as I explained before, it works perfectly on Android in same conditions....

Envoyé de mon iPad en utilisant Tapatalk

Traffic

siulman wroteThe thing is the vpn session is well established but when I try to join some webservices using the private IP on my browser or even trying to connect on SSH to my server it's not working!!

Using 192.168.0.0/24 or 1.0/24 greatly increases your chances of an accidental network conflict .. the simple answer is "do not use those networks" ..

siulman

Traffic wrote
siulman wroteThe thing is the vpn session is well established but when I try to join some webservices using the private IP on my browser or even trying to connect on SSH to my server it's not working!!
Using 192.168.0.0/24 or 1.0/24 greatly increases your chances of an accidental network conflict .. the simple answer is "do not use those networks" ..

I'm sorry but I disagree.
That's what the nat was made for... There is same private networks all over the world so no... It's not a reason for not working.

I insist, Android is working on the same network.

Envoyé de mon iPad en utilisant Tapatalk

Traffic

siulman wroteI'm sorry but I disagree.
That's what the nat was made for...

To which NAT do you refer ?

If you mean your server side LAN router performing NAT to keep your home network private then ..
That level of NAT does not separate your VPN client side LAN from your VPN server side LAN.

siulman wroteAndroid is working on the same network

Are you sure your Android is on the same network provider and even the same network as your ipad ?

BTW: we have no configs or logs with which to diagnose your issue ...

siulman

Traffic wrote
siulman wroteI'm sorry but I disagree.
That's what the nat was made for...
To which NAT do you refer ?

If you mean your server side LAN router performing NAT to keep your home network private then ..
That level of NAT does not separate your VPN client side LAN from your VPN server side LAN.

siulman wroteAndroid is working on the same network
Are you sure your Android is on the same network provider and even the same network as your ipad ?

BTW: we have no configs or logs with which to diagnose your issue ...

I mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP to avoid issues between the commun private networks as 192.168.X.X

And yes, I'm absolutely sure that Android is on the same network because I'm connected to the same WIFI network with both devices (Ipad and Samsung Galaxy).... so...

siulman

siulman wrote
Traffic wrote
siulman wroteI'm sorry but I disagree.
That's what the nat was made for...
To which NAT do you refer ?

If you mean your server side LAN router performing NAT to keep your home network private then ..
That level of NAT does not separate your VPN client side LAN from your VPN server side LAN.

siulman wroteAndroid is working on the same network
Are you sure your Android is on the same network provider and even the same network as your ipad ?

BTW: we have no configs or logs with which to diagnose your issue ...
I mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP to avoid issues between the commun private networks as 192.168.X.X

And yes, I'm absolutely sure that Android is on the same network because I'm connected to the same WIFI network with both devices (Ipad and Samsung Galaxy).... so...
Of course, not the same wifi network than the server. A remote network on my family's place.

Traffic

siulman wroteI'm sorry but I disagree.
That's what the nat was made for...

Traffic wroteTo which NAT do you refer ?

siulman wroteI mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP to avoid issues between the commun private networks as 192.168.X.X

I am still not convinced you understand ...

Traffic wroteBTW: we have no configs or logs with which to diagnose your issue ...

siulman

Traffic wrote
siulman wroteI'm sorry but I disagree.
That's what the nat was made for...
Traffic wroteTo which NAT do you refer ?
siulman wroteI mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP to avoid issues between the commun private networks as 192.168.X.X
I am still not convinced you understand ...

Traffic wroteBTW: we have no configs or logs with which to diagnose your issue ...

🙁 ...

If you have to patience to explain I would certainly read and think about it...

In any case the argument for android is the good one 🙂

Envoyé de mon iPad en utilisant Tapatalk

Traffic

siulman wroteIf you have to patience to explain I would certainly read and think about it

What is NAT ?

siulman wroteI mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP

What is DHCP ?

Traffic wroteBTW: we still have no configs or logs with which to diagnose your issue ...

siulman

Traffic wrote
siulman wroteIf you have to patience to explain I would certainly read and think about it
What is NAT ?

siulman wroteI mean the NAT done by the VPN server which gives to the client a 172.16.X.X IP
What is DHCP ?

Traffic wroteBTW: we still have no configs or logs with which to diagnose your issue ...

Solved.

Thanks.

Envoyé de mon iPad en utilisant Tapatalk