|
Cannot use Juniper Networks VPN with Liquorix kernel
I had installed Liquorix 2.6.36-2 on my CrunchBang Linux desktop, but found that I was unable to use the Juniper Networks "Network Connect" product to VPN into my employer's corporate network. The issue seems to be related to the tunnel device, as seen in this error:
:: Code :: 20110122183402.89522 ncsvc[p3886.t3886] adapter.error Can not open tun device 19 (adapter.cpp:320)
I can provide a larger snippet of the error message if it would be useful. As a workaround, I'm booting the standard Debian kernel (2.6.32-5), which connects to the VPN without issues, but it would be ideal if I could use the much speedier Liquorix kernel! Back to top |
|||||
|
Can you test Debian's trunk kernel? It's easier to confirm if it's just upstream mucking things up first.
Back to top |
|||||
|
Sure, I can try that. Where would I find the trunk kernel? Right now I'm using the sid repository. The relevant line from /etc/apt/sources.list is as follows:
:: Code :: deb http://ftp.us.debian.org/debian/ sid main contrib non-free
Back to top |
|||||
|
Try adding the experimental branch.
:: Code :: deb http://ftp.us.debian.org/debian/ experimental main contrib non-freeBack to top |
|||||
|
Thanks for the reply. I added the branch you recommended and found these kernels available for installation:
:: Code :: pablo@sydcrunch=> sudo apt-cache search kernel | grep linux-image
linux-image-2.6.36-2.dmz.5-liquorix-686 - Linux 2.6.36 for modern PCs linux-image-2.6-liquorix-686 - Linux image for liquorix on modern PCs linux-image-2.6.32-5-486 - Linux 2.6.32 for old PCs linux-image-2.6.32-5-686-bigmem-dbg - Debugging infos for Linux 2.6.32-5-686-bigmem linux-image-2.6.32-5-686-bigmem - Linux 2.6.32 for PCs with 4GB+ RAM linux-image-2.6.32-5-686 - Linux 2.6.32 for modern PCs linux-image-2.6.32-5-amd64 - Linux 2.6.32 for 64-bit PCs linux-image-2.6.32-5-openvz-686-dbg - Debugging infos for Linux 2.6.32-5-openvz-686 linux-image-2.6.32-5-openvz-686 - Linux 2.6.32 for modern PCs, OpenVZ support linux-image-2.6.32-5-vserver-686-bigmem-dbg - Debugging infos for Linux 2.6.32-5-vserver-686-bigmem linux-image-2.6.32-5-vserver-686-bigmem - Linux 2.6.32 for PCs with 4GB+ RAM, Linux-VServer support linux-image-2.6.32-5-vserver-686 - Linux 2.6.32 for modern PCs, Linux-VServer support linux-image-2.6.32-5-xen-686-dbg - Debugging infos for Linux 2.6.32-5-xen-686 linux-image-2.6.32-5-xen-686 - Linux 2.6.32 for modern PCs, Xen dom0 support linux-image-2.6-486 - Linux 2.6 for old PCs (meta-package) linux-image-2.6-686-bigmem - Linux 2.6 for PCs with 4GB+ RAM (meta-package) linux-image-2.6-686 - Linux 2.6 for modern PCs (meta-package) linux-image-2.6-amd64 - Linux 2.6 for 64-bit PCs (meta-package) linux-image-2.6-openvz-686 - Linux 2.6 for modern PCs (meta-package), OpenVZ support linux-image-2.6-vserver-686-bigmem - Linux 2.6 for PCs with 4GB+ RAM (meta-package), Linux-VServer support linux-image-2.6-vserver-686 - Linux 2.6 for modern PCs (meta-package), Linux-VServer support linux-image-2.6-xen-686 - Linux 2.6 for modern PCs (meta-package), Xen dom0 support linux-image-486 - Linux for old PCs (meta-package) linux-image-686-bigmem - Linux for PCs with 4GB+ RAM (meta-package) linux-image-686 - Linux for modern PCs (meta-package) linux-image-amd64 - Linux for 64-bit PCs (meta-package) linux-image-openvz-686 - Linux for modern PCs (meta-package), OpenVZ support linux-image-vserver-686-bigmem - Linux for PCs with 4GB+ RAM (meta-package), Linux-VServer support linux-image-vserver-686 - Linux for modern PCs (meta-package), Linux-VServer support linux-image-xen-686 - Linux for modern PCs (meta-package), Xen dom0 support linux-image-2.6.37-trunk-486 - Linux 2.6.37 for old PCs linux-image-2.6.37-trunk-686-bigmem-dbg - Debugging infos for Linux 2.6.37-trunk-686-bigmem linux-image-2.6.37-trunk-686-bigmem - Linux 2.6.37 for PCs with 4GB+ RAM linux-image-2.6.37-trunk-686 - Linux 2.6.37 for modern PCs linux-image-2.6.37-trunk-amd64 - Linux 2.6.37 for 64-bit PCs I tried installing linux-image-2.6.37-trunk-686 but errored out on dependencies: :: Code :: pablo@sydcrunch=> sudo apt-get install linux-image-2.6.37-trunk-686
Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-2.6.37-trunk-686 : Depends: linux-base (>= 2.6.37-1~experimental.1) but 2.6.32-30 is to be installed Recommends: firmware-linux-free (>= 2.6.37) but 2.6.32-30 is to be installed E: Broken packages Should I be choosing a different kernel? I am currently running on 2.6.32-5-686. Back to top |
|||||
|
With experimental you have to handle the dependencies yourself, like so, until it installs:
apt-get install linux-image-2.6.37-trunk-686 linux-base firmware-linux-free I'm not sure if you have to explicitly use the -t experimental flag here or if that will do it. Note that by installing linux-base you are altering your base system, so only proceed if you understand what is going on. apt-cache show linux-base will give you more info about the package. Personally i have always avoided experimental because it's not actually a true debian package pool, it's just a collection of random packages, ie, it does not have real dependency handling etc like stable/testing/sid do. Back to top |
|||||
|
Add -t experimental to your apt-get commands.
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||