Re: Setting MACADDR with nmcli
Thank you! On 08/07/2018 09:07 AM, Thomas Haller wrote: On Tue, 2018-08-07 at 08:43 -0400, Robert Moskowitz wrote: I hope this is the right list for nmcli. I want to set MACADDR in ifcfg-eth0 I thought it was: nmcli con mod eth0 mac "02:67:15:00:81:0B" but this sets HWADDR, which has a totally different use. I could then change HWADDR to MACADDR with: sed -i -e "s/HWADDR/MACADDR/w /dev/stdout" /etc/sysconfig/network-scripts/ifcfg-eth0 But that is a hack. It would be nice to be able to directly set MACADDR, but I cannot find any documentation that states how to do this. thanks Hi, $ nmcli connection modify "$PROFILE" ethernet.cloned-mac-address "$MAC" I wonder what the history of naming this object 'cloned' mac address? Perhaps because we were cloning the address of the broken card for the new card so the licensed software would work? :) I did that a lot in my early days with 3com cards and VAX ethernet adapters. Now we use it for ARM boards (and others) that come without a MAC address and the uboot or OS has to invent some local scope address. Theoretically, this is documented in `man nm-settings`. However, the manual is generated and for cloned-mac-address the generated documentation is confusing. It's confusing, because `man nm- settings` is undecided whether it documents libnm GObject properties or D-bus API. Especially, since you care about nmcli syntax. In most cases, there is little difference between libnm API, D-Bus API and nmcli, so "nm-settings" manual does apply. For "cloned-mac-address" it's different. And as you seem concerned about ifcfg files, see also `man nm-settings-ifcfg-rh`. But usually, you would not concern yourself with the details of ifcfg files. You do for ARM based servers. No GUI typically. Fixed IP addressing and the like and a predictable MAC addr. Sometimes the uboot is consistent for a given board on how it computes the MAC address. Of course a new version of uboot may compute it differently. So perhaps there is a more modern method than using ifcfg files for servers. I have not encountered it. I have at least switched from hand coding my ifcfg to using nmcli in scripts. If you look at `man nmcli` it has a table: PROPERTY ALIASES Table 3. Wired Ethernet options ┌───┬──┐ │Alias │ Property │ ├───┼──┤ │mtu│ wired.mtu│ ├───┼──┤ │mac│ wired.mac-address│ ├───┼──┤ │cloned-mac │ wired.cloned-mac-address │ └───┴──┘ And you have to realize that mac maps to HWADDR to link the ifcfg to a specific card. While cloned-mac maps to MACADDR to set the MAC address actually used for an interface. I had to read a lot to tease that distinction out. best, Thomas Again, thanks Robert ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Setting MACADDR with nmcli
I hope this is the right list for nmcli. I want to set MACADDR in ifcfg-eth0 I thought it was: nmcli con mod eth0 mac "02:67:15:00:81:0B" but this sets HWADDR, which has a totally different use. I could then change HWADDR to MACADDR with: sed -i -e "s/HWADDR/MACADDR/w /dev/stdout" /etc/sysconfig/network-scripts/ifcfg-eth0 But that is a hack. It would be nice to be able to directly set MACADDR, but I cannot find any documentation that states how to do this. thanks ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Software to test MAC address privacy
On 08/03/2014 04:58 AM, Glen Turner wrote: On 19/07/2014 Robert Moskowitz wrote: Actually the standard uses the first 2 bits for this. It is called local scope MAC addresses. This leaves 46 bits for the random content. Thus if you have a network of 1 devices the probablity of a collision is 7x10^-7 Hello Robert, Not all locally-assigned addresses are available for use as random MAC addresses. Last I looked that are historical uses of LAS for DECnet and other protocols from 00:… through to 05:…. It would be useful if the IEEE recommended a range of LAS for host use (ie, virtual machine MAC addresses) and specified a range for your random MAC address proposal. Such a range should leave sufficient LAS for other potential future applications. This is actually in progress. We are forming a study group in IEEE 802 (first session will be at the November San Antonio meeting) to fully document this and come out with a recommended practice. One of the other drivers is the cloud computing world. There is talk about partitioning the use of the LAS. I am against that as it increases the collision probablity. Perhaps by usage domain. In any case we will have to work out probe/discovery methods to discover collisions for readdressing. thanks for your input. I will see it gets included in the discussion. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Software to test MAC address privacy
On 07/18/2014 11:02 AM, Stuart Gathman wrote: On 07/17/2014 09:05 PM, Robert Moskowitz wrote: draft-ietf-6man-ipv6-address-generation-privacy-01.txt privacy for both global and local scope IPv6 addresses. So how do I get interest in this effort and get some revised test app for me (and other Linux users) to participate? To guarantee compatibility, the first few bits should mark the MAC as a private one, and not conflict with any vendor id or pseudo vendor (like statically generated MACs for virtual machine virtual network interfaces). Actually the standard uses the first 2 bits for this. It is called local scope MAC addresses. This leaves 46 bits for the random content. Thus if you have a network of 1 devices the probablity of a collision is 7x10^-7 And some SOC ARM cards do not have an eeprom so the software install has to create a MAC address. My Cubieboard is one such. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Software to test MAC address privacy
Greetings from IEEE 802 plenay in San Diego. We are winding down, but Monday night we had a talk on Pervasive Surveillance: https://mentor.ieee.org/802-ec/dcn/14/ec-14-0043-00-00EC-internet-privacy-tutorial.pdf I discussed this with the 802 chair and presentation moderator, and we are looking to see if we can actually test the consequences of using random local MAC addresses. The idea is to have an opt-in SSID at future 802 meetings, and perhaps at the IETF as well (same network support company) where only random local MAC addresses are allowed and then to see what problems occur (DHCP, ARP tables, bridging tables, etc.). So we (those of us that want to figure this out to see if it is worth doing) are looking to the OS providers to help. I have been tasked with reaching to the Linux community as I run Fedora. The thought is the MAC address is temporarily overwritten with a local MAC random address. This address should be changed with some periodicity. We have not worked out this part yet. Also per Internet Draft: draft-ietf-6man-ipv6-address-generation-privacy-01.txt privacy for both global and local scope IPv6 addresses. So how do I get interest in this effort and get some revised test app for me (and other Linux users) to participate? thank you ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
WPA-PSK password length requirement
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3. First I was a major contributor to 802.11i and wrote the first paper on the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your typical end user having a complaint on client behaviour. Yesterday, I was at a major corporation for a meeting and the quest SSID had a 6 digit all numeric passcode. NM would not let me connect; it seem to insist that a passcode for WPA2-PSK be at least 8 characters long. The meeting participants using Windows had no difficulty with this 6 digit passcode and were able to get on the guest wireless network. On any SSID I set up, I will use a reasonably strong passcode (though I would REALLY like to start using SAE in place of PSK!), but sometimes you have NO control over what others do. I REALLY need an override on the passcode length requirement; I will again be at that location for a meeting Dec 19. I doubt I will find a way to complain to this company's senior management on their IT department's 'bad' policy. This setup is probably only intended to keep rifraf from trying to get to the NEXT level of access control (you then need an 8 hour user account for hotspot login). Oh, I did not mention that they hide this SSID. Sheesh. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA-PSK password length requirement
On 12/11/2012 10:02 AM, Dan Williams wrote: On Tue, 2012-12-11 at 06:24 -0500, Robert Moskowitz wrote: The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3. First I was a major contributor to 802.11i and wrote the first paper on the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your typical end user having a complaint on client behaviour. Yesterday, I was at a major corporation for a meeting and the quest SSID had a 6 digit all numeric passcode. NM would not let me connect; it seem to insist that a passcode for WPA2-PSK be at least 8 characters long. The meeting participants using Windows had no difficulty with this 6 digit passcode and were able to get on the guest wireless network. If it's a 6 digit passcode, then it's not a valid WPA passphrase. Um, I helped write that section of 802.11i. Of course now it is just part of 802.11-2012: M.4 Suggested pass-phrase-to-PSK mapping The pass-phrase mapping defined in this subclause uses the PBKDF2 method from PKCS #5 v2.0 [B53]. PSK = PBKDF2(PassPhrase, ssid, ssidLength, 4096, 256) Here, the following assumptions apply: — A pass-phrase is a sequence of between 8 and 63 ASCII-encoded characters. The limit of 63 comes from the desire to distinguish between a pass-phrase and a PSK displayed as 64 hexadecimal characters. — Each character in the pass-phrase must have an encoding in the range of 32 to 126 (decimal), inclusive. So, yes, we wrote the standard for 8-63 characters. But there are product out there that allow for smaller. Just bad implementations, but the real world. If you're able to get a scan of that network, I'd be very curious to see what it's output is. It *may* be a WPS network, which is a method to set up a wifi connection somewhat like pairing a Bluetooth device. That allows all numeric PIN codes, and automatically determines the *actual* passphrase from a handshake that uses the PIN. Nope, as there is more involved to use WPS. That does not work well at all in a big office building in the meeting rooms in same. But for the 'fun' of it, I will try it with WPS. On any SSID I set up, I will use a reasonably strong passcode (though I would REALLY like to start using SAE in place of PSK!), but sometimes you have NO control over what others do. I REALLY need an override on the passcode length requirement; I will again be at that location for a meeting Dec 19. Excellent, can you run: iw dev wlan0 scan trigger iw dev wlan0 scan dump and grab the output for any AP of that network. Feel free to out the MAC address and the SSID, since they aren't the interesting part. What we want to know is a block like this: WPS: * Version: 1.0 * Wi-Fi Protected Setup State: 2 (Configured) * Response Type: 3 (AP) * UUID: 3a05b2ad-a879-917c-cc3f-5717fb38815f * Manufacturer: NETGEAR, Inc. * Model: WNDR3400v2 * Model Number: WNDR3400v2 * Serial Number: 01 * Primary Device Type: 6-0050f204-1 * Device name: WNDR3400v2 * Config methods: Label * RF Bands: 0x3 Will do this. For connectivity at the next meeting, I am working on getting Hotspot working on my new Galaxy phone... Dan I doubt I will find a way to complain to this company's senior management on their IT department's 'bad' policy. This setup is probably only intended to keep rifraf from trying to get to the NEXT level of access control (you then need an 8 hour user account for hotspot login). Oh, I did not mention that they hide this SSID. Sheesh. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA-PSK password length requirement
On 12/11/2012 01:53 PM, Dan Williams wrote: On Tue, 2012-12-11 at 13:17 -0500, Robert Moskowitz wrote: On 12/11/2012 10:02 AM, Dan Williams wrote: On Tue, 2012-12-11 at 06:24 -0500, Robert Moskowitz wrote: The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3. First I was a major contributor to 802.11i and wrote the first paper on the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your typical end user having a complaint on client behaviour. Yesterday, I was at a major corporation for a meeting and the quest SSID had a 6 digit all numeric passcode. NM would not let me connect; it seem to insist that a passcode for WPA2-PSK be at least 8 characters long. The meeting participants using Windows had no difficulty with this 6 digit passcode and were able to get on the guest wireless network. If it's a 6 digit passcode, then it's not a valid WPA passphrase. Um, I helped write that section of 802.11i. Of course now it is just part of 802.11-2012: M.4 Suggested pass-phrase-to-PSK mapping The pass-phrase mapping defined in this subclause uses the PBKDF2 method from PKCS #5 v2.0 [B53]. PSK = PBKDF2(PassPhrase, ssid, ssidLength, 4096, 256) Here, the following assumptions apply: — A pass-phrase is a sequence of between 8 and 63 ASCII-encoded characters. The limit of 63 comes from the desire to distinguish between a pass-phrase and a PSK displayed as 64 hexadecimal characters. — Each character in the pass-phrase must have an encoding in the range of 32 to 126 (decimal), inclusive. So, yes, we wrote the standard for 8-63 characters. But there are product out there that allow for smaller. Just bad implementations, but the real world. And these devices pass WiFi Alliance certification? Given who this company is, I suspect yes. I was just thinking; I can get the BSSID and that will give us the MAC manufacture which is probably the device manufacture :) But their security certification has always been weak to compliance. ICSAlabs put in a bit back in the days, but we lost out as all we were 'good' at was the security and did not have experience in RF certification. Dan If you're able to get a scan of that network, I'd be very curious to see what it's output is. It *may* be a WPS network, which is a method to set up a wifi connection somewhat like pairing a Bluetooth device. That allows all numeric PIN codes, and automatically determines the *actual* passphrase from a handshake that uses the PIN. Nope, as there is more involved to use WPS. That does not work well at all in a big office building in the meeting rooms in same. But for the 'fun' of it, I will try it with WPS. On any SSID I set up, I will use a reasonably strong passcode (though I would REALLY like to start using SAE in place of PSK!), but sometimes you have NO control over what others do. I REALLY need an override on the passcode length requirement; I will again be at that location for a meeting Dec 19. Excellent, can you run: iw dev wlan0 scan trigger iw dev wlan0 scan dump and grab the output for any AP of that network. Feel free to out the MAC address and the SSID, since they aren't the interesting part. What we want to know is a block like this: WPS: * Version: 1.0 * Wi-Fi Protected Setup State: 2 (Configured) * Response Type: 3 (AP) * UUID: 3a05b2ad-a879-917c-cc3f-5717fb38815f * Manufacturer: NETGEAR, Inc. * Model: WNDR3400v2 * Model Number: WNDR3400v2 * Serial Number: 01 * Primary Device Type: 6-0050f204-1 * Device name: WNDR3400v2 * Config methods: Label * RF Bands: 0x3 Will do this. For connectivity at the next meeting, I am working on getting Hotspot working on my new Galaxy phone... Dan I doubt I will find a way to complain to this company's senior management on their IT department's 'bad' policy. This setup is probably only intended to keep rifraf from trying to get to the NEXT level of access control (you then need an 8 hour user account for hotspot login). Oh, I did not mention that they hide this SSID. Sheesh. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA-PSK password length requirement
On 12/11/2012 06:27 PM, Dan Williams wrote:
On Tue, 2012-12-11 at 14:01 -0500, Robert Moskowitz wrote:
On 12/11/2012 01:53 PM, Dan Williams wrote:
On Tue, 2012-12-11 at 13:17 -0500, Robert Moskowitz wrote:
On 12/11/2012 10:02 AM, Dan Williams wrote:
On Tue, 2012-12-11 at 06:24 -0500, Robert Moskowitz wrote:
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I was at a major corporation for a meeting and the quest SSID
had a 6 digit all numeric passcode. NM would not let me connect; it
seem to insist that a passcode for WPA2-PSK be at least 8 characters
long. The meeting participants using Windows had no difficulty with
this 6 digit passcode and were able to get on the guest wireless network.
If it's a 6 digit passcode, then it's not a valid WPA passphrase.
Um, I helped write that section of 802.11i. Of course now it is just
part of 802.11-2012:
M.4 Suggested pass-phrase-to-PSK mapping
The pass-phrase mapping defined in this subclause uses the PBKDF2 method
from PKCS #5 v2.0 [B53].
PSK = PBKDF2(PassPhrase, ssid, ssidLength, 4096, 256)
Here, the following assumptions apply:
— A pass-phrase is a sequence of between 8 and 63 ASCII-encoded
characters. The limit of 63 comes
from the desire to distinguish between a pass-phrase and a PSK displayed
as 64 hexadecimal
characters.
— Each character in the pass-phrase must have an encoding in the range
of 32 to 126 (decimal),
inclusive.
So, yes, we wrote the standard for 8-63 characters. But there are
product out there that allow for smaller. Just bad implementations, but
the real world.
And these devices pass WiFi Alliance certification?
Given who this company is, I suspect yes. I was just thinking; I can get
the BSSID and that will give us the MAC manufacture which is probably
the device manufacture :)
But their security certification has always been weak to compliance.
ICSAlabs put in a bit back in the days, but we lost out as all we were
'good' at was the security and did not have experience in RF certification.
Note that wpa_supplicant does not allow passphrases with a shorter
length than 8 characters:
if (len 8 || len 63) {
wpa_printf(MSG_ERROR, Line %d: Invalid passphrase
length %lu (expected: 8..63) '%s'.,
line, (unsigned long) len, value);
return -1;
}
If you plead your case to Jouni (the hostap/wpa_supplicant maintainer
who also helps draft 802.11 standards), and he agrees to allow
shorter-than-8-char passphrases, then I'll entertain lowering the limit
in NetworkManager.
I will probably see Jouni at the January meeting in Vancouver.
Random aside: another problem we periodically have is the character
encoding for hashing passphrases to the actual PSK. When entering the
initial setup passphrase in a browser, and if the browser allows
non-ASCII characters, it's entirely unknown (a) what encoding the
browser is set to, and (b) how the software on the AP hashes the
passphrase to the PSK. We've had problems with passphrases that contain
umlauts, for example.
Oh, we have discussed this endlessly at the IETF, going way back. It can
get very messy. Even Unicode will not help you out here; in fact it can
make it worst! And this is causing major chanellenges for ISN.
When you're next at that location, if there's any chance you get get the
actual hashed passphrase (ie 64 hex chars) from somebody, I'd love to
see see how the shorter-than-8-char passphrase got hashed to a PSK; did
it get padded with zeros or something? Or just hashed straight-up?
I am so rusty with running Wireshark over wireless. I was probably
running F10 when I would be doing this sort of thing. I will try and
brush up early next week (I am off the next 2 days to visit my son in NJ).
I recall now that on the white board where they wrote down the wireless
access, they definitely said WPA2-PSK and that 6 digit code. And windoze
people were getting on the wireless network.
If you're able to get a scan of that network, I'd be very curious to see
what it's output is.
It *may* be a WPS network, which is a method to set up a wifi connection
somewhat like pairing a Bluetooth device. That allows all numeric PIN
codes, and automatically determines the *actual* passphrase from a
handshake that uses the PIN.
Nope, as there is more involved to use WPS. That does not work well at
all in a big office building in the meeting rooms in same. But for the
'fun' of it, I will try it with WPS.
On any SSID I set up, I will use a reasonably strong passcode (though I
would REALLY like to start using SAE in place of PSK!), but sometimes
you have NO control over what others do. I REALLY need an override on
the passcode length requirement; I will again be at that location for a
meeting Dec 19.
Excellent
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 06:09 PM, Brian Morrison wrote: On Wed, 07 Nov 2012 18:02:05 -0500 Robert Moskowitz r...@htt-consult.com wrote: Reboot go NM showing the 'proper' connect icon. Now we go through the suspend/resume cycle and see if it stays working right. Well if not then post your experience here, I'm sure someone will request the needed information to diagnose and fix it if it doesn't work for you. Well it is not working again. Or still. I was having connectivity problems last night in my room, so turned off the wireless and just used the room wired connection. Then this morning I had hall talks all morning and never connected. At noon (lunch) I again used wired. Now I turned on the wireless and at first it connected to the hotel's 'free' SSID and only showed the ...; I then switched to the IETF SSID and it still just shows the ..., but When I click on the connect icon, it shows that it is connected to a network called 'Auto ietf' which I know is NOT an existing SSID here at the conference. Rather the SSID is just 'ietf'. So something else is going on here. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/08/2012 01:01 PM, Dan Williams wrote: On Thu, 2012-11-08 at 12:53 -0500, Robert Moskowitz wrote: On 11/07/2012 06:09 PM, Brian Morrison wrote: On Wed, 07 Nov 2012 18:02:05 -0500 Robert Moskowitz r...@htt-consult.com wrote: Reboot go NM showing the 'proper' connect icon. Now we go through the suspend/resume cycle and see if it stays working right. Well if not then post your experience here, I'm sure someone will request the needed information to diagnose and fix it if it doesn't work for you. Well it is not working again. Or still. I was having connectivity problems last night in my room, so turned off the wireless and just used the room wired connection. Then this morning I had hall talks all morning and never connected. At noon (lunch) I again used wired. Now I turned on the wireless and at first it connected to the hotel's 'free' SSID and only showed the ...; I then switched to the IETF SSID and it still just shows the ..., but When I click on the connect icon, it shows that it is connected to a network called 'Auto ietf' which I know is NOT an existing SSID here at the conference. Rather the SSID is just 'ietf'. So something else is going on here. So there's two parts to this equation. First, NetworkManager and what it's doing. Second, the UI applet and what it's showing. To confirm what NM is actually doing, you can use 'nmcli' and 'nm-tool'. eg nmcli dev list iface wlan0 will dump everything interesting about wlan0 that NM knows. You can compare this output to the applet's output and find out which thing is wrong. Look for APx.ACTIVE: yes to see which AP NM thinks you're connected to. If the issue is actually NetworkManager, then /var/log/messages is your friend here, so we can see where things are going wrong. If the issue is actually the UI applet, be that gnome-shell's network indicator or nm-applet or the KDE applet, then we have to persue the problem there. I am attaching the output of the nmcli and latest content of grep NetworkManageer /var/log/messages Note that there are NO APx ACTIVE: yes lines from nmcli. Perhaps you can make heads or tails of this. GENERAL.DEVICE: wlan0 GENERAL.TYPE: 802-11-wireless GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT:RTL8188CE 802.11b/g/n WiFi Adapter GENERAL.DRIVER: rtl8192ce GENERAL.DRIVER-VERSION: 3.6.2-1.fc16.x86_64 GENERAL.FIRMWARE-VERSION: N/A GENERAL.HWADDR: EC:55:F9:C7:8C:DF GENERAL.STATE: 100 (connected) GENERAL.REASON: 0 (No reason given) GENERAL.UDI: /sys/devices/pci:00/:00:15.1/:04:00.0/net/wlan0 GENERAL.IP-IFACE: wlan0 GENERAL.NM-MANAGED: yes GENERAL.AUTOCONNECT:yes GENERAL.FIRMWARE-MISSING: no GENERAL.CONNECTION: /org/freedesktop/NetworkManager/ActiveConnection/14 CAPABILITIES.CARRIER-DETECT:no CAPABILITIES.SPEED: unknown WIFI-PROPERTIES.WEP:yes WIFI-PROPERTIES.WPA:yes WIFI-PROPERTIES.WPA2: yes WIFI-PROPERTIES.TKIP: yes WIFI-PROPERTIES.CCMP: yes AP1.SSID: 'ietf.1x' AP1.BSSID: 00:17:DF:A8:D2:23 AP1.MODE: Infrastructure AP1.FREQ: 2462 MHz AP1.RATE: 54 MB/s AP1.SIGNAL: 82 AP1.SECURITY: WPA WPA2 Enterprise AP1.ACTIVE: no AP2.SSID: 'ietf.1x' AP2.BSSID: 00:17:DF:AA:0A:63 AP2.MODE: Infrastructure AP2.FREQ: 2412 MHz AP2.RATE: 54 MB/s AP2.SIGNAL: 82 AP2.SECURITY: WPA WPA2 Enterprise AP2.ACTIVE: no AP3.SSID: 'eduroam' AP3.BSSID: 00:17:DF:AA:0A:60 AP3.MODE: Infrastructure AP3.FREQ: 2412 MHz AP3.RATE: 54 MB/s AP3.SIGNAL: 82 AP3.SECURITY: WPA WPA2 Enterprise AP3.ACTIVE: no AP4.SSID: 'eduroam' AP4.BSSID: 00:17:DF:A9:CE:40 AP4.MODE: Infrastructure AP4.FREQ: 2437 MHz AP4.RATE: 54 MB/s AP4.SIGNAL: 87 AP4.SECURITY: WPA WPA2 Enterprise AP4.ACTIVE: no AP5.SSID
Re: F16 NetworkManager icon showing connecting when connected
On 11/08/2012 03:11 PM, Dan Williams wrote: On Thu, 2012-11-08 at 14:31 -0500, Robert Moskowitz wrote: On 11/08/2012 02:10 PM, Dan Williams wrote: On Thu, 2012-11-08 at 13:34 -0500, Robert Moskowitz wrote: Nov 8 12:48:23 lx120e NetworkManager[918]: info (wlan0): roamed from BSSID 00:17:DF:A8:D2:21 (ietf) to (none) ((none)) Is the problem. Let me guess; Broadcom hardware using wl.o perhaps? Or a staging driver? We try to paper over this driver issue when we can, and perhaps we can hack something else in here. GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT:RTL8188CE 802.11b/g/n WiFi Adapter GENERAL.DRIVER: rtl8192ce If possible, can you: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw # dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw method return sender=:1.4 - dest=:1.221 reply_serial=2 (with sudo or as root) and then reconnect to the IETF AP and grab the resulting log output? We're specifically interested in the bits for get_active_ap and why there's no match; also what the values are for: get_active_ap(): (wlan0): active BSSID: 00:30:gg:ff:ee:dd get_active_ap(): (wlan0): active SSID: 'xxx' This is unclear. I turned off the wireless then turned it back on. Here is everything from /var/log/messages from that. How do I turn off the debug logging now? same dbus-send command, just instead of debug put info. OK. done. [nm-device-wifi.c:513] get_active_ap(): (wlan0): active BSSID: 00:00:00:00:00:00 is the problem. The device is saying it's not connected to anything. When it really is. When you see the roamed from... thing, What is the 'roam from'? Do I force a roam to the hotel SSID and then back to IETF'S? can you run iwconfig wlan0 for me? also iw dev wlan0 link. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/08/2012 03:11 PM, Dan Williams wrote: On Thu, 2012-11-08 at 14:31 -0500, Robert Moskowitz wrote: On 11/08/2012 02:10 PM, Dan Williams wrote: On Thu, 2012-11-08 at 13:34 -0500, Robert Moskowitz wrote: Nov 8 12:48:23 lx120e NetworkManager[918]: info (wlan0): roamed from BSSID 00:17:DF:A8:D2:21 (ietf) to (none) ((none)) Is the problem. Let me guess; Broadcom hardware using wl.o perhaps? Or a staging driver? We try to paper over this driver issue when we can, and perhaps we can hack something else in here. GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT:RTL8188CE 802.11b/g/n WiFi Adapter GENERAL.DRIVER: rtl8192ce If possible, can you: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw # dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw method return sender=:1.4 - dest=:1.221 reply_serial=2 (with sudo or as root) and then reconnect to the IETF AP and grab the resulting log output? We're specifically interested in the bits for get_active_ap and why there's no match; also what the values are for: get_active_ap(): (wlan0): active BSSID: 00:30:gg:ff:ee:dd get_active_ap(): (wlan0): active SSID: 'xxx' This is unclear. I turned off the wireless then turned it back on. Here is everything from /var/log/messages from that. How do I turn off the debug logging now? same dbus-send command, just instead of debug put info. [nm-device-wifi.c:513] get_active_ap(): (wlan0): active BSSID: 00:00:00:00:00:00 is the problem. The device is saying it's not connected to anything. When you see the roamed from... thing, can you run iwconfig wlan0 for me? also iw dev wlan0 link. BTW, I am only here for 2 more hours then I have to head over to the airport for my flight home. oh course there is always next week where this would probably happen again! ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/08/2012 03:11 PM, Dan Williams wrote: On Thu, 2012-11-08 at 14:31 -0500, Robert Moskowitz wrote: On 11/08/2012 02:10 PM, Dan Williams wrote: On Thu, 2012-11-08 at 13:34 -0500, Robert Moskowitz wrote: Nov 8 12:48:23 lx120e NetworkManager[918]: info (wlan0): roamed from BSSID 00:17:DF:A8:D2:21 (ietf) to (none) ((none)) Is the problem. Let me guess; Broadcom hardware using wl.o perhaps? Or a staging driver? We try to paper over this driver issue when we can, and perhaps we can hack something else in here. GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT:RTL8188CE 802.11b/g/n WiFi Adapter GENERAL.DRIVER: rtl8192ce If possible, can you: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw # dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw method return sender=:1.4 - dest=:1.221 reply_serial=2 (with sudo or as root) and then reconnect to the IETF AP and grab the resulting log output? We're specifically interested in the bits for get_active_ap and why there's no match; also what the values are for: get_active_ap(): (wlan0): active BSSID: 00:30:gg:ff:ee:dd get_active_ap(): (wlan0): active SSID: 'xxx' This is unclear. I turned off the wireless then turned it back on. Here is everything from /var/log/messages from that. How do I turn off the debug logging now? same dbus-send command, just instead of debug put info. [nm-device-wifi.c:513] get_active_ap(): (wlan0): active BSSID: 00:00:00:00:00:00 is the problem. The device is saying it's not connected to anything. When you see the roamed from... thing, can you run iwconfig wlan0 for me? also iw dev wlan0 link. Anyway, this is what I am seeing right now: # iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:off # iw dev wlan0 link Not connected. And yet I know I am connected as this message will be going out when I click on send! ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/08/2012 04:49 PM, Dan Williams wrote: On Thu, 2012-11-08 at 16:23 -0500, Robert Moskowitz wrote: On 11/08/2012 03:11 PM, Dan Williams wrote: On Thu, 2012-11-08 at 14:31 -0500, Robert Moskowitz wrote: On 11/08/2012 02:10 PM, Dan Williams wrote: On Thu, 2012-11-08 at 13:34 -0500, Robert Moskowitz wrote: Nov 8 12:48:23 lx120e NetworkManager[918]: info (wlan0): roamed from BSSID 00:17:DF:A8:D2:21 (ietf) to (none) ((none)) Is the problem. Let me guess; Broadcom hardware using wl.o perhaps? Or a staging driver? We try to paper over this driver issue when we can, and perhaps we can hack something else in here. GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT:RTL8188CE 802.11b/g/n WiFi Adapter GENERAL.DRIVER: rtl8192ce If possible, can you: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw # dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:debug string:wifi,wifi_scan,core,device,hw method return sender=:1.4 - dest=:1.221 reply_serial=2 (with sudo or as root) and then reconnect to the IETF AP and grab the resulting log output? We're specifically interested in the bits for get_active_ap and why there's no match; also what the values are for: get_active_ap(): (wlan0): active BSSID: 00:30:gg:ff:ee:dd get_active_ap(): (wlan0): active SSID: 'xxx' This is unclear. I turned off the wireless then turned it back on. Here is everything from /var/log/messages from that. How do I turn off the debug logging now? same dbus-send command, just instead of debug put info. [nm-device-wifi.c:513] get_active_ap(): (wlan0): active BSSID: 00:00:00:00:00:00 is the problem. The device is saying it's not connected to anything. When you see the roamed from... thing, can you run iwconfig wlan0 for me? also iw dev wlan0 link. Anyway, this is what I am seeing right now: # iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:off # iw dev wlan0 link Not connected. And yet I know I am connected as this message will be going out when I click on send! So at this point it's completely a driver problem. If you're actually connected, then *both* these commands should report that fact. NM trusts the kernel here, and the kernel is letting us down. NM has no way of knowing that we're connected to anything at all if the kernel doesn't report that correctly :( Great. So how do I get all this to the proper REALTEK people? One would think This is after all a Lenovo that once had a hisgtory of great Linux support... ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/06/2012 05:18 PM, Dan Williams wrote: On Tue, 2012-11-06 at 14:02 -0500, Robert Moskowitz wrote: On 11/06/2012 11:43 AM, Brian Morrison wrote: On Tue, 6 Nov 2012 16:30:53 + Brian Morrison wrote: On Tue, 6 Nov 2012 16:15:37 + Brian Morrison wrote: On Tue, 06 Nov 2012 10:30:12 -0500 Robert Moskowitz wrote: I am current on all updates with F16 as of last night. Not sure if it applies to F16, but some updated NM rpms landed for F17 this morning in the UK. See here: https://bugzilla.gnome.org/show_bug.cgi?id=685581 Seems to have made it into Fedora NM packages from 0.9.7.0-4.git20121004 onwards. I can't see anything that new for F16, you might be able to rebuild one of the packages for F18 or F19 if dependencies haven't changed too much. The patch needed is fairly simple: http://bugzilla-attachments.gnome.org/attachment.cgi?id=225900 it should be possible to apply this as a patch in the .spec file for NM and rebuild the packages locally. I am not one for patching. I will take this to the Fedora test list and see if I can get this into updates for F16 and F17. But for what it is worth, I have had this problem for quite some time; at least the past 6 mo of conferences (I am active in IETF and IEEE 802, so have at least 9 week long meetings every year). This is not something recently introduced into NM. I finally decided to ask about it. Update for F16; submitted but not yet pushed to testing: https://admin.fedoraproject.org/updates/NetworkManager-0.9.6.4-1.fc16 The update for F17 should already be in updates-testing, I think: https://admin.fedoraproject.org/updates/FEDORA-2012-17387/NetworkManager-0.9.6.4-1.fc17 Please give bodhi feedback on either of these, thanks! Well if I get the update before next week, I will have the chance as next week is IEEE 802 plenary. After that I will be at an EU conference start of Dec that MAY have an environment similar enough to trigger the same event! Then nothing on the books until mid-Jan :) ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 08:13 AM, Brian Morrison wrote: On Wed, 07 Nov 2012 07:43:46 -0500 Robert Moskowitz r...@htt-consult.com wrote: Well if I get the update before next week, yum --enablerepo=updates-testing update Network-Manager will get the package from the testing repo and any dependencies that have been updated. # yum --enablerepo=updates-testing update Network-Manager Loaded plugins: langpacks, presto, refresh-packagekit updates-testing/metalink | 2.3 kB 00:00 updates-testing | 4.7 kB 00:00 updates-testing/primary_db | 619 kB 00:03 updates-testing/group_gz | 435 kB 00:01 No Match for argument: Network-Manager No package Network-Manager available. No Packages marked for Update Now what? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 10:24 AM, Derek Atkins wrote: On Wed, November 7, 2012 10:18 am, Robert Moskowitz wrote: On 11/07/2012 08:13 AM, Brian Morrison wrote: On Wed, 07 Nov 2012 07:43:46 -0500 Robert Moskowitz r...@htt-consult.com wrote: Well if I get the update before next week, yum --enablerepo=updates-testing update Network-Manager will get the package from the testing repo and any dependencies that have been updated. # yum --enablerepo=updates-testing update Network-Manager Loaded plugins: langpacks, presto, refresh-packagekit updates-testing/metalink | 2.3 kB 00:00 updates-testing | 4.7 kB 00:00 updates-testing/primary_db | 619 kB 00:03 updates-testing/group_gz | 435 kB 00:01 No Match for argument: Network-Manager No package Network-Manager available. No Packages marked for Update Now what? Try it without the dash yum --enablerepo=updates-testing update NetworkManager yum --enablerepo=updates-testing update NetworkManager Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update Derek, where are you? Can we sit down and get this installed so I can test it? (Brian, Derek is also here at the IETF meeting, and an old colleague of mine). ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 11:00 AM, Derek Atkins wrote: Bob, On Wed, November 7, 2012 10:37 am, Robert Moskowitz wrote: yum --enablerepo=updates-testing update NetworkManager Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update Derek, where are you? Can we sit down and get this installed so I can test it? (Brian, Derek is also here at the IETF meeting, and an old colleague of mine). According to koji[0] it looks like it was just built yesterday, so it might not have made the mirrors yet. You could download and install from koji, or wait for the package to propagate, which might take another day. For what it's worth I see this myself with VPNs too, but I'm on F15 still so have no hope for a fix ;) -derek [0] http://koji.fedoraproject.org/koji/buildinfo?buildID=364798 Ok. I downloaded and did a yum localinstall of: NetworkManager-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-glib-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gnome-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gtk-0.9.6.4-1.fc16.x86_64.rpm Do now do how do I restart NetworkManager? Is there someway other than a reboot? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 05:00 PM, Derek Atkins wrote: On Wed, November 7, 2012 4:50 pm, Robert Moskowitz wrote: On 11/07/2012 11:00 AM, Derek Atkins wrote: Bob, On Wed, November 7, 2012 10:37 am, Robert Moskowitz wrote: yum --enablerepo=updates-testing update NetworkManager Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update Derek, where are you? Can we sit down and get this installed so I can test it? (Brian, Derek is also here at the IETF meeting, and an old colleague of mine). According to koji[0] it looks like it was just built yesterday, so it might not have made the mirrors yet. You could download and install from koji, or wait for the package to propagate, which might take another day. For what it's worth I see this myself with VPNs too, but I'm on F15 still so have no hope for a fix ;) -derek [0] http://koji.fedoraproject.org/koji/buildinfo?buildID=364798 Ok. I downloaded and did a yum localinstall of: NetworkManager-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-glib-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gnome-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gtk-0.9.6.4-1.fc16.x86_64.rpm Do now do how do I restart NetworkManager? Is there someway other than a reboot? For the service you can run, as root: service NetworkManager restart I'm not sure how to restart the applet. I did an alkt F2 then r to restart Gnome, but I am still seeing the ... So here comes the reboot. Sigh. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/07/2012 05:55 PM, Robert Moskowitz wrote: On 11/07/2012 05:00 PM, Derek Atkins wrote: On Wed, November 7, 2012 4:50 pm, Robert Moskowitz wrote: On 11/07/2012 11:00 AM, Derek Atkins wrote: Bob, On Wed, November 7, 2012 10:37 am, Robert Moskowitz wrote: yum --enablerepo=updates-testing update NetworkManager Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update Derek, where are you? Can we sit down and get this installed so I can test it? (Brian, Derek is also here at the IETF meeting, and an old colleague of mine). According to koji[0] it looks like it was just built yesterday, so it might not have made the mirrors yet. You could download and install from koji, or wait for the package to propagate, which might take another day. For what it's worth I see this myself with VPNs too, but I'm on F15 still so have no hope for a fix ;) -derek [0] http://koji.fedoraproject.org/koji/buildinfo?buildID=364798 Ok. I downloaded and did a yum localinstall of: NetworkManager-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-glib-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gnome-0.9.6.4-1.fc16.x86_64.rpm NetworkManager-gtk-0.9.6.4-1.fc16.x86_64.rpm Do now do how do I restart NetworkManager? Is there someway other than a reboot? For the service you can run, as root: service NetworkManager restart I'm not sure how to restart the applet. I did an alkt F2 then r to restart Gnome, but I am still seeing the ... So here comes the reboot. Sigh. Reboot go NM showing the 'proper' connect icon. Now we go through the suspend/resume cycle and see if it stays working right. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
F16 NetworkManager icon showing connecting when connected
On my Lenovo X120e with F16 and Gnome 3 at conferences in hotels (where there tend to be LOTS of SSIDs with overlapping channel usage), I frequently get a situation where the Network Manager icon is showing the ... when it is connected. I am constantly taking my computer in and out of suspend mode as I move from meeting session to meeting session and then connecting to a different AP on the same SSID and perhaps the same channel (I HATE the current Network Manager that does not provide connection info like channel, performance, BSSID, etc.). It is not uncommon that at some point I get into the situation I am now with the ... showing when I can tell I am connected (as I will have no trouble sending this email!). If I click on the icon I can see that I am connected with all 4 lines of the radio symbol. This problem will persist across all SSIDs (here I am switching between the hotel and conference SSID) until I reboot. I am current on all updates with F16 as of last night. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F16 NetworkManager icon showing connecting when connected
On 11/06/2012 11:43 AM, Brian Morrison wrote: On Tue, 6 Nov 2012 16:30:53 + Brian Morrison wrote: On Tue, 6 Nov 2012 16:15:37 + Brian Morrison wrote: On Tue, 06 Nov 2012 10:30:12 -0500 Robert Moskowitz wrote: I am current on all updates with F16 as of last night. Not sure if it applies to F16, but some updated NM rpms landed for F17 this morning in the UK. See here: https://bugzilla.gnome.org/show_bug.cgi?id=685581 Seems to have made it into Fedora NM packages from 0.9.7.0-4.git20121004 onwards. I can't see anything that new for F16, you might be able to rebuild one of the packages for F18 or F19 if dependencies haven't changed too much. The patch needed is fairly simple: http://bugzilla-attachments.gnome.org/attachment.cgi?id=225900 it should be possible to apply this as a patch in the .spec file for NM and rebuild the packages locally. I am not one for patching. I will take this to the Fedora test list and see if I can get this into updates for F16 and F17. But for what it is worth, I have had this problem for quite some time; at least the past 6 mo of conferences (I am active in IETF and IEEE 802, so have at least 9 week long meetings every year). This is not something recently introduced into NM. I finally decided to ask about it. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
NM serious usablity challenges
F16, Gnome3. I am at a friend's house in Amsterdam trying to get connect to his wireless and it is failing, so this message SHOULD go out when I get to the KLM lounge tommorrow (that was working friday)... A major defiency is the loss of deleting SSID configurations. There is no 'delete' feature anymore in the Network Settings panel. There is a network near here that has the same SSID as at another friends (let's call it NETGEAR), but this one has a different password that I do not know. Doesn't matter, NM keeps trying to connect and asks me for a different password when it fails. I have no way (or found no way), to delete or even deactivate this SSID from NM. So it keeps trying and trying. Connection to my friend's wireless SEEMs to be a DHCP problem. I have this hunch by watching /var/log/messages; this 'new' network manager does not tell me why it is failing. Now I shoud preface the next part with I work in 802.11 standards. Right now I am active in 802.11ai (FIA), so I KNOW the .11 state machine. Is the problem in initial connection (AUTH,ASSOC); note it is possible to be receiving BEACONs, but be too far to actually ASSOCIATE with an AP. The user should be told the problem is here. Or is it a bad password; well that is the guess when it presents the dialog for the password but i KNOW the password is correct. Oh, perhaps the problem is DHCPv4 (or v6?) and since there is no way to tell the user to fix the DHCP allocation in the router, the poor user gets asked to try a different password? You KNOW what the failure is. PLEASE give some information as to which step things stop at. Plus change the icon from that strange ... thing to something showing trying and trying what? (ASSOC, SECURE, ADDRESS). Also be so informed that when 11ai gets done (you do have 2 years) we are going to do all this in a couple/few roundtrips. My proposal does the whole shabang in 2. The AUTH starts the securing and the ASSOC finishes the securing and does the addressing, though there are times where addressing extends the ASSOC for another roundtrip. Now back to feature loss over Gnome2 NM I cannot turn off wireless from the NM pulldown if it is currently trying (and really failing) to connect. I have to open the Network Settings dialog and turn off wireless there. While attempting to connect the on/off switch is replaced with the text 'connecting'. I know that, I want to stop it trying to connect, and the only way to do that is turn the wireless off. Does turning NM off turn off the wireless radio? I have a Lenovo x120 and it does not have a wireless radio switch and on airplanes, I like to turn off my radio and save battery. All I can do is turn off NM, but I have no way of knowing WHAT is being turned off! Enough challenges for tonight. Tomorrow it is off to the airport and hopefully connectivity there on my way to the IETF meeting. (yes I am a standards guy). ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Fedora16 - Brain dead wireless network manager
f16 and gnome 3. I don't know what ver of Network Manager... Now I know a little bit about 802.11. I am currently at the IEEE 802 wireless interim meeting in Jacksonville, FL. Most of my time is in 802.15.9 (I am the chair), but I still attend 802.11 sessions. That is I know something about the guts of 802.11 setup... So here I am switching between the hotel's questionably usable ESS and the conference's ESS. Of course both have different SSIDs (SSID defines an ESS, generally) and each has lots of Access Points many on the same channel. So I am in a meeting room on the VeriLAN SSID. I suspend my system and go to my room to the Hyatt SSID. The icon shows the SSID selected and a signal strength but has 'unavailable' after the word 'Wireless'. What is going on here? There is no easy way to restart the connection. I have to go into Network Settings, turn off wireless and turn it on. ARGH! Then I am not getting anything to work on the Hyatt SSID, yet it is showing 3 bars of signal strength. But is there any textual info on S/N or anything worthwhile? Of course not. WiFi is suppose to be used by cellphone users that only know to look at bars on their cellphones, so that must be good enough? When you are working on multiple ESSes as you will in a hotel (many have a different SSID for the lobby from the rooms from the meeting rooms even without the meeting having its own!), you need better. Or at least what I had with f14 and Gnome 2. Oh, this is on a Lenovo x120e where I see the following in the log messages: Jan 16 22:16:42 lx120e kernel: [81433.007709] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin I would like some help on getting things to work better... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fedora16 - Brain dead wireless network manager
On 01/17/2012 08:38 AM, Dan Winship wrote: On 01/17/2012 08:14 AM, Robert Moskowitz wrote: Oh, this is on a Lenovo x120e where I see the following in the log messages: Jan 16 22:16:42 lx120e kernel: [81433.007709] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin The driver for that chipset is apparently broken in the current kernel: https://bugzilla.redhat.com/show_bug.cgi?id=729618 (There are links to various testing kernels with different patches in that bug, but it's hard to tell from the comments if they fix the problem...) Now why does that not supprise me? I did notice one update to the driver a while back. And I have 'real work' (spec writing!) to do to test f17... But it does not address the removal of information from the UI nor the control over SSID selection/control. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fedora16 - Brain dead wireless network manager
On 01/17/2012 10:45 AM, Martin Langhoff wrote: OTOH, reconnection to wlans seems to be faster than F15, which had some crazy long timeouts. Still slower than iOS, perhaps almost on par w Android devices. cheers, m 802.11ai is looking at how to streamline the whole setup process. You can access the documents for this wg via: https://mentor.ieee.org/802.11/documents?is_group=00ai Still no agreement on way forward, so relief is a while off. Sigh. And yes, I have my proposals here. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Gnome 3 - wireless connection info
In Gnome 2 I would right click on the NM icon to get connection info. In Gnome 3 both left and right are giving me the list of connections. And clicking on the current connection does not produce anything. I am wireless at my son's appt. Well actually in the appt benieght him and I am dropping packets. So I wanted to see my connection info, but can't find it :( BTW, There are so many wireless networks here that I was not finding his in the list, even though it was the closest AP to me! I had to hand enter his SSID. Something does not seem to be right on either the scanning or the listing... ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Please add SAE support for WiFi
The 802.11s standard is now published. Boy did that take long enough! :) There is a new password authentication method in 11s that the way it was defined will work just fine between an AP and STA, or in adhoc between two STAs. This method is called Secure Authentication of Equals or SAE. It is a zero-based knowledge authenticaiton method that is immune to offline attacks and an active attack gets only one guess per attack. SAE is defined in Section 8.2a of 802.11s-2011. It is already in the OpenAP code (or so its author, Dan Harkins of Aruba told me). We finally have a strong password authentication method for WiFi. BTW, I am the author of the first paper on how to attack WPA-PSK, so I am directly involved in 802.11 security issues. I would hope to see SAE in APs in the near future. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Please add SAE support for WiFi
On 12/16/2011 12:19 PM, Dan Williams wrote: On Fri, 2011-12-16 at 11:36 -0500, Robert Moskowitz wrote: The 802.11s standard is now published. Boy did that take long enough! :) There is a new password authentication method in 11s that the way it was defined will work just fine between an AP and STA, or in adhoc between two STAs. This method is called Secure Authentication of Equals or SAE. It is a zero-based knowledge authenticaiton method that is immune to offline attacks and an active attack gets only one guess per attack. SAE is defined in Section 8.2a of 802.11s-2011. It is already in the OpenAP code (or so its author, Dan Harkins of Aruba told me). We finally have a strong password authentication method for WiFi. BTW, I am the author of the first paper on how to attack WPA-PSK, so I am directly involved in 802.11 security issues. I would hope to see SAE in APs in the near future. The process typically is to make sure that wpa_supplicant and the kernel drivers support the feature in question, and then finally we can modify NM to make use of it too. I'll be on the lookout for SAE support there... I sent this message also to the Fedora test list. That is the closest list I am on to the developers. I am right now in the need of a new AP, so I am searching for one that I can afford that will be able to get SAE support. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Please add SAE support for WiFi
On 12/16/2011 01:06 PM, Larry Finger wrote: On 12/16/2011 11:43 AM, Robert Moskowitz wrote: I sent this message also to the Fedora test list. That is the closest list I am on to the developers. I am right now in the need of a new AP, so I am searching for one that I can afford that will be able to get SAE support. You should send your request to linux-wirel...@vger.kernel.org. That is where most of the developers of the IEEE80211 MAC layer, the supplicant, and the device drivers can be found. Thanks. I sent a subscribe for the list, and a search of the archives found: http://marc.info/?l=linux-wirelessm=130145440930760w=2 Which seems to show SAE support in user space. So I wonder if it is in my f16 install? When SAE support is available in Linux, you would be able to implement it in nearly every router that runs openWRT. Only those units with very limited memory would be excluded. As openWRT-capable APs are mostly consumer grade, they should be affordable. And f16 with gnome 3.2 as well ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Please add SAE support for WiFi
On 12/16/2011 01:47 PM, Larry Finger wrote: On 12/16/2011 12:29 PM, Robert Moskowitz wrote: On 12/16/2011 01:06 PM, Larry Finger wrote: On 12/16/2011 11:43 AM, Robert Moskowitz wrote: I sent this message also to the Fedora test list. That is the closest list I am on to the developers. I am right now in the need of a new AP, so I am searching for one that I can afford that will be able to get SAE support. You should send your request to linux-wirel...@vger.kernel.org. That is where most of the developers of the IEEE80211 MAC layer, the supplicant, and the device drivers can be found. Thanks. I sent a subscribe for the list, and a search of the archives found: http://marc.info/?l=linux-wirelessm=130145440930760w=2 Which seems to show SAE support in user space. So I wonder if it is in my f16 install? When SAE support is available in Linux, you would be able to implement it in nearly every router that runs openWRT. Only those units with very limited memory would be excluded. As openWRT-capable APs are mostly consumer grade, they should be affordable. And f16 with gnome 3.2 as well That set of patches were accepted into the wireless-testing tree on April 7, 2011, and should be in any 3.1 or later kernel. I think you should have it in f16. I have no idea where to get the userspace tools. f16 is at 3.1.5 so looks good. Now I 'just' need SAE added to Network Manager in Gnome 3.2.1 If your wireless device supports AP mode (not all do), then you could use your laptop as an AP. That would work for testing purposes, but not operationally! I have to see if it is in OpenWRT yet. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
On 11/05/2010 11:00 AM, José Queiroz wrote: 2010/11/5 Marc Herbert marc.herb...@gmail.com mailto:marc.herb...@gmail.com PS: this does not look specific to IPv6 This does not look specific to NetworkManager, as long as NM is working strictly in the limits created by the RFCs... The last 64 bits are recommended to be based on the MAC address, but not only is this not required, it is not recommended for a server. For example: $ host www.ietf.org www.ietf.org has address 64.170.98.32 www.ietf.org has IPv6 address 2001:1890:1112:1::20 I could dig through the RFCs or ask my friends. But they are busy for IETF in Bejing next week and I am going to IEEE 802 next week in Dallas. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
On 11/05/2010 10:43 AM, Marc Herbert wrote: Le 04/11/2010 18:02, Robert Moskowitz a écrit : I want to control the IPv6 suffix for my interfaces and let the prefix be set with RA. Currently I can either have the RA prefix with the MAC address for the suffix, or I can specify a complete IPv6 address (and gateway) and ignore RA (doing this manually in the ifcfg-eth0 file as I don't see how to do this with Network manager). The first approach causes problems with DNS if I change the interface. Do you change the network interface that often? Updating the DNS once in a while does not look like a huge burden. It is the principle of the thing. Yes, if I am changing my prefix I have to change the DNS. But if I am only changing the hardware, why am I having to change the DNS? You could force the old MAC address on the new interface. Of course if you still use the old interface elsewhere you will be in trouble. The old mapping of MAC addresses has always been old from the days that I was dealing with this back on 3COM 501C cards and SUN servers. The second approach causes problems if I change the network prefix. ... and you still have the same DNS problem in this case, right? If you are changing prefixes, there are LOTs of things in DNS that are impacted. It is a pain; I have done it for IPv4 (but not for a few years). But much of IPv6 was to 'automate' readdressing for the systems. So we have the ability to use MAC addresses as part of the address. What I am saying is to add flexiblity so that other suffixes can be use. You seem to have an incredibly dynamic network environment, can you give more details about it? PS: this does not look specific to IPv6 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Specifying an IPv6 suffix
On 11/05/2010 01:41 PM, José Queiroz wrote: Em 5 de novembro de 2010 15:33, Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com escreveu: On 11/05/2010 11:00 AM, José Queiroz wrote: 2010/11/5 Marc Herbert marc.herb...@gmail.com mailto:marc.herb...@gmail.com PS: this does not look specific to IPv6 This does not look specific to NetworkManager, as long as NM is working strictly in the limits created by the RFCs... The last 64 bits are recommended to be based on the MAC address, but not only is this not required, it is not recommended for a server. For example: $ host www.ietf.org http://www.ietf.org www.ietf.org http://www.ietf.org has address 64.170.98.32 www.ietf.org http://www.ietf.org has IPv6 address 2001:1890:1112:1::20 How can you tell that this address was dinamically assigned, or a full static address was designed to it? I suspect that it a full static address as that is all any of the OSs out there can do. What I am asking for is, to the best of my knowledge, not supported on any platform. It just makes sense to me that has worked with addresses for quite some time (close to 20 years. What I am saying is to add flexiblity so that other suffixes can be use. Have you ever seen this feature in any other system? No. And it limits the usablity of RA IMHO. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Specifying an IPv6 suffix
I want to control the IPv6 suffix for my interfaces and let the prefix be set with RA. Currently I can either have the RA prefix with the MAC address for the suffix, or I can specify a complete IPv6 address (and gateway) and ignore RA (doing this manually in the ifcfg-eth0 file as I don't see how to do this with Network manager). The first approach causes problems with DNS if I change the interface. The second approach causes problems if I change the network prefix. Or I could implement DHCPv6, but would still have to change its content if I change the MAC address. And I don't want to ge the DHCPv6 approach anyway. The way I want would be better:) but I don't see that it is supported. My current systems are Centos 5.5 and FC12, so I am stuck, probably with the world as it is, but at least with FC14, it would be nice ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Creating AdHoc wireless network
Using NetworkManager 0.6.4 in Centos 5.2 Does it support AdHoc wireless network definitions? If so, how? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: About NM Connection Editor
Daniel Qarras wrote: I have been following this thread and wondering what the NM Connection Editor is and how I recognize I am using it! I do see something 'new' in the menus in systemPreferencesNetworkProxy, but that is probably not it or only a part You need a recent NM (0.6.6 or later), then just right-click on nm-applet and select Edit Connection where you'll see Wired/Wireless/. g. It looks like my 0.6.4 is in the Centos base repo, this means I have to find a rpm for 0.6.6 that I can put into my 'local' repo, as I problably won't see a newer version from upstream until 5.2 So is there an rpm for 6.6 out there? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How many SSIDs can be listed?
Matthew Saltzman wrote: On Tue, 2008-03-11 at 10:55 -0400, Robert Moskowitz wrote: Dan Williams wrote: Are any of the APs hidden? If they are 'hidden' (which is a myth, read my paper on this), they are not of interest. Hidding an SSID is a waste of effort. And it seriously breaks AP roaming. But we're talking about the client side here. There are, unfortunately, still admins that insist (contrary to all advice) on hiding their SSIDs. I may (do!) need to connect to one of these nets, and I have no influence over their policy 8^(. And thus you have to hand-craft your connect information. Your client has to do an active scan to find the APs for this SSID, doing it when you need it, not when it can check other channels in passive scanning during 'free time'. Sigh. 802.11 scanning is really dorky. OH, hopefully you only have ONE hidden SSID definition active. If you have more, then EACH is a separate active scan operation. And on the A band, boy does this HURT! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Any USB dongle support?
Anyone have experience with any USB dongles? Particularly ones that support WPA and use wext, not ndiswrapper? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How many SSIDs can be listed?
Dan Williams wrote: On Mon, 2008-03-10 at 23:40 -0400, Robert Moskowitz wrote: Ver 0.6.4 in Centos 5.1 I am seeing 17 SSIDs in the current list. But I am not seeing one that I expected to see. And some of the listed SSIDs are 'stale'; that is they were visible in the part of the hotel I was in a couple minutes ago, but not in this part. So I guess a second question is how do you force a scan to produce a current SSID list? You don't force a scan. NetworkManager will periodically scan with a backoff algorithm; it will start at 20 seconds and back off to 2 minutes. APs are kept in the scan list for a maximum of 6 minutes before being culled. This is a problem when you are moving around a lot. Well maybe not so much a problem if you are always wanting to connect to SSID ietf-a, regardless of which AP. But a problem if you are moving around in an area with a lot of open networks and you are looking for something to ride on... The problem is that wireless is hard, Tell me about it. I work on the standards. Will be in Orlando next week for the 802 plenary meeting. and sometimes cards/drivers miss beacons. Of course. Until we change 'everything' with 802.11s, scanning requires the radio to listen to each channel, one at a time, and hope to catch the BEACON for that channel. And not just a BEACON, but all the APs using a given channel. The standard does not allow for a radio to listen on all channels. 802.11n does change this a bit. 11s basically requires it (well for the mesh nodes at least). Often they will not report all the APs that are known to be around at a given time. Because they frequently have table limit sizes and can only record so many. So NetworkManager takes a composite of the last few scans as the scan list. Ouch. Not good for an actively moving device. A person walking can easily encounter a few APs for a given SSID on the same channel. Which one is really current? So when you do an ASSOCIATE on a given channel, which AP do you put in as the destination BSSID? 0.6.x also combines APs with the same SSID in the UI. As it should. People don't understand lots of APs in an SSID unless they install them! 0.7 splits them out at the NetworkManager layer, AH, so NetworkManager controls the ASSOCIATE, not the device driver? while the applet combines APs that are similar based on more than just SSID (SSID, security settings, band, channel). Channel/band? well other than b/g vs a vs n. And within an SSID you cannot have different security settings, per the spec. Perhaps the question may be how many APs can be handled and then those are turned into the SSID list (when more than one AP per SSID is found as in the case of some of these SSIDs). Are any of the APs hidden? If they are 'hidden' (which is a myth, read my paper on this), they are not of interest. Hidding an SSID is a waste of effort. And it seriously breaks AP roaming. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Any USB dongle support?
Dan Williams wrote: On Tue, 2008-03-11 at 07:50 -0400, Robert Moskowitz wrote: Anyone have experience with any USB dongles? Particularly ones that support WPA and use wext, not ndiswrapper? Anything zd1211 related should work pretty well. There are a _lot_ of those out there: http://www.linuxwireless.org/en/users/Drivers/zd1211rw/devices Oh, thank you I have been looking for this information for a long time browsing around and asking over on the Centos list. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How many SSIDs can be listed?
Yo Derek! Fancy meeting you here. I will look you up later. Derek Atkins wrote: There's another problem. The wireless extensions have a size limit for the scan results data. The buffer size is a u16, which means you're limited to 65535 bytes. The network manager buffer increase algorithm keeps doubling the buffer size, so you get 2k, 4k, 8k, 16k, 32k, 64k.. but 64k mod 2^16 == 0! Meaning you never actually get to try a full 64k buffer. A workaround to this issue is to change the NM code to max out at 65535 instead of 65536 or 10 (which is the current limit).. This is being a MAJOR problem to a bunch of us at the IETF because we can easily hear well over 100 APs most of the time. Please! We are use to seeing some of the worst-case work environments with too many APs and SSIDs for most code to cope with. Quoting Dan Williams [EMAIL PROTECTED]: On Mon, 2008-03-10 at 23:40 -0400, Robert Moskowitz wrote: Ver 0.6.4 in Centos 5.1 I am seeing 17 SSIDs in the current list. But I am not seeing one that I expected to see. And some of the listed SSIDs are 'stale'; that is they were visible in the part of the hotel I was in a couple minutes ago, but not in this part. So I guess a second question is how do you force a scan to produce a current SSID list? You don't force a scan. NetworkManager will periodically scan with a backoff algorithm; it will start at 20 seconds and back off to 2 minutes. APs are kept in the scan list for a maximum of 6 minutes before being culled. The problem is that wireless is hard, and sometimes cards/drivers miss beacons. Often they will not report all the APs that are known to be around at a given time. So NetworkManager takes a composite of the last few scans as the scan list. 0.6.x also combines APs with the same SSID in the UI. 0.7 splits them out at the NetworkManager layer, while the applet combines APs that are similar based on more than just SSID (SSID, security settings, band, channel). Perhaps the question may be how many APs can be handled and then those are turned into the SSID list (when more than one AP per SSID is found as in the case of some of these SSIDs). Are any of the APs hidden? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How many SSIDs can be listed?
Benoit Boissinot wrote: On Tue, Mar 11, 2008 at 2:08 PM, Dan Williams [EMAIL PROTECTED] wrote: 0.6.x also combines APs with the same SSID in the UI. 0.7 splits them out at the NetworkManager layer, while the applet combines APs that are similar based on more than just SSID (SSID, security settings, band, channel). Does that mean that with 0.7, you can choose to connect to a 802.11a network instead of a b/g network (with the same SSID and security settings) ? 'traditionally' you do that by limiting what channels you scan for the AP for an SSID. Here at the IETF and next week at the IEEE 802 meeting, the practice is to run different SSIDs for the different channel groups... How would the information be presented to the user in the UI? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Some questions
Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) I am plowing through the archives to find answers, but this is slow! No way that I can find to download them and import them into Thunderbird for better searching. So here goes: The nc2400 expects the OS to manage the card. There are no buttons to turn the radio on and off like on my old nc4010. Here I am on a plane with the radio on. Now I work with Boeing people (and work on 802.11 standards), so I have some inside knowledge of 802.11 and airplanes in flight, but that is not the point. The radio is eating power! I need that battery life! How can I turn off the radio. I tried iwconfig eth1 power on (to turn on power management), but the card is still happily scanning for APs, I think. I seem to recall a way with lmsensor to turn the LEDs on and off, but I think that only tied the LEDs into the reality of the operation of the card, not impacting the card at all. This notebook also has builtin ethernet. But shortly I will be at the IETF conference in Philly, and I want to run Firestarter with its NATing functions so I can plug another computer into the notebook to give it access through my one wireless connection. How can I get NetworkManager to leave the wired alone so Firestarter can manage it and run services like DHCP? My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. Now I notice that my AP is on channel 1, and I am picking up Oakland Wireless also on channel 1. This should NOT be causing the problem (I hope), but I add the data point. Actually I would like the option to tell NetworkManager to ignore Oakland Wireless when I am at home, just not when I am over at the local park, come springtime. When I used wpa_supplicant.conf, I could comment out various configs (or uncomment them) and reload the conf file at least. Ah the pains of a real nice integrated gui! I can't test anything at home until I get back on friday, but thought I would mention it now while I am venting. Plane is decending. Will be connected in a couple hours. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- wpa_supplicant
Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please keep replies on-list for everyone's benefit. oops. Just did a reply, am use that on most lists this replys to the list, not to the original sender... For this list, I have to do a reply to all, the edit the to/cc headers (using Thunderbird 1.5) Robert Moskowitz wrote: Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You might want to write a more specific subject next time, for everyone's benefit. Everyone who writes to the list has some questions. Robert Moskowitz wrote: Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) Incorrect. It probably best supports that card, but as far as I know, all Intel cards are supported. Really any card that has a driver supporting Wireless Extensions. Well I tried running: /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw3945 -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf And I get Unsupported driver 'ipw3945' So I read the man wpa_supplicant and find that I should say -D ipw and that only ipw2200 is supported. But I tried anyway: /usr/sbin/wpa_supplicant wpa_supplicant -B -D ipw -i eth1 -c /etc/wpa_supplicant/wpa_supplicant.conf And still got unsupported device. No, you want wext for basically all modern cards, not ipw. Those other drivers are really legacy holdovers, and hopefully will go away. OH. I missed this one. Well actually I recall that how I finally even got NetworkManager working was to edit /etc/sysconfig/wpa_supplicant to have: wpa_supplicant:DRIVERS=-Dwext I did not 'get' this previously! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- turnoff radio
Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: If you uncheck Wireless Enabled after right-clicking the applet, this should down the interface, which if the driver is correctly written (some are not), should turn off the wireless power to the card. Well it did not. The LED lights were happily flashing away, seemingly indicating something going out the card (like active scanning). If your card doesn't turn off the TX power when you run 'iwconfig eth1 down' then it's a driver bug. I will try this next. I only did an iwconfig eth1 power on to turn on power management. Obviously the wrong piece of magic. Mine used to do work this way and does no longer. I also use ipw3945, so I figured this was worth mentioning. It is somewhat disappointing, because it used to be my way of making sure there was no radio noise. Now if I really want to do that, it's the killswitch only. Kill is not an option. The whole point is to use the computer without any power draw by the wireless radio! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions -- WPA-PSK failure
The Holy ettlz wrote: Hmmm... My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. Does it authenticate OK when you take down the interface and restart NetworkManager? (I ask because I have a similar problem with one WAP that'll only authenticate once, *guaranteed*, but then never again; yet with another WAP backending to the same RADIUS server, it'll re-authenticate with no problems whenever I ask. See RH Bugzilla #434821.) I will have to wait until friday to test this (provided it fails then!), but for what it is worth, I could connect to the unsecured Oakland Wireless AP near my home, but not my WPA-PSK AP that was under my desk. I did not try taking the interface down. Should have. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Some questions
Dan Williams wrote: On Mon, 2008-03-10 at 08:19 -0400, Robert Moskowitz wrote: Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) As Ryan pointed out, NM will work with any card that properly supports wireless extensions. For RHEL5 (because the kernel is slightly older) that means ipw3945 (_not_ iwl3945), iwl4965 (as a tech preview only), airo, orinoco/hostap, atmel, ipw2100, ipw2200, ipw2915, zd1201, and bcm43xx. I am plowing through the archives to find answers, but this is slow! No way that I can find to download them and import them into Thunderbird for better searching. So here goes: The nc2400 expects the OS to manage the card. There are no buttons to turn the radio on and off like on my old nc4010. Here I am on a plane with the radio on. Now I work with Boeing people (and work on 802.11 standards), so I have some inside knowledge of 802.11 and airplanes in flight, but that is not the point. The radio is eating power! I need that battery life! How can I turn off the radio. I tried iwconfig eth1 power on (to turn on power management), but the card is still happily scanning for APs, I think. If you uncheck Wireless Enabled after right-clicking the applet, this should down the interface, which if the driver is correctly written (some are not), should turn off the wireless power to the card. If your card doesn't turn off the TX power when you run 'iwconfig eth1 down' then it's a driver bug. No such command as iwconfig eth1 down. You mean ifconfig eth1 down? I just went trough a 'farrowing' time with this. Everything wireless stopped. So I tried this. I could not get the wireless back up. Rebooted a number of times. No wireless at all! Then the LED came on and things started working after I did a dmesg command, which makes no sense that that turned the radio on. Could just have been a heat glitch. But in all this I learned that iwconfig eth1 down is not a valid command :) One of the joys of a meeting like the IETF is there are lots of APs visable with lots of clients around and all sorts of nonsense to make wireless go bump in the middle of a lookup. IEEE 802.11 meetings are just as bad! Interop has been worst (all those vendors running their own wireless demo network). If you want to test out your code, go to a big conference or trade show! I seem to recall a way with lmsensor to turn the LEDs on and off, but I think that only tied the LEDs into the reality of the operation of the card, not impacting the card at all. This notebook also has builtin ethernet. But shortly I will be at the IETF conference in Philly, and I want to run Firestarter with its NATing functions so I can plug another computer into the notebook to give it access through my one wireless connection. How can I get NetworkManager to leave the wired alone so Firestarter can manage it and run services like DHCP? Add the line NM_CONTROLLED=no to your /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface name your wired card is) and NetworkManager will ignore it. NM will still manage the default route then when wireless is enabled and active. My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. You probably have to switch the ipw3945 into monitor mode; if you google around you can probably find out how, but I think it includes inserting the ipw3945 module with the rtap_iface=1 argument, then 'ifconfig rtap0 up' and then using wireshark. Now I notice that my AP is on channel 1, and I am picking up Oakland Wireless also on channel 1. This should NOT be causing the problem (I hope), but I add the data point. Actually I would like the option to tell NetworkManager to ignore Oakland Wireless when I am at home, just not when I am over at the local park, come springtime. When I used wpa_supplicant.conf, I could comment out various configs (or uncomment them) and reload the conf file at least. Ah the pains of a real nice integrated gui! NetworkManager will attempt to connect to the network you last used (via a timestamp of the last
Re: Some questions -- more radio misshaps
I am going to have to check my bios settings again. Almost like they changed Robert Moskowitz wrote: Dan Williams wrote: On Mon, 2008-03-10 at 08:19 -0400, Robert Moskowitz wrote: Hello, I am new here. Running 0.6.4 in Centos 5.1 on an HP nc2400 notebook with the Intel ipw3945 dkms code from rpmforge. I just switched my operation over the this nc2400 from my old nc4010 which had an Atheros card using the madwifi dkms code from rpmforge and I did everything via wpa_supplicant.conf (and the wpa_cli program!). So with this install, I could not get the wpa_supplicant working. Seems like it only supports the ipw2200 card? And I found NetworkManager; good job! So far :) As Ryan pointed out, NM will work with any card that properly supports wireless extensions. For RHEL5 (because the kernel is slightly older) that means ipw3945 (_not_ iwl3945), iwl4965 (as a tech preview only), airo, orinoco/hostap, atmel, ipw2100, ipw2200, ipw2915, zd1201, and bcm43xx. I am plowing through the archives to find answers, but this is slow! No way that I can find to download them and import them into Thunderbird for better searching. So here goes: The nc2400 expects the OS to manage the card. There are no buttons to turn the radio on and off like on my old nc4010. Here I am on a plane with the radio on. Now I work with Boeing people (and work on 802.11 standards), so I have some inside knowledge of 802.11 and airplanes in flight, but that is not the point. The radio is eating power! I need that battery life! How can I turn off the radio. I tried iwconfig eth1 power on (to turn on power management), but the card is still happily scanning for APs, I think. If you uncheck Wireless Enabled after right-clicking the applet, this should down the interface, which if the driver is correctly written (some are not), should turn off the wireless power to the card. If your card doesn't turn off the TX power when you run 'iwconfig eth1 down' then it's a driver bug. No such command as iwconfig eth1 down. You mean ifconfig eth1 down? I just went trough a 'farrowing' time with this. Everything wireless stopped. So I tried this. This time when things stopped working I looked first before typing. Radio went off. I had unplugged the notebook and closed the unit. But I have done that earlier today. I plugged back in and while I was doing lsmod and dmesg commands, the radio came back on. More likely not related, just with power it 'woke up'? ARGH. I could not get the wireless back up. Rebooted a number of times. No wireless at all! Then the LED came on and things started working after I did a dmesg command, which makes no sense that that turned the radio on. Could just have been a heat glitch. But in all this I learned that iwconfig eth1 down is not a valid command :) One of the joys of a meeting like the IETF is there are lots of APs visable with lots of clients around and all sorts of nonsense to make wireless go bump in the middle of a lookup. IEEE 802.11 meetings are just as bad! Interop has been worst (all those vendors running their own wireless demo network). If you want to test out your code, go to a big conference or trade show! I seem to recall a way with lmsensor to turn the LEDs on and off, but I think that only tied the LEDs into the reality of the operation of the card, not impacting the card at all. This notebook also has builtin ethernet. But shortly I will be at the IETF conference in Philly, and I want to run Firestarter with its NATing functions so I can plug another computer into the notebook to give it access through my one wireless connection. How can I get NetworkManager to leave the wired alone so Firestarter can manage it and run services like DHCP? Add the line NM_CONTROLLED=no to your /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever interface name your wired card is) and NetworkManager will ignore it. NM will still manage the default route then when wireless is enabled and active. My home network runs WPA-PSK (yeah, I know the risks, I wrote the attack paper, but my Radius server is currently down). I frequently run into the situation where NetworkManager is not succeeding in authenticating to the AP. I have no sniffing data; I would like to see some packets, but Wireshark does not show interface eth1 (the wireless one). I end up having to reboot to get wireless working, or switch to wired. You probably have to switch the ipw3945 into monitor mode; if you google around you can probably find out how, but I think it includes inserting the ipw3945 module with the rtap_iface=1 argument, then 'ifconfig rtap0 up' and then using wireshark. Now I notice that my AP is on channel 1, and I am picking up Oakland Wireless also on channel 1
How many SSIDs can be listed?
Ver 0.6.4 in Centos 5.1 I am seeing 17 SSIDs in the current list. But I am not seeing one that I expected to see. And some of the listed SSIDs are 'stale'; that is they were visible in the part of the hotel I was in a couple minutes ago, but not in this part. So I guess a second question is how do you force a scan to produce a current SSID list? Perhaps the question may be how many APs can be handled and then those are turned into the SSID list (when more than one AP per SSID is found as in the case of some of these SSIDs). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
