Connected to a smartphone used as modem something avoid to reach the net.
Using hotspot or tethering similar message:
Networks
WiFi: Connected to moto g9 (my smartphone)2537 G (limited connectivity).
Middle click to turn on Aeroplane Mode
I get the same message when I connect to my printer using wi-fi connection.
Note that with the same hardware and phone using LinuxMint works normally.
Do you routinely use the WiFi interface with another router and does it work?
I guess there is something wrong with the firewall setup, try disabling it just for a quick test and check if you can reach the internet.
Check the firewall…
sudo firewall-cmd --get-active-zones
You may need to activate the smartphone connection first so that its interface and assigned firewall zone appear in the output.
Stopped firewall with ~> sudo systemctl stop firewalld still " limited connectivity".
~> sudo firewall-cmd --get-active-zones
[sudo] password di root:
docker
interfaces: docker0
public (default)
interfaces: wlp3s0
Ok, this looks like tested while using Wi-Fi connectivity.
Can you post the output of…
ip a
ip r
Also nmcli dev show wlp3s0 | grep -E 'IP4.DNS|IP4.GATEWAY'
Yes, connected to smartphone via wifi.
~> 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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 70:5a:0f:94:1d:d7 brd ff:ff:ff:ff:ff:ff
altname enx705a0f941dd7
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:1c:a8:48:b1:b7 brd ff:ff:ff:ff:ff:ff
altname wlx441ca848b1b7
inet 10.47.206.184/24 brd 10.47.206.255 scope global dynamic noprefixroute wlp3s0
valid_lft 2975sec preferred_lft 2975sec
inet6 fe80::cd8:a6ce:ff8f:d934/64 scope link noprefixroute
valid_lft forever preferred_lft forever
~> ip r
default via 10.47.206.229 dev wlp3s0 proto dhcp src 10.47.206.184 metric 20600
10.47.206.0/24 dev wlp3s0 proto kernel scope link src 10.47.206.184 metric 600
:~> nmcli dev show wlp3s0 | grep -E 'IP4.DNS|IP4.GATEWAY'
IP4.GATEWAY: 10.47.206.229
IP4.DNS[1]: 10.47.206.229
That output looks ok. Show the results from
ping -c 3 10.47.206.229
ping -c 3 8.8.8.8
ping -c 3 google.com
It might be just the NetworkManager connectivity check that is failing.
~> ping -c 3 10.47.206.229
PING 10.47.206.229 (10.47.206.229) 56(84) bytes of data.
64 bytes from 10.47.206.229: icmp_seq=1 ttl=64 time=12.9 ms
64 bytes from 10.47.206.229: icmp_seq=2 ttl=64 time=5.23 ms
64 bytes from 10.47.206.229: icmp_seq=3 ttl=64 time=3.07 ms
--- 10.47.206.229 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 3.073/7.055/12.859/4.197 ms
~> ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=178 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=200 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=223 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 178.023/200.310/222.583/18.191 ms
~> ping -c 3 google.com
ping: google.com: Temporary failure in name resolution
Ok, so there is a name resolution issue at play. Check whether the phone is actually answering DNS requests, and also try another DNS server…
dig @10.47.206.229 google.com
dig @8.8.8.8 google.com
This should tell us whether the DNS service provided by the smartphone is the problem.
Not so clear to me what it means but note that at present my smartphone is connected with two pc, the one wich connection isn’t working and my pc I’m using to write here.
~> dig @10.47.206.229 google.com
; <<>> DiG 9.20.26 <<>> @10.47.206.229 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21510
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: b71d2a1e7bce9637010000006abcc6ea847ac4e927be48fd (good)
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 73 IN A 192.178.194.138
google.com. 73 IN A 192.178.194.102
google.com. 73 IN A 192.178.194.139
google.com. 73 IN A 192.178.194.100
google.com. 73 IN A 192.178.194.101
google.com. 73 IN A 192.178.194.113
;; Query time: 253 msec
;; SERVER: 10.47.206.229#53(10.47.206.229) (UDP)
;; WHEN: Wed Sep 30 10:23:02 CEST 2026
;; MSG SIZE rcvd: 163
~> dig @8.8.8.8 google.com
; <<>> DiG 9.20.26 <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58285
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 16 IN A 192.178.194.139
google.com. 16 IN A 192.178.194.100
google.com. 16 IN A 192.178.194.113
google.com. 16 IN A 192.178.194.101
google.com. 16 IN A 192.178.194.138
google.com. 16 IN A 192.178.194.102
;; Query time: 173 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Wed Sep 30 10:23:17 CEST 2026
;; MSG SIZE rcvd: 135
Ok, both respond correctly, but the ping command failed.
What is shown by
cat /etc/resolv.conf
Maybe the following as well…
grep '^hosts:' /etc/nsswitch.conf
grep '^hosts:' /usr/etc/nsswitch.conf
Sorry for delay in answer but in the meantime I changed smartphone and I had several problems to solve to make it working normally. Aniway problem with limited connectivity remain.
:~> cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
~> grep '^hosts:' /etc/nsswitch.conf
hosts: files mdns_minimal [NOTFOUND=return] dns
~> grep '^hosts:' /usr/etc/nsswitch.conf
hosts: files dns
Something broken in your system… check if cat /run/netconfig/resolv.conf reports nothing too.
This isn’t as expected. Do
sudo ln -sf /run/NetworkManager/resolv.conf /etc/resolv.conf
then verify name resolution is now working
ping -c 3 google.com
~> cat /run/netconfig/resolv.conf
cat: /run/netconfig/resolv.conf: No such file or directory
~> ping -c 3 google.com
PING google.com (192.178.194.100) 56(84) bytes of data.
64 bytes from mu-in-f100.1e100.net (192.178.194.100): icmp_seq=1 ttl=109 time=203 ms
64 bytes from mu-in-f100.1e100.net (192.178.194.100): icmp_seq=2 ttl=109 time=51.6 ms
64 bytes from mu-in-f100.1e100.net (192.178.194.100): icmp_seq=3 ttl=109 time=62.3 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 51.596/105.713/203.251/69.107 ms
May be the simplest way to solve this problem is reinstall Tumbleweed?
No! That is not the way to solve issues like this.
Anyway, your last shared ping results were successful. Did you create the link as I suggested?
I agree but not always there is enough time to solve in “logical” way nor there is a valid expert that can find a solution. As an example I have a big problem that is still unsolved.
You’re right. I’m writing from my friend’s pc. Then problem solved but not clear to me which is the solution.
I don’t saw any link suggested. Sorry.
If you refer to sudo ln -sf /run/NetworkManager/resolv.conf /etc/resolv.conf yes I did it.
…And???
Show the current state (don’t leave us to guess)
ls -l /etc/resolv.conf
cat /etc/resolv.conf
ping -c 3 google.com
If that now works with the hotspot connection, all is well with name resolution?
Never ever 
:~> ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 31 Sep 30 23:43 /etc/resolv.conf -> /run/NetworkManager/resolv.conf
~> cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.230.106
~> ping -c 3 google.com
PING google.com (192.178.194.102) 56(84) bytes of data.
64 bytes from mu-in-f102.1e100.net (192.178.194.102): icmp_seq=1 ttl=109 time=42.8 ms
64 bytes from mu-in-f102.1e100.net (192.178.194.102): icmp_seq=2 ttl=109 time=55.7 ms
64 bytes from mu-in-f102.1e100.net (192.178.194.102): icmp_seq=3 ttl=109 time=53.6 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 42.763/50.698/55.712/5.675 ms