Arch Linux

teagum

Member

Registered: 2024-11-07

Posts: 7

Only IPv6 route for wlan

I noticed that I suddenly cannot reach certain sites, like duckduckgo.com for example. I believe the reason for that is that I have only IPv6 address for my wlan connection. What do I have to configure to also get connected over IPv4?

I use NetworkManager with systemd-resolved. Both services are up and running and did not report any errors. I can successfully connect to a wlan network. There aren't any other connections.

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 20:1e:88:5d:5b:24 brd ff:ff:ff:ff:ff:ff
    inet6 2a02:8108:3083:b00:dd5f:d1f2:bead:97dd/64 scope global dynamic noprefixroute
       valid_lft 6992sec preferred_lft 3392sec
    inet6 fe80::692a:c872:8a32:b6c4/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

ip -6 r

2a02:8108:3083:b00::/64 dev wlan0 proto ra metric 600 pref medium
2a02:8108:3083:b00::/64 via fe80::de15:c8ff:fe33:a0f8 dev wlan0 proto ra metric 605 pref medium
fe80::/64 dev wlan0 proto kernel metric 1024 pref medium
default via fe80::de15:c8ff:fe33:a0f8 dev wlan0 proto ra metric 600 pref medium

systemctl status systemd-resolved

● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-01-23 11:16:43 CET; 48min ago
 Invocation: d08ba742ff3f467e91d144f13ccaa9b8
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             [url]https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS[/url]
             [url]https://systemd.io/WRITING_RESOLVER_CLIENTS[/url]
   Main PID: 343 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 37902)
     Memory: 7.5M (peak: 8.4M)
        CPU: 247ms
     CGroup: /system.slice/systemd-resolved.service
             └─343 /usr/lib/systemd/systemd-resolved

Jan 23 11:20:29 starfish systemd-resolved[343]: wlan0: Bus client set default route setting: no
Jan 23 11:20:29 starfish systemd-resolved[343]: wlan0: Bus client reset DNS server list.
Jan 23 11:20:30 starfish systemd-resolved[343]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Jan 23 11:20:38 starfish systemd-resolved[343]: wlan0: Bus client set default route setting: yes
Jan 23 11:20:38 starfish systemd-resolved[343]: wlan0: Bus client set DNS server list to: fd00::de15:c8ff:fe33:a0f8, 2a02:8108:3083:b00:de15:c8ff:fe33:a0f8
Jan 23 11:40:50 starfish systemd-resolved[343]: wlan0: Bus client set default route setting: no
Jan 23 11:40:50 starfish systemd-resolved[343]: wlan0: Bus client reset DNS server list.
Jan 23 11:40:51 starfish systemd-resolved[343]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Jan 23 11:40:56 starfish systemd-resolved[343]: wlan0: Bus client set default route setting: yes
Jan 23 11:40:56 starfish systemd-resolved[343]: wlan0: Bus client set DNS server list to: fd00::de15:c8ff:fe33:a0f8, 2a02:8108:3083:b00:de15:c8ff:fe33:a0f8

systemctl status NetworkManager

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Thu 2025-01-23 11:40:51 CET; 26min ago
 Invocation: b73baee5aefb496a88bb179d4e5fb00e
       Docs: man:NetworkManager(8)
   Main PID: 4672 (NetworkManager)
      Tasks: 4 (limit: 37902)
     Memory: 4M (peak: 5M)
        CPU: 399ms
     CGroup: /system.slice/NetworkManager.service
             └─4672 /usr/bin/NetworkManager --no-daemon

Jan 23 11:40:56 starfish NetworkManager[4672]: <info>  [1737628856.1622] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 11:40:56 starfish NetworkManager[4672]: <info>  [1737628856.1626] policy: set 'Salvation' (wlan0) as default for IPv6 routing and DNS
Jan 23 11:40:56 starfish NetworkManager[4672]: <info>  [1737628856.1669] dhcp6 (wlan0): state changed new lease
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5010] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5036] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5038] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5043] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5058] device (wlan0): Activation: successful, device activated.
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5069] manager: startup complete
Jan 23 11:40:57 starfish NetworkManager[4672]: <info>  [1737628857.5975] manager: NetworkManager state is now CONNECTED_GLOBAL

Last edited by teagum (2025-01-24 06:22:16)

-thc

Member

Registered: 2017-03-15

Posts: 803

Re: Only IPv6 route for wlan

Either your Fritz!Box doesn't provide you with an IPv4 address or your Arch box no longer accepts one.

Can you verify that other devices in your home are IPv4 capable?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,118

Re: Only IPv6 route for wlan

Moderator side note, please wrap the actual outputs in code tags as well instead of quote

teagum

Member

Registered: 2024-11-07

Posts: 7

Re: Only IPv6 route for wlan

I am connect over IPv4 on the wifi at work. I also get an IPv4 address in my home network when I use my phone as man in the middle and connect to its hotspot. So all in all it seems that this is a problem with my home network.

-thc

Member

Registered: 2017-03-15

Posts: 803

Re: Only IPv6 route for wlan

That seems to be the case. Look into the configuration of your Fritz!Box and check all IPv4 parameters.