[SOLVED] Wireless connection not working

scorpion77 · 11-01-2017, 12:33 PM

Hi, I purchased a Wi-Fi adapter, a Netis WF2190 (http://www.netis-systems.com/Home/detail/id/96.html). The official driver is for Ubuntu. I discovered this adapter uses a RealTek RTL8812AU chip. I compiled the driver using this guide (https://www.linuxquestions.org/quest...2au-4175606244). So I edited rc.inet1.conf and wpa_supplicant.conf. Then I run this command: rc.inet1 restart. I get this output:

Code:

./rc.inet1:  wlan0 information: 'Any ESSID'
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan0 ; Operation not permitted.
Successfully initialized wpa_supplicant
ioctl[SIOCSIWAP]: Operation not permitted

This is my rc.inet1.conf:

Code:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY="192.168.1.1"

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

## Example config information for wlan0.  Uncomment the lines you need and fill
## in your data.  (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
IPADDR[4]="192.168.1.130"
NETMASK[4]="255.255.255.0"
USE_DHCP[4]=""
#DHCP_HOSTNAME[4]="icculus-wireless"
DHCP_TIMEOUT[4]=10
DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[4]=MYSSID
WLAN_MODE[4]="Managed"
#WLAN_RATE[4]="54M auto"
WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5A31F54ACF0487C2D0B1C10D2"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
WLAN_WPACONF[4]="/etc/wpa_supplicant.conf"
#WLAN_WPAWAIT[4]=30

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0"              # Use a different interface name instead of
                                # the default 'eth4'
#IFNAME[4]="eth0:1"             # Set up an IP alias.
#HWADDR[4]="00:01:23:45:67:89"  # Overrule the card's hardware MAC address
#MTU[4]=""                      # The default MTU is 1500, but you might need
                                # 1360 when you use NAT'ed IPSec traffic.
#DHCP_TIMEOUT[4]=15             # The default timeout for the DHCP client to
                                # wait for server resonse is 30 seconds, but
                                # you might want a shorter wait.
#DHCP_KEEPRESOLV[4]="yes"       # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes"          # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes"           # If you don't want the DHCP server to change
                                # your default gateway
#DHCP_IPADDR[4]=""              # Request a specific IP address from the DHCP
                                # server
#WLAN_ESSID[4]=DARKSTAR         # An example of how you can override _any_
                                # parameter defined in rc.wireless.conf, by
                                # prepending 'WLAN_' to the parameter's name.
                                # Useful with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
                                # Some drivers require a private ioctl to be
                                # set through the iwpriv command. If more than
                                # one is required, you can place them in the
                                # IWPRIV parameter (separated with the pipe (|)
                                # character, see the example).
#WLAN_WPA[4]="wpa_supplicant"   # Run wpa_supplicant for WPA support
#WLAN_WPADRIVER[4]="ndiswrapper"# Tell wpa_supplicant to specifically use the
                                # ndiswrapper driver (if you leave this empty
                                # the 'wext' driver is used by default)
#WLAN_WPAWAIT[4]=30             # In case it takes long for the WPA association
                                # to finish, you can increase the wait time
                                # (defaults to 10 seconds)

This is my wpa_supplicant.conf:

Code:

# See /usr/doc/wpa_supplicant-0.5.7/wpa_supplicant.conf.sample
# for many more options that you can use in this file.

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# 
network={
ssid="myssid"
scan_ssid=0
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="mypsk"
}

This is the output of lsmod | grep 8812:

Code:

8812au               1665036  0
cfg80211              524168  1 8812au

How can I solve? Thanks in advance.

Scorpion77

business_kid · 11-01-2017, 03:50 PM

I'd get a driver for that if you haven't got one. Use google. That's up to you.

As for ine
t1.conf, I'd suggest a few changes.

Code:

#IFNAME[4]="eth0:1" *Use wlan0 or whatever your interface is
USE_DHCP[4]="" * I would put yes if you use dhcp, no otherwise. |Don't sit on the fence.
#DHCP_HOSTNAME[4]="icculus-wireless" * I have my box's hostname - not sure if it' needed

I don't have my keys in inet1.conf but in wpa_supplicant.conf. They're read from there. Don't make the mistake of posting them to a public forum. Put things like <my username>, <my password>, or <my wpa key>.

scorpion77 · 11-01-2017, 04:44 PM

I solved! I was wrong to write the ssid in wpa_supplicant.conf.

bassmadrigal · 11-01-2017, 06:54 PM

Quote:

Originally Posted by scorpion77

I solved! I was wrong to write the ssid in wpa_supplicant.conf.

Normally you do have your SSID in your /etc/wpa_supplicant.conf file. In fact, you can use wpa_passphrase to generate the network section of your wpa_supplicant.conf that should work with no other options for most networks (although, you can customize it, if needed). You can remove the #psk="myuniquepassword" line if desired... only the hex psk is needed.

Code:

root@craven-moorhead:~# wpa_passphrase mycustomssid myuniquepassword
network={
        ssid="mycustomssid"
        #psk="myuniquepassword"
        psk=ee4c844dd89acd5817f768015505edcd385259d2e3c04bcd7c9f9f9ed09c3c12
}

You can redirect that output to append it to the end of your wpa_supplicant.conf file.

Code:

wpa_passphrase mycustomssid myuniquepassword >> /etc/wpa_supplicant.conf

My guess is you went a little heavy on your configuration of /etc/rc.d/rc.inet1.conf file and added things that would conflict with the content in wpa_supplicant.conf, but once you removed those conflicts, in either file, it would work fine.

That being said, if this computer won't be connecting to multiple wireless networks, it should work fine, but if this is a laptop and you're likely to connect it to multiple networks, I'd suggest getting all your various network config in the wpa_supplicant.conf file rather than in rc.inet1.conf or switch to a graphical front-end like Network Manager (pre-installed) or wicd (available in extra/ on your installation media or favorite mirror).

business_kid · 11-02-2017, 03:50 AM

Code:

psk=<big-long-alphanumeric-=string>

Don't post that stuff on a public forum - you've told any local hacker how to crack your wifi. As one smart-alec put it: "The biggest security gap - an open mouth!" Post it as I've shown you.

Alien Bob · 11-02-2017, 04:28 AM

Quote:

Originally Posted by business_kid

Code:

psk=<big-long-alphanumeric-=string>

Don't post that stuff on a public forum - you've told any local hacker how to crack your wifi. As one smart-alec put it: "The biggest security gap - an open mouth!" Post it as I've shown you.

Did you actually look at that string?
Did you actually try to run the literal command

Code:

wpa_passphrase mycustomssid myuniquepassword

Did you notice that that command emits exactly what bassmadrigal posted.
It's called 'an example' ;-)

And yes, in real life you must never post your private passphrase of course.

bassmadrigal · 11-02-2017, 06:44 AM

Quote:

Originally Posted by business_kid

Code:

psk=<big-long-alphanumeric-=string>

Don't post that stuff on a public forum - you've told any local hacker how to crack your wifi. As one smart-alec put it: "The biggest security gap - an open mouth!" Post it as I've shown you.

As Alien showed you, I just provided an example. But, even if that was my real SSID or PSK (it isn't), someone would still need to be within range of my wifi for it to be of any benefit. As you can see from my profile, I live in Newport News, VA, but even if someone is local, it is a relatively big city that has 70 square miles of land with almost 75,000 household units (as of the 2010 census).

That being said, I do agree that someone shouldn't post their info online, but it certainly wouldn't make it easy for "any local cracker" to crack it unless they happen to drive within range of my router while monitoring networks and their locations (wardriving -- which let's be honest... nobody really does anymore).

scorpion77 · 11-02-2017, 10:36 AM

Thanks to everybody. But, obviously, "myssid" and "mypsk" aren't my real SSID and password.