You are not logged in.

#1 2022-03-30 01:31:36

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

[solved?] netctl wpa connection (intel 8265/827) & unknown wep params

I've started having problems with my internet connection when other devices don't experience difficulties. This has been happening for at least a couple of days, but possibly a bit longer. It didn't follow any update or configuration changes.

This is a laptop connecting wirelessly using netctl. I'm using the netctl-auto@.service and netctl-ifplugd@.service:

lrwxrwxrwx 1 root root 44 Hyd   1  2017 '/etc/systemd/system/multi-user.target.wants/netctl-auto@wlan0.service' -> '/usr/lib/systemd/system/netctl-auto@.service'
lrwxrwxrwx 1 root root 47 Hyd   1  2017 '/etc/systemd/system/multi-user.target.wants/netctl-ifplugd@eth0.service' -> '/usr/lib/systemd/system/netctl-ifplugd@.service'

When I look at the status of netctl-auto@wlan0.service, I see complaints about unrecognised parameters.

● netctl-auto@wlan0.service - Automatic wireless network connection using netctl profiles
     Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2022-03-29 20:41:10 BST; 5h 31min ago
       Docs: man:netctl.special(7)
    Process: 583 ExecStart=/usr/bin/netctl-auto start wlan0 (code=exited, status=0/SUCCESS)
      Tasks: 3 (limit: 9372)
     Memory: 10.9M
        CPU: 1.569s
     CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlan0.service
             ├─ 711 wpa_supplicant -q -B -P /run/wpa_supplicant-wlan0.pid -i wlan0 -D nl80211,wext -c/run/netctl/wpa_supplicant-wlan0.conf -W
             ├─ 715 wpa_cli -i wlan0 -p /run/wpa_supplicant -B -a /usr/lib/netctl/auto.action
             └─1622 dhclient -4 -q -e TIMEOUT=30 -pf /run/dhclient-wlan0-4.pid wlan0

Maw 29 20:41:10 MyComputer netctl-auto[657]: Included profile 'stradey'
Maw 29 20:41:10 MyComputer netctl-auto[663]: Included profile 'cartrefrees'
Maw 29 20:41:10 MyComputer netctl-auto[670]: Line 51: unknown network field 'wep_tx_keyidx'.
Maw 29 20:41:10 MyComputer netctl-auto[670]: Line 51: unsupported WEP parameter
Maw 29 20:41:10 MyComputer netctl-auto[670]: Line 52: unknown network field 'wep_key0'.
Maw 29 20:41:10 MyComputer netctl-auto[670]: Line 52: unsupported WEP parameter
Maw 29 20:41:10 MyComputer systemd[1]: Started Automatic wireless network connection using netctl profiles.
Maw 29 20:41:57 MyComputer dhclient[1622]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 29 20:41:57 MyComputer dhclient[1622]: DHCPACK of 192.168.0.10 from 192.168.0.1
Maw 29 20:41:57 MyComputer dhclient[1622]: bound to 192.168.0.10 -- renewal in 33431 seconds.

I've updated the system and the firmware, which I hope will help, but I'm still seeing complaints about unrecognised parameters from netctl.

I assumed I had something mistaken or outdated in one of the profiles in /etc/netctl, but the parameters in question aren't in any of those files. Nor are they mentioned in any of the hooks etc. The only place I've found them so far is in /usr/lib/netctl/wpa, which I suppose ought to be correct?

## Generate a network block for wpa_supplicant
# $Security: type of wireless security
wpa_make_config_block() {
    case $Security in
      none)
        echo "key_mgmt=NONE"
      ;;
      wep)
        echo "key_mgmt=NONE"
        echo "wep_tx_keyidx=0"
        if [[ $Key == +([[:xdigit:]][[:xdigit:]]) ]]; then
            echo "wep_key0=$Key"
        else
            echo "wep_key0=$(wpa_quote "$Key")"
        fi
      ;;
      wpa)
        echo "key_mgmt=WPA-PSK SAE"
        echo "ieee80211w=1"
        if [[ "${#Key}" -eq 64 && $Key == +([[:xdigit:]]) ]]; then
            echo "psk=$Key"
        else
            echo "psk=$(wpa_quote "$Key")"
        fi
      ;;
      wpa-configsection)
        printf '%s\n' "${WPAConfigSection[@]}"
        return
      ;;
      *)
        report_error "Unsupported security setting: '$Security'"
        return 1
      ;;
    esac

    echo "ssid=$(wpa_quote "$ESSID")"
    [[ $AP ]] && echo "bssid=${AP,,}"
    is_yes "${Hidden:-no}" && echo "scan_ssid=1"
    is_yes "${AdHoc:-no}" && echo "mode=1"
    [[ $ScanFrequencies ]] && echo "scan_freq=$ScanFrequencies"
    [[ $Frequency ]] && echo "frequency=$Frequency"
    [[ $Priority ]] && echo "priority=$Priority"
}

I'm not using wep in any case - both the networks I've used at all recently use some form of wpa. (Well, eduroam is complicated but it is certainly not using wep.) So I'm not sure this has anything to do with my problems connecting, but are these complaints expected or am I looking in the wrong place for the problem?

EDIT

I'm using intel wifi, so I don't think this is connected by the recent kernel regression affecting the module for Atheros.

03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

Last edited by cfr (2022-04-08 18:47:52)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#2 2022-03-30 05:36:00

seth
Member
Registered: 2012-09-03
Posts: 29,931

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

https://bbs.archlinux.org/viewtopic.php … 8#p2024988

Edit: looking at /run/netctl/wpa_supplicant-wlan0.conf might give you a clue what profile is causes those.

Last edited by seth (2022-03-30 05:40:52)

Offline

#3 2022-03-30 05:36:41

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

It seems to be worse now I've updated everything. What's worse yet is restarting netctl-auto@wlan0.service isn't often working and neither is restarting netctl.service.

Here's a portion of the journal:

Maw 30 06:18:27 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:09
Maw 30 06:18:27 MyComputer kernel: wlan0: bad VHT capabilities, disabling VHT
Maw 30 06:18:27 MyComputer kernel: wlan0: 80 MHz not supported, disabling VHT
Maw 30 06:18:27 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:18:27 MyComputer kernel: wlan0: authenticated
Maw 30 06:18:27 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:18:27 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:09 (capab=0x1431 status=0 aid=2)
Maw 30 06:18:27 MyComputer kernel: wlan0: associated
Maw 30 06:18:27 MyComputer dhclient[6075]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:18:27 MyComputer dhclient[6075]: DHCPACK of 192.168.0.10 from 192.168.0.1
Maw 30 06:18:27 MyComputer avahi-daemon[487]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:18:27 MyComputer avahi-daemon[487]: New relevant interface wlan0.IPv4 for mDNS.
Maw 30 06:18:27 MyComputer avahi-daemon[487]: Registering new address record for 192.168.0.10 on wlan0.IPv4.
Maw 30 06:18:27 MyComputer dhclient[6075]: bound to 192.168.0.10 -- renewal in 42742 seconds.
Maw 30 06:18:28 MyComputer kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 18:35:d1:c8:ec:09
Maw 30 06:18:31 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
Maw 30 06:18:31 MyComputer dhclient[6097]: Killed old client process
Maw 30 06:18:31 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:18:31 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:18:31 MyComputer kernel: wlan0: authenticated
Maw 30 06:18:31 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:18:31 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:18:31 MyComputer kernel: wlan0: associated
Maw 30 06:18:31 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:18:32 MyComputer avahi-daemon[487]: Withdrawing address record for 192.168.0.10 on wlan0.
Maw 30 06:18:32 MyComputer avahi-daemon[487]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:18:32 MyComputer avahi-daemon[487]: Interface wlan0.IPv4 no longer relevant for mDNS.
Maw 30 06:18:32 MyComputer dhclient[6097]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:18:35 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:18:49 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:18:49 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:18:49 MyComputer kernel: wlan0: authenticated
Maw 30 06:18:49 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:18:49 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:18:49 MyComputer kernel: wlan0: associated
Maw 30 06:18:49 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:18:53 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:19:17 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:19:17 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:19:17 MyComputer kernel: wlan0: authenticated
Maw 30 06:19:17 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:19:17 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:19:17 MyComputer kernel: wlan0: associated
Maw 30 06:19:17 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:19:21 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:20:25 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:09
Maw 30 06:20:25 MyComputer kernel: wlan0: bad VHT capabilities, disabling VHT
Maw 30 06:20:25 MyComputer kernel: wlan0: 80 MHz not supported, disabling VHT
Maw 30 06:20:25 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:20:25 MyComputer kernel: wlan0: authenticated
Maw 30 06:20:25 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:20:25 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:09 (capab=0x1431 status=0 aid=3)
Maw 30 06:20:25 MyComputer kernel: wlan0: associated
Maw 30 06:20:25 MyComputer dhclient[6146]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:20:25 MyComputer dhclient[6146]: DHCPACK of 192.168.0.10 from 192.168.0.1
Maw 30 06:20:25 MyComputer avahi-daemon[487]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:20:25 MyComputer avahi-daemon[487]: New relevant interface wlan0.IPv4 for mDNS.
Maw 30 06:20:25 MyComputer avahi-daemon[487]: Registering new address record for 192.168.0.10 on wlan0.IPv4.
Maw 30 06:20:25 MyComputer dhclient[6146]: bound to 192.168.0.10 -- renewal in 42555 seconds.
Maw 30 06:20:26 MyComputer kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 18:35:d1:c8:ec:09
Maw 30 06:20:29 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
Maw 30 06:20:29 MyComputer dhclient[6169]: Killed old client process
Maw 30 06:20:29 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:20:29 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:20:29 MyComputer kernel: wlan0: authenticated
Maw 30 06:20:29 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:20:29 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:20:29 MyComputer kernel: wlan0: associated
Maw 30 06:20:29 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:20:30 MyComputer avahi-daemon[487]: Withdrawing address record for 192.168.0.10 on wlan0.
Maw 30 06:20:30 MyComputer avahi-daemon[487]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:20:30 MyComputer avahi-daemon[487]: Interface wlan0.IPv4 no longer relevant for mDNS.
Maw 30 06:20:30 MyComputer dhclient[6169]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:20:33 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:20:45 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:20:45 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:20:45 MyComputer kernel: wlan0: authenticated
Maw 30 06:20:45 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:20:45 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:20:45 MyComputer kernel: wlan0: associated
Maw 30 06:20:45 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:20:49 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:21:11 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:21:11 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:21:11 MyComputer kernel: wlan0: authenticated
Maw 30 06:21:11 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:21:11 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:21:11 MyComputer kernel: wlan0: associated
Maw 30 06:21:11 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:21:15 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:22:18 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:09
Maw 30 06:22:18 MyComputer kernel: wlan0: bad VHT capabilities, disabling VHT
Maw 30 06:22:18 MyComputer kernel: wlan0: 80 MHz not supported, disabling VHT
Maw 30 06:22:18 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:22:18 MyComputer kernel: wlan0: authenticated
Maw 30 06:22:18 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:22:19 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:09 (capab=0x1431 status=0 aid=3)
Maw 30 06:22:19 MyComputer kernel: wlan0: associated
Maw 30 06:22:19 MyComputer dhclient[6208]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:22:19 MyComputer dhclient[6208]: DHCPACK of 192.168.0.10 from 192.168.0.1
Maw 30 06:22:19 MyComputer avahi-daemon[487]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:22:19 MyComputer avahi-daemon[487]: New relevant interface wlan0.IPv4 for mDNS.
Maw 30 06:22:19 MyComputer avahi-daemon[487]: Registering new address record for 192.168.0.10 on wlan0.IPv4.
Maw 30 06:22:19 MyComputer dhclient[6208]: bound to 192.168.0.10 -- renewal in 37302 seconds.
Maw 30 06:22:20 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
Maw 30 06:22:20 MyComputer dhclient[6230]: Killed old client process
Maw 30 06:22:20 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:22:20 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:22:20 MyComputer kernel: wlan0: authenticated
Maw 30 06:22:20 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:22:20 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:22:20 MyComputer kernel: wlan0: associated
Maw 30 06:22:21 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:22:21 MyComputer avahi-daemon[487]: Withdrawing address record for 192.168.0.10 on wlan0.
Maw 30 06:22:21 MyComputer avahi-daemon[487]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:22:21 MyComputer avahi-daemon[487]: Interface wlan0.IPv4 no longer relevant for mDNS.
Maw 30 06:22:21 MyComputer dhclient[6230]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:22:24 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)

Am I right in thinking it is (1) trying to use ip6 and (2) reducing power of something or other? If so, how do I stop (1) and is (2) problematic?

Here's where it succeeds for no obvious reason I can discern:

Maw 30 06:33:53 MyComputer dhclient[7461]: bound to 192.168.0.10 -- renewal in 42067 seconds.
Maw 30 06:33:55 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
Maw 30 06:33:55 MyComputer dhclient[7482]: Killed old client process
Maw 30 06:33:55 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f
Maw 30 06:33:55 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:33:55 MyComputer kernel: wlan0: authenticated
Maw 30 06:33:55 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:0f (try 1/3)
Maw 30 06:33:55 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:0f (capab=0x1511 status=0 aid=1)
Maw 30 06:33:55 MyComputer kernel: wlan0: associated
Maw 30 06:33:55 MyComputer kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 18:35:d1:c8:ec:0f
Maw 30 06:33:56 MyComputer avahi-daemon[487]: Withdrawing address record for 192.168.0.10 on wlan0.
Maw 30 06:33:56 MyComputer avahi-daemon[487]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:33:56 MyComputer avahi-daemon[487]: Interface wlan0.IPv4 no longer relevant for mDNS.
Maw 30 06:33:56 MyComputer dhclient[7482]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:33:59 MyComputer kernel: wlan0: disassociated from 18:35:d1:c8:ec:0f (Reason: 2=PREV_AUTH_NOT_VALID)
Maw 30 06:34:07 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:f696:34ff:fedc:aaf5 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=807438 PROTO=UDP SPT=5353 DPT=5353 LEN=44 
Maw 30 06:34:13 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:09
Maw 30 06:34:13 MyComputer kernel: wlan0: bad VHT capabilities, disabling VHT
Maw 30 06:34:13 MyComputer kernel: wlan0: 80 MHz not supported, disabling VHT
Maw 30 06:34:13 MyComputer kernel: wlan0: send auth to 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:34:13 MyComputer kernel: wlan0: authenticated
Maw 30 06:34:13 MyComputer kernel: wlan0: associate with 18:35:d1:c8:ec:09 (try 1/3)
Maw 30 06:34:13 MyComputer kernel: wlan0: RX AssocResp from 18:35:d1:c8:ec:09 (capab=0x1431 status=0 aid=3)
Maw 30 06:34:13 MyComputer kernel: wlan0: associated
Maw 30 06:34:13 MyComputer dhclient[7498]: DHCPREQUEST for 192.168.0.10 on wlan0 to 255.255.255.255 port 67
Maw 30 06:34:13 MyComputer dhclient[7498]: DHCPACK of 192.168.0.10 from 192.168.0.1
Maw 30 06:34:13 MyComputer avahi-daemon[487]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.10.
Maw 30 06:34:13 MyComputer avahi-daemon[487]: New relevant interface wlan0.IPv4 for mDNS.
Maw 30 06:34:13 MyComputer avahi-daemon[487]: Registering new address record for 192.168.0.10 on wlan0.IPv4.
Maw 30 06:34:13 MyComputer dhclient[7498]: bound to 192.168.0.10 -- renewal in 33093 seconds.
Maw 30 06:34:13 MyComputer kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 18:35:d1:c8:ec:09
Maw 30 06:34:34 MyComputer kernel: IN=wlan0 OUT= MAC= SRC=192.168.0.10 DST=255.255.255.255 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=49720 DF PROTO=UDP SPT=21327 DPT=21327 LEN=120 

I take it the avahi-daemon stuff is irrelevant but I wasn't completely sure, so I've included it anyway.

Last edited by cfr (2022-03-30 05:43:01)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#4 2022-03-30 05:47:29

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 8#p2024988

Edit: looking at /run/netctl/wpa_supplicant-wlan0.conf might give you a clue what profile is causes those.

Ah, that explains it. I don't think that's the cause of my problems, though? My home network (which I was using when I took the stuff from the journal above) is using WPA2. It is absolutely not using WEP as I've not used that for years on any network I have any control over.

Thanks for pointing me to the /run/netctl/ conf file. That let me track it down and disable the profile. It seems that any netctl profile containing
[config]
Security=wep
[/config]
will trigger the error? If I understand correctly, this is because wpa_supplicant no longer knows how to use wep unless either you set something in a configuration file somewhere or you compile it with a non-default setting. I haven't figured out which of those at the moment, because I don't currently need it and will be all too happy to never need wep again.

But I would be kidding myself if I thought this was all there is to my connection problems, wouldn't I? I mean, the problematic profile isn't one I've used in years. I think it predates my far-from-new laptop. So those errors can't explain why I keep having trouble on my WPA2 network?

Last edited by cfr (2022-03-30 05:59:47)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#5 2022-03-30 05:52:45

seth
Member
Registered: 2012-09-03
Posts: 29,931

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

I'd try to connect w/ wpa_supplicant and the desired profile directly, sidestepping netctl-auto, to see whether the connection still goes wild.

Offline

#6 2022-03-30 06:02:57

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

seth wrote:

I'd try to connect w/ wpa_supplicant and the desired profile directly, sidestepping netctl-auto, to see whether the connection still goes wild.

OK. Thanks. I'll do that next time it happens and report back. I don't know whether to hope that's soon (so I can sort it out before the enormous batch of online marking comes in) or not (so I can hope the problem goes away on its own).


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#7 2022-03-30 06:37:47

seth
Member
Registered: 2012-09-03
Posts: 29,931

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

If the situation is intermittent, I'd suspect
1. conflicting services
2. wonky connection
3. iffiness

Maw 30 06:18:31 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
…
Maw 30 06:18:31 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f

It moves from one AP to another and all "PREV_AUTH_NOT_VALID" are from 18:35:d1:c8:ec:0f - so check which AP that is since it's the one that's causing you troubles.

Offline

#8 2022-03-30 17:24:12

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

seth wrote:

If the situation is intermittent, I'd suspect
1. conflicting services

Thanks for this list. I have checked for this and I'm pretty sure I don't have anything conflicting. NetworkManager is installed because I use KDE, but

lrwxrwxrwx 1 root root    9 Hyd   4  2017 NetworkManager.service -> /dev/null

2. wonky connection

This definitely happens at times, but my laptop is having issues even when other devices do fine, including one which historically has a harder time picking up the wifi signal than the laptop. So I don't think it is the LAN in this case.

3. iffiness

By process of elimination?

Maw 30 06:18:31 MyComputer kernel: wlan0: Connection to AP 18:35:d1:c8:ec:09 lost
…
Maw 30 06:18:31 MyComputer kernel: wlan0: authenticate with 18:35:d1:c8:ec:0f

It moves from one AP to another and all "PREV_AUTH_NOT_VALID" are from 18:35:d1:c8:ec:0f - so check which AP that is since it's the one that's causing you troubles.

Are these are MAC addresses? Will look into this as there should be only one access point, provided by my ISP's router. There's no booster or similar, so it shouldn't be trying to connect to anything else on this network and it isn't configured to attempt connection to any other network available here. (The others are all for when I'm somewhere else and I'm well out of range for those.)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#9 2022-03-30 19:13:47

seth
Member
Registered: 2012-09-03
Posts: 29,931

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

Are these are MAC addresses?

Yes, of access points. They should™ show up in your profiles as well as on a wifi scan - maybe 2.4/5GHz with differen MACs/SSIDs?
AP mode in your smartphone?

Offline

#10 2022-04-01 19:21:32

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

seth wrote:

Yes, of access points. They should™ show up in your profiles as well as on a wifi scan - maybe 2.4/5GHz with differen MACs/SSIDs?
AP mode in your smartphone?

They don't show up in the profiles that I can find, but they do show up in a scan. They seem to be 2.4/5GHz on different channels with the same SSID?

...
        Cell 02 - Address: 18:35:D1:C8:EC:09
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=40/70  Signal level=-70 dBm  
                    Encryption key:on
                    ESSID:"My Network"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000b836a54a12
                    Extra: Last beacon: 367ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030106
                    IE: Unknown: 0706474220010D14
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown: 460573D000000C
                    IE: Unknown: 2D1AAD011BFFFF0000000000000000000001000000000406E6A70C00
                    IE: Unknown: 3D1606000500000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0805000F0200000040
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0900037F01010000FF7F
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
...
         Cell 06 - Address: 18:35:D1:C8:EC:0F
                    Channel:44
                    Frequency:5.22 GHz (Channel 44)
                    Quality=35/70  Signal level=-75 dBm  
                    Encryption key:on
                    ESSID:"My Network"
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000b83a5e0fba
                    Extra: Last beacon: 97ms ago
                    IE: Unknown: 000C436172747265662052656573
                    IE: Unknown: 01088C129824B048606C
                    IE: Unknown: 03012C
                    IE: Unknown: 073C4742202401172801172C01173001173401173801173C011740011764011E68011E6C011E70011E74011E78011E7C011E80011E84011E88011E8C011E
                    IE: Unknown: 460573D000000C
                    IE: Unknown: 2D1AEF091BFFFFFF0000000000000000000100000000000000000000
                    IE: Unknown: 3D162C050000000000000000000000000000000000000000
                    IE: Unknown: 7F0804000F0200000040
                    IE: Unknown: BF0CB2018033EAFF0000EAFF0000
                    IE: Unknown: C005012A00FCFF
                    IE: Unknown: C30402D2D2D2
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0900037F01010000FF7F
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
...

'My Network' is a substitution, but it's the same SSID in each.

So is the router advertising wifi on two different channels at different speeds but, for some reason, I can only authenticate to one?

Neither MAC seems to correspond with the MAC printed on the label on the bottom of the router and I don't really understand how it could have two?

Last edited by cfr (2022-04-01 19:23:04)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#11 2022-04-01 20:44:07

seth
Member
Registered: 2012-09-03
Posts: 29,931

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

18:35:d1:c8:ec:0f is the 5GHz MAC and netctl wants to connect to it but fails (you probably have different passwords configured for the two frequencies?)

Neither MAC seems to correspond with the MAC printed on the label

"Papier ist geduldig"… you should log into the router and check its configuration there. (In reality, the MAC might have changed w/ an update)
You could either
* align the credentials for the 5GHz and 2.4GHz AP (so you can log into either)
* disable the 5GHz connection (though on short range, you'll have more throughput there)
* upgrade your netctl profile to contain "AP=18:35:D1:C8:EC:09" to restrict netctl to only access that AP

Offline

#12 2022-04-07 14:49:51

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

seth wrote:

You could either
* align the credentials for the 5GHz and 2.4GHz AP (so you can log into either)
* disable the 5GHz connection (though on short range, you'll have more throughput there)
* upgrade your netctl profile to contain "AP=18:35:D1:C8:EC:09" to restrict netctl to only access that AP

Thanks. Managed to forget password and have delayed resetting router in hope I'd get through marking first but losing stuff I've done is too frustrating. Have now reset router and reconfigured it. The security definitely now matches for the two APs. So I'll see how that goes. I think I'm probably a bit far from the router for 5GHz but we'll see.


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#13 2022-04-08 18:46:26

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,145

Re: [solved?] netctl wpa connection (intel 8265/827) & unknown wep params

It *seems* netctl is now connecting successfully to both `09` and `0f` so I *think* this is solved. I'm just cautious because I didn't really identify the problem. I certainly hadn't configured the router to use different credentials for different speeds. (And nobody else would have configured it to do anything.)

Thanks for all the help. I wouldn't have figured this out even in a roundabout way without somebody telling me what the logs meant. I thought MAC addresses went with devices for some reason so it never occurred to me the thing might have two. And I wasn't really sure they were MACs .... (Still not very clear what distinguishes MACs from IPv6 addresses etc., though IPv6 isn't really a thing yet around here.)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

Board footer

Powered by FluxBB