|
|
|||||||
| OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
 |
|
|
Thread Tools | Display Modes |
8th June 2022
|
|||
|
|||
Cannot connect to wifi with OpenBSD 7.1 + RaLink RT3070
Hi,
I have an ASUS X751L PC with a RaLink RT3070 Wifi dongle connected by USB (as the internal RealTek RTL8723BE does not seem to be supported: I get it as ugen0). I've been trying to connect to various access points, but to no success. The connection gets into the "active state", but I cannot manage to get any IP/route/DNS config. Particularities : - the access point is configured to use chan13, which is not supposed to be used in my country (France). However the connection perfectly works under Linux Mint, and works under Win10 after some configuration to allow for such a channel to be used. - the access point is using WEP - the access point is not under my control (I cannot change its config) - Card is recognized: Code:
$ ifconfig ... run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:0f:00:32:e9:c8 ...
I've also tried to change the access point (tethering on my with phone, using WPA + simple key like "xxx00000", where x is a digit) and repeated almost all the above steps. Does not work either... The problem seems to be with dhcp, not the wifi card, nor the accesss point. I'm running out of ideas. So, if anyone has any idea I would be glad to try it... 
|
|
9th June 2022
|
|||
|
|||
|
What is the output of
# ifconfig run0 scan? Does it show WEP? When I do a scan with my urtwn0 it only shows wpa2 as no accesspoints offer it anymore: Code:
nwid VRV9517592245 chan 1 bssid bc:30:d9:59:22:45 -76dBm HT-MCS23 privacy,spectrum_mgmt,short_slottime,radio_measurement,wpa2 nwid 0x00000000000000000000000000 chan 1 bssid 62:30:d9:59:22:47 -80dBm HT-MCS23 privacy,spectrum_mgmt,short_slottime,wpa2 nwid TP-LINK_32E2 chan 4 bssid c0:25:e9:01:32:e2 -80dBm HT-MCS23 privacy,short_preamble,short_slottime,wpa2 nwid "Danny en kim" chan 7 bssid c0:06:c3:50:31:6a -84dBm HT-MCS15 privacy,short_preamble,short_slottime,radio_measurement,wpa2 nwid Ziggo chan 1 bssid ae:22:15:e8:b7:cb -84dBm HT-MCS15 privacy,short_slottime,radio_measurement,wpa2,802.1x nwid TP-LINK_32E2 chan 1 bssid 48:8d:36:39:3b:a8 -84dBm HT-MCS15 privacy,short_slottime,radio_measurement,wpa2 nwid VRV9517208734 chan 11 bssid 64:cc:22:20:87:34 -84dBm HT-MCS23 privacy,spectrum_mgmt,short_slottime,radio_measurement,wpa2 nwid 0x00000000000000000000000000 chan 11 bssid 6a:cc:22:20:87:36 -84dBm HT-MCS23 privacy,spectrum_mgmt,short_slottime,wpa2 nwid Ziggo85993E9 chan 1 bssid ac:22:05:e8:b7:cb -84dBm HT-MCS15 privacy,short_slottime,radio_measurement,wpa2 nwid "" chan 7 bssid c6:06:c3:50:31:6a -84dBm HT-MCS15 privacy,short_preamble,short_slottime,radio_measurement,wpa2 nwid "" chan 7 bssid c6:06:c3:50:30:fa -92dBm HT-MCS15 privacy,short_preamble,short_slottime,radio_measurement,wpa2
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|
|
9th June 2022
|
||||
|
||||
|
Hello, and welcome!
Please note that there is a patch for the latest release -- OpenBSD 7.1 -- that fixes a channel scanning issue with some WiFi NICs, including run(4). You haven't posted your dmesg(8) so it is unclear what you're running; if you are running OpenBSD 7.1 without the patch, this could explain the issue. It's errata patch #001 for 7.1, installable with syspatch(8) on popular architectures. From the commit log for sys/dev/usb/if_run.c: Quote:
|
|
22nd June 2022
|
|||
|
|||
|
Thanks for the info.
As stated in the initial message, I have 5 patches installed, which would be impossible if I had the buggy patch n°1, so this should not be the problem.
|
|
22nd June 2022
|
||||
|
||||
|
Thanks for clarifying. I'd missed that in your initial post.
|
|
22nd June 2022
|
|||
|
|||
|
Quote:
Quote:
Quote:
|
|
22nd June 2022
|
|||
|
|||
|
Additional info:
- I have this error message when I run /etc/netstart with a parameter (interface) Quote:
Quote:
|
|
23rd June 2022
|
|||
|
|||
|
Yes, it shows 'wep' indeed .....
Code:
----->nwid NUMERICABLE-64FC chan 13 bssid c0:3f:0e:d8:74:b1 -53dBm 54M privacy,short_slottime,wep <----- Does the key contain French special characters that are not defined in the ASCII range? See ascii(7). Then the question whether an encoding in UTF-8 hexadecimal will be accepted? See locale(1)
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|
|
23rd June 2022
|
|||
|
|||
|
I think just a string of hexadecimal character should be accepted:
Code:
$ cat Fr_password.txt limité à $ cat Fr_password.txt | hexdump -C 00000000 6c 69 6d 69 74 c3 a9 20 c3 a0 0a |limit.. ...| Code:
6c - l 69 - i 6d - m 69 - i 74 - t c3 a9 - é 20 - space c3 a0 - à 0a - newline
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump Last edited by J65nko; 26th June 2022 at 12:57 AM. Reason: It should be 0x6c..... and not %x6c............
|
|
23rd June 2022
|
|||
|
|||
|
Quote:
As a side note, this same key works perfectly in Linux Mint and Windows 10. So this should not be the problem either.
|
|
23rd June 2022
|
|||
|
|||
|
Quote:
|
|
26th June 2022
|
|||
|
|||
|
Yes, you are right. It should start with 0x and not %x Silly me
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|
|
| Tags |
| dhcp, openbsd 7.1, wifi |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Unable to connect to wifi | stanl | OpenBSD General | 3 | 11th July 2021 12:06 AM |
| [Solved] OpenBSD cannot connect to the WiFi | LeFrettchen | OpenBSD General | 0 | 17th May 2018 01:41 PM |
| Can I connect to unprotected Wifi ? | e1-531g | OpenBSD General | 17 | 15th August 2017 07:44 PM |
| connect to wifi networks without GUI | spermwhale_warrior | NetBSD Installation and Upgrading | 6 | 24th November 2015 07:27 PM |
| Ralink RT2860 | ccc | FreeBSD General | 9 | 5th March 2009 01:56 PM |
Linear Mode
