Re: ral0: device timeout
The 'ifconfig ral0 debug' printout when the client device gets time out. ral0: begin active scan ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 12 ral0: received probe_resp from 00:13:f7:2a:f4:ab rssi 119 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 13 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 14 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 2 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 3 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 4 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 5 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 6 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 7 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 8 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 9 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 10 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 11 ral0: end active scan ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 12 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 13 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 14 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 2 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 3 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 4 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 5 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 6 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 7 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 8 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 9 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 10 ral0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 11 ral0: end active scan ral0: end passive scan ral0: received beacon from 00:13:f7:2a:f4:ab rssi 117 ral0: end passive scan ral0: sending auth to 00:13:f7:2a:f4:ab on channel 11 ral0: device timeout And this is what I get on the AP ral0: received auth from 00:13:f7:1e:a7:86 rssi 119 ral0: sending auth to 00:13:f7:1e:a7:86 on channel 11 ral0: station 00:13:f7:1e:a7:86 newly authenticated (open) But for some reason that doesn't seem to arrive. I'm not buying that it is a bad Ralink radio (http://marc.theaimsgroup.com/?l=openbsd-miscm=116570938017614w=2) since when I do get a connection, the range is acceptable. /Markus Markus Bergkvist wrote: I have not yet been able to get a debug print from client ral when it is failing, is there a way to set that in hostname.if? If the device is not failing during boot, it is hard to get it to fail.
Re: ral0: device timeout
Some new findings. Hopefully these means something to someone because I don't really know where to go from here. I noticed that I can't reproduce the 'device timeout' if I turn off the device at the AP. Could the AP be responding with something fishy? I also found out that if I change the ral-cards to explicitly use 'media OFDM54' the 'device timeout' would occur less often, and when they do, I can most often get it to work by bring it down and then #sh /etc/netstart ral0 When I get 'device timeout' I see the following at the AP ral0: received auth from 00:13:f7:1e:a7:86 rssi 119 ral0: sending auth to 00:13:f7:1e:a7:86 on channel 11 ral0: station 00:13:f7:1e:a7:86 newly authenticated (open) I have not yet been able to get a debug print from client ral when it is failing, is there a way to set that in hostname.if? If the device is not failing during boot, it is hard to get it to fail. I have also seen the timeout on the AP once when I rebooted it while the client was up, but it didn't occur repeatedly as it does on the client. == AP hostname.if == # cat /etc/hostname.ral0 inet 192.168.0.2 255.255.255.0 NONE media OFDM54 mode 11g mediaopt hostap chan 11 nwid himmet_wlan == Client hostname.if == # cat /etc/hostname.ral0 dhcp NONE NONE NONE media OFDM54 mode 11g chan 11 nwid himmet_wlan /Markus For some time now I've been trying to get my SMC wireless cardbus[1] with Ralink RT2600 chipset[2] to work on my laptop running OpenBSD 4.0 -stable but I keep getting 'ral0: device timeout'. If I bring the device down and then up (sometimes I have to do this several times) I finally get it to work. After that I don't get any more 'device timeout' until next reboot. This is what ral(4) has to say about that error: ral%d: device timeout A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware. This should not happen. Unfortunately, it does happen. My question is, why? And what can i do to remedy this? I have a SMC pci-card[3] in the AP but I have not seen that problem there. I enclose dmesg and ifconfig ral0 from client and ap.
Re: ral0: device timeout
According to Sepherosa Ziehau rt2661's led is not programmed at all in OpenBSD. Best Regards, sephe So I guess that the LED is always on is ok. I've done tcpdump(8) on the AP and I get no output from that while the client gets time out on the ral0 device, so I don't think the interface is flooded. Also, when the client finally gets a network connection there is no more time outs. The problem occurs only after reboot and sometimes after 'ifconfig up'. If the device is connected to a network when I put it to sleep, it has no problem reconnecting when it wakes up. What do you mean by 'That would indicate that the error is generated internally', firmware issue? Thanks for the feed back. /Markus Bill Maas wrote: From http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ie2116/install/cables.htm#wp1043436 : The bottom LED is the Ethernet activity LED. When it flashes, it indicates that data is being transmitted or received between the server and a network device. The flashing frequency is proportional to the amount of traffic on the network link. So if the LED stays ON then something might be flooding the interface with packets [or the interface is trying to send the same packet over and over again - beyond my knowledge]. Which might as well indicate a software [config] problem. Did you run tcpdump(8) on that interface? Did you reboot the device while off the net and was there still a problem? That would indicate that the error is generated internally. I wouldn't bet my life on an OS or hardware issue here. Bill On Tue, 2006-12-05 at 23:11 +0100, Markus Bergkvist wrote: I have a RT2600 also on my AP so I guess I have to get my hands on a working out-of-the-box AP to verify that it is no hardware problem. /Markus Bill Maas wrote: On 12/4/06, Markus Bergkvist [EMAIL PROTECTED] wrote: Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. Check the other end. I've had a similar problem with sis0 on a Soekris (both LEDs continuously on), and it turned out to be the Vigor ADSL modem that was in trouble. Bill
Re: ral0: device timeout
On 12/4/06, Markus Bergkvist [EMAIL PROTECTED] wrote: Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. Check the other end. I've had a similar problem with sis0 on a Soekris (both LEDs continuously on), and it turned out to be the Vigor ADSL modem that was in trouble. Bill -- Good that there are standards, and enough of them
Re: ral0: device timeout
Ok, thanks. Good to know, then I don't have to think about that anymore. /Markus Sepherosa Ziehau wrote: On 12/4/06, Markus Bergkvist [EMAIL PROTECTED] wrote: Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. rt2661's led is not programmed at all in OpenBSD. Best Regards, sephe
Re: ral0: device timeout
I have a RT2600 also on my AP so I guess I have to get my hands on a working out-of-the-box AP to verify that it is no hardware problem. /Markus Bill Maas wrote: On 12/4/06, Markus Bergkvist [EMAIL PROTECTED] wrote: Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. Check the other end. I've had a similar problem with sis0 on a Soekris (both LEDs continuously on), and it turned out to be the Vigor ADSL modem that was in trouble. Bill
Re: ral0: device timeout
From http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ie2116/install/cables.htm#wp1043436 : The bottom LED is the Ethernet activity LED. When it flashes, it indicates that data is being transmitted or received between the server and a network device. The flashing frequency is proportional to the amount of traffic on the network link. So if the LED stays ON then something might be flooding the interface with packets [or the interface is trying to send the same packet over and over again - beyond my knowledge]. Which might as well indicate a software [config] problem. Did you run tcpdump(8) on that interface? Did you reboot the device while off the net and was there still a problem? That would indicate that the error is generated internally. I wouldn't bet my life on an OS or hardware issue here. Bill On Tue, 2006-12-05 at 23:11 +0100, Markus Bergkvist wrote: I have a RT2600 also on my AP so I guess I have to get my hands on a working out-of-the-box AP to verify that it is no hardware problem. /Markus Bill Maas wrote: On 12/4/06, Markus Bergkvist [EMAIL PROTECTED] wrote: Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. Check the other end. I've had a similar problem with sis0 on a Soekris (both LEDs continuously on), and it turned out to be the Vigor ADSL modem that was in trouble. Bill -- Good that there are standards, and enough of them
Re: ral0: device timeout
Also, the connection light and the transmission light is always on, regardsless if it is connected to the network or sending/receiving or not. Only when I take the network interface down the lights go out. If that means anything to anyone. /Markus
