Re: NetworkManager-0.6.4 and dhcp-3.0.4
- From: Thorsten Kolb <thorsten_kolb urz uni-hd de>
- To: Dan Williams <dcbw redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: NetworkManager-0.6.4 and dhcp-3.0.4
- Date: Mon, 15 Jan 2007 18:58:58 +0100
Thank you,
I got It running as user. The strange thing is that If I run it as user I can
not direktly click on the wlan-list, I have to type my wlan-date manually in.
Is Root this does not happen.
Any Idea hov I can solve this?
Thorsten
>On Monday, 15. January 2007 15:24, Dan Williams wrote:
> On Mon, 2007-01-15 at 15:00 +0100, Thorsten Kolb wrote:
> > Hi there,
> >
> > I am trying now for several weeks to get networkmanager/knetworkmanager
> > running.
> > This day I had sucess, with NetworkManager-0.6.4 and knetworkmanager-0.1.
> > The Problam I had all the time was that the poore unpatched dhcp-3.0.4
> > which comes with my distro (slackware-11.0) does not work with
> > NetworkManager nor the poore dhcp-3.0.4 which I compiled for myself did
> > the trick. So I took some patches from a gentooo-overlay and patched dhcp
> > for my self, now it works.
> >
> > Maybe you can say me which ones are nessesary?!
> > This are all I used:
> >
> > dhcp-3.0-fix-perms.patch
> > dhcp-3.0-paranoia.patch
> >
> >
> > dhcp-3.0.2-dhclient-script-dbus-dhcdbd.patch
> > dhcp-3.0.2-extended_option_environment.patch
>
> ^^^ I think these two are likely the only ones necessary for the dbus
> support.
>
> Dan
>
> > dhcp-3.0.3-no_isc_blurb.patch
> > dhcp-3.0.3-libdst.patch
> > dhcp-3.0.3-dhclient-ntp.patch
> > dhcp-3.0.2-gmake.patch
> >
> >
> > So for the future it would be good that you write the need for a patched
> > dhcp somewhere on your Homepage :-)
> >
> > Just one Question.
> > How can I use knetworkmanager as a non-root user? What must I change
> > in /etc/dbus.1/system.d/knetworkmanager?
>
> You should be. Slackware has lagged somewhat with D-Bus though. The
> way other distributions, for example Fedora, deal with the non-root user
> issue is through a special PAM module called pam_console. Essentially,
> if the user is sitting in front of the machine, they are allowed to
> configure the network. Then, your /etc/dbus-1/system.d/knetworkmanager
> would have the following bits somewhere:
>
> <policy at_console="true">
> <allow own="org.freedesktop.NetworkManagerInfo"/>
>
> <allow
> send_destination="org.freedesktop.NetworkManagerInfo"/> <allow
> send_interface="org.freedesktop.NetworkManagerInfo"/> </policy>
>
> This _only_ works if you have pam_console set up. Debian-based
> distributions do this through groups. There, you need to be in the
> 'netdev' group and replace the above at_console="true" with
> group="netdev".
>
> I really don't know how slackware does the D-Bus authorization bits, but
> it really should be doing them with either groups (like Debian) or
> pam_console (like Fedora and SUSE). You'll have to figure out which
> one, since it appears that nobody has already figured that out for
> slackware.
>
> Cheers,
> Dan
--
************************************************************************
Thorsten Kolb
Fritz-Frey-Strasse 10
69121 Heidelberg
Germany
Phone: 015114164444
E-mail: thorsten_kolb urz uni-hd de
************************************************************************
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]