search

shennushi / android-openvpn-settings

Automatically exported from code.google.com/p/android-openvpn-settings
GNU General Public License v3.0
0 stars 0 forks source link

"Connected" and cannot ping. Browser does not use tunnel #80

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Opening a connection 
2. ping -c 1 -I tun0 192.168.1.1 | ping: unknown iface tun0
3.

What is the expected output? What do you see instead?
Should be able to ping the gateway

What version of the product are you using?
0.4.7

Which Android phone are you using?
Rooter thunderbolt Das BAMF 1.8.6

Which firmware version are you using?

Please provide any additional information below.
Running android-openvpn-settings on Das BAMF 1.8.6 rooted thunderbolt.

My config file:
[code]
remote mine.dyndns.org 443
client
proto tcp
nobind
dev tap
comp-lzo
verb 4
log /sdcard/openvpn/openvpn.log
resolv-retry infinite
persist-key
persist-tun
redirect-gateway def1
dhcp-option DNS 192.168.1.1
route-gateway 192.168.1.1
route-delay 10
ns-cert-type server
key-direction 1
ca "camine.crt"
cert "mine2.crt"
[/code]

Had to manually add this route for the log file to be free of errors.  
route-default would cause some route add/del's that would give Invalid 
Parameter or No Such Process errors since 192.168.1.0 wasnt anywhere in the 
table.  So running this before opening the VPN tunnel got rid of the errors:
[code]busybox route add -net 192.168.1.0 netmask 255.255.255.0 
rmnet_sdio0[/code]

Heres what my routing table looks like after android-openvpn-settings runs and 
says the tunnel is open:
[code]
# busybox route -n
busybox route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
98.249.31.333 192.168.1.1    255.255.255.255 UGH   0      0        0 rmnet_sdio0
98.249.31.333 10.189.54.12   255.255.255.255 UGH   0      0        0 rmnet_sdio0
10.189.54.11   0.0.0.0         255.255.255.240 U     0      0        0 
rmnet_sdio0
192.168.1.0    0.0.0.0         255.255.255.0   U     0      0        0 
rmnet_sdio0
0.0.0.0         192.168.1.1    128.0.0.0       UG    0      0        0 
rmnet_sdio0
128.0.0.0       192.168.1.1    128.0.0.0       UG    0      0        0 
rmnet_sdio0
0.0.0.0         192.168.1.1    0.0.0.0         UG    0      0        0 
rmnet_sdio0
0.0.0.0         10.189.54.12   0.0.0.0         UG    0      0        0 
rmnet_sdio0
[/code]

No clue if the table is OK now.  One weird thing is I can't ping through tun0 
at all.  Don't see tun0 in ifconfig either...  Did I miss some huge step?
[code]# ping -c 1 -I tun0 192.168.1.1
ping -c 1 -I tun0 192.168.1.1
ping: unknown iface tun0[/code]

only background I have is with that config (except redirect-gateway instead of 
redirect-gateway def1) used to work on my old WM phone.

Anyone have any ideas?  Let me know if I can provide any more details...  Ive 
been racking my brain on this the past couple of days.  Out of ideas.

Original issue reported on code.google.com by Jonathan...@gmail.com on 11 Jul 2011 at 3:36

GoogleCodeExporter commented 9 years ago 
Saw "netcfg tap0 dhcp" in issue 79.  That got mine working.

Can that be an option in the next build? to run that after the connection is 
made?

Original comment by Jonathan...@gmail.com on 25 Jul 2011 at 5:23

GoogleCodeExporter commented 9 years ago

Original comment by friedrich.schaeuffelhut on 29 Dec 2011 at 12:52

GoogleCodeExporter commented 9 years ago

Original comment by friedrich.schaeuffelhut on 3 Jan 2012 at 8:31

GoogleCodeExporter commented 9 years ago

Original comment by friedrich.schaeuffelhut on 17 Jan 2012 at 10:27

GoogleCodeExporter commented 9 years ago

Original comment by friedrich.schaeuffelhut on 28 Jan 2012 at 2:59