NM 0.7.0 on SLED11
I am not able to connect to my companies WPA2 enterprise wireless. A windows-savvy network friend of mine says he thinks the problem is: the company is not using client-side certificates AFAIK. The problem is probably that the certificate is invalid (expired) because our PKI at the company is not properly configured. You will need to get SLED to trust the invalid certificate presented during connection time. I know where this option is in Windows but not in the EAP supplicant. I can see in NM the option to use system CA certificates -- I wonder if I need to add the company CA cert to the system cert store? Is this done using NM, in some fashion? Peter The aftermath of battle, is art http://www.the-brights.net http://xkcd.com/167 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multi-active devices
On Mon, Mar 10, 2008 at 10:08 AM, Dan Williams [EMAIL PROTECTED] wrote: snip active device support to NM SVN trunk this weekend; each device is now independent and can be active/inactive irrespective of any other device. ya! :-) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: has anyone had a chance to look at my nm-applet patch?
On 10/28/07, Darren Albers [EMAIL PROTECTED] wrote: I am not a dev but my first thought was Great idea but then I realized that it is probably way too much info for the user. In /most/ cases the user will see a large number of AP's and will pick the one with the best signal and this is what NM does now automatically. I think it only confuses the issue for the user to see all the different channels. I quickly am tiring of this attitude, as it finds expression in the gnome desktop. Far too much is assumed, far too little is tested (ie usability and user reaction) and the default impulse seems always to be limit choice. In /MOST/ situations, I want and need to see what wireless networks are around and available. /occasionally/ there might be /too many/ for the interface. So, it would be good to: 1)offer the choice/ability to see all and 2)offer the ability to scroll the presentation to show more than a page-view snip Maybe it would be better to make this an option that can be enabled by changing a gconf value for advanced users who want to see this information but otherwise leave it disabled? Out of curiosity how do other OS's deal with this? no maybe about it. But -- the choice should be in the NM interface itself. Choice must be a/the priority. Always. I love the idea of the patch and I always like seeing more information so if I had an option I would personally enable this feature but I don't think it should be the default. To gnome devs, from a fan: Please do not assume the average or default user is dumb, or somehow less capable than you. Please do assume that there are a range of abilities, and try to design an interface that meets the needs of the broadest range possible. Peter -- Those who can make you believe absurdities can make you commit atrocities -- Voltaire www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Newbie question: advice in adding a new feature to network manager...
I don't know how you should get started ... but here is my vote for that as a a worthy feature. P On 8/16/07, Doug Anson [EMAIL PROTECTED] wrote: Hi: I'm new to NetworkManager and have an interest in coding up a new feature into it. I think it would be great to have the ability to partition out adhoc networks from infrastructure networks in the available wireless network list. That way, if it happens to be the case that there is a lurking adhoc network called say foo and an infrastructure network called foo, the user can differentiate between the two and choose which one they want to associate with. Additionally, with that kind of segmentation, it would be nice to ONLY see adhoc networks or infrastructure networks in the list (as a configurable option). For a managed network environment, users may only be interested in seeing one kind of network at a given time. So, any advice on how I can quickly ramp up into the design aspects of NetworkManager? Any advice on where I would likely begin to experiment with changes? Thanks! Doug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Everything is vague to a degree you do not realize till you have tried to make it precise. Bertrand Russell www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/8/07, Thomas M Steenholdt [EMAIL PROTECTED] wrote: The right way to fix the problem as I see it, would probably be to get the mac80211 pre-auth scanning working properly. whatever the right way is, this really needs to be fixed. NM is entirely needed for users who depend on gui utilities to attach to networks. (ie me, and my peers, and the 150 or so knowledge workers whom I am trying to convince to use a linux desktop) Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/8/07, Thomas M Steenholdt [EMAIL PROTECTED] wrote: wpa_supplicant only - ap_scan=1: The hidden network is found during the scanning, but is never identified as my network, since wpa_supplicant expects a certain SSID and the hidden net shows an SSID of (SSID mismatch). The device SSID is never set. (as soon as I set the device SSID with iwconfig in this mode, wpa_supplicant makes the association happen) perhaps I am just being dull ... but is not the above exactly what should happen? From the perspective of NM, if an SSID is hidden, a user would need to supply it by choosing connect to other wireless network. Once the user types in the SSID, NM *should* pass that to wpa_supplicant, and then association should occur. Or, am I missing something? In my case ... since connect to other wireless network does not work, it appears that one of two things must be going wrong: 1)NM is not properly handing the SSID to wpa_supplicant (is failing to do what iwconfig does when you use it to set SSID), or 2)wpa_supplicant is not running in ap_scan=1 mode So ... either the hand-off is broken or the mode is wrong. (and the mode appears to be unsettable from the NM gui, which is another issue to my mind --- linux is about choice, right?) :-) Anyway ... we don't need wpa_supplicant to find the hidden SSID, do we? We just need it to succeed connecting, when we TELL it the SSID. Peter ps -- sorry if I am being obtuse, perhaps my sig line below applies? :-) -- Everything is vague to a degree you do not realize till you have tried to make it precise. Bertrand Russell www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/8/07, Thomas M Steenholdt [EMAIL PROTECTED] wrote: As to why we don't just use the AP_SCAN 1 workaround - AP_SCAN 2 works for other drivers, it should work for the iwl4965 people too. This is a problem of fixing things in the place that need fixing, not working around thing everywhere else. That said - the workaround is a temporary solution if you need it *now*. ok, so the fix then is to correct the faulty behaviour of AP_SCAN mode 2 .. since I am not going to be helpful in that regard, I have a few more questions: my wireless driver is: IPW3945 Intel PRO/Wireless 3945ABG Network connection 1)is that one of the devices that is supposed to be effected (I am not familiar with iwl4965)? 2)Has setting the SSID using NM with the AP_SCAN mode at 1 (instead of using iwconfig to set the SSID) been tested and it works? 3)if simply changing the AP_SCAN mode to 1 will work, then how would one do this, and still use NetworkManager ... is it as simple as creating a wpa_supplicant.conf file and specifying that value? Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/8/07, Thomas M Steenholdt [EMAIL PROTECTED] wrote: That's strange. I've been running with that device for ages with no problem at all. What's your distro/version etc.? SLED10 -- no sp1 yet By me and yes - but it's a hack in the current state of affairs. 3)if simply changing the AP_SCAN mode to 1 will work, then how would one do this, and still use NetworkManager ... is it as simple as creating a wpa_supplicant.conf file and specifying that value? Nope - You'd have to apply my patch and rebuild the application as things are now. bummer - I guess I'll wait p ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/6/07, Thomas M Steenholdt [EMAIL PROTECTED] wrote: I'll force it to use 1 or 2 this evening, and see what kind of success that will give me. I'll keep you guys posted. Thank you Thomas. If changing this value works, then the next challenge for me will be figuring out how to do it, while still using NetworkManager -- as I need to quite often connect to a wide variety of wireless networks ... and I just do not know how to do that easily, without it. If there is a simple way to continue using networkmanager AND resolve this business of not being able to connect when the SSID is hidden, that would be terrific. Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/5/07, Darren Albers [EMAIL PROTECTED] wrote: I have seen others post the same issues and they generally have various levels of success by using wpa_supplicant with ap_scan=2 or 1. I forgot which one NM uses but you may have need to use the other to connect to a hidden AP however changing that in NM and rebuilding the package is probably too much of a hassle for the very little (if any) benefit that not broadcasting your SSID gives you. I'm having the same issue, but since I don't controll the AP configuration, and since Windows users don't seem to be having any problems well you know the rest of that line! So, I'd like to try change the ap_scan parameter, but I cannot find my wpa _supplicant.conf file. It is not in /etc or in /etc/NetworkManager. Where can I find it, what can I do? Peter -- Everything is vague to a degree you do not realize till you have tried to make it precise. Bertrand Russell www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM does not work with iwl4965 device
On 8/5/07, Peter Van Lone [EMAIL PROTECTED] wrote: ps -- forgot to include that I'm using SLED10 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
