NetworkManager problem in TW
While using Slowroll I set up NetworkManager to connect to my smartphone hot-spot (my ONLY internet connection for the next 2-3 months!). Everything works as expected and I'm posting thois from Slowroll, with these settings (all else being defaults): General config tab: "Connect automatically with priority 0" Wifi tab: shows SSID name with padlock WiFi Security tab: Wpa2 personal password shows on clicking eye "Store pwd for all users (not encrypted) But using the same settings in TW all I get is "Connected but unable to reach the internet" or words to that effect. That's a relatively recent install and there is no other internet connection so I need to fix *it* first. Which files does this dialog edit? Maybe I should compare them. What else can I look at?
On 15.02.2024 15:31, Ben T. Fender wrote:
While using Slowroll I set up NetworkManager to connect to my smartphone hot-spot (my ONLY internet connection for the next 2-3 months!). Everything works as expected and I'm posting thois from Slowroll, with these settings (all else being defaults):
General config tab: "Connect automatically with priority 0"
Wifi tab: shows SSID name with padlock
WiFi Security tab: Wpa2 personal password shows on clicking eye "Store pwd for all users (not encrypted)
But using the same settings in TW all I get is "Connected but unable to reach the internet" or words to that effect.
The only comments about "words to that effect" can be "something may be wrong". Show the actual configuration after connection is established. ip a ip -4 r ip -6 r ping -4 dns.google.com ping -6 dns.google.com ping -4 8.8.8.8 ping -6 2001:4860:4860::8888 ls -l /etc/resolv.conf cat /etc/resolv.conf
That's a relatively recent install and there is no other internet connection so I need to fix *it* first.
Which files does this dialog edit? Maybe I should compare them. What else can I look at?
Thu, 15 Feb 2024 19:41:30 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On 15.02.2024 15:31, Ben T. Fender wrote:
While using Slowroll I set up NetworkManager to connect to my smartphone hot-spot (my ONLY internet connection for the next 2-3 months!). Everything works as expected and I'm posting thois from Slowroll, with these settings (all else being defaults):
General config tab: "Connect automatically with priority 0"
Wifi tab: shows SSID name with padlock
WiFi Security tab: Wpa2 personal password shows on clicking eye "Store pwd for all users (not encrypted)
But using the same settings in TW all I get is "Connected but unable to reach the internet" or words to that effect.
The only comments about "words to that effect" can be "something may be wrong".
(seconds before, booted into Slowroll, same hotspot worked perfectly) "Limited Connectivity. This device appears to be connected to a network but is unable to reach the inmternet."
Show the actual configuration after connection is established.
I had to boot back into Slowroll to be able to send this so at the same time I repeated the commands there.
ip a ======
TW: 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: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether f4:6d: 04:28:43:55 brd ff:ff:ff:ff:ff:ff 3: wlp0s18f2u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c4:41:1e:32:1e:ca brd ff:ff:ff:ff:ff:ff inet 192.168.190.61/24 brd 192.168.190.255 scope global dynamic noprefixroute wlp0s18f2u5 valid_lft 3396sec preferred_lft 3396sec inet6 fe80::88a0:abf4:aab1:b808/64 scope link noprefixroute valid_lft forever preferred_lft forever Slowroll (looks identical): 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: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether f4:6d: 04:28:43:55 brd ff:ff:ff:ff:ff:ff 3: wlp0s18f2u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c4:41:1e:32:1e:ca brd ff:ff:ff:ff:ff:ff inet 192.168.190.61/24 brd 192.168.190.255 scope global dynamic noprefixroute wlp0s18f2u5 valid_lft 3426sec preferred_lft 3426sec inet6 fe80::3c3:6c6c:8ff3:532b/64 scope link noprefixroute valid_lft forever preferred_lft forever
ip -4 r =========
TW: default via 192.168.190.227 dev wlp0s18f2u5 proto dhcp src 192.168.190.61 metric 20600 192.168.190.0/24 dev wlp0s18f2u5 proto kernel scope link src 192.168.190.61 metric 600 Slowroll: default via 192.168.190.227 dev wlp0s18f2u5 proto dhcp src 192.168.190.61 metric 600 192.168.190.0/24 dev wlp0s18f2u5 proto kernel scope link src 192.168.190.61 metric 600
ip -6 r =========
TW: fe80::/64 dev wlp0s18f2u5 proto kernel metric 1024 pref medium Slowroll: fe80::/64 dev wlp0s18f2u5 proto kernel metric 1024 pref medium
ping -4 dns.google.com ========================
TW: no return Slowroll: PING dns.google.com (8.8.4.4) 56(84) bytes of data. 64 bytes from dns.google (8.8.4.4): icmp_seq=1 ttl=113 time=82.0 ms 64 bytes from dns.google (8.8.4.4): icmp_seq=2 ttl=113 time=104 ms 64 bytes from dns.google (8.8.4.4): icmp_seq=3 ttl=113 time=66.0 ms 64 bytes from dns.google (8.8.4.4): icmp_seq=4 ttl=113 time=85.6 ms ^C --- dns.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 66.029/84.526/104.475/13.673 ms
ping -6 dns.google.com ========================
TW: ping: dns.google.com: Temporary failure in name resolution Slowroll: ping: connect: Network is unreachable
ping -4 8.8.8.8 =================
TW: 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=112 time=259 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=112 time=49.5 ms .... 64 bytes from 8.8.8.8: icmp_seq=15 ttl=112 time=72.8 ms ^C --- 8.8.8.8 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 14020ms rtt min/avg/max/mdev = 31.644/67.550/258.579/52.919 ms Slowroll: 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=112 time=113 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=112 time=135 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=112 time=160 ms ^C --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 112.869/135.660/159.596/19.093 ms
ping -6 2001:4860:4860::8888 ==============================
TW: ping: connect: Network is unreachable Slowroll: ping: connect: Network is unreachable
ls -l /etc/resolv.conf ========================
TW: -rw-r--r-- 1 root root 53 Feb 12 18:28 /etc/resolv.conf Slowroll: lrwxrwxrwx 1 root root 30 Jun 13 2022 /etc/resolv.conf -> /var/run/netconfig/resolv.conf
cat /etc/resolv.conf ======================
TW: # Generated by NetworkManager nameserver 172.20.10.1 Slowroll: ### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf ### autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. nameserver 192.168.190.227
On 15.02.2024 22:59, Ben T. Fender wrote:
cat /etc/resolv.conf ======================
TW: # Generated by NetworkManager nameserver 172.20.10.1
Well, find out where you configured this DNS server. I expect you can see from other commands that your Internet connectivity is perfectly fine, just DNS resolution fails.
Thu, 15 Feb 2024 23:05:12 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On 15.02.2024 22:59, Ben T. Fender wrote:
cat /etc/resolv.conf ======================
TW: # Generated by NetworkManager nameserver 172.20.10.1
Well, find out where you configured this DNS server. I expect you can see from other commands that your Internet connectivity is perfectly fine, just DNS resolution fails.
All I did was select options provided for by NetworkManager GUI interface. I noticed that unlike in Slowroll in TW the file /etc/resolv.conf was NOT a link to /etc/netconfig/resolve.conf but a standalone file generated by NM. I have no clue what any of this means so I made it a link in TW the same as it is in Slowwroll. Now it works. The content of /etc/NetworkManager/system-connections/ and entries in NM "Configure Network Connections" do not appear to reflect each other in real time. I habven't investigated this aapect further though.
participants (2)
-
Andrei Borzenkov -
Ben T. Fender