announcement: cnetworkmanager 0.7.1
[10]Cnetworkmanager is a command-line client for [11]NetworkManager, intended to supplement and replace the GUI applets. So far it is a single python script. What is new in version 0.7.1: * it does not need a configuration file anymore: cnetworkmanager -C publicnet cnetworkmanager -C myessid --wep-hex 112234445566778899aabbccdd cnetworkmanager -C another --wpa-psk-hex \ 112233445566778899aabbccddeeff00112233445566778899aabbccddeeff00 * it works with NM 0.6 (tested on [12]Ubuntu 8.04 Hardy and a pre-release [13]OLPC) in addition to the older support for NM 0.7pre (tested on [14]openSUSE 11.0) What is still left to do: * sooner: * specifying the key as a non-hex passphrase * reading the configuration stored by the GNOME nm-applet * possibility to quit after a connection is established * later: * more encryption schemes (WPA2?) * more connection types (dial-up, VPN) Links: 10. http://vidner.net/martin/software/cnetworkmanager/ 11. http://www.gnome.org/projects/NetworkManager/ 12. http://www.ubuntu.com/ 13. http://laptop.org/ 14. http://software.opensuse.org/ http://mvidner.blogspot.com/2008/07/cnetworkmanager-071.html -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 3G; wireless auth; policies; docs
On Wed, Jul 16, 2008 at 05:53:06PM -0300, [EMAIL PROTECTED] wrote: > Thanks for the quick answer. > > The --with-docs tag worked but spec.html is generated only when I run > 'make' for > the second time. In the first time it gives me this error and stops the > compilation: > > """ > xsltproc --xinclude --nonet tools/doc-generator.xsl introspection/all.xml > > docs/spec.html > ERR: Unable to find type 'NM_DEVICE_STATE_REASON' > make: *** [docs/spec.html] Error 10 > """ I made a stub API documentation pointing at a static copy of spec.html: http://live.gnome.org/NetworkManagerDBusInterface It would be great if Dan or someone could host a more frequently updated copy. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Enable dhcpcd instead of dhclient
On Thu, 2008-07-17 at 10:14 -0400, Dan Williams wrote: > I don't have a problem with that. So lets: > > 1) if given a full path that ends in dhclient or dhcpcd, don't do > further checks just use that > 2) Document the required versions in the README > 3) If nothing is found or specified, default to dhclient since that's > what it's been up until now Sounds good to me. Thanks Roy ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Enable dhcpcd instead of dhclient
On Thu, 2008-07-17 at 14:44 +0200, Michael Biebl wrote: > Roy Marples wrote: > > On Thu, 2008-07-17 at 04:36 +0200, Michael Biebl wrote: > >> Roy Marples wrote: > >>> On Tue, 15 Jul 2008 15:29:43 +0100, Roy Marples <[EMAIL PROTECTED]> wrote: > Please apply this to NetworkManager :) > >> I don't quite like the configure bits yet. It forces you to have either > >> dhclient or dhcpd installed for a successful build. > >> > >> This effectively makes the dhcp client a build depenency. > >> This doesn't really matter for a (source-based) distro like gentoo, but > >> on other distros, where the packages are built in a separate build > >> environment this means, that you now have to install a dhcp client. > > > > The current configure environment forced me to install ppp for the > > development headers. I neither use nor care about ppp, so the same > > argument could be applied there. > > > > The reason why it's a build time check is that it's a lot easier to > > check the clients work in a shell script than in C at runtime. > > > > 1) Only dhcpcd-4 works with NM - older versions will not > > 2) Only ISC dhclient works with NM - derived versions will not > > (OpenBSD and FreeBSD have their own trimmed down versions with POSIX > > command line and don't have all the options needed) > > > > That doesn't necessarily work for binary distros though, as the > build-environment can differ from the run-time environment. > > Imo, it's better to simply document such runtime dependencies (e.g. in a > README file), so the package maintainer can enforce the correct software > versions via dependencies in the package management system. I don't have a problem with that. So lets: 1) if given a full path that ends in dhclient or dhcpcd, don't do further checks just use that 2) Document the required versions in the README 3) If nothing is found or specified, default to dhclient since that's what it's been up until now Thoughts? Dan > Cheers, > Michael > > > ___ > 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
Re: disabling polkit?
On Thu, 2008-07-17 at 12:44 +0300, Tambet Ingo wrote: > On Thu, Jul 17, 2008 at 11:58 AM, Steve <[EMAIL PROTECTED]> wrote: > > Hello! How integrated is polkit in NetworkManager? I would like to > > build NM for Slackware, which doesn't come with polkit, and I would like > > to try avoid installing it if I could. I'm just if it would be possible > > (without major changes to code) to build nm without it? At the moment > > I'm using an older version of NM from svn that doesn't require polkit. > > There's one place in NetworkManager > (system-settings/src/nm-polkit-helpers.c) and one place in > NetworkManager-gnome (src/connection-editor/nm-connection-list.c) > where you can patch it out. But that would mean any user would be able > to change system network configuration and it's probably not a good > idea. > I must admit I'm not too familiar with the pam/policy kit stuff. At the moment, I use nm svn r3645, which builds with only a bit of trouble, but successfully on Slackware 12.1. I modify the the nm dbus conf to use the group netdev for the policy group, and then any user who wants to be able to use nm/nm-applet must be in that group to change any network settings. Seems to work, and I think secure enough to keep meddling users from disabling network devices. :) I've poked about in the code some but I'm hardly familiar with it. How difficult would you guess it be to modify system-settings/src/dbus-settings.c system-settings/src/nm-sysconfig-connection.c etc. to avoid using policy kit and instead resort to dbus policy group behaviour listed above? I'm not a savvy coder. > It would probably be a better bet to convince slackware to include > policy kit as more and more programs are starting to use it. > You're not the first to suggest this; but, for good or evil, Slackware will not be moving (at least upstream) to pam/policy kit any time soon. Some people do offer a pam/policykit solution for Slackware by replacing some standard system packages, however a lot of users of Slackware, at least in my experience, would like to avoid that if they could. I admit that most major linux distros are including/implementing pam, but not all (notably slackware, and distros based off it like vector and slax). Nonetheless, NM is shaping up to be a great piece of standard software and it would be great to support non-policykit systems upstream. :) Cheers, -= Steve =- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Enable dhcpcd instead of dhclient
Roy Marples wrote: On Thu, 2008-07-17 at 04:36 +0200, Michael Biebl wrote: Roy Marples wrote: On Tue, 15 Jul 2008 15:29:43 +0100, Roy Marples <[EMAIL PROTECTED]> wrote: Please apply this to NetworkManager :) I don't quite like the configure bits yet. It forces you to have either dhclient or dhcpd installed for a successful build. This effectively makes the dhcp client a build depenency. This doesn't really matter for a (source-based) distro like gentoo, but on other distros, where the packages are built in a separate build environment this means, that you now have to install a dhcp client. The current configure environment forced me to install ppp for the development headers. I neither use nor care about ppp, so the same argument could be applied there. The reason why it's a build time check is that it's a lot easier to check the clients work in a shell script than in C at runtime. 1) Only dhcpcd-4 works with NM - older versions will not 2) Only ISC dhclient works with NM - derived versions will not (OpenBSD and FreeBSD have their own trimmed down versions with POSIX command line and don't have all the options needed) That doesn't necessarily work for binary distros though, as the build-environment can differ from the run-time environment. Imo, it's better to simply document such runtime dependencies (e.g. in a README file), so the package maintainer can enforce the correct software versions via dependencies in the package management system. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: disabling polkit?
On Thu, Jul 17, 2008 at 11:58 AM, Steve <[EMAIL PROTECTED]> wrote: > Hello! How integrated is polkit in NetworkManager? I would like to > build NM for Slackware, which doesn't come with polkit, and I would like > to try avoid installing it if I could. I'm just if it would be possible > (without major changes to code) to build nm without it? At the moment > I'm using an older version of NM from svn that doesn't require polkit. There's one place in NetworkManager (system-settings/src/nm-polkit-helpers.c) and one place in NetworkManager-gnome (src/connection-editor/nm-connection-list.c) where you can patch it out. But that would mean any user would be able to change system network configuration and it's probably not a good idea. It would probably be a better bet to convince slackware to include policy kit as more and more programs are starting to use it. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Enable dhcpcd instead of dhclient
On Thu, Jul 17, 2008 at 11:24 AM, Roy Marples <[EMAIL PROTECTED]> wrote: > The current configure environment forced me to install ppp for the > development headers. I neither use nor care about ppp, so the same > argument could be applied there. Not really. ppp is a build time dependency, NM would not build without it. dhcp clients are runtime dependencies. Tambet > The reason why it's a build time check is that it's a lot easier to > check the clients work in a shell script than in C at runtime. > > 1) Only dhcpcd-4 works with NM - older versions will not > 2) Only ISC dhclient works with NM - derived versions will not > (OpenBSD and FreeBSD have their own trimmed down versions with POSIX > command line and don't have all the options needed) > >> I'd say, if an absolute path is given (i.e. >> --with-dhcp-client=/sbin/dhclient), simply take this path and do no >> further checks. Imo it's safe to assume, if someone is using the >> configure flag this way, he knows what he's doing. > > That's probably a safe assumption to make. > > Thanks > > Roy > > ___ > 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
disabling polkit?
Hello! How integrated is polkit in NetworkManager? I would like to build NM for Slackware, which doesn't come with polkit, and I would like to try avoid installing it if I could. I'm just if it would be possible (without major changes to code) to build nm without it? At the moment I'm using an older version of NM from svn that doesn't require polkit. Cheers, -= Steve =- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] Enable dhcpcd instead of dhclient
On Thu, 2008-07-17 at 04:36 +0200, Michael Biebl wrote: > Roy Marples wrote: > > On Tue, 15 Jul 2008 15:29:43 +0100, Roy Marples <[EMAIL PROTECTED]> wrote: > >> Please apply this to NetworkManager :) > > > > I don't quite like the configure bits yet. It forces you to have either > dhclient or dhcpd installed for a successful build. > > This effectively makes the dhcp client a build depenency. > This doesn't really matter for a (source-based) distro like gentoo, but > on other distros, where the packages are built in a separate build > environment this means, that you now have to install a dhcp client. The current configure environment forced me to install ppp for the development headers. I neither use nor care about ppp, so the same argument could be applied there. The reason why it's a build time check is that it's a lot easier to check the clients work in a shell script than in C at runtime. 1) Only dhcpcd-4 works with NM - older versions will not 2) Only ISC dhclient works with NM - derived versions will not (OpenBSD and FreeBSD have their own trimmed down versions with POSIX command line and don't have all the options needed) > I'd say, if an absolute path is given (i.e. > --with-dhcp-client=/sbin/dhclient), simply take this path and do no > further checks. Imo it's safe to assume, if someone is using the > configure flag this way, he knows what he's doing. That's probably a safe assumption to make. Thanks Roy ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
