RE: NetworkManager keeps asking for secret phrase
On Sat, 2007-11-10 at 14:48 +0200, Firas Swidan, PhD wrote: >> Hi, >> >> I am trying to connect to my WAP wireless network and NetworkManager >> keeps asking for the secret phrase without connecting. Is there anything >> specific that I need to do to stop this and make the connection? >> >> Thanks in advance, >> Firas. >There is some confusion here. I suspect you mean WEP. If it is asking you >for a >secret phrase it means is is not open to anyone who connects. You need >to know the (usually 40 bit or 104 bit) string that was set up on the >AP. Note that 104 bits is 13 ASCII characters. Isn't it the case that the key for WEP or WPA is stored in the PAM keyring if you have PAM installed? I run Ubuntu (Gnome) so PAM is already installed, but if you run another distro/desktop and PAM isn't installed or configured then maybe it's not storing the WEP key? Once stored in PAM, then you only get asked for the PAM passphrase, but in the version of PAM supplied in Ubuntu 7.10 there is a checkbox in the passphrase dialog to always remember the PAM passphrase. --andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: FW: integration with /etc/network/interfaces
On Thu, 2007-11-08 at 18:04 +0100, Alexander Sack wrote: > On Thu, Nov 08, 2007 at 10:13:35AM +0100, Henry Andrew wrote: > > It does not seem that there is any integration with > > /etc/network/interfaces at all, and that there is no equivalent way of > > scripting in custom pre-up/post-down commands etc. like you can with > > standard networking. > > > > Seems like NetworkManager sits on top of standard Linux networking and > > is not a functionally equivalent tool. Are they mutually > > incompatible? > > The concepts of NetworkManager and ifupdown don't go together well, > which is why we decided to make these mutually exclusive in gutsy. Correct; with 0.6.x they are definitely mutually exclusive. Dan > We (ubuntu) will revisit this decision once network-manager 0.7 gets > to a state where you can bring up multiple devices at the same time. > > Thanks, > > - Alexander Thanks for your replies. I can appreciate the difficulty in integrating the two, but if I could send in a feature request for this, then I would do! It would be much nicer to be able to restart "/etc/init.d/Network-manager" and have it cascade so that it also restarted /etc/init.d/networking. Would also be nice to be able to script with network-manager, but if this is not at all possible, then at least to be able to script with standard pre|post-up|down, but I suppose that nm would have to be compatible with manually defined interfaces in that case. --andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
FW: integration with /etc/network/interfaces
> -Original Message- > From: Paulus Esterhazy [mailto:[EMAIL PROTECTED] > Sent: 07 November 2007 18:29 > Cc: Henry Andrew > Subject: Re: integration with /etc/network/interfaces > > > If there is an equivalent tool supplied with network-manager, does it do > > exactly the same thing that /etc/init.d/networking restart does, > > including restarting the nm-applet stuff? > > To restart NetworkManager on Ubuntu, run: > > /etc/dbus-1/event.d/25NetworkManager restart > /etc/dbus-1/event.d/26NetworkManagerDispatcher restart > > These scripts are not located in /etc/init.d, I suppose, because they > are executed only in the event that a network card is detected, or > plugged in (like a USB WLAN stick). > > To restart nm-applet, you can use (in bash): > > killall nm-applet > nm-applet --sm-disable & > > HTH, > Paulus Thankyou for the info Paulus, but now I need some more help... I looked at the help for /usr/sbin/NetworkManager and there are very few options to specify when restarting the daemon, and the script in /etc/dbus-1/event.d/ doesn't do much other than call /usr/sbin/NetworkManager. It does not seem that there is any integration with /etc/network/interfaces at all, and that there is no equivalent way of scripting in custom pre-up/post-down commands etc. like you can with standard networking. Seems like NetworkManager sits on top of standard Linux networking and is not a functionally equivalent tool. Are they mutually incompatible? I suppose it will probably work to script killall nm-applet and restart NetworkManager in a post-up/pre-down script, but will this allow me to still hard code a specific interface in /etc/network/interfaces without NetworkManager complaining about it when it starts up? Eg. To hard code the Ethernet interface, but still use nm-applet for wireless without it complaining that my eth0 is hard coded? I must admit that I do not really know what happens when I do /etc/init.d/networking restart, but my assumption is that this restarts the entire network stack (unloads all net modules and then loads them again), whereas restarting Network-Manager simply restarts that one daemon. I assume that I cannot stop networking entirely with "/etc/init.d/networking stop" and still expect nm-applet to work? --andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
integration with /etc/network/interfaces
I depend heavily on network-manager for my laptops as it just works, but I am concerned that it does not seem to integrate well, if at all, with /etc/network/interfaces, but that there are still many apps that rely on /etc/network/interfaces. If I need to restart the entire networking stack, I have to do "/etc/init.d/networking restart". When something borks, it is extremely easy to restart the network stack instead of rebooting. However I do not know if this can be done with an equivalent command toll with network-manager? If there is an equivalent tool supplied with network-manager, does it do exactly the same thing that "/etc/init.d/networking restart" does, including restarting the nm-applet stuff? On my server I have configured the interfaces file manually and do not use nm-applet, so that I can easily restart the stack if something fails. My server is an old laptop with an 802.11g Broadcom but as I do not know how to easily restart nm-applet from the console, I configure everything via iwconfig in /etc/network/interfaces. When say that something may bork, I mean that sometimes, I need to reload the bcm43xx module and it is so easy to script this into the interfaces file with pre-up etc. Another thing that I wonder about is why there has to be specific driver support within nm-applet? I heard on an ubuntu forum when they were getting ready to release 70.4 that network-manager 0.64 was required because that version had support for ipw3945. The ipw3945 driver was included already in the kernel that was used for 7.04, but they still had nm-applet 0.63 in the repositories during the alpha phase. Why does nm-applet need specific support for drivers or have I misunderstood this? As long as the driver exists in the kernel, shouldn't that be enough? Regards, andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
