HOWTO: NetworkManager with LEAP support

[misha680]

!!! THIS IS REALLY OUTDATED. nm-applet 0.6.5 and later on has LEAP support (this is the version in gutsy) !!!

Feisty debs are http://ubuntuforums.org/showthread.p...64#post2663064

Hi, these are debs I have made of the CVS version of NetworkManager. This includes LEAP support and also one checkinstalled deb that is included is the VPNC plugin. To install these debs simply click on the attachment that starts with dapper for Dapper Drake 6.06 systems or the one that starts with Edgy for Edgy Eft 6.10 systems, open with Archive Manager (this should be an option from firefox), and extract the files somewhere (e.g., /tmp). Then, either type:

cd /tmp
sudo dpkg -i *.deb

or find /tmp in Nautilus (Places->Filesystem->tmp) and double click on each .deb file to install with the GDebi installer. Then log out, log in and you should see the network manager applet in your top right-hand corner. That is all you need to do. To create a new LEAP wireless network, click on the network manager icon, click on "Create a new Wirless network" and you will see LEAP as an allowed network protocol. Enjoy!

Misha

p.s. In order for the vpnc plug-in to work correctly you must have the vpnc package installed. Either type:

sudo aptitude install vpnc

or "Search" for the vpnc plugin in Synaptic Pacakage Manager, right click on it, and select "Mark for Installation" then Apply.

p.p.s If you'd like to compile it yourself, it is very easy too. To get the CVS repositories, just type these commands:

sudo apt-get remove network-manager.*
sudo apt-get remove libnm.*
sudo apt-get install automake1.9
sudo apt-get build-dep network-manager
cvs -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login
cvs -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co NetworkManager
cd NetworkManager
gedit configure.in

Now, find the line that says:

        CFLAGS="-Wall -Werror -std=gnu89 $CFLAGS"

and change it to read:

        CFLAGS="-Wall -std=gnu89 $CFLAGS"

Great, now to compile and install it (I am using the checkinstall utility to make the debs and install it, if you just want to install it without it also making debs just use "sudo make install" instead):

./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var
make
sudo checkinstall --pkgname=network-manager

Only catch here, checkinstall (and debian packages) don't like certain things in the version numbers, so you must change it. I use something like cvs20060914 to indicate the date when I made the package.

That's it. You will still need the two files in network-manager-scripts.tar.bz2 that are attached. You can try getting them off the old network-manager debs from the repositories too if you want (they are both in /etc/dbus-1/system.d).

[dave_abrahams]

Some obstacles I ran into here:

1. building from CVS requires automake-1.9. No need to download the automake sources as I discovered after much flailing. Simply

sudo apt-get install automake1.9

2. In addition to removing network-manager before starting this process, I had to

sudo apt-get remove libnm-util0

3. The icon nm-vpn-lock is not present in my theme, which causes problems for nm-applet.

The NetworkManager applet could not find some required resources. It cannot continue.

The fix, from elsewhere on this forum, is:

sudo gtk-update-icon-cache -f /usr/share/icons/hicolor

I hope this helps someone. Maybe this HOWTO should be copied off the forums to some Wiki?

[misha680]

Deleted

[deception1]

Is this the normal dialoge when connecting to a vpn?

Memory status: size: 18178048 vsize: 0 resident: 18178048 share: 0 rss: 6520832 rss_rlim: 0
CPU usage: start_time: 1156658273 rtime: 0 utime: 19 stime: 0 cutime:16 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/nm-vpnc-auth-dialog'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224554832 (LWP 632]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb74982e3 in __waitpid_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f2bed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xb7536da2 in gnome_keyring_find_network_password_sync ()
from /usr/lib/libgnome-keyring.so.0
#5 0x0804a10c in ?? ()
#6 0x08063618 in ?? ()
#7 0x00000000 in ?? ()

Thread 1 (Thread -1224554832 (LWP 632):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb74982e3 in __waitpid_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2 0xb7f2bed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xb7536da2 in gnome_keyring_find_network_password_sync ()
from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#5 0x0804a10c in ?? ()
No symbol table info available.
#6 0x08063618 in ?? ()
No symbol table info available.
#7 0x00000000 in ?? ()
No symbol table info available.
#0 0xffffe410 in __kernel_vsyscall ()


Pascal.

[misha680]

Hmm... doesn't seem like it is for me. Does the VPN connection still work? If not, I'd suggest joining the network-manager developer list (see the NetworkManager web site, the developers subsection) and sending it to them. I'm sure they'd be more than likely to help.

Misha

Originally Posted by deception1 Is this the normal dialoge when connecting to a vpn? Memory status: size: 18178048 vsize: 0 resident: 18178048 share: 0 rss: 6520832 rss_rlim: 0 CPU usage: start_time: 1156658273 rtime: 0 utime: 19 stime: 0 cutime:16 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/nm-vpnc-auth-dialog' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224554832 (LWP 632] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb74982e3 in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7f2bed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 <signal handler called> #4 0xb7536da2 in gnome_keyring_find_network_password_sync () from /usr/lib/libgnome-keyring.so.0 #5 0x0804a10c in ?? () #6 0x08063618 in ?? () #7 0x00000000 in ?? () Thread 1 (Thread -1224554832 (LWP 632): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0xb74982e3 in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 No symbol table info available. #2 0xb7f2bed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #3 <signal handler called> No symbol table info available. #4 0xb7536da2 in gnome_keyring_find_network_password_sync () from /usr/lib/libgnome-keyring.so.0 No symbol table info available. #5 0x0804a10c in ?? () No symbol table info available. #6 0x08063618 in ?? () No symbol table info available. #7 0x00000000 in ?? () No symbol table info available. #0 0xffffe410 in __kernel_vsyscall () Pascal.

[TheAngryPenguin]

Upon trying to compile Network Manager from CVS, I receive the following errors:

During ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var:

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

...and then during sudo checkinstall --pkgname=network-manager:

Striping ELF binaries and libraries...OK

Compressing man pages...OK

Building file list...OK

Building Debian package... FAILED!

*** Failed to build the package

Do you want to see the log file?  [y]:

log file:

dpkg-deb: parse error, in file `/var/tmp/cAMpnBAUkEkrlSgLMdBba/package/DEBIAN/control' near line 8 package `network-manager':
 newline in field name `0.7.0'

Any ideas?

[minchina]

It looks like a new knetworkmanager package just came online in adept. Is this the same package that you are talking about manually installing? If so, I am still having problems finding LEAP support in the options. There are three WEP options and two WPA options, but none of them seem to have metion LEAP anywhere. If this new update is not the one that you have been manually updating, is there anything that I should change in the instructions when installing on Kubuntu?

Thanks

[misha680]

Ok, I think the first one may be solved by
doing

sudo apt-get install gnome-common

maybe also try

sudo apt-get automake1.9

But if you're getting to the make install part, it's probably not a problem.

As for the checkinstall problem, you just have
to remember to change the version number
(the package system doesn't like a bunch of
them, I don't remember the exact rules,
I use something like cvs20060914 to keep
track of mine as version numbers).

Misha

Originally Posted by TheAngryPenguin Upon trying to compile Network Manager from CVS, I receive the following errors: During ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var: Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. ...and then during sudo checkinstall --pkgname=network-manager: Striping ELF binaries and libraries...OK Compressing man pages...OK Building file list...OK Building Debian package... FAILED! *** Failed to build the package Do you want to see the log file? [y]: log file: dpkg-deb: parse error, in file `/var/tmp/cAMpnBAUkEkrlSgLMdBba/package/DEBIAN/control' near line 8 package `network-manager': newline in field name `0.7.0' Any ideas?

[misha680]

I would guess that they would not be putting up
the CVS versions, but probably 0.64 (or is it
0.6.4?). CVS is pretty much the most up-to-date
development version, and I think they are
slating LEAP support for 0.7. In any case,
if you don't see it it is not there. I am not
sure if you need to do anything different for
KDE. How do you run network-manager on KDE
(I assume it is not using nm-applet)?

Misha

Originally Posted by minchina It looks like a new knetworkmanager package just came online in adept. Is this the same package that you are talking about manually installing? If so, I am still having problems finding LEAP support in the options. There are three WEP options and two WPA options, but none of them seem to have metion LEAP anywhere. If this new update is not the one that you have been manually updating, is there anything that I should change in the instructions when installing on Kubuntu? Thanks

[minchina]

I just start knetworkmanager from the K menu. I can also do wireless with the wireless assistant application, but knetworkmanager seems like a more sophisticated option. I want to have this LEAP capability, but I am far from a linux ninja and I am worried that if I remove knetworkmanager and something goes wrong on the installation I will be totallly without wireless.
I will try and find some information about dealing with deb packages in kubuntu so that I can do it this way. This may be a question that you can't answer, but do you have any sense as to the kind of time frame this version would be released indo adept?

thanks