Re: [SOLVED] Re: setting up usb wireless
On Sat 21 Dec 2013 at 21:10:41 -0500, Frank McCormick wrote: > Yes I noticed on the Ralink Tech site that some of the drivers > cover a wide range of chipsets. It was weird that the adapter seemed > to be setup but couldn't function under dhcp. . . . . . . . . In and earlier message you said: Well it's really frustrating! iwconfig output looks ok then again I am not really sure what I should be looking for. root@frank-debian:/home/frank# iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm So the adapter is not set up (Access Point: Not-Associated) and the dhcp server cannot be contacted. -- 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/22122013135605.b1543a380...@desktop.copernicus.demon.co.uk
Re: [SOLVED] Re: setting up usb wireless
Frank McCormick wrote: > Yes I noticed on the Ralink Tech site that some of the drivers > cover a wide range of chipsets. It was weird that the adapter seemed > to be setup but couldn't function under dhcp. I have seen wifi associate and then not obtain a dhcp address on a variety of chipsets and drivers. Intel, Broadcom, Realtek. And so I conclude that the problem must be at a different layer since there is no commonality below. > But today I had different problems with the passphrase which I > finally sorted out. And then the adapter kept dropping out and > reverting to wired...and it's only a few feet from the router. You have a wire? If I have a wire then I always use it. Wired connections are always going to be more reliable than radio because radio is susceptible to noise among other problems. > Wireless under Linux can be a PITA. All I have to do is mention "Limited or no connectivity" and cringe. I am sure others reading this will too. If you type that into a search engine with auto-prompting on the only hits after that are for MS Windows. Typically that means network connected but no DNS servers are configured. But useless error messages like that make it very difficult for people. Things are much better under Debian GNU/Linux than under MS-Windows by a long distance! Bob signature.asc Description: Digital signature
Re: [SOLVED] Re: setting up usb wireless
On 21/12/13 04:35 PM, Bob Proulx wrote: Frank McCormick wrote: Selim T. Erdogan wrote: Frank McCormick, 19.12.2013: Solved my problem. +1 for wicd in the Debian repositories...-10 for gnome-nettool :) If you are having wireless setup problems, it's the tool to goto. FWIW, I have a cheap usb wireless adabter with the same identifier listed in your lsusb (ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter) and it's been working fine with Network Manager in Gnome (in fallback mode) in wheezy. Haven't needed wicd, or anything else for that matter, to get it working. (The performance isn't too great but that's probably due to the driver and/or hardware.) I don't like NM but the symptoms you reported don't seem to be due to the difference between wicd and NM. The symptoms showed that the wifi was associated but no dhcp response was received. I sometimes get this too using the Intel 2200BG driver. I think it might more likely have been a driver issue. I find that unloading and reloading the driver fixes the problem. And another list member reported the same thing recently too. //snip// I am using the ralink driver with a USB RT3070 device. That is different from the RT5370 device you are using but I think the driver is the same? For me it is the rt2800usb family. The ralink driver has been working well for me. I am using one as a client and two as an access points and found they work pretty well for me. So far I would give them a thumbs up. Yes I noticed on the Ralink Tech site that some of the drivers cover a wide range of chipsets. It was weird that the adapter seemed to be setup but couldn't function under dhcp. But today I had different problems with the passphrase which I finally sorted out. And then the adapter kept dropping out and reverting to wired...and it's only a few feet from the router. Wireless under Linux can be a PITA. Anyway, it's good that you solved your problem, whichever way was handy. Any port in a storm :) Agreed. Glad that your problem is solved. For now anyway :) -- Your mail is being read by tight-lipped NSA agents who fail to see the humor in Doctor Strangelove. -- 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/52b64a21.6030...@videotron.ca
Re: [SOLVED] Re: setting up usb wireless
Frank McCormick wrote: > Selim T. Erdogan wrote: > >Frank McCormick, 19.12.2013: > > >Solved my problem. +1 for wicd in the Debian repositories...-10 > > > for gnome-nettool :) > > > > > > If you are having wireless setup problems, it's the tool to goto. > > > > FWIW, I have a cheap usb wireless adabter with the same identifier > > listed in your lsusb (ID 148f:5370 Ralink Technology, Corp. RT5370 > > Wireless Adapter) and it's been working fine with Network Manager in > > Gnome (in fallback mode) in wheezy. Haven't needed wicd, or anything > > else for that matter, to get it working. (The performance isn't too > > great but that's probably due to the driver and/or hardware.) > > Well try as I might..I could not get the darned thing to operate. > It was setup properly but I couldn't use it. As I said wicd solved > the problem for me in Debian. On the other hand, I just booted into > Fedora 19 and it recognized the device, set it up..called dhcp and > it was ready and waiting when I reached the desktop. Weird or what. I don't like NM but the symptoms you reported don't seem to be due to the difference between wicd and NM. The symptoms showed that the wifi was associated but no dhcp response was received. I sometimes get this too using the Intel 2200BG driver. I think it might more likely have been a driver issue. I find that unloading and reloading the driver fixes the problem. And another list member reported the same thing recently too. I think that may have been more likely the issue rather than the choice of system management software. I think for this particular case either wicd or NetworkManager would have been okay and that it isn't a particular problem with NM. On the surface if there isn't a dhcp received then I would expect that one wasn't sent on the server side. However in practice I find that I have had kernel driver issues more often and reloading the driver fixes it and therefore it cannot be due to missing dhcp frames. The unanswered question is what situation causes the device to report being associated but fails to communicate data? Don't know. I am using the ralink driver with a USB RT3070 device. That is different from the RT5370 device you are using but I think the driver is the same? For me it is the rt2800usb family. The ralink driver has been working well for me. I am using one as a client and two as an access points and found they work pretty well for me. So far I would give them a thumbs up. > >Anyway, it's good that you solved your problem, whichever way was handy. > > Any port in a storm :) Agreed. Glad that your problem is solved. Bob signature.asc Description: Digital signature
Re: [SOLVED] Re: setting up usb wireless
On 19/12/13 05:32 PM, Selim T. Erdogan wrote: Frank McCormick, 19.12.2013: On 19/12/13 10:25 AM, Frank McCormick wrote: On 19/12/13 01:32 AM, Charlie wrote: On Thu, 19 Dec 2013 01:09:03 -0500 Frank McCormick sent: It appears it is supported - I have the ralink-firmware installed, but when Debian (sid) boots it tries dhcpdiscover 255.255.255.255 about 10 times then gives up after getting no reply. root@frank-debian:/home/frank# 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:off Fragment thr:off Encryption key:off Power Management:on This is from syslog Dec 19 10:17:37 frank-debian dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 Dec 19 10:17:44 frank-debian dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Dec 19 10:17:52 frank-debian dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 database - sleeping. Solved my problem. +1 for wicd in the Debian repositories...-10 for gnome-nettool :) If you are having wireless setup problems, it's the tool to goto. FWIW, I have a cheap usb wireless adabter with the same identifier listed in your lsusb (ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter) and it's been working fine with Network Manager in Gnome (in fallback mode) in wheezy. Haven't needed wicd, or anything else for that matter, to get it working. (The performance isn't too great but that's probably due to the driver and/or hardware.) Well try as I might..I could not get the darned thing to operate. It was setup properly but I couldn't use it. As I said wicd solved the problem for me in Debian. On the other hand, I just booted into Fedora 19 and it recognized the device, set it up..called dhcp and it was ready and waiting when I reached the desktop. Weird or what. Anyway, it's good that you solved your problem, whichever way was handy. Any port in a storm :) -- Your mail is being read by tight-lipped NSA agents who fail to see the humor in Doctor Strangelove. -- 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/52b3a727.9000...@videotron.ca
Re: [SOLVED] Re: setting up usb wireless
Frank McCormick, 19.12.2013: > On 19/12/13 10:25 AM, Frank McCormick wrote: > >On 19/12/13 01:32 AM, Charlie wrote: > >>On Thu, 19 Dec 2013 01:09:03 -0500 Frank McCormick sent: > >> > >>>It appears it is supported - I have the ralink-firmware installed, but > >>>when Debian (sid) boots it tries dhcpdiscover 255.255.255.255 about > >>>10 times then gives up after getting no reply. > >> > >>There has been a recent thread about wireless. Some interesting > >>information. > >> > >>I have no idea at all about wireless. > >> > >>Try 'iwconfig" as root and see what wlan should be seeking. I wore > >>myself out putting wlan1 in my /etc/network/interfaces and jumping > >>through all manner of hoops. It should have been wlan2 and when I > >>changed it, all was well. > >> > > > >Well it's really frustrating! iwconfig output looks ok then again I > >am not really sure what I should be looking for. > > > >root@frank-debian:/home/frank# 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:off Fragment thr:off > > Encryption key:off > > Power Management:on > > > > > > > >This is from syslog > > > >Dec 19 10:17:37 frank-debian dhclient: DHCPDISCOVER on wlan0 to > >255.255.255.255 port 67 interval 7 > >Dec 19 10:17:44 frank-debian dhclient: DHCPDISCOVER on wlan0 to > >255.255.255.255 port 67 interval 8 > >Dec 19 10:17:52 frank-debian dhclient: DHCPDISCOVER on wlan0 to > >255.255.255.255 port 67 interval 10 > >database - sleeping. > > > Solved my problem. +1 for wicd in the Debian repositories...-10 > for gnome-nettool :) > > > If you are having wireless setup problems, it's the tool to goto. FWIW, I have a cheap usb wireless adabter with the same identifier listed in your lsusb (ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter) and it's been working fine with Network Manager in Gnome (in fallback mode) in wheezy. Haven't needed wicd, or anything else for that matter, to get it working. (The performance isn't too great but that's probably due to the driver and/or hardware.) Anyway, it's good that you solved your problem, whichever way was handy. -- 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/20131219223214.ga13...@cs.utexas.edu
