|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
dhclient -> urtw0: no link ....... sleeping
Hey everyone. I'm tyring to get my Alfa usb wifi dongle to work. I'll try to post as much information as possible.
So I plug in the usb device and it gets recognized, in fact a nice little message pops up on the screen : Code:
urtw0 at ubut2 post 2 "Realtek RTL8187" rev 1.10/1.00 addr2 urtw0: RTL8187 rev 0x04, RFv2, address 00:c0:ca:1c:44:2a" Code:
#ifconfig urtw0 urtw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:c0:ca:1c:44:2a priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid "" 100dBm Code:
#ifconfig urtw0 up #ifconfig urtw0 nwid MyESSID #ifconfig urtw0 nwkey 0xmynetkey Code:
#dhclient urtw0 urtw0: no link ............. sleeping Thanks everyone |
|
|||
So I forgot to post the model of the alfa usb dongle, in case it's helpful :
Mode: AWUS036H |
|
|||
Quote:
As for potential work-arounds:
Quote:
Likewise, the main source file associated with this driver, src/sys/dev/usb/if_urtw.c, has not changed since OpenBSD 4.7 was tagged. Perhaps you are using 4.7, maybe 4.6. Your message didn't state such fundamental information. If you are using 4.6 or an earlier version, upgrading is in order. If you are using 4.7, installing -current is still justified -- especially if you want the project developers to take interest. Even if you are already running -current, installing a recent snapshot may help your case. If you are unclear as to what is -current, familiarize yourself with the information found in Section 5.1 of the FAQ. Submitting a formal problem report may be your best next move. Since the developers are far more interested in the behavior seen on -current, this is the motivating reason for installing it. The fact that the driver's source has not changed since 4.7's tagging should not raise your hopes for a miraculous change in observed behavior. I cannot say definitively that filing a report will resolve your issue or resolve your issue quickly, but by going through the appropriate channels, your information will get to those familiar with the driver's internals. Information on submitting problem reports can be found at the following: http://www.openbsd.org/report.html
Good luck. |
|
|||
As mentioned by polera, specifying just nwid/nwkey may be insufficient.. run a scan and then directly indicate which channel to use, post the output of ifconfig(8) here after doing so.
|
|
|||
first off... you guys rock. thanks so much for the fast and quality responses. And I am using 4.7 stable, sorry I forgot to mention that.
@ocicat : I setup an /etc/hostname.urtw0 : Code:
dhcp NONE NONE NONE nwkey 0xmysecretkey chan 1 Code:
#ifconfig urtw0 urtw0: no such interface #inconfig urtw0 up ifconfig: SIOCGIFFLAGS: Device not configured Scanning doesn't work, it just says the information like ifconfig rather than showing all the networks (the pcmcia picks them up) Code:
#ifconfig urtw0 scan urtw0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladder 00:c0:ca:1c:44:2a priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid "" 100dBm Code:
#ifconfig urtw0 urtw0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladder 00:c0:ca:1c:44:2a priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid mynetwork chan 1 nwkey 0xmykey 100dBm inet6 fe80::.....snip....442a%urtw0 prefixlen 64 scopeid 0x6 #dhclient urtw0 urtw0: no link ............. sleeping Trying to set it up statically doesn't seem to get me anywhere, but maybe this will help you guys : Code:
#ifconfig urtw0 inet 192.168.1.57 netmask 255.255.255.0 broadcast 192.168.1.255 #ifconfig urtw0 urtw0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladder 00:c0:ca:1c:44:2a priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid mynetwork chan 1 nwkey 0xmykey 100dBm inet6 fe80::.....snip....442a%urtw0 prefixlen 64 scopeid 0x6 inet 192.168.1.57 netmask 0xffffff00 broadcast 192.168.1.255 #ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes ping: sendto: Network is down ping: wrote 192.168.1.1 64 chars, ret=-1 |
|
|||
I do this all the time with urtw0. do it like this without the quotes "sudo ifconfig urtw0 scan" --> should get you a list of nwid's ( net work id's ) that the radio in the usb wifi nic is picking up. usually they're public at places like Borders, McDonalds, Taco Bell, etc. If you ain't got a nwid you ain't gonna get nowhere -- that's been my luck. you have to have a nwid or if it's hidden who knows I don't go there anyway.
then with the nwid do this "sudo ifconfig urtw0 nwid "theNameOfTheAccessPoint" -chan up" --> that's about it. give it 30 seconds to connect fully. the dash chan tells the urtw0 driver to automatically pick a channel that's gonna work. don't make things harder than they have to be. the light should light up on your usb stick wifi thingy. then, do the "sudo dhclient urtw0" and get a lease and then rock out. hope this helps. |
|
|||
about that hostname.urtw0 you're making ... just put this in there without the quotes "dhcp" that's it. nothing else cause that causes problems and confusion. keep it simple. openbsd takes care of the hard stuff so you don't have to.
|
|
|||
Most wireless cards will automatically try to associate with an access point, this may or may not be a good thing.. you should always manually scan for and join one yourself, specifying the appropriate nwid and operating channel.
Wireless works in a different way, you should probably keep hostname.if(5) files empty for them.. that's my opinion of it. |
|
|||
I was having a similar problem with getting a "no link .... sleeping" message. Turned out the authentication mode defaulted to 'open'. Once i used ifconfig to set it to 'shared', everything worked fine.
note: the access point was using shared key WEP. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CARP interface with DHClient | xinform3n | OpenBSD General | 5 | 22nd July 2009 12:41 PM |
dhclient at startup | bsdnewbie999 | OpenBSD General | 3 | 31st March 2009 03:55 AM |
kde .desktop file link doesn't act like a link when opening files | caesius | FreeBSD Ports and Packages | 3 | 14th October 2008 07:35 AM |
dhclient.conf: multiple fixed-address statements | xiphias | FreeBSD General | 14 | 19th June 2008 06:42 AM |
dhclient iwi0 "Could not read iwi-bss' error | FreeMan | OpenBSD General | 2 | 15th May 2008 08:01 PM |