[SOLVED] Wifi connected but no network access

anarki@buttereblume · 2023-07-06 13:53:17

I'm connected to a WPA2 network 'BertaBlock-Guests' using iwd and iwlwifi. While dhcp works and ip and gateway are configured, there is no network access. Ping and traceroute to e.g. the networks gateway do not return anything.

My phone running LineageOS however can connect to the same network without issues. I use it as access point while typing this.

Output of networkctl status -a while directly connected to the network in question:

 
● 3: wlp59s0
                     Link File: /usr/lib/systemd/network/99-default.link
                  Network File: /etc/systemd/network/wifi.network
                         State: routable (configured)
                  Online state: online
                          Type: wlan
                          Path: pci-0000:3b:00.0
                        Driver: iwlwifi
                        Vendor: Intel Corporation
                         Model: Wireless 8265 / 8275 (Dual Band Wireless-AC 8265)
              Hardware Address: 74:e5:f9:64:52:08 (Intel Corporate)
                           MTU: 1500 (min: 256, max: 2304)
                         QDisc: noqueue
  IPv6 Address Generation Mode: eui64
             WiFi access point: BertaBlock-Guests (02:ec:da:3f:48:1b)
      Number of Queues (Tx/Rx): 1/1
                       Address: 10.10.0.170 (DHCP4 via 10.10.0.1)
                                fe80::76e5:f9ff:fe64:5208
                       Gateway: 10.10.0.1
                           DNS: 10.10.0.1
             Activation Policy: up
           Required For Online: yes
               DHCP4 Client ID: IAID:0xb50c77d7/DUID
             DHCP6 Client DUID: DUID-EN/Vendor:0000ab116daded9b649acd890000

Jul 06 14:43:15 butterblume systemd-networkd[5042]: wlp59s0: Connected WiFi access point: BertaBlock-Guests (02:ec:da:3f:48:1b)
Jul 06 14:43:15 butterblume systemd-networkd[5042]: wlp59s0: Gained carrier
Jul 06 14:43:15 butterblume systemd-networkd[5042]: wlp59s0: Reconfiguring with /etc/systemd/network/wifi.network.
Jul 06 14:43:15 butterblume systemd-networkd[5042]: wlp59s0: DHCPv6 lease lost
Jul 06 14:43:15 butterblume systemd-networkd[5042]: wlp59s0: DHCPv4 address 10.10.0.170/16, gateway 10.10.0.1 acquired from 10.10.0.1

The only difference I discovered between dhcp of notebook and phone is the ip region: 10.10.0.X for notebook, 10.10.1.X for phone.

Last edited by anarki@buttereblume (2024-01-24 16:52:17)

seth · 2023-07-06 14:55:48

using iwd and iwlwifi. While dhcp works and ip and gateway are configured

Quick sanity check:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
grep -ri EnableNetworkConfiguration /etc/iwd*

anarki@buttereblume · 2023-07-06 15:37:41

Thanks seth. EnableNetworkConfiguration is not configured in /etc/iwd/main.conf and thereby defaulting to false.

After setting it true, however, I get two ip addresses shown by iwctl:

iwctl station wlp59s0 show
...
            IPv4 address          10.10.0.170
            IPv4 address          10.10.1.7
...

Why does it show multiple ip addresses? The second ip is of the same region like the one of my phone: 10.10.1.X. Looks good, but still no network access.

Is there a dhcp race between iwd and systemd-networkd? The latter is is configured as follows:

cat /etc/systemd/network/wifi.network
[Match]
Name=wlp59s0

[Network]
DHCP=ipv4

[DHCP]
UseDomains=true
RouteMetric=10

Edit: The services you asked for:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
...
iwd.service                              | multi-user.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-resolved.service                 | multi-user.target.wants
wifi.network                             | network
...

Last edited by anarki@buttereblume (2023-07-06 15:42:08)

anarki@buttereblume · 2023-07-06 16:30:02

I now let iwd manage my wifi device:

mv /etc/systemd/network/wifi.network /etc/systemd/network/wifi.networkd

Both iwd and networkctl now show a single ip address that seems right:

iwctl station wlp59s0 show
...
            Connected network     BertaBlock-Guests
            IPv4 address          10.10.1.7
...

Also, systemctl status iwd.service dows not complain about failing to manage DNS entries anymore. But still, no network access at all.

seth · 2023-07-06 19:13:28

You're in 10.10.0.0/16 so 10.10.0.170 and 10.10.1.7 should™ be in the same segment anyway.
systemd-network and iwd won't trip over each other unless you had EnableNetworkConfiguration enabled - I was more concerned that there also was an additional dhcpcd service.

Please post the full outputs of

ip a
ip r

and ideally a complete system journal.

Sicne the gateway apparently responds to ICMP requests and if you're just losing the packages, they're either misrouted or killed in a firewall or the carrier is failing (ie. your wifi chip is yelling errors into the system - hopefully)

Can you ping
* localhost
* 0.0.0.0
* 10.10.1.7

anarki@buttereblume · 2023-07-06 20:40:31

seth wrote:

Please post the full outputs of
ip a
ip r
and ideally a complete system journal.

ip route
default via 10.10.0.1 dev wlp59s0 proto dhcp src 10.10.1.7 metric 303
10.10.0.0/16 dev wlp59s0 proto dhcp scope link metric 3030 metric 1024

ip addr
...
3: wlp59s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 74:e5:f9:64:52:08 brd ff:ff:ff:ff:ff:ff
    inet 10.10.1.7/16 scope global dynamic noprefixroute wlp59s0
       valid_lft 50838sec preferred_lft 50838sec
    inet6 fe80::76e5:f9ff:fe64:5208/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
...

journalctl
...
Jul 06 19:16:41 butterblume iwd[38710]: Terminate
Jul 06 19:16:41 butterblume iwd[38710]: Removing scan context for wdev 1
Jul 06 19:16:41 butterblume systemd[1]: Stopping Wireless service...
Jul 06 19:16:41 butterblume kernel: wlp59s0: deauthenticating from 02:ec:da:3e:48:1b by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 06 19:16:41 butterblume systemd-networkd[27936]: wlp59s0: Link DOWN
Jul 06 19:16:41 butterblume systemd-networkd[27936]: wlp59s0: Lost carrier
Jul 06 19:16:42 butterblume iwd[38710]: Removing scan context for wdev e
Jul 06 19:16:42 butterblume iwd[38710]: D-Bus disconnected, quitting...
Jul 06 19:16:42 butterblume systemd[1]: iwd.service: Deactivated successfully.
Jul 06 19:16:42 butterblume systemd[1]: Stopped Wireless service.
Jul 06 19:16:42 butterblume systemd[1]: Starting Wireless service...
Jul 06 19:16:42 butterblume iwd[38995]: Wireless daemon version 2.6
Jul 06 19:16:42 butterblume iwd[38995]: Loaded configuration from /etc/iwd/main.conf
Jul 06 19:16:42 butterblume systemd[1]: Started Wireless service.
Jul 06 19:16:42 butterblume iwd[38995]: Wiphy: 0, Name: phy0
Jul 06 19:16:42 butterblume iwd[38995]:         Permanent Address: 74:e5:f9:64:52:08
Jul 06 19:16:42 butterblume iwd[38995]:         2.4Ghz Band:
Jul 06 19:16:42 butterblume iwd[38995]:                 Bitrates (non-HT):
Jul 06 19:16:42 butterblume iwd[38995]:                          1.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                          2.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                          5.5 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         11.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                          6.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                          9.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         12.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         18.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         24.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         36.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         48.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         54.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                 HT Capabilities:
Jul 06 19:16:42 butterblume iwd[38995]:                         HT40
Jul 06 19:16:42 butterblume iwd[38995]:                         Short GI for 20Mhz
Jul 06 19:16:42 butterblume iwd[38995]:                         Short GI for 40Mhz
Jul 06 19:16:42 butterblume iwd[38995]:                 HT RX MCS indexes:
Jul 06 19:16:42 butterblume iwd[38995]:                         0-15
Jul 06 19:16:42 butterblume iwd[38995]:         5Ghz Band:
Jul 06 19:16:42 butterblume iwd[38995]:                 Bitrates (non-HT):
Jul 06 19:16:42 butterblume iwd[38995]:                          6.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                          9.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         12.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         18.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         24.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         36.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         48.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                         54.0 Mbps
Jul 06 19:16:42 butterblume iwd[38995]:                 HT Capabilities:
Jul 06 19:16:42 butterblume iwd[38995]:                         HT40
Jul 06 19:16:42 butterblume iwd[38995]:                         Short GI for 20Mhz
Jul 06 19:16:42 butterblume iwd[38995]:                         Short GI for 40Mhz
Jul 06 19:16:42 butterblume iwd[38995]:                 HT RX MCS indexes:
Jul 06 19:16:42 butterblume iwd[38995]:                         0-15
Jul 06 19:16:42 butterblume iwd[38995]:                 VHT Capabilities:
Jul 06 19:16:42 butterblume iwd[38995]:                         Short GI for 80Mhz
Jul 06 19:16:42 butterblume iwd[38995]:                         Max RX MCS: 0-9 for NSS: 2
Jul 06 19:16:42 butterblume iwd[38995]:                         Max TX MCS: 0-9 for NSS: 2
Jul 06 19:16:42 butterblume iwd[38995]:         Ciphers: BIP-CMAC-128 CCMP-128 TKIP
Jul 06 19:16:42 butterblume iwd[38995]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Jul 06 19:16:42 butterblume iwd[38995]: Wiphy phy0 will only use the default interface
Jul 06 19:16:42 butterblume sudo[38988]: pam_unix(sudo:session): session closed for user root
Jul 06 19:16:42 butterblume systemd-networkd[27936]: wlp59s0: Link UP
Jul 06 19:16:44 butterblume iwd[38995]: wiphy_estimate_data_rate() failed
Jul 06 19:16:44 butterblume iwd[38995]: wiphy_estimate_data_rate() failed
Jul 06 19:16:44 butterblume kernel: wlp59s0: authenticate with 02:ec:da:3f:48:1b
Jul 06 19:16:44 butterblume kernel: wlp59s0: send auth to 02:ec:da:3f:48:1b (try 1/3)
Jul 06 19:16:44 butterblume kernel: wlp59s0: authenticated
Jul 06 19:16:44 butterblume kernel: wlp59s0: associate with 02:ec:da:3f:48:1b (try 1/3)
Jul 06 19:16:44 butterblume kernel: wlp59s0: RX AssocResp from 02:ec:da:3f:48:1b (capab=0x1501 status=0 aid=9)
Jul 06 19:16:44 butterblume systemd-networkd[27936]: wlp59s0: Connected WiFi access point: BertaBlock-Guests (02:ec:da:3f:48:1b)
Jul 06 19:16:44 butterblume iwd[38995]: [DHCPv4] l_dhcp_client_start:1219 Entering state: DHCP_STATE_SELECTING
Jul 06 19:16:44 butterblume kernel: wlp59s0: associated
Jul 06 19:16:44 butterblume iwd[38995]: [DHCPv4] dhcp_client_handle_offer:811 Entering state: DHCP_STATE_REQUESTING
Jul 06 19:16:44 butterblume systemd-networkd[27936]: wlp59s0: Gained carrier
Jul 06 19:16:44 butterblume kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
Jul 06 19:16:44 butterblume iwd[38995]: [DHCPv4] dhcp_client_rx_message:915 Entering state: DHCP_STATE_BOUND
Jul 06 19:16:44 butterblume iwd[38995]: [DHCPv4] dhcp_client_rx_message:948 T1 expiring in 23290301 ms
Jul 06 19:16:44 butterblume systemd-timesyncd[545]: Network configuration changed, trying to establish connection.
Jul 06 19:16:44 butterblume systemd-resolved[27939]: wlp59s0: Bus client set DNS server list to: 10.10.0.1
Jul 06 19:16:44 butterblume kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 02:ec:da:3f:48:1b
Jul 06 19:16:45 butterblume systemd-networkd[27936]: wlp59s0: Gained IPv6LL
Jul 06 19:16:54 butterblume systemd-timesyncd[545]: Timed out waiting for reply from 212.18.3.19:123 (0.arch.pool.ntp.org).
Jul 06 19:17:05 butterblume systemd-timesyncd[545]: Timed out waiting for reply from 185.120.22.12:123 (0.arch.pool.ntp.org).
...

networkctl status -a
...
● 3: wlp59s0
                     Link File: /usr/lib/systemd/network/99-default.link
                  Network File: n/a
                         State: routable (unmanaged)
                  Online state: unknown
                          Type: wlan
                          Path: pci-0000:3b:00.0
                        Driver: iwlwifi
                        Vendor: Intel Corporation
                         Model: Wireless 8265 / 8275 (Dual Band Wireless-AC 8265)
              Hardware Address: 74:e5:f9:64:52:08 (Intel Corporate)
                           MTU: 1500 (min: 256, max: 2304)
                         QDisc: noqueue
  IPv6 Address Generation Mode: eui64
             WiFi access point: BertaBlock-Guests (02:ec:da:3e:48:1b)
      Number of Queues (Tx/Rx): 1/1
...

The latter outputs show a state of wlp59s0 unmanaged by systemd-networkd and with

/etc/iwd/main.conf
EnableNetworkConfiguration=true

Edit: Fixed formatting

Last edited by anarki@buttereblume (2023-07-09 09:40:56)

anarki@buttereblume · 2023-07-06 20:52:33

seth wrote:

Can you ping
* localhost
* 0.0.0.0
* 10.10.1.7

Don't have access to that network anymore. Will do next time.

seth · 2023-07-06 21:19:02

Full "ip a", the ellipsis suggest there're NIC #2 (ethernet?) and #4 (VPN? Docker?)

The formatting is kinda messed up, but the 4th code block holds a copy of the complete(?) post where there's an extra

10.10.0.1 dev wlp59s0 proto dhcp scope link src 10.10.0.170 metric 1024

route and the metric of the default route differs.
Meanwhile the segment route has "proto kernel" in all versions what suggests a different source.

Don't get creative with this, post the actual and complete outputs, notably of the enabled services ip a and ip r.
If you're changing the config of the running system (though there's probably little point, there's no indication so far of you not getting a dhcp lease at all) check ip a/r inbetween to make sure there're no stale static entries.
You also didn't address the FW situation.

Edit: in case you're doing something stupid like manually transcribing this because the internet doesn't work: don't! Dump the outputs into files and usb-walk them to an online system or use https://wiki.archlinux.org/title/Tethering

Last edited by seth (2023-07-06 21:20:29)

anarki@buttereblume · 2023-07-09 09:51:42

seth wrote:

The formatting is kinda messed up, but the 4th code block holds a copy of the complete(?) post where there's an extra
10.10.0.1 dev wlp59s0 proto dhcp scope link src 10.10.0.170 metric 1024
route and the metric of the default route differs.

This code block was a false paste. It represents a state where wlp59s0 was managed by systemd-networkd. I fixed formatting and removed redundant code blocks. Please have a look again.

The code shown of

ip route

is the full output and not shortened.

seth wrote:

Full "ip a", the ellipsis suggest there're NIC #2 (ethernet?) and #4 (VPN? Docker?)

Yes, #2 is a disabled ethernet device, which actually has no corresponding jack on X280 and #4 is a OpenVPN managed tun0.

Thanks for your help.

seth · 2023-07-09 10:15:03

seth wrote:

Can you ping
* localhost
* 0.0.0.0
* 10.10.1.7

and certainly disable the VPN for this test.

And post the complete command outputs, not isolated to a spcific NIC.
Chances are, something else gets in the way (and for now I'll just speculate that it's the VPN)

anarki@buttereblume · 2024-01-24 16:51:26

Solved: The whole issue was a gateway at an obscure ip asking to accept terms of usage.

Arch Linux

#1 2023-07-06 13:53:17

[SOLVED] Wifi connected but no network access

#2 2023-07-06 14:55:48

Re: [SOLVED] Wifi connected but no network access

#3 2023-07-06 15:37:41

Re: [SOLVED] Wifi connected but no network access

#4 2023-07-06 16:30:02

Re: [SOLVED] Wifi connected but no network access

#5 2023-07-06 19:13:28

Re: [SOLVED] Wifi connected but no network access

#6 2023-07-06 20:40:31

Re: [SOLVED] Wifi connected but no network access

#7 2023-07-06 20:52:33

Re: [SOLVED] Wifi connected but no network access

#8 2023-07-06 21:19:02

Re: [SOLVED] Wifi connected but no network access

#9 2023-07-09 09:51:42

Re: [SOLVED] Wifi connected but no network access

#10 2023-07-09 10:15:03

Re: [SOLVED] Wifi connected but no network access

#11 2024-01-24 16:51:26

Re: [SOLVED] Wifi connected but no network access

Board footer