Re: New features in the 0.6 branch

2008-02-04 Thread Gabriele Monti
Hi,
Thanks a lot, I really needed wired authentication! I compiled and 
packaged the 0.6 branch for Ubuntu and it works really fine!
Now I don't need a script and a manually edited configuration file anymore!
I found no critical bug so far, but I'd like to submit a feature request:
When I connected to the authenticated network for the first time I gave 
it a name (let's say network a). I noticed that the keyring manager 
(and seahorse as well) added the to its stored ones.
Now, whenever I plug the cable to that network I see a new network a 
in the network list but when I click on it I'm asked for user and 
password again. Is there a way to let it store somewhere (just as it 
happens with wireless networks)?

Thanks!

On Jan 31, 2008 12:04 PM, Tambet Ingo tambet gmail com wrote:
  Hey,
 
  All of you waiting for 0.7 and new features, here's something new for
  the change in 0.6 branch to play with. I implemented wired 802.1x
  authentication and would appreciate bug reports of any issues people
  find with it. Also, there's a new wireless network editor so that you
  can change and remove wireless networks without using the gconf
  directly.
 
  Tambet
  ___
  NetworkManager-list mailing list
  NetworkManager-list gnome org
  http://mail.gnome.org/mailman/listinfo/networkmanager-list


-- 

Gabriele Monti
e-mail: [EMAIL PROTECTED]
GPG Key: 0x238F7E1E

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Stopping NetworkManager without taking the interface down.

2008-02-04 Thread Alexander Sack
On Sun, Feb 03, 2008 at 09:24:44PM -0500, Dan Williams wrote:
 
 Yes, but probably not before 0.8 I think.  I believe it would require
 quite a bit of coding and architecting to ensure that it's not an
 un-manageable hack.

OK, I understand that (though I hoped that we could have this once we
support for multiple interfaces).

So do you advice distributors to not restart NetworkManager on upgrade
and defer this until reboot? Is that the way fedora is (not-)dealing
with this issue too?

 - Alexander

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Stopping NetworkManager without taking the interface down.

2008-02-04 Thread Michael Biebl
Dan Williams wrote:
 On Sat, 2008-02-02 at 15:15 +0100, Michael Biebl wrote:
 Hi everyone,

 as NetworkManager (especially the 0.7 version) tries to be more than
 just a network configuration for the laptop, but also desktops and
 servers, there is one issue, that's currently suboptimal imho.
 That is, that NM always deconfigures the network interface when it is
 stopped. This is especially unfortunate, when you remotely administer
 machines and you have to restart NetworkManager (e.g. after installing a
 security update of NM. Rebooting is not ideal for servers...).
 
 Right, but the NM startup is the part that's going to kill you here...
 

Understood. Would it still be possible to add the feature though, to not
deconfigure the device on shutdown, even if we can't handle the startup yet?

This would still be useful, as it cuts down the possible downtime to a
minimum.

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: New features in the 0.6 branch

2008-02-04 Thread Tambet Ingo
On Feb 4, 2008 4:24 AM, Gabriele Monti [EMAIL PROTECTED] wrote:
 Thanks a lot, I really needed wired authentication! I compiled and
 packaged the 0.6 branch for Ubuntu and it works really fine!

Thanks for trying it out, I'm glad it works!

 Now I don't need a script and a manually edited configuration file anymore!
 I found no critical bug so far, but I'd like to submit a feature request:
 When I connected to the authenticated network for the first time I gave
 it a name (let's say network a). I noticed that the keyring manager
 (and seahorse as well) added the to its stored ones.
 Now, whenever I plug the cable to that network I see a new network a
 in the network list but when I click on it I'm asked for user and
 password again. Is there a way to let it store somewhere (just as it
 happens with wireless networks)?

It is supposed to work like wireless and get the secrets from keyring
automatically, sounds like there's a bug somewhere. I'll look into it.

Tambet
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list