My Laptop
I wanted to see if I could get some advise on what to do concerning wireless on my laptop. I have a Dell Inspiron B130 with a Dell wireless card, 1370 WLAN, mini-PC card. It works fine on windows as does a Linksys WUSB54G. I have Ubuntu loaded right now in a dual boot, that one of my geek friends worked on and am not sure if it will ever work right again. I have been unable to get get any drivers that will load or work with Ubuntu and network manager at all. I was using Fedora 6, but had problems with that. I am fairly new to Linux as you can guess. Daniel Fetchinson (I believe) wrote that he installed Fedora 8 and network manager was working just fine and he connected to his wireless network. I was thinking seriously of going back to Fedora but unable to find a way to get a copy were we are staying for the winter in Florida. Not sure if my Dell (Broadcom card I believe) will work the same way with Fedora 8. Wish I knew more about this stuff. Linux out performs Windows in all ways, but right now I am stuck using windows while I am down down here for 5 months. Any suggestions on what I might be able to do would be greatly appreciated. If I could get this thing to work I could drop windows completely. Thanks so much Herb Taylor ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager-MobileBroadband and network choossing
Hi, from http://fedoraproject.org/wiki/Features/NetworkManager-MobileBroadband : # scanning for available cellular networks (GSM only) # selection of a cellular network (GSM only) # show signal strength of currently connected cellular network Which strikes me as odd. GSM networks aren't like Wi-Fi, user very very seldom has to choose one. In fact, choosing GSM network is very corner case, only close to country borders. In this situation foreign GSM network can be stronger (signal strenth wise) than local one, and user has to manually switch to one of national networks to avoid roaming charges. It at least was true some 10 years ago, I don't know how it's handled now and how data connections are billed. In short, indicator for current strongest available GSM signal would be nice. Displaying all available networks won't. And would unnecessaty clutter interface. I'm currently using GPRS via Bluetooth via Nokia on Ubuntu. In future I'm planning either replacing EVDO card in my Thinkpad by some approved UMTS card, or using PCMCIA or USB HSDPA modem. (please keep me CC'ed on replies, I'm not subscribed). -- Tomasz TorczFuneral in the morning, IDE hacking [EMAIL PROTECTED]in the afternoon and evening. - Alan Cox pgpPdYn5vYoEu.pgp Description: PGP signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager-MobileBroadband and network choossing
On Wed, 2007-12-12 at 15:09 +0100, Tomasz Torcz wrote: Hi, from http://fedoraproject.org/wiki/Features/NetworkManager-MobileBroadband : # scanning for available cellular networks (GSM only) # selection of a cellular network (GSM only) # show signal strength of currently connected cellular network Which strikes me as odd. GSM networks aren't like Wi-Fi, user very very seldom has to choose one. In fact, choosing GSM network is very corner case, only close to country borders. In this situation foreign GSM Not really; in the US for example T-Mobile has coverage on the coasts, but not much in the middle. There are plenty of times that when roaming even in the US I've needed to pick which carrier I wanted to use on my phone. You can certainly automatically pick one that will probably be a good choice, but when dealing with a system that has the potential to bill you shedloads of $$$ if you make the wrong choice, we have to err on the side of caution. You'll definitely have to pick the carrier-of-choice when setting up the GSM connection, but you probably won't need to change that much later on. That said, NM won't be scanning for GSM networks like it scans for wifi networks. I don't think anyone is 100% sure how it's going to work UI-wise, but GSM scanning certainly takes a really long amount of time and isn't something that can be done in-band. network can be stronger (signal strenth wise) than local one, and user has to manually switch to one of national networks to avoid roaming charges. It at least was true some 10 years ago, I don't know how it's handled now and how data connections are billed. That's the problem; there's no way to know the billing, so we have to ensure that the GSM part is 100% under the user's control. We may be able to offer the user roaming guards or something like that to have NM kill the connection if the home network is no longer available. In short, indicator for current strongest available GSM signal would be nice. Displaying all available networks won't. And would unnecessaty clutter interface. Definitely agreed. There won't be a GSM network list like there is a list of WiFi APs. You'll have to pick a network when setting up the connection for now if that can't be determined from your SIM directly. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Tue, 2007-12-11 at 17:10 -0500, Dan Williams wrote: WEP ASCII passphrases are standardized, WEP104 passphrases are de-facto standard (some implemented hashing for 40-bit WEP keys, but that's not really standardized at all), and Apple uses a completely different hashing scheme for it's password. So no, WEP doesn't have a standardized passphrase-key hashing scheme. That's why you get 3 choices. WPA fixed this, where there is a standard for hashing a passphrase into a key, _plus_ they made it easy to differentiate a passphrase and a hex key, which is great because you can't do this with WEP, leading to people using what _look_ like hex keys as actual WEP passphrases. Dan I am sure you think the above explanation is clear but it is not to me. From what I have read the WEP pasphrase is the encryption key. and an ASCII passphrase is just a hex passphrase expressed in ASCII characters, What is the difference between a passphrase and a hex key and where does hashing come in for WEP? -- === You know that feeling when you're leaning back on a stool and it starts to tip over? Well, that's how I feel all the time. -- Steven Wright === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Saving other Wireless network
Is there anyway to save the configuration you give nm-applet when you connect to an other wireless network? It's great to be able to connect, but I don't like having to enter my password and everything. -Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Saving other Wireless network
Quoting Peter Davoust [EMAIL PROTECTED]: Is there anyway to save the configuration you give nm-applet when you connect to an other wireless network? It's great to be able to connect, but I don't like having to enter my password and everything. Once it successfully connects it should remember those settings in gconf and attempt to connect the next time it sees that AP. -Peter -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Saving other Wireless network
well, it should automatically save working configuration and automatically connect to the network when within reach. this would not be the case with networks that don't broadcast their name. on these networks you'd either have to wait some time before nm-applet gets them or try reconnecting with the manual method. 2007/12/12, Peter Davoust [EMAIL PROTECTED]: Is there anyway to save the configuration you give nm-applet when you connect to an other wireless network? It's great to be able to connect, but I don't like having to enter my password and everything. -Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- dott. ing. beso ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: My Laptop
Herbert Taylor wrote: I wanted to see if I could get some advise on what to do concerning wireless on my laptop. I have a Dell Inspiron B130 with a Dell wireless card, 1370 WLAN, mini-PC card. It works fine on windows as does a Linksys WUSB54G. I have Ubuntu loaded right now in a dual boot, that one of my geek friends worked on and am not sure if it will ever work right again. I have been unable to get get any drivers that will load or work with Ubuntu and network manager at all. I was using Fedora 6, but had problems with that. I am fairly new to Linux as you can guess. Daniel Fetchinson (I believe) wrote that he installed Fedora 8 and network manager was working just fine and he connected to his wireless network. I was thinking seriously of going back to Fedora but unable to find a way to get a copy were we are staying for the winter in Florida. Not sure if my Dell (Broadcom card I believe) will work the same way with Fedora 8. Wish I knew more about this stuff. Linux out performs Windows in all ways, but right now I am stuck using windows while I am down down here for 5 months. Any suggestions on what I might be able to do would be greatly appreciated. If I could get this thing to work I could drop windows completely. The Dell 1370 is a BCM4318 and will work with the driver named bcm43xx in kernels 2.6.21 and later. Kernel 2.6.24-rc5 also includes a better driver named b43. One problem you will have with Ubuntu is that they configure their kernels without enabling the debug messages for bcm43xx, which greatly complicates getting started. To use bcm43xx or b43, you will have to install firmware as the Broadcom copyright prevents distribution of this firmware. Consult http://linuxwireless.org/en/users/Drivers/b43#devicefirmware for instructions on downloading _AND_ installing the correct firmware (version 3 for bcm43xx, version 4 for b43). In any future postings regarding this issue, please include the output of the 'uname -r' command, and the output of 'dmesg | grep bcm43xx' or 'dmesg | grep b43'. The flavor you use will be determined by the driver you are trying to use. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Wed, 2007-12-12 at 09:28 -0600, Aaron Konstam wrote: On Tue, 2007-12-11 at 17:10 -0500, Dan Williams wrote: WEP ASCII passphrases are standardized, WEP104 passphrases are de-facto standard (some implemented hashing for 40-bit WEP keys, but that's not really standardized at all), and Apple uses a completely different hashing scheme for it's password. So no, WEP doesn't have a standardized passphrase-key hashing scheme. That's why you get 3 choices. WPA fixed this, where there is a standard for hashing a passphrase into a key, _plus_ they made it easy to differentiate a passphrase and a hex key, which is great because you can't do this with WEP, leading to people using what _look_ like hex keys as actual WEP passphrases. Dan I am sure you think the above explanation is clear but it is not to me. From what I have read the WEP pasphrase is the encryption key. and an ASCII passphrase is just a hex passphrase expressed in ASCII characters, What is the difference between a passphrase and a hex key and where does hashing come in for WEP? The standard WEP passphrase is a string up to 64 characters in length. If less than 64 bytes, it gets repeated into a 64 byte buffer, which them gets hashed with MD5. The digest resulting from the MD5 hash is then used as the actual WEP key that is given to the driver. user input:abcdefghijklm 1) repeat 'abcdefghijklm' over and over until 64 bytes are filled 2) hash the 64 bytes using MD5 wep key (hex): f343dcef2a6ea4ce5d63dabc45 A WEP ASCII passphrase is a 5 or 13 character ASCII string. To derive the actual WEP key, the ASCII values of the string are used directly for the WEP key like so: user input:abcdefghijklm wep key (hex): 6162636465666768696a6b6c6d a = 61, b = 62, c = 63, d = 64, etc. So the problem with ASCII passphrases is that the _range_ of values you can enter is smaller and limited to the printable ASCII range, which is roughly 0x20 - 0x7E. Note that in the standard WEP passphrase example above, the passphrase contains the byte 0xF3 at the start, which is not ASCII and therefore can't be contained in an ASCII passphrase. The _best_ way to get a secure WEP key (not that WEP is secure _at all_) is to have a random number generator generate the key for you. Don't use passphrases. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp using NM
On Dec 6, 2007 12:27 AM, Dan Williams [EMAIL PROTECTED] wrote: On Wed, 2007-12-05 at 18:38 +, Jon Escombe wrote: Tambet Ingo wrote: On Dec 4, 2007 4:17 PM, Jon Escombe [EMAIL PROTECTED] wrote: Good stuff, got connected first time ;) Only issues were that it didn't set up resolv.conf, and also added three entries to the Hi, 1.Is there any list of adapters working with current code ? 2.I am trying to to do ppp over RS-232 / USB /... (between 2 PCs ) using NM. any changes needed in NM for this purpose ? regards Vikram applet menu (as the card presents three ports). Both of these issues should be fixed in the SVN now. Tambet Confirmed, thanks! Latest bits are in http://koji.fedoraproject.org/koji/taskinfo?taskID=276538 too, which should get pushed out as an update. I haven't disabled the PPP functionality for F8 updates because you still need the .fdi file to enable the 3G cards for now. Dan ___ 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
Re: ppp using NM
On Wed, 2007-12-12 at 23:13 +0530, vikram b wrote: On Dec 6, 2007 12:27 AM, Dan Williams [EMAIL PROTECTED] wrote: On Wed, 2007-12-05 at 18:38 +, Jon Escombe wrote: Tambet Ingo wrote: On Dec 4, 2007 4:17 PM, Jon Escombe [EMAIL PROTECTED] wrote: Good stuff, got connected first time ;) Only issues were that it didn't set up resolv.conf, and also added three entries to the Hi, 1.Is there any list of adapters working with current code ? Sierra Wireless 860, Sierra Wireless 875, and whatever Huwei card Tambet is using. 2.I am trying to to do ppp over RS-232 / USB /... (between 2 PCs ) using NM. any changes needed in NM for this purpose ? Yes; there's a generic serial device class but that device isn't activate-able at this time. Right now all modem-tagged devices are treated as GSM devices because there isn't a way with HAL to differentiate the different serial devices. Dan regards Vikram applet menu (as the card presents three ports). Both of these issues should be fixed in the SVN now. Tambet Confirmed, thanks! Latest bits are in http://koji.fedoraproject.org/koji/taskinfo?taskID=276538 too, which should get pushed out as an update. I haven't disabled the PPP functionality for F8 updates because you still need the .fdi file to enable the 3G cards for now. Dan ___ 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
Re: NetworkManager connects to DHCP AP but dhclient doesn't
Kamran Riaz Khan [EMAIL PROTECTED] writes: Any ideas about what I'm doing wrong? Does dmesg have any interesting output? -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 0.7 this year?
On Wed, 2007-12-12 at 15:17 -0500, Stuart D. Gathman wrote: On Tue, 11 Dec 2007, Bjoern Martensen wrote: how are the chances we might get our (desperately waiting) hands on NM 0.7 by the end of this year? maybe a christmas present? ;) I am running Fedora Core 8, and it has NM 0.7. Lo and behold, WPA works with NM! (It didn't work with NM 0.6 on EL5). So download the werewolf and enjoy. i'm pretty happy with arch linux, thanks ;) btw, fedora 8 uses a pre-release, not 0.7 final. if multiple active devices are already implemented, i might try building packages from svn. can anyone tell me if this works already? greets, björn signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.7 can't connect to WPA network
I built NM 0.7 from SVN (current as of this morning) and when I try to connect to a WPA network, I get these messages. Unfortunately, I'm not certain where to even begin looking to debug this, but hopefully some info about the network itself is a start. The SSID contains only alphanumeric characters, but the passphrase contains non-alphanumeric characters, including # and !. It's WPA/TKIP. The same thing also happens on a WPA-Enterprise network using TTLS/PAP. In this case, both the SSID and passphrase contain non-alphanumeric characters, including ! and @. I'm running Ubuntu 7.10 and the driver is madwifi 0.9.3. Both these networks worked perfectly using NM 0.6.5. Any pointers on where to look to help debug this or suggestions to get this working would be greatly appreciated. [EMAIL PROTECTED]:~/Code/network-manager-applet]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Bringing up device ath0 NetworkManager: info Deactivating device ath0. NetworkManager: info (eth0) supplicant interface is now in state 2 (from 1). NetworkManager: info (ath0) supplicant interface is now in state 2 (from 1). NetworkManager: info User request for activation of ath0. NetworkManager: info Activating device ath0 NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info Activation (ath0/wireless): access point 'Auto GamerCorner' has security, but secrets are required. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet.c.3297 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'.. NetworkManager: info Activation (ath0) failed for access point (GamerCorner) NetworkManager: info Marking connection 'Auto GamerCorner' invalid. NetworkManager: info Activation (ath0) failed. NetworkManager: info Deactivating device ath0. --- [EMAIL PROTECTED]:~/Code/network-manager-applet]$ nm-applet --sm-disable ** (nm-applet:4949): WARNING **: No connections defined ** (nm-applet:4949): WARNING **: No networks found in the configuration database ** Message: info No keyring secrets found for Auto GamerCorner/802-11-wireless-security; ask the user ** Message: info Got setting name: 802-11-wireless-security ** (nm-applet:4949): CRITICAL **: nm_setting_to_hash: assertion `NM_IS_SETTING (setting)' failed ** (nm-applet:4949): WARNING **: applet.c.3295 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'. -- Joel Goguen http://jgoguen.ca/ The goal of Computer Science is to build something that will last at least until we've finished building it. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
