No tun module in 10.04 breaks my vpn client

[grahams]

I use a SSLvpn-plus client

It's start up script looks for lsmod |grep tun.

On 10.04 tun is in the kernel and not a module, so SSLvpn-plus fails to start. Is there a way to fake that is there?

[cdenley]

Why not edit the startup script?

[grahams]

Tried that, but then the daemon starts and then fails.

[cdenley]

Tried that, but then the daemon starts and then fails.

Then it sounds like "faking" lsmod output for the startup script isn't going to help with your problem.

[jmercado]

I am experiencing this same issue but with Juniper's Network Connect Client (error "Modprobe for Tun driver failed"). Does anyone have any other suggestions on how we can get around this?

[cdenley]

Sorry, I mixed up this thread with another VPN-related one.

[grahams]

VPN can't establish that is the issue.

BTW. anyone know why tun is in the kernel now rather than staying as a module? Unless most users use vpn this makes no sense IMHO.

[cdenley]

You can try this, at your own risk.

mkdir faketun
cd faketun
echo -e "#include <linux/module.h>\nstatic int start__module(void) {return 0;}\nstatic void end__module(void){return 0;}\nmodule_init(start__module);\nmodule_exit(end__module);">tun.c
echo -e "obj-m += tun.o\nall:\n\tmake -C /lib/modules/\$(shell uname -r)/build/ M=\$(PWD) modules\nclean:\n\tmake -C /lib/modules/\$(shell uname -r)/build/ M=\$(PWD) clean\nclean-files := Module.symvers">Makefile
make -C /lib/modules/`uname -r`/build/ M=`pwd`
sudo insmod tun.ko

I'm running 9.10 and already have a tun module, so I haven't tested it. It basically creates a kernel module "tun" which does nothing.

[jmercado]

I tried out your code but it doesn't seem to help my situation with Juniper's VPN client. It might help grahams because "lsmod |grep tun" returns a line for tun (not after reboot, but that's a good thing for me).

The Juniper Network Connect client checks for tun via modprobe tun and I still got "FATAL: Module tun not found."

Thanks for the code cdenley!

[afriendinit]

Any luck? I am facing the same issue. I saw a bug on this but it says invalid bug as the module is already a part of kernel. They should at least mention a work around. This is the reason why many folks don't switch over...