On Wed, June 22, 2005 3:04 pm, Ray Hooker said:
> Hmm I did a chkconfig --add dhcdbd
> It clearly tries to get the address but even when I reboot with the
> ethernet plugged in, it does not setup routing or dhcp properly. Any
> other hints?
I seem to recal there being some conflict with selinux.
On Wed, 2005-06-22 at 23:49 -0400, David Zeuthen wrote:
> So, I guess my point is that we shouldn't care too much about annoying
> gnome-keyring dialogs at this point. Not that it doesn't matter, cause
> it does, however all that work is elsewhere really.
Nod.
We can do a lot better, though. Ri
On Wed, 2005-06-22 at 22:20 -0400, Colin Walters wrote:
> On Wed, 2005-06-22 at 22:02 -0400, Robert Love wrote:
> > Attached patch adds support for gnome-keyring to nm-applet and stores
> > the essid key encrypted in the keyring instead of cleartext in gconf.
> >
> > It is a first pass, but it see
On Wed, 2005-06-22 at 22:15 -0400, Dan Williams wrote:
> On Wed, 22 Jun 2005, Robert Love wrote:
> > May I apply?
>
> Looks good, go ahead.
Committed. Thanks.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
htt
On Tue, 2005-06-21 at 15:44 -0400, Robert Love wrote:
> On Tue, 2005-06-21 at 15:42 -0400, Robert Love wrote:
>
> > The attached email implements a "Connection Information" dialog,
> > accessible from the right-click menu, with connection-related
> > information such as IP address, subnet mask, ac
On Wed, 2005-06-22 at 22:20 -0400, Colin Walters wrote:
> Offtopic, but IMO we should just get rid of that dialog (and the whole
> keyring access control). It is a pretty small barrier versus a
> compromised application, confusing to users, and it's also annoying.
I'm not talking about the "Shou
On Wed, 2005-06-22 at 22:02 -0400, Robert Love wrote:
> Attached patch adds support for gnome-keyring to nm-applet and stores
> the essid key encrypted in the keyring instead of cleartext in gconf.
>
> It is a first pass, but it seems to work well [1].
>
> One issue is it causes the gnome-keyring
On Wed, 22 Jun 2005, Robert Love wrote:
> Attached patch adds support for gnome-keyring to nm-applet and stores
> the essid key encrypted in the keyring instead of cleartext in gconf.
>
> It is a first pass, but it seems to work well [1].
>
> One issue is it causes the gnome-keyring "decrypt you
On Wed, 22 Jun 2005, Robert Love wrote:
> May I apply?
Looks good, go ahead.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Attached patch adds support for gnome-keyring to nm-applet and stores
the essid key encrypted in the keyring instead of cleartext in gconf.
It is a first pass, but it seems to work well [1].
One issue is it causes the gnome-keyring "decrypt your keyring" dialog
to pop up as soon as the applet loa
Hmm I did a chkconfig --add dhcdbd
It clearly tries to get the address but even when I reboot with the
ethernet plugged in, it does not setup routing or dhcp properly. Any
other hints?
Ray
On 6/22/05, Paul Dugas <[EMAIL PROTECTED]> wrote:
> I fired up the rawhide updates last night. The dhcdbd
Hi,
FIXME in dispatcher-daemon/NetworkManagerDispatcher.c reads:
``We should check the permissions and only execute files that
are 0700 or 0500.''
Indeed we should.
Attached patch fixes the FIXME.
( Actually, I just check for
! (s->st_mode & (
I fired up the rawhide updates last night. The dhcdbd rpm is not doing
the 'chkconfig -add'. Did that myself and started it up and it's working
for me now.
On Wed, June 22, 2005 10:54 am, Paul Ionescu said:
> On Wed, 22 Jun 2005 09:39:04 -0400, Ray Hooker wrote:
>
>> Well I am both encouraged an
On Wed, 22 Jun 2005 09:39:04 -0400, Ray Hooker wrote:
> Well I am both encouraged and stuck. NetworkManager was working but
> without the VPNC, so I upgraded to the versions as per:
> http://people.redhat.com/davidz/nm-vpnc2/
>
> When upgrading, it complained that I needed dhcdbd, so I got and
Well I am both encouraged and stuck. NetworkManager was working but
without the VPNC, so I upgraded to the versions as per:
http://people.redhat.com/davidz/nm-vpnc2/
When upgrading, it complained that I needed dhcdbd, so I got and
installed dhcdbd-1.6-1.rpm.
When I rebooted, logged in under gno
When I'm at work, I have to forward queries to a local DNS to resolve internal
names, but at home I want a normal DNS setup. How can I achieve this? I had
used profiles on Fedora without Networkmanager, but with NetworkManager I
don't know how to force DNS to forward in my work environment.
__
Hi,
I am using NM now quite some time and I really like it very much - still
I have a problem that I am currently unable to solve how to do it with
NM.
The situation is that I can use NM for my wireless stuff perfectly well,
as all places I've been are using dhcp for their wireless stuff. But for
17 matches
Mail list logo