| View previous topic :: View next topic |
| Author |
Message |
sog
Guru
Joined: 04 Apr 2004
Posts: 356
|
 Posted: Fri Jun 17, 2005 6:34 pm Post subject: NetworkManager, netapplet, and ipw2200 |
 |
|
just wanted to drop in a quick post for folks interested in wireless on Gentoo, and who've used either the NetworkManager or netapplet to connect to networks.
like many other folks, i've been very grateful for the work that rabbit and Fergus put it on netapplet, and used it quite happily on my old machine (Thinkpad x23).
unfortunately, my new machine (Thinkpad x40) has an Intel ipw2200bg PCI card, which despite working fine wirelessly, does not play nicely with my ipw2200 setup. [see post here https://forums.gentoo.org/viewtopic-t-214228-start-125.html]
so while waiting to see if anyone has ideas on a fix there, i've been casting about for an alternative and looked at NetworkManager, which while occasionally disparaged on these boards is a reasonable facsimile of netapplet's functionality. what made NetworkManager even more interesting was that Robert Love, one of the guys behind netapplet, now seems to be contributing to NetworkManager [see here http://mail.gnome.org/archives/networkmanager-list/2005-June/thread.html].
unfortunately, the latest version (0.4) wouldn't install for me, and while casting about for the dependencies (there's no ebuild yet and the NetworkManager site doesn't appear to list them), i found this site (http://www.ces.clemson.edu/linux/nm.shtml) which indicates that among other things NetworkManager requires DBUS 0.33 and HAL 0.5.2.
given that neither of those are in portage yet - even masked - i then tried to install the .31 version of the software from BMG, but the NetworkManager-0.3.1.050205.tar.bz2 required is no longer on BMG or the NetworkManager site.
so two questions:
1. does anyone happen to have that file, either downloaded or in their Portage distfiles?
2. is there any possibility of seeing one of these packages (netapplet or NetworkManager) in Portage any time soon? the only bug i found was here (https://bugs.gentoo.org/show_bug.cgi?id=92541) - am i missing any? is there wireless work going on that i'm not aware of?
_________________
------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
| Back to top |
|
 |
steevdave
Retired Dev
Joined: 25 Oct 2004
Posts: 73
Location: Tulsa, OK
|
| Posted: Sat Jun 18, 2005 5:30 am Post subject: |
|
|
Do a search on bugzilla for Gentopia - it is a bit bleeding edge, but it includes support for dbus > .33 and hal > .4
There is also a NetworkManager ebuild in the overlay for it. |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Thu Jul 07, 2005 8:05 pm Post subject: networkmanager |
|
|
I got NetworkManager running on my Laptop nx7010 with 2200BG interface & driverloader Linuxant (I never got ipw2200 running for now...  ), whith the Gentopia ebuild and some tricks I found in the NetworkManager mailing-list but I never got it connect to my access point & get an IP for my interface with dhcp...
I also read that there could be some problems on gentoo because of the specifity of its network config system...
Rgds,
jvlalonde |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Wed Jul 13, 2005 4:42 pm Post subject: |
|
|
| Anyone got NetworkManager to work in gentoo ? |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Thu Jul 14, 2005 9:42 am Post subject: NetworkManager |
|
|
I still have the same DHCP Problem...
Try the NetworkManager Mailing-List:
| Code: |
http://mail.gnome.org/mailman/listinfo/networkmanager-list
|
jvlalonde |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Thu Jul 14, 2005 1:15 pm Post subject: networkmanager |
|
|
Ok,
I got NetworkManager running for my wired interface on my nx7010 Laptop.
Here's what I did:
1.) Updated dhcp to dhcp-3.0.2 which I patched with the dhcp patch found in the gentopia ticket system:
https://dev.cardoe.com/gentopia/ticket/18
2.) Created a /sbin/dhclient-script script. I found an error in my NetworkManager log about this missing script. The solution was in the mailing-list where I found an example of the script:
| Code: |
#!/bin/bash
#set -vx
if [ -n "${dhc_dbus}" ]; then
/usr/bin/dbus-send \
--system \
--dest=com.redhat.dhcp \
--type=method_call \
/com/redhat/dhcp/$interface \
com.redhat.dhcp.set \
'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
if (( ( dhc_dbus & 31 ) == 31 )); then
exit 0;
fi;
fi;
|
3.) started NetworkManager with my wireless device disabled and it worked (got an ip etc... from dhcp server). Yoooo-hooooo...
The only things that doesn't work is the nm-applet which doesn't show the connection.
I'll now try to connect my wireless device and give you a feedback.
jvlalonde |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Thu Jul 14, 2005 2:13 pm Post subject: |
|
|
That's interesting. Is it networkmanager-0.4 ?
Afaik from asking the gentoo devs, the problem with networkmanager right now is the gentoo backend, which is not ported to the network scripts of gentoo. |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Thu Jul 14, 2005 8:23 pm Post subject: networkmanager |
|
|
Yes, it's NetworkManager-0.4.
Theres a patch in the Gentopia overlay refering to the gentoo backend.
To compile, I also had to include the dbus-34 patch from gentopia.
I had no success with my wireless device for now. The nm-applet keeps telling "No network devices have been found."
When I plug a cable in, the wired interface initiate dhcp and works but the applet still complains... I posted this problem to the mailing list.
jvlalonde. |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Thu Jul 14, 2005 8:31 pm Post subject: |
|
|
| I use gentopia overlay on my system. Do you just 'emerge networkmanager', or did you add any more patches ? Also did you emerge dhcdbd, or emerge diamond ? |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Thu Jul 14, 2005 8:47 pm Post subject: networkmanager |
|
|
I use the the gentopia ebuild which I modified to use a dbus patch. You'll find the whole story here:
https://dev.cardoe.com/gentopia/ticket/16
Here's my ebuild:
| Code: |
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
inherit gnome2 debug eutils
DESCRIPTION="Network configuration and management in an easy way. Desktop env independent"
HOMEPAGE="http://people.redhat.com/dcbw/NetworkManager/"
SRC_URI="http://people.redhat.com/dcbw/NetworkManager/${PV}/NetworkManager-${PV}.cvs20050506.tar.gz"
LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE="crypt wifi debug doc gnome"
RDEPEND=">=sys-apps/dbus-0.23
=net-misc/dhcp-3.0.2-r1
>=sys-apps/hal-0.2.91
>=sys-apps/iproute2-2.6.10.20050112-r1
wifi? net-wireless/wireless-tools
>=dev-libs/glib-2.0
gnome? ( >=x11-libs/gtk+-2
>=gnome-base/libglade-2
>=gnome-base/gnome-keyring-0.4
>=gnome-base/gnome-panel-2
>=gnome-base/gconf-2
>=gnome-base/libgnomeui-2 )
crypt? ( dev-libs/libgcrypt )"
DEPEND="${RDEPEND}
dev-util/pkgconfig
dev-util/intltool"
S=${WORKDIR}/NetworkManager-${PV}
DOCS="AUTHORS COPYING ChangeLog INSTALL NEWS README"
USE_DESTDIR="1"
G2CONF="${G2CONF} \
`use_with crypt gcrypt` \
--disable-more-warnings \
--with-distro=gentoo \
--with-dbus-sys=/etc/dbus-1/system.d \
--enable-notification-icon"
src_unpack () {
unpack ${A}
cd ${S}
epatch ${FILESDIR}/NetworkManager-${PV}-dbus_34.patch
epatch ${FILESDIR}/NetworkManager-${PV}-gentoo_backend.patch
}
|
I'm running dhcdbd. |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Fri Jul 15, 2005 4:04 pm Post subject: networkmanager |
|
|
Coooooooooooolllllllll!!!
I got my wireless interface works as well with NetworkManager!
I changed the permissions in /etc/dbus-1/system.d/NetworkManager.conf (I added my user with the same perissions as root, as I did in nm-applet.conf), and now everything work like a charm...
I could enter my wlan settings in the applet (essid & 128 WEP Key) and the interface connected and got IP settings with dhcp.
jvlalonde |
|
| Back to top |
|
|
FruitCake
n00b
Joined: 24 Oct 2002
Posts: 34
Location: Perth, Western Australia
|
| Posted: Sat Jul 16, 2005 1:31 am Post subject: |
|
|
I've had NetworkManager fully working on my laptop for about 4 months. It's an ASUS S5200N with an Intel IPW2100 wireless card in it.
I've been sticking with the 0.3 branch and rolling my own cvs snapshots based on the bmg gnome-extra/NetworkManager ebuild. Currently running a snapshot from 3rd of May 2005. Should probably update but its all working perfectly.
Well almost perfectly, for some reason it creates resolv.conf with 0600 perms when it connects to a new network.
One thing i did change is the NetworkManager dbus config files. Seems the standard dbus supplied with gentoo does support the at_console conditions, so move the entries from that xml block into the default allow one makes it all work. |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Mon Jul 18, 2005 2:53 am Post subject: |
|
|
| You guys got 0.3 to work or 0.4 too ? |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Mon Jul 18, 2005 4:50 am Post subject: |
|
|
| OK - I got it to work with the tweaks in /etc/dbus. I hope soon there will be a better way to make it work out of the box (without console pam). Too bad there's no wpa support yet ... |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Mon Jul 18, 2005 7:57 am Post subject: NetworkManager |
|
|
| I got it work with 0.4. |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Mon Jul 18, 2005 12:04 pm Post subject: |
|
|
| It would be nice to test some cvs snapshot, there's many changes since 0.4 |
|
| Back to top |
|
|
fuoco
Guru
Joined: 23 May 2004
Posts: 386
Location: Israel
|
| Posted: Mon Jul 18, 2005 5:50 pm Post subject: |
|
|
| the wireless network identification works, but it doesn't get ip from dhcp. I have installed dhcdbd-1.6. How did you get the dhcp part to work ? |
|
| Back to top |
|
|
jvlalonde
n00b
Joined: 11 May 2002
Posts: 46
|
| Posted: Tue Jul 19, 2005 10:06 am Post subject: networkmanager |
|
|
Have you created this script?:
| Code: |
2.) Created a /sbin/dhclient-script script. I found an error in my NetworkManager log about this missing script. The solution was in the mailing-list where I found an example of the script:
Code:
#!/bin/bash
#set -vx
if [ -n "${dhc_dbus}" ]; then
/usr/bin/dbus-send \
--system \
--dest=com.redhat.dhcp \
--type=method_call \
/com/redhat/dhcp/$interface \
com.redhat.dhcp.set \
'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
if (( ( dhc_dbus & 31 ) == 31 )); then
exit 0;
fi;
fi;
|
I have created a compressed tar from the networkmanager cvs and copied it to /usr/portage/distfiles. It works if you plan to try it as well. Don't forget to update the ebuild file and update the digests.
Rgds,
jvlalonde |
|
| Back to top |
|
|
steevdave
Retired Dev
Joined: 25 Oct 2004
Posts: 73
Location: Tulsa, OK
|
| Posted: Fri Jul 22, 2005 4:11 am Post subject: |
|
|
I have my own personal overlay at http://www.steev.net/files/overlay which includes a snapshot from yesterday (20 Jul 2005) with the backend patch applied, as well as the dbus patch to work with dbus .35.2 (also in my overlay) - the one thing is that I named it 0.4_pre20050720, so you have to mask the ebuild that is in Gentopia.
It works here when I manually add a wireless connection (I use dhcpdbd in my overlay) but I haven't got a working wifi card, so I would appreciate if people would test this out (I don't have the dhclient-script setup at all) and give me feedback. (Prefer if they were emails to [url]mailto:steev@steev.net[/url]) but I will attempt to watch this forum (I have a bad habit of not checking forums often due to dialup.) |
|
| Back to top |
|
|
jamesshuang
Tux's lil' helper
Joined: 08 Aug 2002
Posts: 120
|
| Posted: Sat Jul 23, 2005 1:07 am Post subject: |
|
|
| Any chance you can post that complete overlay as a package somewhere? or CVS? It's a bit annoying to have to download it file by file... |
|
| Back to top |
|
|
steevdave
Retired Dev
Joined: 25 Oct 2004
Posts: 73
Location: Tulsa, OK
|
| Posted: Sat Jul 23, 2005 3:00 am Post subject: |
|
|
You don't need the entire overlay, just the NetworkManager stuff - it should work with the Gentopia overlay, I just have a few packages that are more experimental than Gentopia  But yes, I will post a tarball of it, I am a dialup user though, so I tend to just rsync it daily. |
|
| Back to top |
|
|
jamesshuang
Tux's lil' helper
Joined: 08 Aug 2002
Posts: 120
|
| Posted: Sat Jul 23, 2005 5:04 am Post subject: |
|
|
Ok, thanks... I tried the whole thing earlier, and it seems to work until fetching an address... It's doing some really REALLY weird things to the routing. First of all, none of the networks retrieve an IP. Log is as follows:
| Code: |
Jul 23 00:22:04 alexa NetworkManager: <information> FORCE: device '/org/freedesktop/NetworkManager/Devices/eth0', network 'linksys'
Jul 23 00:22:04 alexa NetworkManager: <information> Deactivating device eth0.
Jul 23 00:22:06 alexa NetworkManager: <debug info> [1122092526.281945] (): Forcing AP 'linksys'
Jul 23 00:22:06 alexa dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 23 00:22:06 alexa NetworkManager: <information> Device eth0 activation scheduled...
Jul 23 00:22:06 alexa NetworkManager: <debug info> [1122092526.286665] (): NetworkManagerInfo triggered update of wireless network 'linksys'
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) started...
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) scheduled...
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) started...
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) scheduled...
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) complete.
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) starting...
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0/wireless) Stage 1 (Device Configure) will connect to access point 'linksys'.
Jul 23 00:22:06 alexa NetworkManager: <information> Activation (eth0/wireless): access point 'linksys' is unencrypted, no key needed.
Jul 23 00:22:06 alexa NetworkManager: <information> Old device 'eth0' activating, won't change.
Jul 23 00:22:08 alexa NetworkManager: <information> Activation (eth0/wireless): using essid 'linksys', with no authentication.
Jul 23 00:22:08 alexa NetworkManager: <information> Activation (eth0/wireless) Stage 2 (Device Configure) successful. Connected to access point 'linksys'.
Jul 23 00:22:08 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) scheduled.
Jul 23 00:22:08 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) complete.
Jul 23 00:22:08 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) started...
Jul 23 00:22:09 alexa NetworkManager: <information> Activation (eth0) Beginning DHCP transaction.
Jul 23 00:22:09 alexa dhcdbd: Unrequested down ?:3
Jul 23 00:22:09 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) complete.
Jul 23 00:22:09 alexa NetworkManager: <information> DHCP daemon state now 14 for interface eth0
Jul 23 00:22:30 alexa dhcdbd: dbus_svc_init failed: org.freedesktop.DBus.Error.NoReply No reply within specified time
Jul 23 00:22:30 alexa dhcdbd: Failed to initialise D-Bus service.
Jul 23 00:22:34 alexa NetworkManager: <information> Device 'eth0' DHCP transaction took too long (>25s), stopping it.
Jul 23 00:22:34 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) scheduled...
Jul 23 00:22:34 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) started...
Jul 23 00:22:34 alexa NetworkManager: <information> No DHCP reply received. Automatically obtaining IP via Zeroconf.
Jul 23 00:22:34 alexa NetworkManager: <information> autoip: Sending probe #0 for IP address 169.254.228.27.
Jul 23 00:22:34 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:36 alexa NetworkManager: <information> autoip: Sending probe #1 for IP address 169.254.228.27.
Jul 23 00:22:36 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:38 alexa NetworkManager: <information> autoip: Sending probe #2 for IP address 169.254.228.27.
Jul 23 00:22:38 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:41 alexa NetworkManager: <information> autoip: Sending announce #0 for IP address 169.254.228.27.
Jul 23 00:22:41 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:44 alexa NetworkManager: <information> autoip: Sending announce #1 for IP address 169.254.228.27.
Jul 23 00:22:44 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:47 alexa NetworkManager: <information> autoip: Sending announce #2 for IP address 169.254.228.27.
Jul 23 00:22:47 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 23 00:22:50 alexa NetworkManager: <information> Activation (eth0) Stage 5 (IP Configure Commit) scheduled...
Jul 23 00:22:50 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) complete.
Jul 23 00:22:50 alexa NetworkManager: <information> Activation (eth0) Stage 5 (IP Configure Commit) started...
Jul 23 00:22:50 alexa NetworkManager: <information> Your IP address = 169.254.228.27
|
In any case, whatever networkmanager does, it does some funky things to the routing after I start it. If I start the service at boot time, my networking ability is shot. Even if I stop the service, kill all related processes, DNS doesn't resolve anything. I can fetch my own ip with dhcpcd or dhclient, and they would both fill in the /etc/resolv.conf file properly... I can ping the addresses in them, but nothing would resolve. Any ideas on getting this working? Networkmanager really does look spiffy...
I really don't understand why this has to be so hard though... Before I found gtkwifi or networkmanager, I had my own bash script that would very efficiently find, and connect to a few preferred networks. I didn't like it though, because it had no visual feedback for success or failure. Why does a simple little thing that checks a few logs, and acts appropriately need fancy-shmancy dbus, its own dhcp client, the whole kit? Just makes it more complex, harder to fix, and easier to break... |
|
| Back to top |
|
|
steevdave
Retired Dev
Joined: 25 Oct 2004
Posts: 73
Location: Tulsa, OK
|
| Posted: Sat Jul 23, 2005 3:42 pm Post subject: |
|
|
How are you starting X ? it seems you don't have a dbus session running. Or dhcdbd cannot connect to it.
do this (as a user) export | grep DBUS (from a terminal inside X) Let me see the output of that.
Also, paste the NetworkManager.conf and nm-applet.conf from /etc/dbus-1/system.d/ if you would?
And what useflags are you using for NetworkManager, which version of dbus, and which version of hal ? |
|
| Back to top |
|
|
steevdave
Retired Dev
Joined: 25 Oct 2004
Posts: 73
Location: Tulsa, OK
|
| Posted: Sat Jul 23, 2005 5:11 pm Post subject: |
|
|
| Ok, apparently, nscd --invalidate=hosts doesn't re-read /etc/resolv.conf like i thought it does, so, I have added a patch to my overlay that removes that. |
|
| Back to top |
|
|
jamesshuang
Tux's lil' helper
Joined: 08 Aug 2002
Posts: 120
|
| Posted: Mon Jul 25, 2005 2:35 am Post subject: |
|
|
Hello, sorry I've been busy this weekend. I'm currently trying your new ebuilds. export | grep DBUS gives me this:
| Code: | declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-lVx1Hmjgy8,guid=f647e4429437d0410afc87c9d5270200"
declare -x DBUS_SESSION_BUS_PID="19735" |
BTW, the new dbus seems to kill gnome-volume-manager. Complains about this:
| Code: | | gnome-volume-manager: error while loading shared libraries: libdbus-glib-1.so.0: cannot open shared object file: No such file or directory |
When I try to reemerge gnome-volume-manager, it oddly gives me a whole bunch of compile errors both for the 1.2.1 version and the 1.2.2 version. Any ideas on how to fix this? Thanks for your help! |
|
| Back to top |
|
|
|
Networking & Security
