[Q] Android KITKAT - VPNService Route Exclusion - Nexus 5 Q&A, Help & Troubleshooting

Hi All,
It is know that IP exclusion is almost impossible using Android VPN Service API in NON ROOTED Device.
But I have rooted device . So I first connect VPN ( openvpn ).
After than from ADB ROOT SHELL - I run following command
./route add -net <<DESTINATION_IP>> netmask 255.255.255.255 gw 192.168.1.1
For example if I run following command
./route add -net 141.101.120.15 netmask 255.255.255.255 gw 192.168.1.1
All traffic to whatismyip DOT com/ go directly ( Not passing through VPN )
Hence whatismyip.com reports my Local ISP IP in Its home page.
By these way I could exclude IPs from VPN path. This is working fine in ICS and Jelly without any issue.
But this same procedure not working in KITKAT. I tested both in 4.4.2 and 4.4.4
If I modify route, traffic still goes through VPN path. Whatismyip.com displaying VPN Server IP in its home page.
My KITKAT routing table shows following same as ICS and jelly. Command is successfully executed in routing table..But just not working..
Can anybody please point out what changes I need to make for KITKAT.
Thank you
----Fresh Routing Table -----
Code:
ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324
192.168.1.1 dev wlan0 scope link
----- After VPN Connected------
Code:
ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324
172.22.1.4/30 dev tun0 proto kernel scope link src 172.22.1.6
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324
192.168.1.1 dev wlan0 scope link
------ After whatismyip dot com [141.101.120.15] exclusion ------
Code:
ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324
[B]141.101.120.15 via 192.168.1.1 dev wlan0[/B]
172.22.1.4/30 dev tun1 proto kernel scope link src 172.22.1.6
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324
192.168.1.1 dev wlan0 scope link

Related

OpenVPN for PocketPC doesn't work - why?

Hallo zusammen,
I try to make a make a OpenVPN-Connection with my HTC-Hemes to my OpenVPN-Server. When I connect a Computer to my Hermes I can establish a VPN-Connection without any problems.
When I try to use the same Client-Config-File on my HTC-Hermes with OpenVPN for PocketPC it doesn't work.
I use the official ROM of WM6 (T-Mobile Germany) on my Hermes
I use this Version of OpenVPN for PocketPC:
http://ovpnppc.ziggurat29.com/ovpnppc-main.htm
I used the cab-File to install it directly on the Hermes
Where is the problem?
What do I have to change?
My OpenVPN-Server config:
# OpenVPN 2.1 Config, Sat Mar 21 10:01:07 CET 2009
proto udp
dev tap
ca /tmp/flash/ca.crt
cert /tmp/flash/box.crt
key /tmp/flash/box.key
dh /tmp/flash/dh.pem
tls-server
tls-auth /tmp/flash/static.key 0
port 1194
push "redirect-gateway"
ifconfig 192.168.201.97 255.255.255.0
push "route-gateway 192.168.201.97"
push "route 192.168.3.0 255.255.255.0"
max-clients 4
tun-mtu 1500
mssfix
verb 3
daemon
cipher BF-CBC
comp-lzo
float
keepalive 10 120
push "route-gateway 192.168.3.101"
Click to expand...
Click to collapse
my Client-Config:
client
dev tap
proto udp
remote tauscher.dyndns.org 1194
nobind
persist-key
persist-tun
ca "\\Programme\\OpenVPN\\config\\ca.cer"
cert "\\Programme\\OpenVPN\\config\\client1.cer"
key "\\Programme\\OpenVPN\\config\\client1.key"
tls-remote Eumex
tls-auth "\\Programme\\OpenVPN\\config\\ovpnstatic.key" 1
auth SHA1
cipher BF-CBC
comp-lzo
verb 4
Click to expand...
Click to collapse
Log of the Client:
http://pastebin.com/f447ce60b
Best wishes
UP

How do I spoof the mac address?

Is there a way to change the MAC address functionally, so that other devices think it has that address?
I have tried these methods (tiwlan0 corresponds to the wifi mac, no, it's not eth0)
In ADB: # ip link set tiwlan0 address 00:12:f0:dd:cc:dc
error: ip: SIOCSIFHWADDR: Operation not supported on transport endpoint
In terminal emulator on the phone: ip link set tiwlan0 address 00:12:f0:dd:cc:dc
error: ip: socket: operation not permitted
I have heard that some do change it but it reverts when communicating with a device.
It is working via fastboot.. There was a method somewhere in the Hero section.
Does this work on the G1?
Yes, it works flawlessly.
forum dot xda-developers dot com/showthread dot php?t=686789&highlight=mac+address+fastboot
Or search for mac fastboot in hero development forum.
On demand!
But how to do it on demand?
I usually can't launch fastboot in the airport
Removed...

asus transformer ubuntu wifi

Hi!
So finally I could make dual boot my transformer, (actually it's not as easy as I thought for first) and there is a problem:I can't use wifi, I ran the firmware-injector. I can modprobe it, the only problem is this: when I try to
iwlist wlan0 scan
Code:
wlan0 interface doesn't support scanning : Invalid argument
that's when I'm doing it as root if I'm non-root it just gives me:
Code:
no scan results
I tried, ifconfig wlan0 up as well. Of course I can't connect to my network.
ifconfig:
Code:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2260 (2.2 KB) TX bytes:2260 (2.2 KB)
wlan0 Link encap:Ethernet HWaddr 44:a7:cf:9a:d2:8f
inet6 addr: fe80::46a7:cfff:fe9a:d28f/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:181 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:696 (696.0 B) TX bytes:33285 (33.2 KB)
wlan0:avahi Link encap:Ethernet HWaddr 44:a7:cf:9a:d2:8f
inet addr:169.254.11.39 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
lsmod
Code:
Module Size Used by
bcm4329 194611 0
I'm using linux (debian) everywhere so it would be great to have a full (debian like) distro on my tf.
Other
Battery:
Actually the ubuntu sees the battery, and the battery temperature as well, check out the /sys/class/power_supply/battery/
so you just need to cat the voltage_now file and you know where you are.
Thanks:RiseR
I have the same problem. Here's what works for me:
-You can use 'iwlist wlan0 ap' instead of scan, although the results don't look quite right
-Even though scan doesn't work, you can still connect to open wifi points. Use 'ifconfig wlan0 down; iwconfig wlan0 mode managed; iwconfig wlan0 essid MyWifiNetwork; ifconfig wlan0 up; dhclient -v wlan0'
-Others claim to have had luck connecting to secure networks using wpa_supplicant, but without the ability to use scan it's really hit and miss. I'm just going to keep disabling my WPA when I need to transfer something until lilstevie fixes it.
With regard to the battery, voltage is not proportional to how fully charged the battery is. I suppose it could serve as an indicator of sorts in theory, but in practice the drop would be so close to going flat it wouldn't be of much use.
rdnetto said:
I have the same problem. Here's what works for me:
-You can use 'iwlist wlan0 ap' instead of scan, although the results don't look quite right
-Even though scan doesn't work, you can still connect to open wifi points. Use 'ifconfig wlan0 down; iwconfig wlan0 mode managed; iwconfig wlan0 essid MyWifiNetwork; ifconfig wlan0 up; dhclient -v wlan0'
-Others claim to have had luck connecting to secure networks using wpa_supplicant, but without the ability to use scan it's really hit and miss. I'm just going to keep disabling my WPA when I need to transfer something until lilstevie fixes it.
With regard to the battery, voltage is not proportional to how fully charged the battery is. I suppose it could serve as an indicator of sorts in theory, but in practice the drop would be so close to going flat it wouldn't be of much use.
Click to expand...
Click to collapse
Thanks for reply.
So, I'll disable the WPA but the problem is, I'm just home until October, and then I'll just be able to connect WPA secured network, so I have to install everything now. But OK so really thanks! and if you hear anything about WPA connection, and you have time please tell me.
Thanks:RiseR
Hello,
Ubuntu on the transformer is amazing and I am considering using this as a permanent os. I tried it with lxde or fluxbox and it works even better.
The major inconvenience for now is WIFI: I have exactly the same problem. Except for me 'iwlist eth0 scan' seems to work when I run it as a regular user, but it gives the same output when ran as root (interface doesn't support scanning : Invalid argument). wpasupplicant returns the same error (except if I use apscan=2, but it doesn't connect at all with no error this way)
The wifi driver is apparently opens soruce and I found the driver source files for android. Maybe it could work by recompiling the kernel with the driver source files ported from Android? (have no idea.. just a guess)
Anyway, a big thanks to all who made native ubuntu possible on the transformer!
follow the ubuntu eMMC thread. I finally got everything working but flash...but that could just be repository issues.
dcosmin said:
Hello,
Ubuntu on the transformer is amazing and I am considering using this as a permanent os. I tried it with lxde or fluxbox and it works even better.
The major inconvenience for now is WIFI: I have exactly the same problem. Except for me 'iwlist eth0 scan' seems to work when I run it as a regular user, but it gives the same output when ran as root (interface doesn't support scanning : Invalid argument). wpasupplicant returns the same error (except if I use apscan=2, but it doesn't connect at all with no error this way)
The wifi driver is apparently opens soruce and I found the driver source files for android. Maybe it could work by recompiling the kernel with the driver source files ported from Android? (have no idea.. just a guess)
Anyway, a big thanks to all who made native ubuntu possible on the transformer!
Click to expand...
Click to collapse
I suggest to us, what rdnetto said:remove the WPA. Now it works for me, and it is really, really cool It's amazing to run my opengl applications on the transformer. The biggest problems (why I'm still using dual boot)
1:I don't have keyboard dock yet, so i have to do everything with touchscreen --> there's no right click, and no xorg.conf where I can set that thing up.
2:Speakers don't work
3:this WPA problem
4:icewm don't work for now. Well I don't know. But when I choose from gdm menu it just gives me back to login screen.I'll try some other solution, but I think I can do that.
So, yeah Thanks for this hard work at xda! hope theese problems will be repaired and I can use my transformer as a netbook.
other:Try to use debian repos, if you don't have the package you're looking for. There's everything.

[Q] [ Reverse Tethering ] DNS is not working

When I did same thing on Galaxy S3, it's working fine.
But When it did it on Galaxy Note2, it some times works. once out of 10 times works.
If you look below, ping is working. but it's not working with the domain name.
I did nslookup and it's working.
I browsed to a website throught IP and it's working. but it's not working with domain.
I tried to adjust DNS info in ADB shell but still not working.
it's working some times. but most out of times it's not working.
Please some body gives me any hint.
thank you.
--------------------------------------------------------------
C:\Users\JaeHo>ipconfig
Ethernet adapter Local Area Connection 9:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::99d3:e644:18aa:c0fe%49
IPv4 Address. . . . . . . . . . . : 192.168.137.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
---------------------------------------------------------------
C:\Users\JaeHo>adb shell
[email protected]:/ $ su
su
[email protected]:/ # netcfg rndis0 dhcp
netcfg rndis0 dhcp
[email protected]:/ # route add default gw 192.168.137.1 dev rndis0
route add default gw 192.168.137.1 dev rndis0
[email protected]:/ # ping -c5 philgo.com
ping -c5 philgo.com
ping: unknown host philgo.com
2|[email protected]:/ # ping -c5 168.126.63.1
ping -c5 168.126.63.1
PING 168.126.63.1 (168.126.63.1) 56(84) bytes of data.
64 bytes from 168.126.63.1: icmp_seq=1 ttl=52 time=105 ms
64 bytes from 168.126.63.1: icmp_seq=2 ttl=52 time=100 ms
64 bytes from 168.126.63.1: icmp_seq=3 ttl=52 time=100 ms
64 bytes from 168.126.63.1: icmp_seq=4 ttl=52 time=132 ms
64 bytes from 168.126.63.1: icmp_seq=5 ttl=52 time=100 ms
--- 168.126.63.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 100.747/108.058/132.237/12.238 ms
[email protected]:/ # getprop net.dns1
getprop net.dns1
[email protected]:/ # nslookup philgo.com
nslookup philgo.com
nslookup: can't resolve '(null)': Name or service not known
Name: philgo.com
Address 1: 116.122.36.242
[email protected]:/ # ip route show
ip route show
default via 192.168.137.1 dev rndis0
192.168.137.0/24 dev rndis0 proto kernel scope link src 192.168.137.131
When setprop does not set the prop... :
Code:
iptables -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to-destination 8.8.8.8:53

[Q] Manually configure routing options for VPN tunnel

Hi All,
I have a stupid Juniper VPN device at work which does not support 64 bit linux clients using netconnect. I have found ways around this previously, but now we are setting up 2 factor auth which throws a lot of javascript into the mix, making the scripts I used pretty much obsolete. The Junos pulse client works well for android, so I am thinking I want to use an android device as a router. Connecting to the VPN and using wifi tethering does not work, same with USB tethering does not work, and those are not exactly what I want anyway.
So basically I want to be able to connect my android device to my wifi here at home, connect to the VPN on it, run a script to do my setup on the Android device, lastly add a route on my client pc to tunnel through the android device. here is what I tried so far on the device:
Code:
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
iptables -P FORWARD ACCEPT
iptables -t nat -I POSTROUTING -s 192.168.0.0/16 -d 10.0.0.0/8 -j MASQUERADE
ip rule add from all to 10.0.0.0/8 fwmark 0x3c lookup 60
and on the client PC:
Code:
route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.1.29
where 192.168.1.29 is the IP of my android device, and 10.0.0.0/8(I know its lazy) is the IP range I want to go through tun0 on the device. This is however not working.
The only thing I need to do on a standard linux box to do this would be:
Code:
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -I POSTROUTING -s 192.168.0.0/16 -d 10.0.0.0/8 -j MASQUERADE
And setup the same route command on the client but point it at the linux box instead. This currently works, but when we decide to flip the switch and use the 2 factor auth only I will not be able to make it work on a standard linux box, but 2 factor does work on android via the Junos app.
I fear I am missing something simple in Android land, please help...

Categories

Resources