Re: NetworkManager Cannot Connect to Wireless Network
On Thursday 15 July 2010 10:26:05 John Frankish wrote: > > -Original Message- > > From: Lisi [mailto:lisi.re...@gmail.com] > > Sent: Thursday, 15 July, 2010 13:13 > > To: debian-user@lists.debian.org > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > > > > Oh dear!! > > > > Setting my granddaughter's laptop to talk to her school's wireless > > network was a nightmare, and I never did find out why. It connected to > > other wireless routers without a problem. I tried 3 - or was it 4? - > > different distros, I tried 3 different wireless cards, I asked for help > > from someone more knowledgable and experienced than I, I tore my hair > > out. Eventually, with Open Suse 11.00, I was getting some sort of > > response, but still not an actual connection. In the end, the one person > > in the school IT department who knew anything about Linux took the > > almost-connecting Open Suse install off to the school IT lab, and came > > back with it working, having worked thro' several wireless cards that > > they had lying around, and found one that worked, which they donated to > > her. He may also have done some tweaking, > > > > My laptop with Lenny and that same card does not connect at her school > > - but connects without hesitation anywhere else. > > > > I believe the American expression is "go figure!". You have my > > sympathy, but I am for now out of ideas. > > > > I assume that you have checked the driver? > > > > Lisi > > Thanks for the suggestions - since things work "the old fashioned way" with > /etc/network/interfaces, I presume the driver is good - I'll probably leave > Networkmanager uninstalled, uninstall wicd and use "the old fashioned way" > for Both wired and wireless connections That sounds like a very good idea! I confess that I had forgotten that the old fashioned way worked for you. If it ain't broke don't fix it. ;-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201007151153.38613.lisi.re...@gmail.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: Lisi [mailto:lisi.re...@gmail.com] > Sent: Thursday, 15 July, 2010 13:13 > To: debian-user@lists.debian.org > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > Oh dear!! > > Setting my granddaughter's laptop to talk to her school's wireless > network was a nightmare, and I never did find out why. It connected to other > wireless routers without a problem. I tried 3 - or was it 4? - different > distros, I tried 3 different wireless cards, I asked for help from someone > more > knowledgable and experienced than I, I tore my hair out. Eventually, > with Open Suse 11.00, I was getting some sort of response, but still not an > actual connection. In the end, the one person in the school IT department who > knew anything about Linux took the almost-connecting Open Suse install off > to the school IT lab, and came back with it working, having worked thro' > several wireless cards that they had lying around, and found one that worked, > which they donated to her. He may also have done some tweaking, > > My laptop with Lenny and that same card does not connect at her school > - but connects without hesitation anywhere else. > > I believe the American expression is "go figure!". You have my > sympathy, but I am for now out of ideas. > > I assume that you have checked the driver? > > Lisi > Thanks for the suggestions - since things work "the old fashioned way" with /etc/network/interfaces, I presume the driver is good - I'll probably leave Networkmanager uninstalled, uninstall wicd and use "the old fashioned way" for Both wired and wireless connections -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e033400d...@nl0105exc01v01.eur.slb.com
Re: NetworkManager Cannot Connect to Wireless Network
On Thursday 15 July 2010 08:53:03 John Frankish wrote: > > -Original Message- > > From: Lisi [mailto:lisi.re...@gmail.com] > > Sent: Thursday, 15 July, 2010 11:40 > > To: debian-user@lists.debian.org > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > > > On Thursday 15 July 2010 05:08:13 John Frankish wrote: > > > > -Original Message- > > > > From: Lisi [mailto:lisi.re...@gmail.com] > > > > Sent: Tuesday, 13 July, 2010 18:46 > > > > To: debian-user@lists.debian.org > > > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > > > > > > > Why not try uninstalling Network Mangler and using someother method - > > > > e.g. > > > > WICD (my own preferred solution), /etc/network/interfaces or some > > > > other manager? > > > > > > > > Lisi > > > > > > I tried a few more things: > > > > > > 1. NetworkManager > > > I get the errors below and rmmod/modprobe ipw2100 does not help. Since > > > only NetworkManager and not wicd nor "the old way" produces these error > > > messages, I presume this is a bug. > > > > > > $ dmesg | grep ipw2100 > > > [6.807473] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, > > > git-1.2.2 [6.807478] ipw2100: Copyright(c) 2003-2006 Intel Corporation > > > [6.829420] ipw2100 :01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 > > > (level, low) -> IRQ 11 > > > [6.830090] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection > > > [6.830117] ipw2100 :01:0a.0: firmware: requesting ipw2100-1.3.fw > > > [39.906727] ipw2100: Fatal interrupt. Scheduling firmware restart. > > > [78.668486] ipw2100: Fatal interrupt. Scheduling firmware restart. > > > [130.105385] ipw2100: Fatal interrupt. Scheduling firmware restart. > > > > > > 2. wicd > > > All attempts to connect to the wireless network result in an error > > > message "bad password" There are no errors in dmesg > > > > > > 3. This works without errors in dmesg and wcid recognizes the link is > > > connected > > > > > > $ cat /etc/network/interfaces > > > ... > > > # wireless > > > allow-hotplug eth2 > > > iface eth2 inet dhcp > > > wireless-essid myessid > > > wireless-key 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB > > > wireless-keymode restricted > > > > When trying WICD did you: > > > > 1. Uninstall Network Mangler > > > > 2. Comment out the wireless entries in /etc/network/interfaces > > > > 3. Reboot > > > > 4. Run WICD > > > > If you have not (and you need to have done all of them), I should try > > it now. > > > > It is possible to stop and restart the network without rebooting, but I > > feel > > that this way makes sure that everyting has to restart. Others MMV. > > > > Lisi > > 1. Yes, 2. Yes, 3. Yes, 4. Yes :) Oh dear!! Setting my granddaughter's laptop to talk to her school's wireless network was a nightmare, and I never did find out why. It connected to other wireless routers without a problem. I tried 3 - or was it 4? - different distros, I tried 3 different wireless cards, I asked for help from someone more knowledgable and experienced than I, I tore my hair out. Eventually, with Open Suse 11.00, I was getting some sort of response, but still not an actual connection. In the end, the one person in the school IT department who knew anything about Linux took the almost-connecting Open Suse install off to the school IT lab, and came back with it working, having worked thro' several wireless cards that they had lying around, and found one that worked, which they donated to her. He may also have done some tweaking, My laptop with Lenny and that same card does not connect at her school - but connects without hesitation anywhere else. I believe the American expression is "go figure!". You have my sympathy, but I am for now out of ideas. I assume that you have checked the driver? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201007151012.49390.lisi.re...@gmail.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: Lisi [mailto:lisi.re...@gmail.com] > Sent: Thursday, 15 July, 2010 11:40 > To: debian-user@lists.debian.org > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > On Thursday 15 July 2010 05:08:13 John Frankish wrote: > > > -Original Message- > > > From: Lisi [mailto:lisi.re...@gmail.com] > > > Sent: Tuesday, 13 July, 2010 18:46 > > > To: debian-user@lists.debian.org > > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > > > Why not try uninstalling Network Mangler and using someother method - > > > e.g. > > > WICD (my own preferred solution), /etc/network/interfaces or some other > > > manager? > > > > > > Lisi > > > > I tried a few more things: > > > > 1. NetworkManager > > I get the errors below and rmmod/modprobe ipw2100 does not help. Since only > > NetworkManager and not wicd nor "the old way" produces these error > > messages, I presume this is a bug. > > > > $ dmesg | grep ipw2100 > > [6.807473] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 > > [6.807478] ipw2100: Copyright(c) 2003-2006 Intel Corporation > > [6.829420] ipw2100 :01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 > > (level, low) -> IRQ 11 > > [6.830090] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection > > [6.830117] ipw2100 :01:0a.0: firmware: requesting ipw2100-1.3.fw > > [39.906727] ipw2100: Fatal interrupt. Scheduling firmware restart. > > [78.668486] ipw2100: Fatal interrupt. Scheduling firmware restart. > > [130.105385] ipw2100: Fatal interrupt. Scheduling firmware restart. > > > > 2. wicd > > All attempts to connect to the wireless network result in an error message > > "bad password" There are no errors in dmesg > > > > 3. This works without errors in dmesg and wcid recognizes the link is > > connected > > > > $ cat /etc/network/interfaces > > ... > > # wireless > > allow-hotplug eth2 > > iface eth2 inet dhcp > > wireless-essid myessid > > wireless-key 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB > > wireless-keymode restricted > > When trying WICD did you: > > 1. Uninstall Network Mangler > > 2. Comment out the wireless entries in /etc/network/interfaces > > 3. Reboot > > 4. Run WICD > > If you have not (and you need to have done all of them), I should try > it now. > > It is possible to stop and restart the network without rebooting, but I > feel > that this way makes sure that everyting has to restart. Others MMV. > > Lisi > 1. Yes, 2. Yes, 3. Yes, 4. Yes :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e033400d...@nl0105exc01v01.eur.slb.com
Re: NetworkManager Cannot Connect to Wireless Network
On Thursday 15 July 2010 05:08:13 John Frankish wrote: > > -Original Message- > > From: Lisi [mailto:lisi.re...@gmail.com] > > Sent: Tuesday, 13 July, 2010 18:46 > > To: debian-user@lists.debian.org > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > Why not try uninstalling Network Mangler and using someother method - > > e.g. > > WICD (my own preferred solution), /etc/network/interfaces or some other > > manager? > > > > Lisi > > I tried a few more things: > > 1. NetworkManager > I get the errors below and rmmod/modprobe ipw2100 does not help. Since only > NetworkManager and not wicd nor "the old way" produces these error > messages, I presume this is a bug. > > $ dmesg | grep ipw2100 > [6.807473] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, > git-1.2.2 [6.807478] ipw2100: Copyright(c) 2003-2006 Intel Corporation > [6.829420] ipw2100 :01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 > (level, low) -> IRQ 11 [6.830090] ipw2100: Detected Intel PRO/Wireless > 2100 Network Connection [6.830117] ipw2100 :01:0a.0: firmware: > requesting ipw2100-1.3.fw [ 39.906727] ipw2100: Fatal interrupt. > Scheduling firmware restart. [ 78.668486] ipw2100: Fatal interrupt. > Scheduling firmware restart. [ 130.105385] ipw2100: Fatal interrupt. > Scheduling firmware restart. > > 2. wicd > All attempts to connect to the wireless network result in an error message > "bad password" There are no errors in dmesg > > 3. This works without errors in dmesg and wcid recognizes the link is > connected > > $ cat /etc/network/interfaces > ... > # wireless > allow-hotplug eth2 > iface eth2 inet dhcp > wireless-essid myessid > wireless-key 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB > wireless-keymode restricted When trying WICD did you: 1. Uninstall Network Mangler 2. Comment out the wireless entries in /etc/network/interfaces 3. Reboot 4. Run WICD If you have not (and you need to have done all of them), I should try it now. It is possible to stop and restart the network without rebooting, but I feel that this way makes sure that everyting has to restart. Others MMV. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201007150840.16087.lisi.re...@gmail.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: Lisi [mailto:lisi.re...@gmail.com] > Sent: Tuesday, 13 July, 2010 18:46 > To: debian-user@lists.debian.org > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > On Tuesday 13 July 2010 08:41:58 John Frankish wrote: > > No, I have not tried turning WEP off, but on the same machine booted in > > tinycorelinux I can connect, albeit after a couple of attempts and not > > using NetworkManager. > > > > Also on three other laptops (none of which use the same hardware) and an > > iPhone there are no problems connecting. > > > > I'll try rmmod/modprobe ipw2100 (google suggests this might work) and if > > not, I guess it's ndiswrapper... > > Why not try uninstalling Network Mangler and using someother method - > e.g. > WICD (my own preferred solution), /etc/network/interfaces or some other > manager? > > Lisi > I tried a few more things: 1. NetworkManager I get the errors below and rmmod/modprobe ipw2100 does not help. Since only NetworkManager and not wicd nor "the old way" produces these error messages, I presume this is a bug. $ dmesg | grep ipw2100 [6.807473] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [6.807478] ipw2100: Copyright(c) 2003-2006 Intel Corporation [6.829420] ipw2100 :01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 (level, low) -> IRQ 11 [6.830090] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [6.830117] ipw2100 :01:0a.0: firmware: requesting ipw2100-1.3.fw [ 39.906727] ipw2100: Fatal interrupt. Scheduling firmware restart. [ 78.668486] ipw2100: Fatal interrupt. Scheduling firmware restart. [ 130.105385] ipw2100: Fatal interrupt. Scheduling firmware restart. 2. wicd All attempts to connect to the wireless network result in an error message "bad password" There are no errors in dmesg 3. This works without errors in dmesg and wcid recognizes the link is connected $ cat /etc/network/interfaces ... # wireless allow-hotplug eth2 iface eth2 inet dhcp wireless-essid myessid wireless-key 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB wireless-keymode restricted -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333fa1...@nl0105exc01v01.eur.slb.com
Re: NetworkManager Cannot Connect to Wireless Network
Why not try uninstalling Network Mangler and using someother method - e.g. WICD (my own preferred solution), /etc/network/interfaces or some other manager? Lisi +1 for WICD With NetworkManager I faced some failures to connect to the (public so no WEP or WAP) Wifi in my favorite bar : few times per month the Wifi was correcly detected but NetworkManager was simply unable to connect to it. Now with WICD it simply works 24/7. Bye, Bruno -- Linux Counter #353844 http://counter.li.org/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100714110602.103697gutcf3c...@webmail.costacurta.org
Re: NetworkManager Cannot Connect to Wireless Network
On Tue, Jul 13, 2010 at 7:45 AM, Lisi wrote: > > Why not try uninstalling Network Mangler and using someother method - e.g. > WICD (my own preferred solution), /etc/network/interfaces or some other > manager? > > Lisi > +1. WICD solved a similar problem on my girlfriend's laptop. NM couldn't connect but WICD had no issues connecting.
Re: NetworkManager Cannot Connect to Wireless Network
On Tuesday 13 July 2010 08:41:58 John Frankish wrote: > No, I have not tried turning WEP off, but on the same machine booted in > tinycorelinux I can connect, albeit after a couple of attempts and not > using NetworkManager. > > Also on three other laptops (none of which use the same hardware) and an > iPhone there are no problems connecting. > > I'll try rmmod/modprobe ipw2100 (google suggests this might work) and if > not, I guess it's ndiswrapper... Why not try uninstalling Network Mangler and using someother method - e.g. WICD (my own preferred solution), /etc/network/interfaces or some other manager? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201007131545.30863.lisi.re...@gmail.com
Re: NetworkManager Cannot Connect to Wireless Network
On Tue, Jul 13, 2010 at 3:41 AM, John Frankish wrote: > > >> -Original Message- >> From: John [mailto:nesre...@gmail.com] >> Sent: Tuesday, 13 July, 2010 11:33 >> To: debian-user@lists.debian.org >> Subject: Re: NetworkManager Cannot Connect to Wireless Network >> >> On Tue, Jul 13, 2010 at 3:14 AM, John Frankish >> wrote: >> > >> > >> > Hmm - now I see the following in dmesg: >> > >> > ipw2100: Fatal interrupt. Scheduling firmware restart >> > >> > There are many, many hits for this in google, but no solutions... >> > >> >> I assume you have gotten things working with WEP turned off? Go the >> the router and disable WEP, and similarly on your computer select "no >> encryption", and make sure everything works. I can't remember if you >> said you had done that or if somebody else mentioned this, but just to >> be sure, it's worth checking that things work properly in the most >> simple setup. >> >> John >> > No, I have not tried turning WEP off, but on the same machine booted in > tinycorelinux I can connect, albeit after a couple of attempts and not using > NetworkManager. > > Also on three other laptops (none of which use the same hardware) and an > iPhone there are no problems connecting. > > I'll try rmmod/modprobe ipw2100 (google suggests this might work) and if not, > I guess it's ndiswrapper... This last bit suggests that you are looking at hardware and compatibility. Someone else on this thread has suggested NetworkManager does not have a great reputation. That gives you lots of variables (aka "suspects"). I have a Mepis 8 live CD that I sometimes use for testing (even if it's a plain Debian system). Mepis 8 is basically Lenny, but Mepis has (and has had for quite a long time) a very effective network control package. If in doubt about an encrypted wifi connection, I find that throwing in this live CD can at least give me a clue about hardware and compatibility. It accepts the WEP key as either Hex or Ascii (automatically translates to Hex), which can be handy. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktincefkerjwdciklvxyznatdua6vxedrrsoqa...@mail.gmail.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: John [mailto:nesre...@gmail.com] > Sent: Tuesday, 13 July, 2010 11:33 > To: debian-user@lists.debian.org > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > On Tue, Jul 13, 2010 at 3:14 AM, John Frankish > wrote: > > > > > > Hmm - now I see the following in dmesg: > > > > ipw2100: Fatal interrupt. Scheduling firmware restart > > > > There are many, many hits for this in google, but no solutions... > > > > I assume you have gotten things working with WEP turned off? Go the > the router and disable WEP, and similarly on your computer select "no > encryption", and make sure everything works. I can't remember if you > said you had done that or if somebody else mentioned this, but just to > be sure, it's worth checking that things work properly in the most > simple setup. > > John > No, I have not tried turning WEP off, but on the same machine booted in tinycorelinux I can connect, albeit after a couple of attempts and not using NetworkManager. Also on three other laptops (none of which use the same hardware) and an iPhone there are no problems connecting. I'll try rmmod/modprobe ipw2100 (google suggests this might work) and if not, I guess it's ndiswrapper... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333f46...@nl0105exc01v01.eur.slb.com
Re: NetworkManager Cannot Connect to Wireless Network
On Tue, Jul 13, 2010 at 3:14 AM, John Frankish wrote: > > > Hmm - now I see the following in dmesg: > > ipw2100: Fatal interrupt. Scheduling firmware restart > > There are many, many hits for this in google, but no solutions... > I assume you have gotten things working with WEP turned off? Go the the router and disable WEP, and similarly on your computer select "no encryption", and make sure everything works. I can't remember if you said you had done that or if somebody else mentioned this, but just to be sure, it's worth checking that things work properly in the most simple setup. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilxv7tm1sst2tsbckjdblvmtxiyjvwqr3ere...@mail.gmail.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: John Frankish [mailto:j-frank...@slb.com] > Sent: Monday, 12 July, 2010 08:05 > To: debian-user@lists.debian.org > Subject: RE: NetworkManager Cannot Connect to Wireless Network > > > > > -Original Message- > > From: Felipe Sateler [mailto:fsate...@debian.org] > > Sent: Sunday, 11 July, 2010 21:46 > > To: debian-user@lists.debian.org > > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > > > On 10/07/10 01:49, John Frankish wrote: > > > Hi, > > > > > > I just installed NetworkManager and started to use it with > > > wired/wireless connections. > > > > > > Things work fine with the wired connection, but although > > > NetworkManager displays several available wireless networks, it will > > > not connect. > > > > > > The problem is that when I select the available network to join, > > > NetworkManager diplays a dialogue "Wireless Network Authentication > > > Required" and requests a "WEP 128-bit Passphrase". Entering the "128 > > > bits 26 hex digits" code for my router does not work, I believe I need > > > to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" > > > button is greyed out and I cannot enter the code. > > > > > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible > > > with NetworkManager? > > > > > > > What are you typing into the textbox? In a later example you are > > putting the : separators to iwconfig. I think you should not add them > > to network manager. > > > > > > -- > Thanks - I'd just came to the same conclusion, i.e. entering: > > 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB > > Causes the "connect" button to be greyed out, but entering: > > 123456789abcdef123456789ab > > Leaves the "connect" button "clickable. > > ..but NetworkManager still does not connect > Hmm - now I see the following in dmesg: ipw2100: Fatal interrupt. Scheduling firmware restart There are many, many hits for this in google, but no solutions... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333f46...@nl0105exc01v01.eur.slb.com
RE: NetworkManager Cannot Connect to Wireless Network
> -Original Message- > From: Felipe Sateler [mailto:fsate...@debian.org] > Sent: Sunday, 11 July, 2010 21:46 > To: debian-user@lists.debian.org > Subject: Re: NetworkManager Cannot Connect to Wireless Network > > On 10/07/10 01:49, John Frankish wrote: > > Hi, > > > > I just installed NetworkManager and started to use it with > > wired/wireless connections. > > > > Things work fine with the wired connection, but although > > NetworkManager displays several available wireless networks, it will > > not connect. > > > > The problem is that when I select the available network to join, > > NetworkManager diplays a dialogue "Wireless Network Authentication > > Required" and requests a "WEP 128-bit Passphrase". Entering the "128 > > bits 26 hex digits" code for my router does not work, I believe I need > > to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" > > button is greyed out and I cannot enter the code. > > > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible > > with NetworkManager? > > > > What are you typing into the textbox? In a later example you are > putting the : separators to iwconfig. I think you should not add them > to network manager. > > > -- Thanks - I'd just came to the same conclusion, i.e. entering: 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB Causes the "connect" button to be greyed out, but entering: 123456789abcdef123456789ab Leaves the "connect" button "clickable. ..but NetworkManager still does not connect -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333e74...@nl0105exc01v01.eur.slb.com
Re: Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network)
On 07/11/2010 06:11 AM, John Frankish wrote: -Original Message- From: Ron Johnson [mailto:ron.l.john...@cox.net] Sent: Sunday, 11 July, 2010 14:04 To: debian-user@lists.debian.org Subject: Re: Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network) On 07/10/2010 11:12 PM, John Frankish wrote: [snip] According to the IEEE, WEP-40 and WEP-104 "have been deprecated as they fail to meet their security goals". You should instead use WPA2-AES or, if that is not possible, WPA2-PSK. Thanks for the suggestion, but my old router does not support either of these encryption formats Then either upgrade your router's firmware to Tomato or DD-WRT (if they support your router) or bite the bullet and buy a new one. You can get really good ones mail order for US$55-60. Well OK, but this still does not solve the issue of why NetworkManager will not Connect to the router :) True enough, but there's a reason it's called Network Mangler... -- Seek truth from facts. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c3a8a08.4010...@cox.net
Re: NetworkManager Cannot Connect to Wireless Network
On 10/07/10 01:49, John Frankish wrote: > Hi, > > I just installed NetworkManager and started to use it with wired/wireless > connections. > > Things work fine with the wired connection, but although NetworkManager > displays several available wireless networks, it will not connect. > > The problem is that when I select the available network to join, > NetworkManager diplays a dialogue "Wireless Network Authentication Required" > and requests a "WEP 128-bit Passphrase". Entering the "128 bits 26 hex > digits" code for my router does not work, I believe I need to enter a "WEP > 40/128-bit Key", but when I select this, the "Connect" button is greyed out > and I cannot enter the code. > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible with > NetworkManager? > What are you typing into the textbox? In a later example you are putting the : separators to iwconfig. I think you should not add them to network manager. -- Saludos, Felipe Sateler signature.asc Description: OpenPGP digital signature
Re: NetworkManager Cannot Connect to Wireless Network
On Sat, Jul 10, 2010 at 1:49 AM, John Frankish wrote: > Hi, > > I just installed NetworkManager and started to use it with wired/wireless > connections. > > Things work fine with the wired connection, but although NetworkManager > displays several available wireless networks, it will not connect. > > The problem is that when I select the available network to join, > NetworkManager diplays a dialogue "Wireless Network Authentication Required" > and requests a "WEP 128-bit Passphrase". Entering the "128 bits 26 hex > digits" code for my router does not work, I believe I need to enter a "WEP > 40/128-bit Key", but when I select this, the "Connect" button is greyed out > and I cannot enter the code. > I don't use NetworkManager so forgive me if this is dumb. Is there a separate text entry box for Passphrase, and if so are you leaving it blank and entering your Hex Password in an entry text box for 128bit key? John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimtiosv-869epo89yzclkpyeojrg-e5g69yt...@mail.gmail.com
RE: Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network)
> -Original Message- > From: Ron Johnson [mailto:ron.l.john...@cox.net] > Sent: Sunday, 11 July, 2010 14:04 > To: debian-user@lists.debian.org > Subject: Re: Wireless Encryption (was Re: NetworkManager Cannot Connect > to Wireless Network) > > On 07/10/2010 11:12 PM, John Frankish wrote: > > > [snip] > >> > >> According to the IEEE, WEP-40 and WEP-104 "have been deprecated as > >> they fail to meet their security goals". > >> > >> You should instead use WPA2-AES or, if that is not possible, WPA2-PSK. > >> > > Thanks for the suggestion, but my old router does not support either of > > these > > encryption formats > > > > Then either upgrade your router's firmware to Tomato or DD-WRT (if > they support your router) or bite the bullet and buy a new one. > > You can get really good ones mail order for US$55-60. > > -- Well OK, but this still does not solve the issue of why NetworkManager will not Connect to the router :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333e74...@nl0105exc01v01.eur.slb.com
Re: NetworkManager Cannot Connect to Wireless Network
On Sun, 11 Jul 2010 06:09:37 +0200, John Frankish wrote: >> Mmm, try by right-clicking on NM icon and select "Edit connections", >> then go to the "Wireless" tab and try to add it from here. >> > Thanks for the suggestion - I'd already tried that with the same result > - i.e. that as soon as I select "WEP 40/128-bit Key", the "apply"/"OK" > button becomes greyed out. (...) Mmm, then I dunno :-? As soon as you select a "WEP 40/128-bit" from the dropdown menu and type a password with the right length, the "apply" button has to become clickeable. Anyway, you can also try with another wifi setup utility, such "wicd". Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.07.11.10.50...@gmail.com
Re: Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network)
On 07/10/2010 11:12 PM, John Frankish wrote: [snip] According to the IEEE, WEP-40 and WEP-104 "have been deprecated as they fail to meet their security goals". You should instead use WPA2-AES or, if that is not possible, WPA2-PSK. Thanks for the suggestion, but my old router does not support either of these encryption formats Then either upgrade your router's firmware to Tomato or DD-WRT (if they support your router) or bite the bullet and buy a new one. You can get really good ones mail order for US$55-60. -- Seek truth from facts. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c399726.1000...@cox.net
RE: Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network)
> On 07/10/2010 12:49 AM, John Frankish wrote: > > Hi, > > > > I just installed NetworkManager and started to use it with > > wired/wireless connections. > > > > Things work fine with the wired connection, but although > > NetworkManager displays several available wireless networks, it will > > not connect. > > > > The problem is that when I select the available network to join, > > NetworkManager diplays a dialogue "Wireless Network Authentication > > Required" and requests a "WEP 128-bit Passphrase". Entering the "128 > > bits 26 hex digits" code for my router does not work, I believe I need > > to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" > > button is greyed out and I cannot enter the code. > > > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible > > with NetworkManager? > > John, > > According to the IEEE, WEP-40 and WEP-104 "have been deprecated as > they fail to meet their security goals". > > You should instead use WPA2-AES or, if that is not possible, WPA2-PSK. > > -- Thanks for the suggestion, but my old router does not support either of these encryption formats -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333e74...@nl0105exc01v01.eur.slb.com
RE: NetworkManager Cannot Connect to Wireless Network
> On Sat, 10 Jul 2010 07:49:41 +0200, John Frankish wrote: > > > I just installed NetworkManager and started to use it with > > wired/wireless connections. > > > > Things work fine with the wired connection, but although > > NetworkManager displays several available wireless networks, it will not > > connect. > > > > The problem is that when I select the available network to join, > > NetworkManager diplays a dialogue "Wireless Network Authentication > > Required" and requests a "WEP 128-bit Passphrase". Entering the "128 > > bits 26 hex digits" code for my router does not work, I believe I > > need to enter a "WEP 40/128-bit Key", but when I select this, the > > "Connect" button is greyed out and I cannot enter the code. > > > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible > > with NetworkManager? > > Mmm, try by right-clicking on NM icon and select "Edit connections", > then go to the "Wireless" tab and try to add it from here. > > Greetings, > > -- Thanks for the suggestion - I'd already tried that with the same result - i.e. that as soon as I select "WEP 40/128-bit Key", the "apply"/"OK" button becomes greyed out. Note that this works on the same machine booted in tinycorelinux: # iwconfig eth1 essid "ssid" # iwconfig eth1 key restricted 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB # udhcpc -b -i eth1
Wireless Encryption (was Re: NetworkManager Cannot Connect to Wireless Network)
On 07/10/2010 12:49 AM, John Frankish wrote: Hi, I just installed NetworkManager and started to use it with wired/wireless connections. Things work fine with the wired connection, but although NetworkManager displays several available wireless networks, it will not connect. The problem is that when I select the available network to join, NetworkManager diplays a dialogue "Wireless Network Authentication Required" and requests a "WEP 128-bit Passphrase". Entering the "128 bits 26 hex digits" code for my router does not work, I believe I need to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" button is greyed out and I cannot enter the code. Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible with NetworkManager? John, According to the IEEE, WEP-40 and WEP-104 "have been deprecated as they fail to meet their security goals". You should instead use WPA2-AES or, if that is not possible, WPA2-PSK. -- Seek truth from facts. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c38b7b9.8020...@cox.net
Re: NetworkManager Cannot Connect to Wireless Network
On Sat, 10 Jul 2010 07:49:41 +0200, John Frankish wrote: > I just installed NetworkManager and started to use it with > wired/wireless connections. > > Things work fine with the wired connection, but although NetworkManager > displays several available wireless networks, it will not connect. > > The problem is that when I select the available network to join, > NetworkManager diplays a dialogue "Wireless Network Authentication > Required" and requests a "WEP 128-bit Passphrase". Entering the "128 > bits 26 hex digits" code for my router does not work, I believe I need > to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" > button is greyed out and I cannot enter the code. > > Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible > with NetworkManager? Mmm, try by right-clicking on NM icon and select "Edit connections", then go to the "Wireless" tab and try to add it from here. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.07.10.16.36...@gmail.com
NetworkManager Cannot Connect to Wireless Network
Hi, I just installed NetworkManager and started to use it with wired/wireless connections. Things work fine with the wired connection, but although NetworkManager displays several available wireless networks, it will not connect. The problem is that when I select the available network to join, NetworkManager diplays a dialogue "Wireless Network Authentication Required" and requests a "WEP 128-bit Passphrase". Entering the "128 bits 26 hex digits" code for my router does not work, I believe I need to enter a "WEP 40/128-bit Key", but when I select this, the "Connect" button is greyed out and I cannot enter the code. Any ideas whey trying to enter a "WEP 40/128-bit Key" is not possible with NetworkManager? Regards John Using debian testing NetworkManager 0.8 Gnome Desktop 2.30.0 Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6ac5a55546f64545ae996f8200e3ac4e0333e74...@nl0105exc01v01.eur.slb.com
