No worries :)
Got any advice on how to diagnose why it's able to scan and lock onto the
ssid (shows it in ifconfig), but not able to get an IP address with DHCP or
communicate with a manual IP address?
On Tuesday, November 18, 2014, Kevin Lo ke...@freebsd.org wrote:
Argh! I think I need more
Hmm... turns out this is an issue with authentication with wpa_supplicant.
If I turn off security I can connect just fine.
Other devices devices on my network are connecting fine with WPA2 AES PSK.
My wifi router is a TP-Link Archer D9 operating with both 2.4GHz and 5GHz.
I will go and try on
from Benjamin Woods:
I am trying to get my D-Link DWA-131 A1 working, with some success but no
network connectivity.
It shows up in my usb list with device id 07d1:3303. The driver pages
suggest this should be working with the rsu(4) driver and potentially
the rsu-rtl8712fw firmware,
2014-11-18 11:04 GMT+01:00 Ben Woods woods...@gmail.com:
Hmm... turns out this is an issue with authentication with wpa_supplicant.
If I turn off security I can connect just fine.
Well, disabling AP security features is not the right solution.
I have the EDUP adapter that uses if_rsu, and when
Hello.
Wi-fi adapter TRENDNET TEW_646UBH is not determined by the system freebsd 10.1.
Chipset Realtek RTL8188SU, that support driver RSU. Driver in the kernel is
loaded. In the log dmesg adapter is defined as: ugen0.3: vendor 0x20f4 at
usbus0
In ifconfig new connection not appear. This problem
On Tue, Nov 18, 2014 at 10:14:41PM +, bolshakov_1--- via freebsd-wireless
wrote:
Hello.
Wi-fi adapter TRENDNET TEW_646UBH is not determined by the system freebsd
10.1. Chipset Realtek RTL8188SU, that support driver RSU. Driver in the
kernel is loaded. In the log dmesg adapter is
