Attempt to resolve non-existant TUN issues on custom roms

[GoogleCodeExporter]

As per the message when the TUN object doesn't exist or isn't readable, this 
may be due to a custom ROM which hasn't correctly created the TUN object. As 
many of these ROMs also ship with root access, perhaps the app could try 
creating it's own TUN object if the one in /dev doesn't exist or is broken.

I would suggest this shouldn't disrupt the contents of /dev so perhaps you 
could create it in the data directory for the app.

You could add to the settings "use our TUN device" if it exists, which means it 
could be disabled if you've used something like Titanium Root to copy all the 
app configs, which may include the newly created TUN object. 

Original issue reported on code.google.com by [email protected] on 27 May 2012 at 8:54

[GoogleCodeExporter]

The problem is that this app relies on the System Service of the tun opening, 
route setting etc. I would have to duplicate all that for the "broken" images. 
And I would prefer if the custom ROMs would fix their VPNService support.

Can you check if /dev/tun exists? Perhaps it has only the wrong rights like on 
my CM9 image.

Original comment by [email protected] on 27 May 2012 at 9:20

[GoogleCodeExporter]

ls -l /dev/tun
crw-r----- vpn vpn 10, 200 2012-05-24 12:21 tun

I have found in the past that deleting and then re-running mknod for the tun 
module (mknod /dev/tun c 10 200) fixed it, but I'm guessing that just reset the 
permissions or the owner of that device?

Original comment by [email protected] on 27 May 2012 at 9:52

[GoogleCodeExporter]

See the FAQ. For my image a chown system /dev/tun is enough. What image are you 
using? CM9?

Original comment by [email protected] on 27 May 2012 at 10:13

[GoogleCodeExporter]

Spot on. It's Andromadus version "Beta_2", which is based off CM9.

Perhaps you could have "If /dev/tun can't be loaded, try su - -c chown system 
/dev/tun"?

Is there a ticket logged for this at all on the CM9 site? If not, I'll raise 
one.

Original comment by [email protected] on 27 May 2012 at 10:39

[GoogleCodeExporter]

I have not checked if there was a ticket on the CM9 site. The Defy port of CM9 
uses a motorola kernel (locked bootloader) and a motorola devtree so I thought 
it I would be specific to my image. I will into the su - stuff.

Original comment by [email protected] on 27 May 2012 at 11:31

[GoogleCodeExporter]

If you raise a ticket please add the URL to the ticket to this bug tracker so 
other people don't have to search the CM bug tracker.

Original comment by [email protected] on 30 May 2012 at 3:17

[GoogleCodeExporter]

"NO NIGHTLIES, UNOFFICIAL, SNAPSHOT, home-builds, or anything "based on"
CyanogenMod.

No CM9 reports will be accepted at this time."

Damn.

Original comment by [email protected] on 30 May 2012 at 3:25

[GoogleCodeExporter]

http:https://bugs.andromadus.com/issues/34 <- Not raised by me, but is relevant for 
my device.

Original comment by [email protected] on 30 May 2012 at 3:29

[GoogleCodeExporter]

Thanks for checking

Original comment by [email protected] on 30 May 2012 at 3:45

[GoogleCodeExporter]

This issue was closed by revision b5a892ae90fa.

Original comment by [email protected] on 30 May 2012 at 10:36

• Changed state: Fixed