NetworkManager

jfryman · 2006-03-20 22:13:52

tor:

You are right on the money! If I go so far as to create a new network association, the encryption options are limited to plain text or WEP combinations.

I know the combination works on my laptop... I've used MN on both FC4 and Dapper before switching to Arch. Arch's network config scripts are very straightfoward, but I also use this laptop to demo linux to many people, and making sure the little niceties are there always counts.

wpa_supplicant is at 0.5.1, and libnl is 1.0pre5, so I'm where I need to be.

That chunk of code you mentioned:

NetworkManager: <WARNING> nm_signal_handler (): Caught signal 2, shutting down normally.

is simply me sending a SIGHUP to the daemon.... it was intentional so all is well.

My next thought would be to try CVS versions of wpa_supplicant/libnl to make sure everything is kosher... but I won't have time for that until later tomorrow.

Any other thoughts?

tor · 2006-03-21 19:51:42

[Edit] Foud something more likely. ipw2200 driver in arch is outdated, 1.0.8 which was released october last year Upgrading to a more recent will surely solve your problems. http://ipw2200.sourceforge.net/ latest as of this writing is 1.1.1, which is unstable, released in March. Or at least try the latest stable 1.0.13.

jfryman: after some digging i actually think that it is the package wireless-tools that is our problem. If i understand correctly it is them that is used to probe the capabilities of the network card.

Arch version of this package is 28pre-9 but there are other versions on their homepage: http://www.hpl.hp.com/personal/Jean_Tou … Tools.html which has a 28pre-15. Could you perhaps try to upgrade that and se if it makes any difference?

Unfortunately i dont have the HW to test this setup easily. So if that dont help i think that we have to ask on the NM maillist.

jfryman · 2006-03-21 22:12:07

I'm not sure if it's the ipw2200 driver... Ubuntu Dapper works just fine on 1.0.8

I'll try the updated wireless_tools (28pre15 I think is the latest) and see what comes of that. Next step will be the wpa_supplicant cvs.

[edit]
I've updated the wireless_tools, that did nothing.... the upgrade to ipw2200 1.1.1 went smoothly, and enabled wpa networks to be detected and enabled in the applet. I had some issues with connecting after the fact of the upgrade, but did another upgrade to wpa_supplicant 0.5.2, and everything started working after that.

Here's a pkgbuild for wpa_supplicant 0.5.2

# Contributor: iztok pizorn <pizorn@gmail.com>
# Contributor: William Rea <sillywilly@gmail.com>
force=y
pkgname=wpa_supplicant
pkgver=0.5.2
pkgrel=1
pkgdesc="A utility providing key negotiation for WPA wireless networks"
depends=('openssl')
backup=('etc/wpa_supplicant.conf')
url="http://hostap.epitest.fi/wpa_supplicant"
source=(http://hostap.epitest.fi/releases/wpa_supplicant-$pkgver.tar.gz 
        config)
md5sums=('a73b5b1be3f20f3e2c4d325f0a7a38e4' '6b9f86d1ea696f235a278b2613942bba')

build() {
  cd $startdir/src/$pkgname-$pkgver
  cp ../config ./.config
  sed -i 's@/usr/local@$(PREFIX)@g' Makefile
  make || return 1
  make PREFIX=/usr DESTDIR=$startdir/pkg install || return 1
  install -D -m644 wpa_supplicant.conf $startdir/pkg/etc/wpa_supplicant.conf
}

_Gandalf_ · 2006-03-22 01:21:05

I apologize for not being contributing with u guys, ive had a HDD failure for my server so i have a lot of work to do anyway i uploaded all the PKGBUILDS related to Gnome Network Manager and Gnome Power Manager to http://w.nasreddine.free.fr/arch/ , check it out

@jfryman Nice to see a new contributor here, glad to have u on Arch ..

keep up the good work guys

Blaasvis · 2006-03-23 14:47:10

i tried it today again

seems to work, but at first it wasnt't able to start at al..... that was dbus
then no device showed up .... hmmm hal...

so i would like recommend to put:
ck_daemon hal && /etc/rc.d/hal start

into the networkmanager rc.d script

_Gandalf_ · 2006-03-23 15:05:41

You batcha Arjan, am on it, that explains why i had to maually kill and start hal/dbus, i didn't know about ck_daemon function

Thx

_Gandalf_ · 2006-03-23 15:50:36

Okay a new version is up, i tested it by killing any hal process ans start it, it worked good
http://w.nasreddine.free.fr/arch/gnome-network-manager/
http://w.nasreddine.free.fr/i686/

ganlu · 2006-03-27 11:50:46

Great news, can we see those patches being accepted by upstream?

tor · 2006-03-27 12:09:25

We are trying to get them included. Unfortunately the NM developers don't seem to focus on new targets at the moment.

I have mailed the NM maillist twice and also submitted the patch to bugzila:http://bugzilla.gnome.org/show_bug.cgi?id=335147

jfryman · 2006-03-27 18:27:21

0.6.2 was released.... lots of bugfixes and Dynamic WEP added! See the changelog http://ftp.gnome.org/pub/GNOME/sources/ … .2.changes

Otherwise, a few things were changed. Here's the PKGBUILD

# Contributor: Wael Nasreddine <gandalf@siemens-mobiles.org>
# Contributor: Tor Krill <tor@krill.nu>
# Contributor: Will Rea <sillywilly@gmail.com>

pkgname=gnome-network-manager
pkgver=0.6.2
pkgrel=1
pkgdesc="A gnome Network Manager"
makedepends=('perlxml' 'pkgconfig')
depends=('wireless_tools' 'dhclient' 'gnome-panel' 'iproute' 'avahi' 'dhcdbd'
    'dbus>=0.60-1' 'libnl' 'wpa_supplicant>=0.5.0-1' 'libnotify' 'notification-daemon')
url="http://www.gnome.org/projects/NetworkManager/"
source=(http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.6/NetworkManager-$pkgver.tar.bz2 
    nm-madwifi-wpa-driver-rml.patch  arch-nm-20060327.patch policy.patch)

md5sums=('1254609e7d6a8de72677d63908bb4bd8' '2e1f48153a90add73b1fe12e0c41601d' 
     '4e3692b37afcabc51936a9011de43e27' 'd6d0e7d7fd037cf9cd062736942790c3')
build() {
  cd $startdir/src/NetworkManager-$pkgver

  # Applying patches
  patch -Np1 -i $startdir/src/nm-madwifi-wpa-driver-rml.patch || return 1
  patch -Np1 -i $startdir/src/arch-nm-20060327.patch || return 1
  patch -Np1 -i $startdir/src/policy.patch || return 1

  autoconf || return 1
  automake || return 1
  ./configure --prefix=/opt/gnome --sysconfdir=/etc --with-distro=arch 
            || return 1 
  make || return 1
  make DESTDIR=$startdir/pkg install || return 1

  # Libtool slay
  find $startdir/pkg -name *.la -exec rm {} ;
}

In addition, there is a function that needs to be added to NetworkManagerArch.c... I've created an updated diff, but I currently have no hosting sites. Below is the code addition

/*
 * nm_system_get_mtu
 *
 * Return a user-provided or system-mandated MTU for this device or zero if
 * no such MTU is provided.
 */
unsigned int nm_system_get_mtu (NMDevice *dev)
{
    return 0;
}

I'd be glad to email my diff file (arch-nm-20060327.patch) for anyone to host. Let me know!

-James

_Gandalf_ · 2006-03-27 18:45:54

jfryman, Can you please add arch-nm-20060327.patch to arch.pastebin.com and post the link so i can update/test it and then Tor update the AUR package ??
Thx

tor · 2006-03-27 19:35:37

Good news!

Just now our patch got added to mainline NM :-)

_Gandalf_ · 2006-03-27 19:54:30

Finally !!
/me building archck 2.6.16, i'll check the latest NM right after

WillySilly · 2006-03-27 20:34:47

tor, really? After all this time...Well, its better than never

jfryman · 2006-03-27 20:43:42

New code for arch-nm-20060327.patch is on arch.pastebin.com - http://arch.pastebin.com/625724

A few notes:

NM 0.6.2 no longer starts up DHCDBD on it's own... this is to prevent various racing conditions seen on various systems. I've created a startup script that needs to be placed in the DAEMONS array in rc.conf. This daemon is appropriately named 'dhcdbd'. Doesn't really matter where in the array you put it... it's not called until nm-applet does it's magic.

I thought about integrating the dhdcbd code into the initscript for networkmanager, but thought that maybe a separation might be a little cleaner and more desirable.... maybe... Suggestions always welcome!

I've also updated the PKGBUILD in the previous post to reflect the dhcdbd initscript addition.

Please test it out and let me know how it works. So far so good on my end.

-James

Tatey · 2006-04-02 13:23:04

I'd like to start with saying I really do appreciate the effort that you guys have contributed towards this package. Unfortunately, I'm unable to successfully build gnome-network-manager. I'm new to Arch Linux, though I come from a Gentoo background. Arch Linux is fantastic, and I can't understand why more people aren't using it .

Anyhow, I grabbed the files from the website that Gandalf linked in addition to the new PKGBUILD and patch from jfryman. I've built all the neccessary dependancies and I experienced a small issue with dbus 6.01-2 that I managed to resolve. My system is up-to-date using current, it's a fresh install from 0.7.1.

Here is the output I get when I execute "makepkg".

[root@nuggets gnome-network-manager]# makepkg
==> Making package: gnome-network-manager 0.6.2-1 (Mon Apr  3 15:06:37 EST 2006)==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==>     Using local copy of NetworkManager-0.6.2.tar.bz2
==>     Found nm-madwifi-wpa-driver-rml.patch in build dir
==>     Found arch-nm-20060327.patch in build dir
==>     Found policy.patch in build dir
==> Validating source files with MD5sums
    NetworkManager-0.6.2.tar.bz2 ... Passed
    nm-madwifi-wpa-driver-rml.patch ... Passed
    arch-nm-20060327.patch ... Passed
    policy.patch ... Passed
==> Extracting Sources...
==>     tar --use-compress-program=bzip2 -xf NetworkManager-0.6.2.tar.bz2
==> Removing existing pkg/ directory...
==> Starting build()...
patching file src/nm-device-802-11-wireless.c
Hunk #1 succeeded at 2425 (offset 144 lines).
patch: **** Only garbage was found in the patch input.
==> ERROR: Build Failed.  Aborting...

I am using the madwifi driver for my Netgear WG511T (Atheros) PCMCIA. I can confirm that wireless works, I'm using it right now . Any assistance would be greatly appreciated.

Cheers.

nightfrost · 2006-04-02 21:23:08

@Tatey: Did you cut and paste? I had that problem first as well. Try instead to download the file http://arch.pastebin.com/pastebin.php?dl=625724 and rename it.

@devs: I've been trying out networkmanager a little, mostly on open access points, and it works fine. At home, however, I have a wep network with shared/restricted key. But networkmanager constantly refuses to connect to it.

Connection is fine using /etc/network-profiles.

I've no clue how to debug it either.

By the way, it would be nice to have a PKGBUILD to grab nm from CVS, now that the arch patch is included (great work, and thanks for that!)

Also, I was wondering if there are any plans to separate networkmanager and the nm-applet, allowing KDE users to use nm-magic as well?

Cheers.

Tatey · 2006-04-03 06:49:40

Thanks very much nightfrost, that did the trick! Now Network Manager compiles and installs cleanly. I've added networkmanager to /etc/rc.conf and nm-applet to the GNOME sessions startup. It runs beautifully with my wired network, however, it refuses to connect to my wireless network. I'm using a 128bit Open Key. I'm also inclined to believe my AP is playing up, at times it wont let me connect to the web based interface and I have to reboot it.

tor · 2006-04-03 07:05:24

nightfrost: Which network card do you use? NM should be able to connect to any wep enabled network. Further more i have a PKGBUILD against CVS here,http://www.krill.nu/arch/NetworkManager/cvs/ , that i maintain since i have to test it ;-)

News in CVS is included check and start of dhcdb and hal and general upgrades to work with latest CVS.

I however have changed the name of the package from gnome-network-manager to networkmanager. Since i have not yet updated the PKGBUILD to handle this smothly, i had to first remove the old package and then install the new one. And another thing, i have not included the madwifi patch in this PKGBUILD so please, if you use it, let me know if problems occur with this.

nightfrost · 2006-04-03 08:57:41

Thanks for the PKGBUILD. I'm running makepkg right now. Let's see how it turns out

I'm using ipw2200 (v. 1.1.2). I'll post back if the cvs-version does the trick for me.

EDIT: Nah, it didn't work. It tries to connect after I give it the key, but simply fails establishing connection. No error message :-?

jfryman · 2006-04-03 13:25:44

I've looked at the CVS sources, and it looks like the dhcdbd init script didn't make it up there. Try this:

dhcdbd --system

Try to reconnect. NM no longer starts up dhcbdb to obtain a DHCP release as of 0.6.2. If that works, create a rc.d script and include it in your daemon array in rc.conf

Create an init in /etc/rc.d called dhcbdb and put this code inside

#!/bin/bash

DHCDBD_BIN=/sbin/dhcdbd

# general config
. /etc/rc.conf
. /etc/rc.d/functions

# Sanity checks.
[ -x $DHCDBD_BIN ] || exit 0

# We need /usr/sbin/ip
[ -x /usr/sbin/ip ] || exit 0

PID=`pidof -o %PPID $DHCDBD_BIN`

case "$1" in
    start)
        ck_daemon dbus && /etc/rc.d/dbus start 
        sleep 1
        stat_busy "Starting the DBUS DHCP Client"
        if [ -z "$PID" ]; then
            $DHCDBD_BIN --system
        fi
        if [ ! -z "$PID" -o $? -gt 0 ]; then
            stat_fail
        else
            add_daemon dhcdbd
            stat_done
        fi
        ;;
    stop)
        stat_busy "Stopping DBUS DHCP Client"
            [ ! -z "$PID" ] && kill $PID &> /dev/null
        if [ $? -gt 0 ]; then
            stat_fail
        else
            rm_daemon dhcdbd
            stat_done
        fi
        ;;
    restart)
        $0 stop
        sleep 1
        $0 start
        ;;
    *)
        echo "usage: $0 {start|stop|restart}"
        ;;
esac
exit 0

Start up dhcdbd and try to reconnect... it should work.

tor: Can you add the dhcdbd initscript to NetworkManagerCVS? I included the automakefile (dhcbdb.in) and changes in the last patch. Can you merge and include? This is to compensate for NM not calling dhcdbd automatically. Otherwise, anyone that uses this pkgbuild will not have a working install without fiddiling around a bit.

-James

tor · 2006-04-03 13:38:48

nightfrost: Have you upgraded your dhcdb to latest aur version? Beyond that ipw2200 of that version, 1.1.2, should work fine.

jfryman: I did not add the initscript to NM cvs. Only a check if dhcdbd is running and if not try to start it. I added your initscript to the aur package of dhcdbd Aur package [edit] But perhaps the NM pkgbuild should have a version requirement matching this.

nightfrost · 2006-04-03 16:30:10

Thanks for the replies. I have upgraded to the latest dhcdbd and made sure it's running:

ps ax | grep dhcd
 2277 ?        Ss     0:00 /sbin/dhcdbd --system
 3287 pts/0    S+     0:00 grep dhcd

But it's still a no-show. Still, it seems to work with open APs, my bet is that it has to do with the authentication part...

jfryman · 2006-04-03 17:04:16

If you are having auth problems with wep/wpa networks, try killing the networkmanager, and running it in no-daemon mode to get an idea of what is going on.

/opt/gnome/sbin/NetworkManager --no-daemon

Should give you a starting point on the reason for the lack of encryption support.

nightfrost · 2006-04-03 18:42:11

Thanks for the tip. Here's part of the output before NM gives up:

NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing own WPA/RSN IE
NetworkManager: <information>   wpa_supplicant(7250): Automatic auth_alg selection: 0x1
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing AP WPA IE
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing AP RSN IE
NetworkManager: <information>   wpa_supplicant(7250): clearing own WPA/RSN IE
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=13
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_drop_unencrypted
NetworkManager: <information>   wpa_supplicant(7250): State: ASSOCIATING -> ASSOCIATING
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_associate
NetworkManager: <information>   wpa_supplicant(7250): Setting authentication timeout: 10 sec 0 usec
NetworkManager: <information>   wpa_supplicant(7250): EAPOL: External notification - portControl=ForceAuthorized
NetworkManager: <information>   wpa_supplicant(7250): Wireless event: cmd=0x8b06 len=8
NetworkManager: <information>   wpa_supplicant(7250): Wireless event: cmd=0x8b1a len=15
NetworkManager: <information>   wpa_supplicant(7250): Wireless event: cmd=0x8b15 len=20
NetworkManager: <information>   wpa_supplicant(7250): Wireless event: new AP: 00:00:00:00:00:00
NetworkManager: <information>   wpa_supplicant(7250): BSSID 00:00:00:00:00:00 blacklist count incremented to 7
NetworkManager: <information>   wpa_supplicant(7250): State: ASSOCIATING -> DISCONNECTED
NetworkManager: <information>   wpa_supplicant(7250): EAPOL: External notification - portEnabled=0
NetworkManager: <information>   wpa_supplicant(7250): EAPOL: External notification - portValid=0
NetworkManager: <information>   wpa_supplicant(7250): eys
NetworkManager: <information>   wpa_supplicant(7250): CTRL_IFACE monitor send - hexdump(len=50): 2f 6f 70 74 2f 67 6e 6f 6d 65 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 37 32 32 33 2d 31 00
NetworkManager: <information>   wpa_supplicant(7250): Wireless event: cmd=0x8b19 len=8
NetworkManager: <information>   wpa_supplicant(7250): Received 189 bytes of scan results (1 BSSes)
NetworkManager: <information>   wpa_supplicant(7250): Scan results: 1
NetworkManager: <information>   wpa_supplicant(7250): Selecting BSS from priority group 0
NetworkManager: <information>   wpa_supplicant(7250): 0: 00:14:85:ba:85:14 ssid='voodoo' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
NetworkManager: <information>   wpa_supplicant(7250):    skip - no WPA/RSN IE
NetworkManager: <information>   wpa_supplicant(7250):    selected non-WPA AP 00:14:85:ba:85:14 ssid='voodoo'
NetworkManager: <information>   wpa_supplicant(7250): Trying to associate with 00:14:85:ba:85:14 (SSID='voodoo' freq=0 MHz)
NetworkManager: <information>   wpa_supplicant(7250): CTRL_IFACE monitor send - hexdump(len=50): 2f 6f 70 74 2f 67 6e 6f 6d 65 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 37 32 32 33 2d 31 00
NetworkManager: <information>   wpa_supplicant(7250): Cancelling scan request
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing own WPA/RSN IE
NetworkManager: <information>   wpa_supplicant(7250): Automatic auth_alg selection: 0x1
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing AP WPA IE
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing AP RSN IE
NetworkManager: <information>   wpa_supplicant(7250): WPA: clearing own WPA/RSN IE
NetworkManager: <information>   wpa_supplicant(7250): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
NetworkManager: <information>   Activation (eth1/wireless): association took too long (>20s), failing activation.
NetworkManager: <information>   Activation (eth1) failure scheduled...
NetworkManager: <information>   Activation (eth1) failed for access point (voodoo)
NetworkManager: <information>   Activation (eth1) failed.
NetworkManager: <information>   Deactivating device eth1.
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <WARNING>        nm_signal_handler (): Caught signal 2, shutting down normally.
NetworkManager: <information>   Caught terminiation signal
NetworkManager: <debug info>    [1144089661.715488] nm_print_open_socks (): Open Sockets List:
NetworkManager: <debug info>    [1144089661.715549] nm_print_open_socks (): Open Sockets List Done.
NetworkManager: <information>   Deactivating device eth0.
NetworkManager: <information>   Deactivating device eth1.

I don't understand the whole wpa-business. It's just a wep encryption so why is wpa_supplicant evoked?

Arch Linux

#76 2006-03-20 22:13:52

Re: NetworkManager

#77 2006-03-21 19:51:42

Re: NetworkManager

#78 2006-03-21 22:12:07

Re: NetworkManager

#79 2006-03-22 01:21:05

Re: NetworkManager

#80 2006-03-23 14:47:10

Re: NetworkManager

#81 2006-03-23 15:05:41

Re: NetworkManager

#82 2006-03-23 15:50:36

Re: NetworkManager

#83 2006-03-27 11:50:46

Re: NetworkManager

#84 2006-03-27 12:09:25

Re: NetworkManager

#85 2006-03-27 18:27:21

Re: NetworkManager

#86 2006-03-27 18:45:54

Re: NetworkManager

#87 2006-03-27 19:35:37

Re: NetworkManager

#88 2006-03-27 19:54:30

Re: NetworkManager

#89 2006-03-27 20:34:47

Re: NetworkManager

#90 2006-03-27 20:43:42

Re: NetworkManager

#91 2006-04-02 13:23:04

Re: NetworkManager

#92 2006-04-02 21:23:08

Re: NetworkManager

#93 2006-04-03 06:49:40

Re: NetworkManager

#94 2006-04-03 07:05:24

Re: NetworkManager

#95 2006-04-03 08:57:41

Re: NetworkManager

#96 2006-04-03 13:25:44

Re: NetworkManager

#97 2006-04-03 13:38:48

Re: NetworkManager

#98 2006-04-03 16:30:10

Re: NetworkManager

#99 2006-04-03 17:04:16

Re: NetworkManager

#100 2006-04-03 18:42:11

Re: NetworkManager

Board footer