Internet seemingly throttled despite expected ping and speedtest-cli outputs

can you post your /etc/resolv.conf,
and a nmcli connection result?

192.168.1.254 is the default gateway for my ethernet and wifi

# cat /etc/resolv.conf

# Generated by NetworkManager
search home
nameserver 192.168.1.254
# nmcli connection

NAME              UUID                                  TYPE      DEVICE 
Ethernet          d8c1ad64-98d6-339f-848b-dd56d67375c8  ethernet  eno1   
Laura Hotspot     a7495e19-9cf9-4720-94c6-d9fa64e1782f  wifi      wlan0  
Wifi              fa789ab6-c80a-43de-b488-047aba7d701a  wifi      --    

what is nmcli con show "Ethernet" |grep P4 and nmcli con show "Laura Hotspot" |grep P4 ?

# nmcli con show "Ethernet" | grep P4

IP4.ADDRESS[1]:                         192.168.1.203/24
IP4.GATEWAY:                            192.168.1.254
IP4.ROUTE[1]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 192.168.1.254, mt = 100
IP4.DNS[1]:                             8.8.8.8
IP4.DNS[2]:                             192.168.1.254
IP4.DOMAIN[1]:                          home
DHCP4.OPTION[1]:                        broadcast_address = 192.168.1.255
DHCP4.OPTION[2]:                        dhcp_client_identifier = 01:48:ba:4e:b3:ea:e6
DHCP4.OPTION[3]:                        dhcp_lease_time = 86400
DHCP4.OPTION[4]:                        dhcp_server_identifier = 192.168.1.254
DHCP4.OPTION[5]:                        domain_name = home
DHCP4.OPTION[6]:                        domain_name_servers = 192.168.1.254
DHCP4.OPTION[7]:                        expiry = 1722980464
DHCP4.OPTION[8]:                        host_name = pigeon
DHCP4.OPTION[9]:                        ip_address = 192.168.1.203
DHCP4.OPTION[10]:                       next_server = 192.168.1.254
DHCP4.OPTION[11]:                       requested_broadcast_address = 1
DHCP4.OPTION[12]:                       requested_domain_name = 1
DHCP4.OPTION[13]:                       requested_domain_name_servers = 1
DHCP4.OPTION[14]:                       requested_domain_search = 1
DHCP4.OPTION[15]:                       requested_host_name = 1
DHCP4.OPTION[16]:                       requested_interface_mtu = 1
DHCP4.OPTION[17]:                       requested_ms_classless_static_routes = 1
DHCP4.OPTION[18]:                       requested_nis_domain = 1
DHCP4.OPTION[19]:                       requested_nis_servers = 1
DHCP4.OPTION[20]:                       requested_ntp_servers = 1
DHCP4.OPTION[21]:                       requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[22]:                       requested_root_path = 1
DHCP4.OPTION[23]:                       requested_routers = 1
DHCP4.OPTION[24]:                       requested_static_routes = 1
DHCP4.OPTION[25]:                       requested_subnet_mask = 1
DHCP4.OPTION[26]:                       requested_time_offset = 1
DHCP4.OPTION[27]:                       requested_wpad = 1
DHCP4.OPTION[28]:                       routers = 192.168.1.254
DHCP4.OPTION[29]:                       subnet_mask = 255.255.255.0
DHCP4.OPTION[30]:                       wpad = 

nmcli con show "Laura Hotspot" | grep P4 seems to return nothing

does nmcli con show "Laura Hotspot" return something?

# nmcli con show "Laura Hotspot"

connection.id:                          Laura Hotspot
connection.uuid:                        a7495e19-9cf9-4720-94c6-d9fa64e1782f
connection.stable-id:                   --
connection.type:                        802-11-wireless
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        0
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   1722895031
connection.permissions:                 user:laura
connection.zone:                        --
connection.controller:                  --
connection.master:                      --
connection.slave-type:                  --
connection.port-type:                   --
connection.autoconnect-slaves:          -1 (default)
connection.autoconnect-ports:           -1 (default)
connection.down-on-poweroff:            -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
connection.dns-over-tls:                -1 (default)
connection.mptcp-flags:                 0x0 (default)
connection.wait-device-timeout:         -1
connection.wait-activation-delay:       -1
802-11-wireless.ssid:                   laura's phone
802-11-wireless.mode:                   infrastructure
802-11-wireless.band:                   --
802-11-wireless.channel:                0
802-11-wireless.bssid:                  --
802-11-wireless.mac-address:            --
802-11-wireless.cloned-mac-address:     --
802-11-wireless.generate-mac-address-mask:--
802-11-wireless.mac-address-denylist:   --
802-11-wireless.mac-address-randomization:default
802-11-wireless.mtu:                    auto
802-11-wireless.seen-bssids:            FA:F3:AD:ED:B2:05
802-11-wireless.hidden:                 no
802-11-wireless.powersave:              0 (default)
802-11-wireless.wake-on-wlan:           0x1 (default)
802-11-wireless.ap-isolation:           -1 (default)
802-11-wireless-security.key-mgmt:      wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:      --
802-11-wireless-security.proto:         --
802-11-wireless-security.pairwise:      --
802-11-wireless-security.group:         --
802-11-wireless-security.pmf:           0 (default)
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:      <hidden>
802-11-wireless-security.wep-key1:      <hidden>
802-11-wireless-security.wep-key2:      <hidden>
802-11-wireless-security.wep-key3:      <hidden>
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  unknown
802-11-wireless-security.psk:           <hidden>
802-11-wireless-security.psk-flags:     1 (agent-owned)
802-11-wireless-security.leap-password: <hidden>
802-11-wireless-security.leap-password-flags:0 (none)
802-11-wireless-security.wps-method:    0x0 (default)
802-11-wireless-security.fils:          0 (default)
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.routing-rules:                     --
ipv4.replace-local-rule:                -1 (default)
ipv4.dhcp-send-release:                 -1 (default)
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-iaid:                         --
ipv4.dhcp-dscp:                         --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.dhcp-hostname-flags:               0x0 (none)
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv4.required-timeout:                  -1 (default)
ipv4.dad-timeout:                       -1 (default)
ipv4.dhcp-vendor-class-identifier:      --
ipv4.link-local:                        0 (default)
ipv4.dhcp-reject-servers:               --
ipv4.auto-route-ext-gw:                 -1 (default)
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       --
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.routing-rules:                     --
ipv6.replace-local-rule:                -1 (default)
ipv6.dhcp-send-release:                 -1 (default)
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.required-timeout:                  -1 (default)
ipv6.ip6-privacy:                       -1 (default)
ipv6.temp-valid-lifetime:               0 (default)
ipv6.temp-preferred-lifetime:           0 (default)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.ra-timeout:                        0 (default)
ipv6.mtu:                               auto
ipv6.dhcp-pd-hint:                      --
ipv6.dhcp-duid:                         --
ipv6.dhcp-iaid:                         --
ipv6.dhcp-timeout:                      0 (default)
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.dhcp-hostname-flags:               0x0 (none)
ipv6.auto-route-ext-gw:                 -1 (default)
ipv6.token:                             --
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --

The config shows that your pc ethernet is configured by dhcp, which is your router, which is also your dns. If you have access to your router’s configuration you might be able to configure the dns settings that the dhcp rolls out to all clients in your network. That is the proper way to set dns. Alternatively you can just edit /etc/resolv.conf and put on first place you nameserver for testing. This will work for testing, but withing some minutes NM will overwrite it. You may stop that by immediately do a chmod 444 /etc/resolv.conf. Not nice, but working for testing. Not for operation.

Your tethering confuses me. No interface name, no config.


Disabling auto dns gives me an option for primary and secondary. I guess I’ll set 8.8.8.8 and see what changes. Is it correct that none of this can have an effect on the fact that my request time out when connected solely to the separate mobile data hotspot?

Well, something is wrong with these tethering settings. In plain theory, each connection is configured separately by NM, so even multiple connections parallel should work because they usually have different priorities. So, these cable settings should not interfere with wifi/tethering settings.

Right. Yeah other than dig -t ANY google.com now giving ns1.google.com as the dns, nothing else seems to have changed, even /etc/resolv.conf is the same.

This shows your internal ip address but it’s not showing your wan ip address. Or did you just not post that?

That’s the entire contents of the file. I haven’t managed to get NetworkManager to add any other ips to it, though it is definitely generated since it reverts any changes I make.

Everything should be automatic. My /etc/resolv.conf shows my internal private ip address and the wan address.

What exactly do you mean by my ip address and the wan address? Addresses of local DNS server and public DNS server?

Okay it’s not the wan address but I’m just saying there are two ip adresses in the file.

The resolver can operate up to three addresses. More does not make sense as they are requested in listed order, with a timeout of about 5 s each. IMHO Multiple nameserver entries make sense if you have options to limit timeout and cause fail rotation in /etc/resolv.conf:

options timeout:1 attempts:1 rotate

This can be configured in NM by

nmcli con mod “NAMEOF THE CONNECTION” ipv4.dns-options “timeout:1 attempts:1 rotate”

That works immediately and writes configuration to NM and propagates it to resolv.conf. Take care for proper syntax of these options, nmcli does not verify them.

It is one of my isp dns servers i guess.

That is only helpful if it is a different one than the one your local dns forwards requests to. If it is the same it does not give any additional security of availability.

1 Like

I resorted to doing this, as even configuring DNS via the GUI settings didn’t help, and it has successfully got the hotspot working. I’m going to do a bunch of mtr tests on different networks (all of which have the slowdown problem) to see what stands out now on 1.1.1.1.

# cat /etc/resolv.conf

# NOT Generated by NetworkManager ANYMORE
search home
nameserver 1.1.1.1

ethernet to home router called Ethernet

[laura@pigeon ~]$ dig google.com

; <<>> DiG 9.20.0 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38288
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             294     IN      A       172.217.169.46

;; Query time: 10 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Tue Aug 06 12:31:35 BST 2024
;; MSG SIZE  rcvd: 55
pigeon (192.168.1.203) -> google.com (142.250.187.238)2024-08-06T12:33:15+0100
                                      Packets               Pings
 Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. _gateway                         0.0%    42    1.0   1.0   0.9   1.3   0.1
 2. (waiting for reply)
 3. 137.hiper04.sheff.dial.plus.net 82.9%    42  3047. 2908. 1017. 5086. 1367.
 4. 136.hiper04.sheff.dial.plus.net  0.0%    42    9.1   8.3   6.9   9.4   0.8
    140.hiper04.sheff.dial.plus.net.uk
 5. peer3-et7-0-2.redbus.ukcore.bt.  0.0%    42   13.5   9.2   7.1  23.3   2.9
    peer8-et3-1-6.telehouse.ukcore.bt.net
    peer7-et-0-1-7.telehouse.ukcore.bt.net
    peer7-et-0-0-2.telehouse.ukcore.bt.net
    peer3-et0-1-7.redbus.ukcore.bt.net
    peer7-et-3-1-5.telehouse.ukcore.bt.net
    peer7-et-0-1-2.telehouse.ukcore.bt.net
    peer3-et0-1-5.redbus.ukcore.bt.net
    peer7-et-3-1-2.telehouse.ukcore.bt.net
 6. 109.159.253.237                  0.0%    41   10.9   9.0   7.4  11.4   1.0
    109.159.253.3
    195.99.126.247
    195.99.126.249
    109.159.253.185
    109.159.253.189
    peer2-xe3-1-3.telehouse.ukcore.bt.net
    142.250.47.6
 7. 192.178.97.189                   0.0%    41    9.0   9.4   8.2  10.7   0.7
    209.85.253.95
    209.85.255.77
    74.125.253.31
    192.178.97.49
    209.85.248.229
    216.239.41.53
    216.239.41.193
 8. 142.251.54.49                    0.0%    41    9.0   8.9   7.9  12.3   0.8
    142.251.54.47
 9. lhr25s34-in-f14.1e100.net        0.0%    41    9.3   8.9   7.6  10.3   0.5
[laura@pigeon ~]$ iperf3 -t 8 -c iperf.as42831.net -p 5300-5400  
Connecting to host iperf.as42831.net, port 5300  
[  5] local 192.168.1.203 port 56168 connected to 31.132.7.130 port 5300  
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd  
[  5]   0.00-1.00   sec  3.00 MBytes  25.2 Mbits/sec    0    166 KBytes
[  5]   1.00-2.00   sec  2.88 MBytes  24.1 Mbits/sec    0    280 KBytes
[  5]   2.00-3.00   sec  2.75 MBytes  23.1 Mbits/sec    0    394 KBytes
[  5]   3.00-4.00   sec  2.75 MBytes  23.1 Mbits/sec    0    506 KBytes
[  5]   4.00-5.00   sec  2.25 MBytes  18.9 Mbits/sec   19    391 KBytes
[  5]   5.00-6.00   sec  2.12 MBytes  17.8 Mbits/sec    0    449 KBytes
[  5]   6.00-7.00   sec  2.12 MBytes  17.8 Mbits/sec    0    492 KBytes
[  5]   7.00-8.00   sec  2.25 MBytes  18.9 Mbits/sec    0    520 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -  
[ ID] Interval           Transfer     Bitrate         Retr  
[  5]   0.00-8.00   sec  20.1 MBytes  21.1 Mbits/sec   19    sender  
[  5]   0.00-8.39   sec  18.1 MBytes  18.1 Mbits/sec         receiver

mobile data hotspot called laura's phone

[laura@pigeon ~]$ dig google.com

; <<>> DiG 9.20.0 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22805
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             78651   IN      A       216.239.38.120

;; Query time: 80 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Tue Aug 06 12:34:57 BST 2024
;; MSG SIZE  rcvd: 44
pigeon (192.168.184.111) -> google.com (216.239.38.1202024-08-06T12:36:53+0100
                                      Packets               Pings
 Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. _gateway                         0.0%    95   37.1  21.4   2.5 126.2  21.8
 2. (waiting for reply)
 3. (waiting for reply)
 4. (waiting for reply)
 5. any-in-2678.1e100.net            0.0%    94   45.4  76.3  32.4 183.9  30.2
[laura@pigeon ~]$ iperf3 -t 8 -c iperf.as42831.net -p 5300-5400  
Connecting to host iperf.as42831.net, port 5300  
[  5] local 192.168.184.111 port 41884 connected to 31.132.7.130 port 5300  
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd  
[  5]   0.00-1.00   sec   256 KBytes  2.10 Mbits/sec    0   65.2 KBytes
[  5]   1.00-2.00   sec   128 KBytes  1.05 Mbits/sec    0   71.8 KBytes
[  5]   2.00-3.00   sec   128 KBytes  1.05 Mbits/sec    0   78.3 KBytes
[  5]   3.00-4.00   sec   128 KBytes  1.05 Mbits/sec    0   86.1 KBytes
[  5]   4.00-5.00   sec   256 KBytes  2.10 Mbits/sec    0   96.5 KBytes
[  5]   5.00-6.00   sec   128 KBytes  1.05 Mbits/sec    0    125 KBytes
[  5]   6.00-7.00   sec   512 KBytes  4.19 Mbits/sec    0    170 KBytes
[  5]   7.00-8.00   sec   256 KBytes  2.10 Mbits/sec    0    222 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -  
[ ID] Interval           Transfer     Bitrate         Retr  
[  5]   0.00-8.00   sec  1.75 MBytes  1.83 Mbits/sec    0    sender  
[  5]   0.00-10.24  sec  1.50 MBytes  1.23 Mbits/sec         receiver  

library wifi called Libraries Guest WiFi

[laura@pigeon ~]$ dig google.com  
  
; <<>> DiG 9.20.0 <<>> google.com  
;; global options: +cmd  
;; Got answer:  
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27956  
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1  
  
;; OPT PSEUDOSECTION:  
; EDNS: version: 0, flags:; udp: 1232  
;; QUESTION SECTION:  
;google.com.                    IN      A  
  
;; ANSWER SECTION:  
google.com.             56      IN      A       172.217.16.238  
  
;; Query time: 84 msec  
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)  
;; WHEN: Tue Aug 06 15:00:08 BST 2024  
;; MSG SIZE  rcvd: 55
pigeon (172.16.84.91) -> google.com (172.217.16.238)   2024-08-06T15:03:21+0100  
                                      Packets               Pings  
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev  
1. _gateway                          0.0%   135    1.5  25.2   0.9 2039. 195.0  
2. 172.18.129.41                     0.0%   134    2.0  18.2   1.0 1027. 123.7  
3. 146.97.181.156                    0.0%   134   60.2  14.3   4.2 1010.  87.0  
4. ae25.erdiss-sbr2.ja.net           0.0%   134    4.6  15.3   4.2 1010.  87.4  
5. ae31.londpg-sbr2.ja.net           0.0%   134    9.8  20.5   8.1 1016.  87.3  
6. ae29.londhx-sbr1.ja.net           0.0%   134    8.6  11.9   8.5  50.8   7.7  
7. 193.62.157.22                     0.0%   134   10.4  50.8   9.9 1039. 193.5  
8. 209.85.249.187                    0.0%   134    9.7  28.5   9.4 1077. 126.9  
   216.239.48.217  
9. 142.251.52.149                    0.0%   134   11.1  21.2  10.7 1021.  87.5  
   142.251.52.151  
10. mad08s04-in-f14.1e100.net         0.0%   134   11.0  12.2   9.1  78.9   8.3
[laura@pigeon ~]$ iperf3 -t 8 -c iperf.as42831.net -p 5300-5400  
Connecting to host iperf.as42831.net, port 5300  
[  5] local 172.16.84.91 port 47050 connected to 31.132.7.130 port 5300  
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd  
[  5]   0.00-1.00   sec  2.75 MBytes  23.0 Mbits/sec    0    145 KBytes
[  5]   1.00-2.00   sec  2.38 MBytes  19.9 Mbits/sec    0    248 KBytes
[  5]   2.00-3.00   sec  2.50 MBytes  21.0 Mbits/sec    0    339 KBytes
[  5]   3.00-4.00   sec  2.75 MBytes  23.1 Mbits/sec    2    199 KBytes
[  5]   4.00-5.00   sec  2.50 MBytes  21.0 Mbits/sec    5    110 KBytes
[  5]   5.00-6.00   sec  2.75 MBytes  23.1 Mbits/sec    0    123 KBytes
[  5]   6.00-7.00   sec  2.12 MBytes  17.8 Mbits/sec    0    136 KBytes
[  5]   7.00-8.00   sec  2.62 MBytes  22.0 Mbits/sec    0    148 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -  
[ ID] Interval           Transfer     Bitrate         Retr  
[  5]   0.00-8.00   sec  20.4 MBytes  21.4 Mbits/sec    7    sender  
[  5]   0.00-8.02   sec  19.4 MBytes  20.3 Mbits/sec         receiver

Hope this helps.