Immediate "Failed to Connect" message then force close.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Added a connection
2. Tried to connect


What is the expected output? What do you see instead?
Connection successful
See failed connection instead and then a Force Closed

What version of the product are you using? On what operating system?
v. 03, using JF 1.5 on G1

Please provide any additional information below.
I am definitely rooted, I got vpnc to work before the front end and tun.ko 
was included on JF 1.5 build. When I try to connect it immediately says 
"Failed to Connect" then gives a "Sorry! The application VPN Connections 
(process org.codeandroid.vpnc_frontend) has stopped unexpectedly. Please 
try again. Force Close" message. 
Unfortunately I have no other log to determine what is needed. I will try 
to completely uninstall vpnc and reinstall the frontend. 

Original issue reported on code.google.com by tsi...@gmail.com on 22 Jul 2009 at 9:02

[GoogleCodeExporter]

Please look under /data/data/org.codeandroid.vpnc_frontend/files and attach the
lastConnection.log

Original comment by babak.mozaffari on 22 Jul 2009 at 9:15

[GoogleCodeExporter]

/data/data/org.codeandroid.vpnc_frontend/files/vpnc --script 
/data/data/org.codeandroid.vpnc_frontend/files/vpnc-script --no-detach
... Login info here

********

process stderr  


vpnc still trying to connect. Will check again in 500 milliseconds
/data/data/org.codeandroid.vpnc_frontend/files/vpnc-script: 
/data/data/org.codeandroid.vpnc_frontend/files/previous_dns_settings: not found
/data/data/org.codeandroid.vpnc_frontend/files/vpnc-script: 
/system/bin/make-tun-
device: not found
can't open /dev/net/tun, check that it is either device char 10 200 or (with 
DevFS) a 
symlink to ../misc/net/tun (not misc/net/tun): No such file or directory
can't initialise tunnel interface: No such file or directory

process stderr  /data/data/org.codeandroid.vpnc_frontend/files/vpnc-script: 
/data/data/org.codeandroid.vpnc_frontend/files/previous_dns_settings: not found
/data/data/org.codeandroid.vpnc_frontend/files/vpnc-script: 
/system/bin/make-tun-
device: not found
can't open /dev/net/tun, check that it is either device char 10 200 or (with 
DevFS) a 
symlink to ../misc/net/tun (not misc/net/tun): No such file or directory
can't initialise tunnel interface: No such file or directory

process had died, return as failed connection


Obviously I need to symlink or copy the make-tun-device over which I can do. 
Basically the prep script. 

Original comment by tsi...@gmail.com on 22 Jul 2009 at 9:26

[GoogleCodeExporter]

It looks that way. We're using the cyanogen ROM (it's JF1.5 + etc) and it seems 
to
have a "tun" device loaded and available under /dev/net

For the sake of our increasing support of various environments, please let us 
know
your exact configuration. Can you find "tun" or "tun.ko" anywhere on your phone
without running a script? If so, was it there as part of the JF ROM or did you
create/load it?

Original comment by babak.mozaffari on 22 Jul 2009 at 9:39

[GoogleCodeExporter]

I ran 
modprobe tun
mkdir /dev/net
ln -s /dev/tun /dev/net/tun
cp /data/data/org.codeandroid.vpnc/bin/make-tun-device /system/bin

I had to rename the address to be the url entry, but now it works great. Will 
restart 
the phone to see if the modprobe and symlink are necessary on boot. 
As of right now it works great. You guys are amazing, thanks so much for all of 
your 
work. 

Original comment by tsi...@gmail.com on 22 Jul 2009 at 9:41

[GoogleCodeExporter]

Those comments were before I saw yours, tun was already built. I had tried to 
load tun 
before it was already included in previous builds but that didn't work out. The 
tun did 
need to be loaded, but was already available.

Original comment by tsi...@gmail.com on 22 Jul 2009 at 9:43

[GoogleCodeExporter]

Our app does the following as needed:

mkdir /dev/net
ln -s /dev/tun /dev/net/tun

So you won't need the above after reboot.

We don't do a modprobe and are trying to find out what environment may require 
it. So
are you saying that with JF 1.5, there is a tun but you need to load it with
modprobe? Where is it and is it called tun.ko?

Original comment by babak.mozaffari on 22 Jul 2009 at 9:49

[GoogleCodeExporter]

I restarted and yes, all I needed was to do a modprobe to get it to work. I 
found tun 
at:
/system/modules/2.6.27-00392-g8312baf/kernel/drivers/net/tun.ko
I'm using JF 1.5 Build # CRB43
You have my kernel from above, on the T-Mobile G1

Original comment by tsi...@gmail.com on 22 Jul 2009 at 10:02

[GoogleCodeExporter]

Thank you for your continued feedback. We're trying to support as many 
environments
as possible and that includes loading the module for JF if need be. Since 
things seem
to be little different on your environment, can you confirm the exact modprobe 
syntax
you use to load it? And it seems like for your environment too, it ends up 
creating
/dev/tun (versus /dev/net/tun as one would expect). I'll try to have it in 
within the
hour after hearing back from you and hopefully get your feedback on whether it 
works
off a fresh reboot.

Original comment by babak.mozaffari on 22 Jul 2009 at 10:17

[GoogleCodeExporter]

I simply use "modprobe tun" As a complete statement which loads it well. 

I sincerely appreciate it, will check and verify as soon as possible after it's 
available. 

Original comment by tsi...@gmail.com on 22 Jul 2009 at 10:30

[GoogleCodeExporter]

Ok, I have v0.4 up for you but couldn't even unit test it myself... so please 
let me
know if it works.

Original comment by babak.mozaffari on 22 Jul 2009 at 10:50

[GoogleCodeExporter]

That's amazing, thank you so much. It worked perfectly. Tested it after a 
reboot with 
no issues.

I noticed it seemed to have issues connecting while not on a wifi but otherwise 
very 
responsive and does exactly what is wanted. 

Original comment by tsi...@gmail.com on 23 Jul 2009 at 1:59

[GoogleCodeExporter]

Please open a new issue and let me know if you have a log that shows a problem 
with
the data network. I wonder if it's timing out too fast for you or something.
Otherwise I can't see it be an issue. I personally have only been running on a 
data
network (non-wifi) so far.

Original comment by babak.mozaffari on 23 Jul 2009 at 2:10

• Changed state: Fixed