Android 2.3.4 stops transfer data a whille after openvpn setup

[GoogleCodeExporter]

Hi,
I've been using azilink on Samsung Galaxy S, Android 2.2.1 and Linux with great 
success.

Now I've upgraded Android to 2.3.4 and have to upgrade ADB to 1.0.26 to talk to 
Galaxy S. I've newly installed azilink 2.0.2.

Everything seems to be OK BUT there are about 1000 bytes transfered IN and OUT 
and after that it stops transfer data. I can download part of the web page or 
make couple of pings and after that it stops communicate.

No errors, no logs, it just does not transfer any byte.

When I stop ADB, openvpn and azilink and run it again I can transfer some bytes 
before it stops communicate.

Milan

Original issue reported on code.google.com by milan.be...@gmail.com on 27 Jun 2011 at 2:51

[GoogleCodeExporter]

I see the same issue on my HTC Evo 4G.  Same behavior as OP, a handful of 
kilobytes make it through, then it stops.  All the byte counters stop 
incrementing.  Nothing in any logs that I can see.

Azilink 2.0.1 worked well when my phone was running Android 2.2, but when I 
upgraded to Android 2.3 it stopped working.  I upgraded to azilink 2.0.2 on the 
phone and that didn't change anything.  I'm running OpenVPN 2.1.0 under Lucid 
on the host.

Let me know if I can help with debugging in any way.

Original comment by seb.kuzm...@gmail.com on 12 Jul 2011 at 3:42

[GoogleCodeExporter]

Same here. Was working fine before on,
HTC Incredible 2
Stock Android 2.2
Verizon carrier
My son accidentally accepted the OTA 2.3.3 update and now azilink is broken.
My connection keeps disconnecting then reconnecting after just a few bytes.

I suspected foul play from Verizon so I reloaded EZtether beta to test and it 
still works fine.

many thanks for the great app. looking forward to a fix.
ken (help debugging also offered)

Original comment by k...@mort.net on 20 Jul 2011 at 4:58

[GoogleCodeExporter]

Same here. Working fine before
SE Xperia X8, Custom ROM 2.2
now: Custom ROM 2.3.4 --> stops at about 1000 bytes

Original comment by mag.mart...@gmail.com on 20 Jul 2011 at 11:24

[GoogleCodeExporter]

Is anybody trying to fix this?

Original comment by ronnie...@gmail.com on 4 Sep 2011 at 1:19

[GoogleCodeExporter]

I seem to have this same issue on my HTC Evo since upgrading to Android 2.3.3.  
I noticed my lockups seems to occur after dns lookups which use the udp 
protocol.  I downloaded the source for azilink and seem to have traced the 
problem to a lockup occurring in UdpDriver.onRead() when calling mChannel.read( 
dat ) the second time through the for loop.  I think this is related to a 
blocking problem with DatagramChannel introduced by gingerbread.

I found this related issue:  
http://code.google.com/p/android/issues/detail?id=16579 (DatagramChannel and 
ServerSocketChannel do not respect non-blocking mode)

I didn't figure out how implement the work arounds they noted but came up with 
my own temporary until someone who knows more can solve the problem or they fix 
gingerbread.

I don't know the total consequences, but my work around has been to remove the 
loop surrounding the mChannel.read( dat ) in UdpDrive.onRead().  I may just be 
having luck with it since udp is mostly used for dns lookups.  Maybe problems 
or slow downs will occur with larger streams using udp.  I've attached my copy 
of my UdpDriver.java source.

Original comment by joexx...@gmail.com on 11 Sep 2011 at 1:29

Attachments:

• UdpDriver.java

[GoogleCodeExporter]

I tried the workaround described in comment 5, but it failed for me. A security 
exception would ultimately be thrown.

I've had a hard time tracking where the problem is. I can set breakpoints in 
Eclipse, but as soon as I try to connect my computer to my phone, the debug 
connection is lost. Furthermore, absolutely none of my log messages appear in 
DDMS. How did you trace the execution to UdpDriver?

Original comment by crj...@gmail.com on 15 Sep 2011 at 1:03

[GoogleCodeExporter]

Can't imagine why commenting out the "for loop" in UdpDrive would cause a 
security exception to be thrown.  Something else different?

Anyways, I only used the logcat portion of DDMS with the command "adb -d logcat 
| grep -i azilink"
I also set VpaNatEngine.sLog = true to utilize existing Log.v statements and 
added my own Log.v statements to narrow down the fact that the UdpDriver looped 
once and then never came back from the second time mChannel.read(dat) was 
called.   I haven't tried using break points on my actual phone.

Original comment by joexx...@gmail.com on 15 Sep 2011 at 3:00

[GoogleCodeExporter]

Guys,

So I've used the pointers from the posters above to modify UdpDriver, and it 
seems to be working on the gingerbread now (got it on verizon droid2). Attached 
is the modified source file.

Original comment by alex.bur...@gmail.com on 12 Nov 2011 at 5:09

Attachments:

• UdpDriver.java

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I tried the new UdpDriver fix from alex above but my browser seemed less 
responsive compared to my shortcut.  But, I modified alex's fix by replacing 
selector.select(500) with selector.selectNow() on line 182.  This is working 
for me and seems more responsive.  Was there a reason for using the select with 
a 500 millisecond delay?  It seems like that would add a half second delay to 
every dns lookup.

Though there is only a tiny difference I've attached my new modified UpdDriver.

Original comment by joexx...@gmail.com on 13 Nov 2011 at 5:11

Attachments:

• UdpDriver.java

[GoogleCodeExporter]

I was just going by some example on use of Selector (I'm new to Android), and 
didn't have enough time on Friday to debug the code. Thanks for the fix!

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:21

[GoogleCodeExporter]

Joe,

I've checked your changes, and I can see you only modified one select(500) to 
selectNow(). Perhaps the second one (inside the loop) needs to be modified too ?

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:37