No internet connection

Dear FreeBSD Community,

I have recently installed FreeBSD 14-RELEASE and am attempting to connect my wireless card to my university's Wi-Fi using the instructions provided in the FreeBSD Handbook.
The router utilizes WPA2-Enterprise security, so I configured "/etc/wpa-supplicant.conf" as the following: (circa the same configuration that I had on a Linux machine)
Code:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
        ssid="myssid"
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="myidentity"
        password="mypassword"
        phase1="peaplabel=0"
        phase2="auth=MSCHAPV2"
}

and "/etc/rc.conf":
Code:
hostname="lumarans30"
keymap="it.kbd"
sshd_enable="YES"
moused_enable="YES"
ntpd_enable="YES"
powerd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
kld_list="nvidia-modeset"
dbus_enable="YES"
sddm_enable="YES"
sddm_lang="it_IT"

wlans_rtw880="wlan0"
ifconfig_wlan0="WPA SYNCDHCP country IT"
ifconfig_re0="DHCP"
ifconfig_ue0="DHCP"

My wireless card is an RTL8822CE 802.11ac PCIe Wireless Network Adapter, which should be supported since the 13.2 release according to what I've read here.
Here's the output of "pciconf -lv | grep -A1 -B3 network":
Code:
re0@pci0:3:0:0: class=0x020000 rev=0x10 hdr=0x00 vendor=0x10ec device=0x8168 subvendor=0x17aa subdevice=0x38f7
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
rtw880@pci0:4:0:0:      class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec device=0xc822 subvendor=0x17aa subdevice=0xc123
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8822CE 802.11ac PCIe Wireless Network Adapter'
    class      = network
vgapci1@pci0:5:0:0:     class=0x030000 rev=0xc6 hdr=0x00 vendor=0x1002 device=0x1636 subvendor=0x17aa subdevice=0x3a44

The command "ifconfig" shows this: (the wlan0 interface succeeds to get an IP from the DHCP server)
Code:
re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 54:05:db:11:87:d0
        media: Ethernet autoselect (none)
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=0
        ether 28:cd:c4:5c:bb:b7
        inet 10.0.18.45 netmask 0xfffff000 broadcast 10.0.31.255
        groups: wlan
        ssid UnicamEasyWiFi channel 36 (5180 MHz 11a) bssid b8:11:4b:e2:56:af
        regdomain ETSI country IT authmode WPA2/802.11i privacy ON
        deftxkey UNDEF AES-CCM 3:128-bit txpower 17 bmiss 7 mcastrate 6
        mgmtrate 6 scanvalid 60 wme roaming MANUAL
        parent interface: rtw880
        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a
        status: associated
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

and "netstat -rn": (The default gateway is correct)
Code:
Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            10.0.16.1          UGS       wlan0
10.0.16.0/20       link#3             U         wlan0
10.0.18.45         link#2             UHS         lo0
127.0.0.1          link#2             UH          lo0

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::/96                             link#2                        URS         lo0
::1                               link#2                        UHS         lo0
::ffff:0.0.0.0/96                 link#2                        URS         lo0
fe80::%lo0/10                     link#2                        URS         lo0
fe80::%lo0/64                     link#2                        U           lo0
fe80::1%lo0                       link#2                        UHS         lo0
ff02::/16                         link#2                        URS         lo0

Resolvconf generates the "/etc/resolv.conf" with the settings from the DHCP:
Code:
# Generated by resolvconf
search Studenti.Amministrazione.Unicam
nameserver 8.8.8.8

Additionally, I've added the following lines in /etc/dhclient.conf based on what I've read on an another thread in this forum:
Code:
interface "wlan0" {
        supersede interface-mtu 0;
}

The issue is that I can't ping any host (including the gateway) which is surprising since the wireless card is able to obtain an IP address and scan nearby networks successfully.
Additionally, running the command "service netif restart" results in a kernel panic.
I tried this things with no success:
  • configuring a static IP
  • pinging the IPs instead of the hostnames (it still doesn't work so I think it's not a DNS issue)
  • etc.
Here's the output of "uname -a":
Code:
FreeBSD lumarans30 14.0-RELEASE FreeBSD 14.0-RELEASE #0 releng/14.0-n265380-f9716eee8ab4: Fri Nov 10 05:57:23 UTC 2023     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

Now I'm writing this post using USB Tethering which seems to work fine, only by using mobile data though.

Apologies for the lenghty post - I'm trying to include all the potentially relevant details.

Thank you for your patience.

Best Regards,
Andrea Marano
 
I've also noticed that during the boot, it says "wpa: no link......." but then it changes the flag of the wlan0 interface to UP and dhclient succeeds to get the IP. Could the output of dmesg be usuful?
 
The issue is that I can't ping any host (including the gateway) which is surprising since the wireless card is able to obtain an IP address and scan nearby networks successfully.
A bit of a long shot but does the AP perhaps have whitelist that only allows known MAC addresses? Although I would expect the AP to refuse to even associate if the MAC was blocked. It's something that might throw a spanner in the works.

You could run wpa_supplicant(8) with the -d option from the console. Maybe that will show some additional diagnostic messages.
 
pinging a working same subnet ip will get you "host is down" or nothing ?
a host is down means arp wont work a "nothing" means arp has worked but no reply
 
A bit of a long shot but does the AP perhaps have whitelist that only allows known MAC addresses? Although I would expect the AP to refuse to even associate if the MAC was blocked. It's something that might throw a spanner in the works.

You could run wpa_supplicant(8) with the -d option from the console. Maybe that will show some additional diagnostic messages.
wpa_supplicant configured the interface successfully. The NIC is associated and dhclient obtained an IP address. This suggests another issue beyond association and grabbing an IP. Try running tcpdump on the NIC to see if any packets are dropped. Also, do you have any firewall rules? What are in the logs?
 
Wow, thank you all! I didn't expect this many replies.
A bit of a long shot but does the AP perhaps have whitelist that only allows known MAC addresses? Although I would expect the AP to refuse to even associate if the MAC was blocked. It's something that might throw a spanner in the works.

You could run wpa_supplicant(8) with the -d option from the console. Maybe that will show some additional diagnostic messages.
I don't think that there's a MAC whitelist on the AP because I am able to connect to the network with any device as long as I authenticate with my identity and password.
However, I can't confirm this because I don't have access to the AP admin page.
The command "wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf" outputs:
Code:
wpa_supplicant v2.10
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
Priority group 0
   id=0 ssid='UnicamEasyWiFi'
wpa_driver_bsd_capa: drivercaps=0x0581c001,cryptocaps=0x00000000
bsd_ctrl_iface: if wlan0 (no change) enable 0 IFF_UP 0 
Add interface wlan0 to a new radio N/A
PTKSA: Initializing
wlan0: Failed to attach pkt_type filter
wlan0: Own MAC address: 28:cd:c4:5c:bb:b7
bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=0
bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=1
bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=2
bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=3
bsd_set_key: alg=0 addr=0x0 key_idx=4 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=4
ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
bsd_set_key: alg=0 addr=0x0 key_idx=5 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=5
ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
wpa_driver_bsd_set_countermeasures: enabled=0
wlan0: RSN: flushing PMKID list in the driver
wlan0: Setting scan request: 0.100000 sec
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
TDLS: Driver does not support TDLS channel switching
wlan0: WPS: UUID based on MAC address: a126e127-9978-5829-8634-0fa1ec9b8a02
ENGINE: Loading builtin engines
ENGINE: Loading builtin engines
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
ctrl_interface_group=0 (from group name 'wheel')
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=DISCONNECTED
TDLS: Tear down peers
wlan0: State: DISCONNECTED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_driver_bsd_set_countermeasures: enabled=0
PTKSA: Deinit. n_ptksa=0
wlan0: WPA: Clear old PMK and PTK
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Remove interface wlan0 from radio 
Remove radio 
wpa_driver_bsd_set_wpa: enabled=0
wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0
bsd_set_opt_ie: set WPA+RSN ie (len 0)
bsd_ctrl_iface: if wlan0 (no change) enable 0 IFF_UP 0 
wpa_driver_bsd_set_wpa_internal: wpa=2 privacy=1

pinging a working same subnet ip will get you "host is down" or nothing ?
a host is down means arp wont work a "nothing" means arp has worked but no reply
When I ping another device within the same subnet, I get the following response:
Code:
PING 10.156.203.123 (10.156.203.123): 56 data bytes
ping: sendto: Network is down
ping: sendto: Network is down
ping: sendto: Network is down
ping: sendto: Network is down
ping: sendto: Network is down
ping: sendto: Network is down
--- 10.156.203.123 ping statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss

However, when I ping an external host like 1.1.1.1, the command doesn't output anything but still I get 100% packet loss.

for WPA-EAP you need trusted certificate.
That's strange, on my Linux machine I checked the "no ca cert" option and it worked fine. I think that PEAP doesn't require a client-side cert.

wpa_supplicant configured the interface successfully. The NIC is associated and dhclient obtained an IP address. This suggests another issue beyond association and grabbing an IP. Try running tcpdump on the NIC to see if any packets are dropped. Also, do you have any firewall rules? What are in the logs?
I shouldn't have any firewall rules. I checked this by executing the command "pfctl -sr" (it says "/dev/pf: No such file or directory")
The command "tcpdump -i wlan0" gave me the following output:
Code:
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
22:14:56.320872 IP 10.0.26.168.16343 > 8.8.8.8.domain: 64052+ A? 0.freebsd.pool.ntp.org. (40)
22:14:56.618929 ARP, Request who-has 10.0.8.204 tell 10.0.8.204, length 48
22:14:56.962533 IP 10.0.26.168.43200 > 8.8.8.8.domain: 50301+ PTR? 168.26.0.10.in-addr.arpa. (42)
22:14:57.314412 IP 10.0.26.168.ntp > 212.6.50.243.ntp: NTPv4, Client, length 48
22:14:57.314429 IP 10.0.26.168.ntp > 85.199.214.99.ntp: NTPv4, Client, length 48
22:15:00.312280 IP 10.0.26.168.ntp > 217.61.62.224.ntp: NTPv4, Client, length 48
22:15:01.034982 ARP, Reply 10.0.8.171 is-at a4:83:e7:92:e4:fd (oui Unknown), length 42
22:15:01.352910 IP 10.0.26.168.16343 > 8.8.8.8.domain: 64052+ A? 0.freebsd.pool.ntp.org. (40)
22:15:01.965276 IP 10.0.26.168.43200 > 8.8.8.8.domain: 50301+ PTR? 168.26.0.10.in-addr.arpa. (42)
22:15:04.309114 IP 10.0.26.168.ntp > 162.159.200.1.ntp: NTPv4, Client, length 48
22:15:05.139350 ARP, Reply 10.0.8.103 is-at 92:dd:8a:bc:15:88 (oui Unknown), length 42
22:15:07.333344 IP 10.0.26.168.ntp > 93.94.88.51.ntp: NTPv4, Client, length 48
22:15:09.645484 ARP, Reply 10.0.0.107 is-at d6:84:5a:28:0f:6f (oui Unknown), length 42
22:15:11.317235 IP 10.0.26.168.ntp > 93.94.88.50.ntp: NTPv4, Client, length 48
22:15:11.393248 IP 10.0.26.168.44821 > 8.8.8.8.domain: 61759+ AAAA? 0.freebsd.pool.ntp.org. (40)
22:15:11.970357 IP 10.0.26.168.65032 > 8.8.8.8.domain: 27405+ PTR? 8.8.8.8.in-addr.arpa. (38)
22:15:15.714886 IP6 fe80::b45e:7474:9d2e:e967 > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::b45e:7474:9d2e:e967, length 32
22:15:16.674406 IP 10.0.26.168.44821 > 8.8.8.8.domain: 61759+ AAAA? 0.freebsd.pool.ntp.org. (40)
22:15:16.687189 IP6 fe80::f04a:d50f:b7c8:2dcf > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f04a:d50f:b7c8:2dcf, length 32
22:15:17.283571 IP 10.0.26.168.65032 > 8.8.8.8.domain: 27405+ PTR? 8.8.8.8.in-addr.arpa. (38)
22:15:17.378056 IP6 fe80::e813:c836:eff:3c42 > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::e813:c836:eff:3c42, length 32
22:15:26.733304 IP 10.0.26.168.22216 > 8.8.8.8.domain: 35322+ A? 0.freebsd.pool.ntp.org.Studenti.Amministrazione.Unicam. (72)
22:15:27.383996 IP 10.0.26.168.29003 > 8.8.8.8.domain: 43868+ PTR? 204.8.0.10.in-addr.arpa. (41)
22:15:27.642780 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 0, length 64
22:15:28.676873 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 1, length 64
22:15:29.699551 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 2, length 64
22:15:29.809724 IP6 fe80::43f1:e1ba:e0c9:ec94 > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::43f1:e1ba:e0c9:ec94, length 32
22:15:30.254682 IP6 fe80::2118:de9b:93ff:fdad > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::2118:de9b:93ff:fdad, length 32
22:15:30.762734 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 3, length 64
22:15:31.802345 IP 10.0.26.168.22216 > 8.8.8.8.domain: 35322+ A? 0.freebsd.pool.ntp.org.Studenti.Amministrazione.Unicam. (72)
22:15:31.825727 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 4, length 64
22:15:32.475048 IP 10.0.26.168.29003 > 8.8.8.8.domain: 43868+ PTR? 204.8.0.10.in-addr.arpa. (41)
22:15:32.888716 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 5, length 64
22:15:33.242144 IP6 fe80::1956:7df6:9b4e:9df0 > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::1956:7df6:9b4e:9df0, length 32
22:15:33.951713 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 6, length 64
22:15:35.014703 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 7, length 64
22:15:35.769154 IP6 fe80::2118:de9b:93ff:fdad > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::2118:de9b:93ff:fdad, length 32
22:15:36.077694 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 8, length 64
22:15:37.140691 IP 10.0.26.168 > 1.1.1.1: ICMP echo request, id 56073, seq 9, length 64
22:15:42.009606 IP 10.0.26.168.42801 > 8.8.8.8.domain: 12759+ AAAA? 0.freebsd.pool.ntp.org.Studenti.Amministrazione.Unicam. (72)
22:15:43.556404 IP 10.0.26.168.10945 > 8.8.8.8.domain: 61481+ PTR? 243.50.6.212.in-addr.arpa. (43)
22:15:47.016121 IP 10.0.26.168.42801 > 8.8.8.8.domain: 12759+ AAAA? 0.freebsd.pool.ntp.org.Studenti.Amministrazione.Unicam. (72)
22:15:47.997719 ARP, Request who-has 10.0.26.168 (28:cd:c4:5c:bb:b7 (oui Unknown)) tell 0.0.0.0, length 46
180 packets received by filter
0 packets dropped by kernel

Do you mean the boot logs? If so, here's the output of "dmesg | grep rtw880":
Code:
rtw880: <rtw_8822ce> port 0x2000-0x20ff mem 0xd1600000-0xd160ffff at device 0.0 on pci4
rtw880: could not load firmware image 'rtw88/rtw8822c_fw.bin'
rtw880: failed to request firmware
rtw880: failed to load firmware
rtw880: failed to setup chip efuse info
rtw880: failed to setup chip information
device_attach: rtw880 attach returned 22
rtw880: <rtw_8822ce> port 0x2000-0x20ff mem 0xd1600000-0xd160ffff at device 0.0 on pci4
rtw880: successfully loaded firmware image 'rtw88/rtw8822c_fw.bin'
rtw880: Firmware version 9.9.10, H2C version 15
rtw880: timed out to flush queue 2
rtw880: <rtw_8822ce> port 0x2000-0x20ff mem 0xd1600000-0xd160ffff at device 0.0 on pci4
rtw880: could not load firmware image 'rtw88/rtw8822c_fw.bin'
rtw880: failed to request firmware
rtw880: failed to load firmware
rtw880: failed to setup chip efuse info
rtw880: failed to setup chip information
device_attach: rtw880 attach returned 22
rtw880: <rtw_8822ce> port 0x2000-0x20ff mem 0xd1600000-0xd160ffff at device 0.0 on pci4
rtw880: successfully loaded firmware image 'rtw88/rtw8822c_fw.bin'
rtw880: Firmware version 9.9.10, H2C version 15
 
Kill all wpa_supplicant processes then try again to run
wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf

Most likely the RADIUS server is not updated and still use TLS1.0/1.1 which is not supported anymore due to MD5-SHA1 was dropped in default CipherString of OpenSSL 3.x

You can try this:

Code:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
ap_scan=1
fast_reauth=1

network={
        ssid="myssid"
        scan_ssid=0
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="myidentity"
        password="mypassword"
        ca_cert="/etc/cert/ca.pem"
        phase1="tls_disable_tlsv1_0=0 tls_disable_tlsv1_1=0 peaplabel=0"
        phase2="auth=MSCHAPV2"
}

IF you don't specify CA certificate using "ca_cert" it will be ignored (accept any server certificate) which is not recommended as you may connect to rogue AP with the same SSID which can intercept your username and password.
 
Kill all wpa_supplicant processes then try again to run
wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf

Most likely the RADIUS server is not updated and still use TLS1.0/1.1 which is not supported anymore due to MD5-SHA1 was dropped in default CipherString of OpenSSL 3.x

You can try this:

Code:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
ap_scan=1
fast_reauth=1

network={
        ssid="myssid"
        scan_ssid=0
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="myidentity"
        password="mypassword"
        ca_cert="/etc/cert/ca.pem"
        phase1="tls_disable_tlsv1_0=0 tls_disable_tlsv1_1=0 peaplabel=0"
        phase2="auth=MSCHAPV2"
}

IF you don't specify CA certificate using "ca_cert" it will be ignored (accept any server certificate) which is not recommended as you may connect to rogue AP with the same SSID which can intercept your username and password.
Hi, I killed the wpa_supplicant process, modified the conf and ran the command. However, when I ran the command I got a kernel panic.

EDIT: I ran the command again after the reboot and this time it didn't give me any errors but the wlan0 interface is not connected to the network.
Here's the output of "ifconfig wlan0":
Code:
wlan0: flags=8c02<BROADCAST,DRV_OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=0
        ether 28:cd:c4:5c:bb:b7
        inet 10.0.18.138 netmask 0xfffff000 broadcast 10.0.31.255
        groups: wlan
        ssid "" channel 11 (2462 MHz 11g)
        regdomain ETSI country IT authmode WPA1+WPA2/802.11i privacy ON
        deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS wme
        roaming MANUAL
        parent interface: rtw880
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

And "wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf":
Code:
wpa_supplicant v2.10
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=2
ap_scan=1
fast_reauth=1
Priority group 0
   id=0 ssid='UnicamEasyWiFi'
wpa_driver_bsd_capa: drivercaps=0x0581c001,cryptocaps=0x00000000
bsd_ctrl_iface: if wlan0 (no change) enable 0 IFF_UP 0  
Add interface wlan0 to a new radio N/A
PTKSA: Initializing
wlan0: Failed to attach pkt_type filter
wlan0: Own MAC address: 28:cd:c4:5c:bb:b7
bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=0
bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=1
bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=2
bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=3
bsd_set_key: alg=0 addr=0x0 key_idx=4 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=4
ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
bsd_set_key: alg=0 addr=0x0 key_idx=5 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=5
ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
wpa_driver_bsd_set_countermeasures: enabled=0
wlan0: RSN: flushing PMKID list in the driver
wlan0: Setting scan request: 0.100000 sec
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
TDLS: Driver does not support TDLS channel switching
wlan0: WPS: UUID based on MAC address: a126e127-9978-5829-8634-0fa1ec9b8a02
ENGINE: Loading builtin engines
ENGINE: Loading builtin engines
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=DISCONNECTED
TDLS: Tear down peers
wlan0: State: DISCONNECTED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_driver_bsd_set_countermeasures: enabled=0
PTKSA: Deinit. n_ptksa=0
wlan0: WPA: Clear old PMK and PTK
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Remove interface wlan0 from radio  
Remove radio  
wpa_driver_bsd_set_wpa: enabled=0
wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0
bsd_set_opt_ie: set WPA+RSN ie (len 0)
bsd_ctrl_iface: if wlan0 (no change) enable 0 IFF_UP 0  
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1

Perhaps reinstalling the operating system could solve the problem? Is it possible that some files got corrupted during the installation?
 
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore Failed to initialize control interface '/var/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
Not sure if it will do anything but did you try what the output suggested?
 
You have wpa_supplicant running at background so you can't see the log messages when you run it again. Stop wpa_supplicant process first then start it manually so you can see the actual error and not this:

Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
 
Not sure if it will do anything but did you try what the output suggested?
Thanks for the suggestion, I followed the output instructions but after a reboot it still doesn't work.
You have wpa_supplicant running at background so you can't see the log messages when you run it again. Stop wpa_supplicant process first then start it manually so you can see the actual error and not this:
Sorry, I've just realized that I made an error in the last reply. After killing the wpa_supplicant process I got a kernel panic. However, after the reboot I ran the same command, but I forgot that wpa_supplicant was running and that is why I did not have a kernel panic.
 
I just noticed a strange thing, after I login if I run the ping command fast enough it works (I can ping 8.8.8.8) but after a few seconds it stops working.
 
The tcpdump output shows packets being sent but receiving no replies.

"Failed to attach pkt_type filter" suggests it's losing carrier.

Are you sure you need phase1 in your wpa_supplicant.conf?

Has the site admin given you the parameters to associate?
 
Back
Top