Re: NM fc5 prism wpa_supp setup?
Thanks for following up folks:) Dan Williams wrote: On Thu, 2006-05-11 at 16:27 +0100, Jon Escombe wrote: Hi Morgan, I can maybe help you with a couple of your points (I don't have your card, but am using NM under FC5).. _Issues_ - When I attempt to authenticate with the uoa wireless network through NM all I'm offered the wep options (as per my home wep network) This list is populated using the capabilities reported by your driver. Is the hostap driver any better in this respect? While I'd like to use the orinoco_cs because of the better reception, I'm *actually* using hostap_cs because it seems to be the only one of the two to do wpa (see orinoco cf. hostap here: http://live.gnome.org/NetworkManagerHardware - contrary to the notes on the hostap, I don't seem to need to blacklist orinoco in /etc/modprobe.d/blacklist any more for hostap, i.e. hostap seems to be the default now - but, in the recent past I've had them fight) ... - I found /etc/sysconfig/wpa_supplicant, which seems to list only configuration for hostap driver (wlan0) or ndiswrapper? -- Is this the config for wpa_supp working with NM? If so, can it be configured for use with other drivers, i.e. orinoco? NM doesn't use the static configuration file, but will start a new instance of wpa_supplicant and pass it the correct parameters - so wpa_supplicant shouldn't be running already. I believe the standard package configures wpa_supp to use wext in all cases (but might be wrong - there have been some patches around to override this). NM 0.6.2 is in the FC5 updates-testing repository, and might be worth a try. However, you'll still be stuck at the first point above without the driver telling NM that the card is capable of WPA... I assume as I'm on hostap this'll be happening anyway - my next comment confirms this? Or, not? Since I first posted I've noticed a little more strangeness: - On the UoA network (wpa) the network shows up under the nm-applet menu under Wireless Networks, but if I click on that network to connect I'm offered only the wep configuration options (like at home), but -- If I select the Connect to Other Wireless Network... option I get the whole smorgasbord of options from wep - wpa2, but -- If I select the Create New Wireless Network... I get only the options from wep - wpa (no wpa2) Is this correct behaviour - shouldn't I get all wpa options by selecting the UoA network? Or is one _supposed_ to set up wpa networks prior to finding them? FYI, it and the newer wpa_supplicant got moved to -updates yesterday. Yes, I saw that and should probably update and check things again before going much further. Thanks. Regards, M. -- Morgan Read NEW ZEALAND mailto:mstuffATreadDOTorgDOTnz get a life; GET FIREFOX! www.getfirefox.com WHY ME? Read on: http://www.theregister.co.uk/2004/06/28/cert_ditch_explorer/ http://www.theregister.co.uk/2004/09/13/german_ie_jitters/ signature.asc Description: OpenPGP digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Fri, 12 May 2006 10:29:38 -0400 Dan Williams [EMAIL PROTECTED] wrote: I think the right approach here is to make things like the applet simple, but provide (a) complex configuration in another application, and (b) a rich (and well documented!) DBUS interface. The applet then becomes the simple interface, but if you want to tinker with the details then you are certainly able to. I second that in 100%. I see no point why wouldn't NM itself provide some more options and let the applet to just show the minimum of this. We could even let people to do something like guessnet (mac detecting etc.) in an advanced mode or sth., so that even when on a static ip network NM would be able to automatically detect it without asking the user to choose a profile. Moreover, couldn't NM on a static IP network, once given the details of the gateway IP, check its MAC and then each time on this network, detect it automatically? This would reduce the profiles to the minimum. Obviously user would have to be able to change these details in some applet dialog in case these have changed, and then NM would recheck the MAC address. -- Regards, Dawid Wróbel mailto:[EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
mailman list manager has a misconfiguration.
I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- === The worst cliques are those which consist of one man. -- G.B. Shaw === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mailman list manager has a misconfiguration.
Aaron Konstam wrote: I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- I've been advised by someone on this list that this list does it correctly and the rest of the world is wrong, but frankly Aaron I detest having to bomb both your mailbox and the list by using reply to all in order for my reply to go to the list. It should default to the list, and only include your private address if I 'reply all'. This is one of the reasons I don't think I have a 'reply to:' set here. -- Cheers, Gene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
Garry T. Williams wrote: [ I call BS on my post :-) ] On Friday 12 May 2006 09:25, Garry Williams wrote: nm-applet will run in KDE just fine. I added /usr/libexec/gnome-settings-daemon /usr/bin/gnome-keyring-daemon to my start-up list. Unfortunately, this isn't going to get gnome-keyring-daemon hooked into the KDE session. The session does not have the keyring environment variables, so nm-applet cannot contact it. I didn't notice this because I did not try to use an encrypted network after setting it up. Here's how it should actually be done (from http://bugzilla.ubuntu.com/show_bug.cgi?id=17463 ): To get KDE to source the environment variables you need for clients to be able to contact the gnome-keyring-daemon, add this script to your ~/.kde/env directory: $ cat ~/.kde/env/start-custom.sh #!/bin/sh # # gnome keyring daemon # set env vars, much like ssh-agent eval `gnome-keyring-daemon` export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET set | grep GNOME $ To make sure the gnome-keyring-daemon is shut down when you exit the KDE session, add this script to your ~/.kde/shutdown directory: $ cat ~/.kde/shutdown/stop-custom.sh #!/bin/sh # # kill any gnome keyring daemons that we were using if [ -n $GNOME_KEYRING_PID ]; then echo killing gnome-keyring-damon $GNOME_KEYRING_PID kill $GNOME_KEYRING_PID fi $ Make both files executable and readable by your uid. The startkde script will source executable scripts in the env directory and will run scripts in the shutdown directory before exiting the KDE session. Do not add gnome-keyring-daemon to the KDE Autostart folder. Humm, but on FC5, there is not an env subdir in ~.kde. Are we to create this from whole cloth? I've done this, but have not restarted X yet. What are the expected results considering that ATM my networking is working fine using network to start it. -- Cheers, Gene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Saturday 13 May 2006 11:09, Gene Heskett wrote: Humm, but on FC5, there is not an env subdir in ~.kde. Are we to create this from whole cloth? mkdir ~/.kde/env ~/.kde/shutdown I've done this, but have not restarted X yet. Just log out of KDE. Then log into KDE. What are the expected results considering that ATM my networking is working fine using network to start it. The original issue was, how do I run nm-applet in KDE? This was just a clarification. The nm-applet uses the GNOME keyring to store passwords for encrypted WiFi networks. I stated before that the gnome-keyring-daemon was usable by merely starting it in your KDE session. That is not true. Clients (including nm-applet) use the environment to determine the Unix socket location so they can contact the gnome-keyring-daemon. KDE allows you to set the environment for the KDE session by placing scripts in ~/.kde/env . These will be sourced at KDE start up time. -- Garry T. Williams --- +1 678 656-4579 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Sat, 2006-05-13 at 11:09 -0400, Gene Heskett wrote: Garry T. Williams wrote: [ I call BS on my post :-) ] On Friday 12 May 2006 09:25, Garry Williams wrote: nm-applet will run in KDE just fine. I added /usr/libexec/gnome-settings-daemon /usr/bin/gnome-keyring-daemon to my start-up list. Unfortunately, this isn't going to get gnome-keyring-daemon hooked into the KDE session. The session does not have the keyring environment variables, so nm-applet cannot contact it. I didn't notice this because I did not try to use an encrypted network after setting it up. Here's how it should actually be done (from http://bugzilla.ubuntu.com/show_bug.cgi?id=17463 ): To get KDE to source the environment variables you need for clients to be able to contact the gnome-keyring-daemon, add this script to your ~/.kde/env directory: $ cat ~/.kde/env/start-custom.sh #!/bin/sh # # gnome keyring daemon # set env vars, much like ssh-agent eval `gnome-keyring-daemon` export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET set | grep GNOME $ To make sure the gnome-keyring-daemon is shut down when you exit the KDE session, add this script to your ~/.kde/shutdown directory: $ cat ~/.kde/shutdown/stop-custom.sh #!/bin/sh # # kill any gnome keyring daemons that we were using if [ -n $GNOME_KEYRING_PID ]; then echo killing gnome-keyring-damon $GNOME_KEYRING_PID kill $GNOME_KEYRING_PID fi $ Make both files executable and readable by your uid. The startkde script will source executable scripts in the env directory and will run scripts in the shutdown directory before exiting the KDE session. Do not add gnome-keyring-daemon to the KDE Autostart folder. Humm, but on FC5, there is not an env subdir in ~.kde. Are we to create this from whole cloth? I've done this, but have not restarted X yet. What are the expected results considering that ATM my networking is working fine using network to start it. Another option and a complete project plug is to use pam_keyring, which will start the gnome-keyring-daemon from pam and setup the proper environment variables. The example config for gdm should work with any pam configuration file. You can check it out at http://www.hekanetworks.com/pam_keyring This won't work with Ubuntu right now because of the pam versions. I am getting ready to roll out a new version today or tomorrow that should allow this to not be the case. Hope this helps. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
My profound thanks to you both, (and to others I will find on this thread as I catch up on my reading.) for opening this thread. While I go into my Ubuntu and run the updates that are always waiting, my hopes that whatever is totally _not_ working with nm will begin working are regularly dashed. Since I have the box connected by cable to a router with numerous other boxes on the internal network, and have netatalk working to connect with my main Mac, I assume I qualify for having some kind of network there for nm to read. Since my first question has been answered, (Yes, it is not limited to wireless. And why is this info so difficult to obtain?) I will gingerly tiptoe to my next one. Is this software meant only for laptops? (Is that why this NM icon sits in my menubar, taunting me with it's deceptively, almost Apple-like look of simplicitybecause it secretly KNOWS it won't work on a desktop box.but it is actually a FEMALE and perversely enjoys my torment and humiliation too much to tell me that!?) Is there something I'm supposed to DOor KNOW.to get this thing started? Replies to my personal email most heartily welcomed. chriss Date: Thu, 11 May 2006 02:48:38 +0200 From: Peter Roediger [EMAIL PROTECTED] Subject: Hi everyone, I thought I should write a little -personal- comment on what I think about the current implementation of NetworkManager and, more importantly, its design goals. As Einstein said: Everything should be made as simply as possible, but not simpler. This is going to be a great application, but it should be feature-complete. It's relatively easy to hide more complicated things in an Advanced... menu or something like that. But dropping features just because the 85-year old grandma will not understand what it is, is not the right way out. Cheers, Peter From: Russell Harrison [EMAIL PROTECTED] Date: May 10, 2006 11:20 PM Subject: Re: A comment on NetworkManager Very well written. I'd like to second everything you've said. NetworkManager is very frustrating to work with. I only use it because I feel like its got some real potential and somebody needs to find the bugs. I am continually in a love hate relationship with the simplicity of the interface. Right now its so simple I don't see how any layperson could understand it, there just isn't any feed back or direction, and the things you expect to see aren't there. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Saturday 13 May 2006 11:33, Jon Nettleton wrote: [snip] Another option and a complete project plug is to use pam_keyring, which will start the gnome-keyring-daemon from pam and setup the proper environment variables. The example config for gdm should work with any pam configuration file. You can check it out at http://www.hekanetworks.com/pam_keyring The URL that works for me is: http://www.hekanetworks.com/index.php/publisher/articleview/frmArticleID/25/staticId/31/ I have installed your very fine pam_keyring. It Just Works(tm) in FC5. I just wanted to correct my previous post (in the GP) without adding another option, but I do recommend pam_keyring. Thank you, Jonathan! -- Garry T. Williams --- +1 678 656-4579 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mailman list manager has a misconfiguration.
On Sat, 2006-05-13 at 10:47 -0400, Gene Heskett wrote: Aaron Konstam wrote: I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- I've been advised by someone on this list that this list does it correctly and the rest of the world is wrong, but frankly Aaron I detest having to bomb both your mailbox and the list by using reply to all in order for my reply to go to the list. It should default to the list, and only include your private address if I 'reply all'. This is one of the reasons I don't think I have a 'reply to:' set here. I of course agree with you. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mailman list manager has a misconfiguration.
Aaron Konstam wrote: On Sat, 2006-05-13 at 10:47 -0400, Gene Heskett wrote: Aaron Konstam wrote: I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- I've been advised by someone on this list that this list does it correctly and the rest of the world is wrong, but frankly Aaron I detest having to bomb both your mailbox and the list by using reply to all in order for my reply to go to the list. It should default to the list, and only include your private address if I 'reply all'. This is one of the reasons I don't think I have a 'reply to:' set here. I of course agree with you. Chuckle, but of course on this list, we are a chorus of 2. -- Cheers, Gene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
