Re: Network manager and Debian sid
Hi, Michael Biebl has done great job preparing NM for Debian. Here is his private repository: http://debs.michaelbiebl.de/network-manager/ BR, Hristo On Mon, 12 May 2008 12:05:21 +0200 Marco [EMAIL PROTECTED] wrote: Thanks guys for your work!! I'have been following the development of NM 0.7 project since January and now I succedded in packaging all the NetworkManager stuff for my debian sid box. After some quarrel on the new nm-system setting service that is now a system-service I can now use NetworkMnager right from the init.d boot process assigning my Eth0 the right address before logging in. I had to delete all entries in /etc/network/interfaces matching eth0 to start NM without racing with /etc/init.d/networking. Even the only auto eth0 lead to a wrong configuration of NM, probably because of debian network scripts bring up eth0 in ipv6. With only loopback in /etc/network/interfaces all is fine. I now use the keyfile plugin under debian and the new PolicyKit rules to manage the system-connections. My system-connection is: [EMAIL PROTECTED]:~$ cat /etc/NetworkManager/system-connections/Casa [connection] id=Casa type=802-3-ethernet autoconnect=true timestamp=1205857717 [802-3-ethernet] port=tp speed=0 duplex=full auto-negotiate=true mtu=0 [ipv4] method=manual address1=192.168.233.2;255.255.255.0;192.168.233.1; I struggled two days before having the right syntax on last line. Anyway, thanks for you good work. Bye Marco ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Network manager and Debian sid
Thanks guys for your work!! I'have been following the development of NM 0.7 project since January and now I succedded in packaging all the NetworkManager stuff for my debian sid box. After some quarrel on the new nm-system setting service that is now a system-service I can now use NetworkMnager right from the init.d boot process assigning my Eth0 the right address before logging in. I had to delete all entries in /etc/network/interfaces matching eth0 to start NM without racing with /etc/init.d/networking. Even the only auto eth0 lead to a wrong configuration of NM, probably because of debian network scripts bring up eth0 in ipv6. With only loopback in /etc/network/interfaces all is fine. I now use the keyfile plugin under debian and the new PolicyKit rules to manage the system-connections. My system-connection is: [EMAIL PROTECTED]:~$ cat /etc/NetworkManager/system-connections/Casa [connection] id=Casa type=802-3-ethernet autoconnect=true timestamp=1205857717 [802-3-ethernet] port=tp speed=0 duplex=full auto-negotiate=true mtu=0 [ipv4] method=manual address1=192.168.233.2;255.255.255.0;192.168.233.1; I struggled two days before having the right syntax on last line. Anyway, thanks for you good work. Bye Marco ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network manager and Debian sid
I didnt know thanks for the info. Availability of up to date debian packages is another point in favour of NM 0.7. Marco ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-editor: Can't make existing configuration a system setting
On Tue, May 6, 2008 at 5:36 PM, Tambet Ingo [EMAIL PROTECTED] wrote: On Tue, May 6, 2008 at 4:50 PM, Michael Biebl [EMAIL PROTECTED] wrote: When I run the connection-editor from within nm-applet, it presents me a list of configured wlan networks (Auto foo, Auto bar, ...). I wanted to make one of those configurations a system setting, so I pressed Edit and checked the System setting checkbox. Unfortunately, this doesn't make nm-system-settings write a config file in /etc/NetworkManager/system_config. If I instead use Add, and check the System setting right from the start, nm-system-settings correctly creates a config file (which works properly). So it seems as if nm-applet doesn't convert an existing (user)configuration into a system setting configuration. Is this a known issue? It's known to me :) I sort of left it like that until the whole thing is secured with PolicyKit. Dan needs to approve my PK patches first, so you can blame him as well. :) Anyway, I'm glad it works properly with the add button for you, this is the first success story I hear. Should be fixed now. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How to connect to my universities WPA2-network via nm-applet (SVN)?
Hi,
I can successfully connect to my universities wlan with the following
config:
# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=uni-ms
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP
password=***
identity=***
priority=5
phase1=peaplabel=0
phase2=auth=MSCHAPV2
}
Somehow I am not able to connect to the same network with the nm-applet
GUI. I think I tried all possible combination, but none works.
So which should work??
I have wpa_supplicant logs of the working and failed attempts ...
I am on openSUSE an using the following packages:
# rpm -qa | grep NetworkM
NetworkManager-gnome-0.7.0.r720-1
NetworkManager-vpnc-0.7.0-52
NetworkManager-glib-0.7.0.r3649-0
NetworkManager-vpnc-gnome-0.7.0-52
NetworkManager-devel-0.7.0.r3649-0
NetworkManager-0.7.0.r3649-0
any help would be appreciated.
TIA
Felix Möller
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-system-settings problem
On Fri, 2008-05-09 at 18:22 -0400, Gene Czarcinski wrote: On Friday 09 May 2008 11:11:51 Gene Czarcinski wrote: I have reported a problem with system-settings/plugins/ifcfg-fedora/plugin.c not detecting changes made by system-config-network because the ifcfg file in /etc/sysconfig/network-scripts/ is really a hardlink rather than the main file. https://bugzilla.redhat.com/show_bug.cgi?id=444502 Besides the patch I have outlined in the bug report (towards the end), it appears that simply adding another int (wd2) to the SCPluginIfcfgPrivate struct definition could be used to hold the value of hardlink's wd. I would appreciate more knowledgable eyes to take a look at the bug report to see if the patch I have outlined makes sense. If this makes sense, I will cobble a patch together and submit it. Yet more fooling around and testing. I MAY have found a quick and simple fix: In ifcfg-fedora/plugin.c around line 52, change: #define IFCFG_DIR SYSCONFDIR/sysconfig/network-scripts/ to: #define IFCFG_DIR SYSCONFDIR/sysconfig/networking/devices/ This change appears to put ifcfg-fedora/plugin.c in sync with system-config-network as the what the real file is being changed. However, the whole business of hardlinks is being ignored stuff_changed() since evt.wd is NOT the expected one. What I have seen so far is the wd==1 for the watched directory but wd1 for hardlinks. Since there can be multiple devices defined, the value of wd can vary all over the place. Now, the question is: What does this change screw up??? Originally we did monitor /etc/sysconfig/networking/profiles/default (which is one of the 3 hardlink locations) but many people expect to change the files in /etc/sysconfig/network-scripts/ instead. Not everyone uses system-config-network evidently. So this change will make the system settings service no longer recognize direct changes to files in /etc/sysconfig/network-scripts/. The actual solution is to fix the inotify bits to accurately track changes to hardlinked files. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network manager and Debian sid
On Mon, 2008-05-12 at 12:05 +0200, Marco wrote: Thanks guys for your work!! I'have been following the development of NM 0.7 project since January and now I succedded in packaging all the NetworkManager stuff for my debian sid box. After some quarrel on the new nm-system setting service that is now a system-service I can now use NetworkMnager right from the init.d boot process assigning my Eth0 the right address before logging in. I had to delete all entries in /etc/network/interfaces matching eth0 to start NM without racing with /etc/init.d/networking. Even the only auto eth0 lead to a wrong configuration of NM, probably because of debian network scripts bring up eth0 in ipv6. With only loopback in /etc/network/interfaces all is fine. I now use the keyfile plugin under debian and the new PolicyKit rules to manage the system-connections. My system-connection is: [EMAIL PROTECTED]:~$ cat /etc/NetworkManager/system-connections/Casa [connection] id=Casa type=802-3-ethernet autoconnect=true timestamp=1205857717 [802-3-ethernet] port=tp speed=0 duplex=full auto-negotiate=true mtu=0 [ipv4] method=manual address1=192.168.233.2;255.255.255.0;192.168.233.1; Sorry about that :) Before 0.7 is out we'll document the format of the options somewhere. At least they are now represented as strings instead of a UINT32... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-system-settings problem
Dan Williams ([EMAIL PROTECTED]) said: Now, the question is: What does this change screw up??? Originally we did monitor /etc/sysconfig/networking/profiles/default (which is one of the 3 hardlink locations) but many people expect to change the files in /etc/sysconfig/network-scripts/ instead. Not everyone uses system-config-network evidently. Moreover, /etc/sysconfig/network-scripts is defined to be the active location for current configuration - networking/profiles/default isn't actually read by the actual scripts, so it's probably not what NM should be looking at to be in sync. Bill ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
current svn doesn't make install properly
Hi,
I'm building snapshot packages from trunk and the last successfull
package i built was 3650. newer packages are empty when i make install.
this is the last output of the build process:
libtool: link: gcc -shared
.libs/libnm_settings_plugin_keyfile_la-nm-keyfile-connection.o
.libs/libnm_settings_plugin_keyfile_la-plugin.o
.libs/libnm_settings_plugin_keyfile_la-reader.o
.libs/libnm_settings_plugin_keyfile_la-writer.o -Wl,-rpath
-Wl,/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs
-Wl,-rpath
-Wl,/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-glib/.libs
-L/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs
../../../libnm-util/.libs/libnm-util.so
../../../libnm-glib/.libs/libnm_glib.so
/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs/libnm-util.so
-lgthread-2.0 -lrt -ldbus-glib-1 -ldbus-1 -lgio-2.0 -lgobject-2.0
-lgmodule-2.0 -ldl -lglib-2.0 -march=i686 -mtune=generic
-Wl,--export-dynamic -pthread -Wl,-soname
-Wl,libnm-settings-plugin-keyfile.so -o .libs/libnm-settings-plugin-keyfile.so
libtool: link: ar cru .libs/libnm-settings-plugin-keyfile.a
libnm_settings_plugin_keyfile_la-nm-keyfile-connection.o
libnm_settings_plugin_keyfile_la-plugin.o
libnm_settings_plugin_keyfile_la-reader.o
libnm_settings_plugin_keyfile_la-writer.o
libtool: link: ranlib .libs/libnm-settings-plugin-keyfile.a
libtool: link: ( cd .libs rm -f libnm-settings-plugin-keyfile.la ln
-s ../libnm-settings-plugin-keyfile.la libnm-settings-plugin-keyfile.la )
make[4]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins/keyfile'
make[4]: Entering directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
make[3]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
make[3]: Entering directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
make[2]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
Making all in tools
make[2]: Entering directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/tools'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/tools'
Making all in policy
make[2]: Entering directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/policy'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/policy'
make[2]: Entering directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
make[1]: Leaving directory
`/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
Makefile:73: *** commands commence before first target. Stop.
and this is the build script from my arch linux PKGBUILD:
build() {
cd $startdir/src
msg Updating from SVN
svn co $_svntrunk -r $pkgver $_svnmod || return 1
msg SVN checkout done.
msg Starting make...
[ -d ./$_svnmod-build ] rm -fr ./$_svnmod-build
svn export ./$_svnmod ./$_svnmod-build
cd ./$_svnmod-build
./autogen.sh --prefix=/usr --sysconfdir=/etc \
--with-distro=arch --localstatedir=/var \
--without-gnome --libexecdir=/usr/lib/networkmanager
make || return 1
sed -i -e '/\slibnm-util\s/d' -e '/\sinclude/d' -e '/\sgnome\s/d' Makefile
make DESTDIR=${startdir}/pkg install
install -d -m755 ${startdir}/pkg/usr/bin
install -m755 test/nm-tool ${startdir}/pkg/usr/bin/nm-tool
# install -m644 ${startdir}/src/NetworkManager.conf
${startdir}/pkg/etc/dbus-1/system.d/NetworkManager.conf
# install -m755 ${startdir}/src/ntpdate
${startdir}/pkg/etc/NetworkManager/dispatcher.d/ntpdate
# install -m755 ${startdir}/src/netfs
${startdir}/pkg/etc/NetworkManager/dispatcher.d/netfs
}
the last lines have to be commented out, or else no package is created at all,
because the
directories don't exist. the only content of the package is the manually
installed nm-tool file.
can anyone confirm this?
björn
signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager and rf_kill
We do need to mark the device down when it's disabled; that somehow went away when rewriting the device state handling. Should be a pretty easy fix in nm-device-802-11-wireless.c::nm_device_802_11_wireless_set_enabled(). I was going to change that code to set the TX power of the card off instead of taking it down, because some hardware (iwl3945) needs firmware loaded to notice rfkill changes, and setting the device down unloads the firmware. So at least on some devices you need to always keep the card up. But HAL isn't smart enough yet to distinguish between soft rfkill and hard rfkill, so setting TX power off, to HAL, looks just like a hard rfkill and you can't turn the rf back on in software :( That's a fairly easy patch to HAL though. Hmpf. That's a bummer. Like so many times before, I really wish I could code. Hope this gets fixed someday soon. And again, thanks a lot for your elaborate explanations! Regards, K. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager and rf_kill
Dan Williams wrote: On Mon, 2008-05-12 at 17:46 +0200, Khashayar Naderehvandi wrote: I really might be misunderstanding something here, but deactivating wireless through nm-applet should in fact (as things are currently with NM from svn), do a ifconfig wlan0 down? Is this correct? Because doing that manually, my wifi doesn't suck battery power anymore. However, nm-applet seems to take down the wireless device _only_ when I deactivate network completely, that is, when I deactivate wireless, wired and GSM capabilities. Only deactivating wireless leaves the device up, and hence reduces uptime on battery. We do need to mark the device down when it's disabled; that somehow went away when rewriting the device state handling. Should be a pretty easy fix in nm-device-802-11-wireless.c::nm_device_802_11_wireless_set_enabled(). I was going to change that code to set the TX power of the card off instead of taking it down, because some hardware (iwl3945) needs firmware loaded to notice rfkill changes, and setting the device down unloads the firmware. So at least on some devices you need to always keep the card up. But HAL isn't smart enough yet to distinguish between soft rfkill and hard rfkill, so setting TX power off, to HAL, looks just like a hard rfkill and you can't turn the rf back on in software :( That's a fairly easy patch to HAL though. I've been following this thread with interest because I've recently implemented this feature on top of network-manager-0.6.6~rc2 ( the version in Ubuntu 8.04 ) as part of some custom Ubuntu Mobile work. I added logic to invoke the Hal KillSwitch::SetPower method from within the wireless_set_enabled() function. I also added a sw_rf_enabled flag to handle allowing the user to re-enable wireless ( otherwise as Dan pointed out, the hw_rf_enabled flag would prevent this ). One caveat...it appeared to me as if the NM code in 0.6.6 was interpreting the GetPower return values incorrectly( ie. it looked like interpreted TRUE as killswitch ON, as opposed to power ON ). I had to reverse the value returned by my KillSwitch::GetPower method, otherwise NM disabled wireless on startup. I additionally implemented a power-saving feature using some of the same logic. I modified the scanning code so that when the scan_interval gets bumped to INACTIVE ( ~2min ), I disable the interface at the beginning of the interval and then wake it up right before the next scheduled scan. Note - the one caveat is that my Hal KillSwitch method utilizes a private DeepSleep ioctl, so the card isn't totally powered off, but is close enough to show some substantial power-savings. I plan on publishing my work via my launchpad PPA ( personal package archive ), and will drop a note to the list when the code's available ( hopefully tomorrow ). Regards, Tony Espy Canonical ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Any success stories with latest SVNs on Ubuntu 8.04?
... anyone? I've been pulling SVN regularly, applied all the Ubuntu-specific patches or changes I could find, and yet I can't get this thing to let me select what wired or wireless network I want via nm-applet. All I get are grayed-out entries for Wired and Wireless Networks, nm-applet sometimes saves the networks I create, and sometimes not, and in either case nm-applet doesn't see them as connection possibilities. I used those files Tambet sent me and they're not seen by nm-applet. I've even gone so far as to change anything that says deny related to NM in /etc/dbus-1/system.d to allow, nothing. If anyone's got this running the SVN stuff running on a recent Ubuntu build, *please* let me know. I've been doing SW for a long time, but I'm stuck. /etc/network/interfaces is wiped out save auto lo. Is there anything more to pull down than gnome-common, NetworkManager and network-manager-applet? I do have a wired connection and it's running, but it didn't come out of being selected by nm-applet. Also, why is it constantly trying to start the supplicant (even on an active wired connection), and evidently failing (and I've updated wpa_supplicant to v0.5.10). Thanks guys, -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Any success stories with latest SVNs on Ubuntu 8.04?
On Mon, May 12, 2008 at 7:32 PM, Kenneth Crudup [EMAIL PROTECTED] wrote: ... anyone? I've been pulling SVN regularly, applied all the Ubuntu-specific patches or changes I could find, and yet I can't get this thing to let me select what wired or wireless network I want via nm-applet. All I get are grayed-out entries for Wired and Wireless Networks, nm-applet sometimes saves the networks I create, and sometimes not, and in either case nm-applet doesn't see them as connection possibilities. I used those files Tambet sent me and they're not seen by nm-applet. I've even gone so far as to change anything that says deny related to NM in /etc/dbus-1/system.d to allow, nothing. If anyone's got this running the SVN stuff running on a recent Ubuntu build, *please* let me know. I've been doing SW for a long time, but I'm stuck. /etc/network/interfaces is wiped out save auto lo. Is there anything more to pull down than gnome-common, NetworkManager and network-manager-applet? I do have a wired connection and it's running, but it didn't come out of being selected by nm-applet. Also, why is it constantly trying to start the supplicant (even on an active wired connection), and evidently failing (and I've updated wpa_supplicant to v0.5.10). Thanks guys, -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list You need to have WPA_Supplicant .6.0. I did the following to get it to work: 1) Installed WPA_Supplicant from Debian Testing (Not always a good idea btw ;-) ) 2) Used Michael's debian SID repo to rebuild it for Ubuntu. I think I had to empty out /etc/network/interfaces and also modify the DBUS permissions for the Network Manager DHCP service (I need to validate this and send it to Michael in case it also applies to Debian.) After that everything worked great. I just reloaded my laptop so I will make notes on how I got NM 0.7 to work and post them here from installing it here. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Error when building from svn
On Thu, May 8, 2008 at 8:11 PM, Michael Biebl [EMAIL PROTECTED] wrote: Ubuntu might sync the Debian dbus-glib 0.74-4 version from Debian: http://packages.debian.org/changelogs/pool/main/d/dbus-glib/current/changelog On Thu, 8 May 2008, Darren Albers wrote: Good catch, I was going to build a package myself but this will be easier. Thanks! Ubuntu and eebian can share the same .deb packages, right (individual distro changes/customizations notwithstanding, of course)? (... and if so, where could I get a real .deb of the above?) -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
