[SOLVED]Machine connected to WiFi but there is no internet

Amasirat · 2023-01-23 20:02:16

Machine connects to wireless network and even obtains an IP address, but it does not communicate with anyother servers. Even local ones as I've tried to ping my friend's mobile phone connected to the same network. It gives this:
PING 172.30.101.156 (172.30.101.156) 56(84) bytes of data
And stays there for long while until I terminate the process. Basically no packets were able to be sent.

Pinging websites is different however, it gives for example:
ping: google.com: Temporary failure in name resolution

Before this dilemma I used plain networkmanager to connect to WiFi but after this happened, I tried installing iwd by chrooting into the system with the live iso. After that I added this to /etc/iwd/main.conf

[General]
EnableNetworkConfiguration=true

[Network]
NameResolvingService=systemd

Output of iwctl station wlan0 show:

            Scanning              no                                               
            State                 connected                                        
            Connected network     UT-WiFi                                          
            IPv4 address          172.30.101.248                                   
            ConnectedBss          00:bf:77:f8:84:00                                
            Frequency             2437                                             
            Security              Open                                             
            RSSI                  -61 dBm                                          
            AverageRSSI           -59 dBm                                          
            RxMode                802.11n                                          
            RxMCS                 4                                                
            TxBitrate             1000 Kbit/s                                      
            RxBitrate             39000 Kbit/s

Which seems normal to me.

output of ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether a8:1e:84:09:da:02 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 8a:fd:1d:87:4e:21 brd ff:ff:ff:ff:ff:ff permaddr 94:e9:79:de:d6:85

output of dmesg | firmware

[   17.698904] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   18.271917] ath10k_pci 0000:03:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877

output of ip route:

default via 172.30.100.1 dev wlan0 proto dhcp src 172.30.102.9 
172.30.100.0/22 dev wlan0 proto dhcp scope link

It did however give me an interesting log when outputting journalctl -f

output of journalctl -f:

             
kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
kernel: ath10k_pci 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
kernel: ath10k_pci 0000:03:00.0:   device [168c:0042] error status/mask=00000080/00006000
kernel: ath10k_pci 0000:03:00.0:    [ 7] BadDLLP               
kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0

Which repeats at a particular time interval along with other services that fail due to the internet connection.
I wonder what the issue is even stemming from, I would appreciate people more knowledgable than me to help me see the bigger picture here.
If there are other information you would like to see, I'll deliver.
I'm new to arch forums so sorry if the formatting might be wrong in some way.

Edit:
I'm not 100% sure what had caused this because I eventually just reinstalled arch again, but after some time later I assume it could have just been me not configuring my hosts file correctly while installing Arch that time.

Last edited by Amasirat (2023-08-16 12:11:00)

Adriik · 2023-01-23 20:13:52

Please use code tags: BBCode

I don't know much about network stuff, but what I read from others as Seth is that NetworkManager uses wpa_supplicant as backend, and you said that you installed iwd when chrooting in your system, so maybe iwd and wpa_supplicant are fighting to control the network.

Post the output of

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

Last edited by Adriik (2023-01-23 20:15:30)

Amasirat · 2023-01-23 20:44:24

Thank you so much for the heads up about BBCode. I edited my post to use it.

I made a mistake at first, and put '-' instead of '_' so I didn't find wpa supplicant at first.
~~I'll try to remove it and see what happens~~
Scratch that, removing wpa_supplicant obviously breaks networkmanager dependancy. I'm probably sleep deprived!
I'll see what I can do tomorrow.

Meanwhile,
This is also the output of the command.

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
muse-hub.service                         | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
windscribe-helper.service                | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants

Last edited by Amasirat (2023-01-23 21:00:33)

seth · 2023-01-23 20:56:28

You now have NM and iwd enabled what's not going to work.
Disable iwd, reboot, check the output of "ip a", try to "ping -c1 8.8.8.8" and post a complete system journal ("sudo journalctl -b", redirect that into a file or pipe it into "curl -F 'file=@-' 0x0.st" if you've an internet connection by other means. Don't copy and paste out of the terminal)

Is "UT-WiFi" maybe some eduroam thing?

Adriik · 2023-01-23 21:02:43

I'll try to remove it and see what happens

If you going to delete wpa_supplicant and use iwd, follow this: https://wiki.archlinux.org/title/Networ … Fi_backend
Otherwise, use wpa_supplicant, the default for NetworkManager

But the idea is using just one, NetworkManager + wpa_supplicant, or NetworkManager + iwd.

But for the two options, you need to disable the services (wpa_supplicant or iwd) and remove all configuration made, because NetworkManager will start and configure it itself.

Edit: I write too slow

Last edited by Adriik (2023-01-23 21:03:48)

Amasirat · 2023-01-23 21:09:16

Is "UT-WiFi" maybe some eduroam thing?

Yes, it most likely is. I study at Tehran University, so it's most likely that. You have to sign in to the network to connect to non-"ut.ac.ir" servers. Although I'm just a first term.

Thanks a lot. I'll try and do as you suggested tomorrow morning. Although I remember the issue happening before installing iwd, i attempted that because I was more familiar with using iwd. Maybe that was a mistake

Last edited by Amasirat (2023-01-23 21:13:29)

seth · 2023-01-23 21:21:34

Yes, it most likely is. I study at Tehran University, so it's most likely that.

It's also most likely the problem, try to disable resolved and make sure NM isn't using it:
https://bbs.archlinux.org/viewtopic.php?id=282947
https://wiki.archlinux.org/title/Networ … forwarding (make sure /etc/resolv.conf is NOT a symlink)

Amasirat · 2023-01-24 09:13:03

seth wrote:

You now have NM and iwd enabled what's not going to work.
Disable iwd, reboot, check the output of "ip a", try to "ping -c1 8.8.8.8" and post a complete system journal ("sudo journalctl -b", redirect that into a file or pipe it into "curl -F 'file=@-' 0x0.st" if you've an internet connection by other means. Don't copy and paste out of the terminal)

This is the output of 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 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether a8:1e:84:09:da:02 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether ea:ed:7b:e8:14:23 brd ff:ff:ff:ff:ff:ff permaddr 94:e9:79:de:d6:85

This is what happens when pinging 8.8.8.8 after that:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Since journalctl -b's output was a lot. I made a quick github repo containing a redirected output of the command. Hope that's acceptable.
Now this is the output of journalctl -b:
https://github.com/Amasirat/journal

I'll try to disable resolved and see if the issue is because of that or not

seth · 2023-01-24 09:23:22

This is what happens when pinging 8.8.8.8 after that:

But at this point you have neither lease nor carrier - it cannot work.
This doesn't fit

Jan 24 11:57:24 amirAcerAspireF5 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 24 11:57:24 amirAcerAspireF5 wpa_supplicant[441]: wlan0: Trying to associate with f0:9f:c2:3d:e8:09 (SSID='library1' freq=2462 MHz)
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2313] device (wlan0): supplicant interface state: authenticating -> associating
Jan 24 11:57:24 amirAcerAspireF5 wpa_supplicant[441]: wlan0: Associated with f0:9f:c2:3d:e8:09
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2313] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Jan 24 11:57:24 amirAcerAspireF5 wpa_supplicant[441]: wlan0: CTRL-EVENT-CONNECTED - Connection to f0:9f:c2:3d:e8:09 completed [id=0 id_str=]
Jan 24 11:57:24 amirAcerAspireF5 wpa_supplicant[441]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2469] device (wlan0): supplicant interface state: associating -> completed
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2470] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "library1"
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2470] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2487] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 24 11:57:24 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548844.2496] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jan 24 11:57:24 amirAcerAspireF5 wpa_supplicant[441]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-41 noise=-114 txrate=1000
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <warn>  [1674548846.0184] ndisc[0x5643b1a9c2d0,"wlan0"]: solicit: failure sending router solicitation: Operation not permitted (1)
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.4583] dhcp4 (wlan0): state changed new lease, address=172.18.165.241
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.4600] policy: set 'library1 1' (wlan0) as default for IPv4 routing and DNS
Jan 24 11:57:26 amirAcerAspireF5 systemd-resolved[371]: wlan0: Bus client set default route setting: yes
Jan 24 11:57:26 amirAcerAspireF5 systemd-resolved[371]: wlan0: Bus client set DNS server list to: 192.168.20.14
Jan 24 11:57:26 amirAcerAspireF5 dbus-daemon[374]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=391 comm="/usr/bin/NetworkManager --no-daemon")
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.5524] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 24 11:57:26 amirAcerAspireF5 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 24 11:57:26 amirAcerAspireF5 dbus-daemon[374]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 24 11:57:26 amirAcerAspireF5 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 24 11:57:26 amirAcerAspireF5 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 24 11:57:26 amirAcerAspireF5 kernel: audit: type=1130 audit(1674548846.577:95): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.6080] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.6089] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.6108] manager: NetworkManager state is now CONNECTED_SITE
Jan 24 11:57:26 amirAcerAspireF5 NetworkManager[391]: <info>  [1674548846.6134] device (wlan0): Activation: successful, device activated.

Afterwards you receive a lot of bus errors, but they all get corrected:

Jan 24 11:57:32 amirAcerAspireF5 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Jan 24 11:57:32 amirAcerAspireF5 kernel: ath10k_pci 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Jan 24 11:57:32 amirAcerAspireF5 kernel: ath10k_pci 0000:03:00.0:   device [168c:0042] error status/mask=00000080/00006000
Jan 24 11:57:32 amirAcerAspireF5 kernel: ath10k_pci 0000:03:00.0:    [ 7] BadDLLP

Amasirat · 2023-01-24 10:06:06

seth wrote:

This is what happens when pinging 8.8.8.8 after that:
But at this point you have neither lease nor carrier - it cannot work.
This doesn't fit

I don't quite know why that happened but now I made sure I was connected to a network and here it is again:

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 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether a8:1e:84:09:da:02 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:e9:79:de:d6:85 brd ff:ff:ff:ff:ff:ff
    inet 172.18.165.241/22 brd 172.18.167.255 scope global dynamic noprefixroute wlan0
       valid_lft 28616sec preferred_lft 28616sec
    inet6 fe80::be80:24c:c823:9a01/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

However the problem still persists. I'll try other ways of diagnosing the problem right now.

Amasirat · 2023-01-24 10:54:40

seth wrote:

It's also most likely the problem, try to disable resolved and make sure NM isn't using it:
https://bbs.archlinux.org/viewtopic.php?id=282947
https://wiki.archlinux.org/title/Networ … forwarding (make sure /etc/resolv.conf is NOT a symlink)

I went into the live iso and installed dnsmasq. After that I deleted resolv.conf and restarted networkmanager, then I made a dns.conf in /etc/NetworkManager/conf.d/dns.conf and wrote

[main]
dns=dnsmasq

Per the wiki's instructions. The issue still prrsists, but what's interesting is that now my interface changed from wlan0 to wlp3s0.
Does that indicate something? My knowledge regarding networks is very limited.

Last edited by Amasirat (2023-01-24 10:56:58)

seth · 2023-01-24 11:10:18

Who said "use dnssq"?
Any caching resolver is ppotentially a problem.
Make sure to use the default resolver.

The device name changed because you removed iwd which blocked systemd's questionable " predictable" renaming, but thats likely irrelevant.

Post an updated journal, ip a, ip r and "dig archlinux.com"

Amasirat · 2023-01-24 11:42:46

seth wrote:

Who said "use dnssq"?
Any caching resolver is ppotentially a problem.
Make sure to use the default resolver.
The device name changed because you removed iwd which blocked systemd's questionable " predictable" renaming, but thats likely irrelevant.
Post an updated journal, ip a, ip r and "dig archlinux.com"

Oh right, I must have misinterpreted since it was the first thing listed after 4.7.1 on the wiki link. I apologize. I made sure NetworkManager uses systemd-resolved. I don't currently have the dig utility though, I'll try and install dnsutils from the live iso in the meantime:
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 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether a8:1e:84:09:da:02 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:e9:79:de:d6:85 brd ff:ff:ff:ff:ff:ff
    inet 172.18.165.241/22 brd 172.18.167.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 28738sec preferred_lft 28738sec
    inet6 fe80::8079:3c10:ba5c:2f7f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r:

default via 172.18.164.1 dev wlp3s0 proto dhcp src 172.18.165.241 metric 20600 
172.18.164.0/22 dev wlp3s0 proto kernel scope link src 172.18.165.241 metric 600

Updated-journal:
It's in the same repo, a new file new_journal is in there now
https://github.com/Amasirat/journal

seth · 2023-01-24 14:55:49

I made sure NetworkManager uses systemd-resolved

Nonono.
You're supposed to use the default resolver and avoid that being resolved by having /etc/resolv.conf NOT be a synlink but a proper file.
Then

seth wrote:

Post
- an updated journal
ip a; ip r
- and "dig archlinux.com"

Amasirat · 2023-01-24 15:47:24

seth wrote:

I made sure NetworkManager uses systemd-resolved
Nonono.
You're supposed to use the default resolver and avoid that being resolved by having /etc/resolv.conf NOT be a synlink but a proper file.
Then
seth wrote:
Post
- an updated journal
ip a; ip r
- and "dig archlinux.com"

Based on archwiki, networkmanager uses systemd-resolved automatically, all I did is remove resolv.conf and restart networkmanager. Was I mistaken in thinking systemd-resolved is the default resolver? Is there something else that has to be done? I've checked with ls -l and resolv.conf does not point to any directory.

Well, the result of the dig is basically a time out.

;; communications error to 192.168.20.14#53: timed out
;; communications error to 192.168.20.14#53: timed out
;; communications error to 192.168.20.14#53: timed out

; <<>> DiG 9.18.10 <<>> archlinux.com
;; global options: +cmd
;; no servers could be reached

The rest are identical

Scimmia · 2023-01-24 15:50:04

The default resolver is part of glibc.

For NM to use systemd-resolved, it checks whether /etc/resolv.conf is a file or a symlink. Just deleting it all together isn't valid.

seth · 2023-01-24 15:54:20

Based on archwiki, networkmanager uses systemd-resolved automatically

No.
Welcome to the systemd-resolved madness where the behavior is defined by the type of a file…

The wiki wrote:

Note: If /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf, /run/systemd/resolve/resolv.conf,/lib/systemd/resolv.conf or /usr/lib/systemd/resolv.conf, NetworkManager will choose systemd-resolved automatically.

Make sure "stat /etc/resolv.conf" says it's a regular file and ensure to have "dns=default" (or not set at all)

According to your previous post you're in the 172.18.165.241/22 segment, 192.168.20.14 won't be accessible, so DNS will fail.

stat /etc/resolv.conf
cat /etc/resolv.conf

Make sure you've no custom DNS configured in NM.

Also, random intervention: eduroam comes often (always?) along some script to setup and login, did your university provide anything like this?

Amasirat · 2023-01-24 16:30:57

Also, random intervention: eduroam comes often (always?) along some script to setup and login, did your university provide anything like this?

I didn't even know we had eduroam until now. It makes sense since it's less strict than any other internet service inside Iran in regards to blocking VPN services but I'm still just assuming. There is no useful information about the service readily available. I'll have to ask around.

Thanks for the information. I couldn't have found out about this on my own.

I have somewhere to be right now but I'll make sure to try that out

Last edited by Amasirat (2023-01-24 16:31:47)

Amasirat · 2023-01-24 20:53:28

Make sure "stat /etc/resolv.conf" says it's a regular file and ensure to have "dns=default" (or not set at all)
Make sure you've no custom DNS configured in NM.

resolv.conf is a regular file alright. Here's its contents also:

# Generated by NetworkManager
nameserver 192.168.20.14
nameserver 192.168.20.15

According to your previous post you're in the 172.18.165.241/22 segment, 192.168.20.14 won't be accessible, so DNS will fail

My knowledge is very low but shouldn't a local ip be assigned to the machine by the main ISP? I assumed that's what it is and it's getting it fine as well.

Make sure you've no custom DNS configured in NM.

I had never messed around with the DNS before this, so I don't think there should be any custom DNS.

seth · 2023-01-24 22:35:33

My knowledge is very low but shouldn't a local ip be assigned to the machine by the main ISP?

You're typically getting the LAN IP via dhcp, from your last journal:

Jan 24 15:01:59 amirAcerAspireF5 wpa_supplicant[448]: wlp3s0: Trying to associate with f0:9f:c2:3d:eb:ab (SSID='library2' freq=2437 MHz)
Jan 24 15:01:59 amirAcerAspireF5 NetworkManager[397]: <info>  [1674559919.6989] dhcp4 (wlp3s0): state changed new lease, address=172.18.165.241

172.16.0.0 - 172.31.255.255 and 192.168.0.0 - 192.168.255.255 are both private network segments, they're not part of the internet and unless the gateway on 172.18.164.1 routes you into 192.168.20.0/24 (what is possible but not very likely) you cannot reach that host from the current segment (hence the timeout)

I don't think believe there should be any custom DNS.

ftfy.
resolved said

Jan 24 15:01:59 amirAcerAspireF5 systemd-resolved[379]: wlp3s0: Bus client set DNS server list to: 192.168.20.14

so it's coming from NM, but whether it gets advertised by the dhcp server or is configured in NM is not possible to say from here.

Can you

ping -c1 8.8.8.8
dig @8.8.8.8 google.com
tracepath 192.168.20.14

?

I didn't even know we had eduroam until now. It makes sense since it's less strict than any other internet service inside Iran in regards to blocking VPN services but I'm still just assuming. There is no useful information about the service readily available. I'll have to ask around.

Did you?

Jan 24 15:01:59 amirAcerAspireF5 NetworkManager[397]: <info>  [1674559919.4138] device (wlp3s0): Activation: (wifi) connection 'library2' requires no security.  No secrets needed.

It's an open network, so there's reasonably some 2nd layer authentication required?

Amasirat · 2023-01-27 15:28:09

Sorry for the late reply,

It's an open network, so there's reasonably some 2nd layer authentication required?

Yes, indeed. The process is:
when you connect to the network, you are then prompted by a browser to sign in, which redirects you to an authentication portal. No such thing happens now obviously.
Although I've tried mobile hotspot and it's the same story for that. USB thethering seems to not work either, so I believe the issue doesn't stem directly from the uni network, I may definitely be wrong however.

ping:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

dig:

;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out

; <<>> DiG 9.18.10 <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; no servers could be reached

Tracepath:

 1?: [LOCALHOST]                      pmtu 1500
 1:  send failed
 1:  send failed
     Resume: pmtu 1500

seth · 2023-01-27 15:48:20

YOur problem is that you end up w/ a nameserver in an unreachable segment.
It shoudl™ probably be more like 172.18.165.1 or so and be provided by the dhcp server.
Since there's no reasonable way how you could end up w/ 192.168.20.14 in this environment I suspect that this is explicitly configured in the networkmanager connection or global configuration.
Check the files in /etc/NetworkManager/ and https://wiki.archlinux.org/title/Networ … connection
Also https://wiki.archlinux.org/title/Networ … connection - pay attention to the ignore-auto-dns settings.

Amasirat · 2023-02-02 17:21:57

seth wrote:

YOur problem is that you end up w/ a nameserver in an unreachable segment.
It shoudl™ probably be more like 172.18.165.1 or so and be provided by the dhcp server.
Since there's no reasonable way how you could end up w/ 192.168.20.14 in this environment I suspect that this is explicitly configured in the networkmanager connection or global configuration.
Check the files in /etc/NetworkManager/ and https://wiki.archlinux.org/title/Networ … connection
Also https://wiki.archlinux.org/title/Networ … connection - pay attention to the ignore-auto-dns settings.

Hey! I've been incredibly busy for a few days.
I checked the global config but it was pretty much blank, so that can't be an issue. I became free recently so I decided to spend a few days reinstalling Arch from the ground up. I had installed Arch fairly recently so I didn't have many important files on the machine, so I could afford to do that fortunately.

I tried to go completely safe with network manager. no dhcp clients or custom dns and let networkmanager handle everything.
The network works correctly now.

I'm not sure if I should put this post as solved or not since I just avoided the problem entirely.
I'll try to be extra careful about my network activity and read up on general network things and system maintenance.

Thanks to everyone who helped. you're great for taking time out of your day to help out complete strangers. It's you guys that keep the community alive, but I'm sure you've already heard that before.

Still thanks anyway!

Last edited by Amasirat (2023-02-02 17:23:05)

seth · 2023-02-02 20:08:39

Out of curiosity, can you post

ip a; ip r
dig google.com
resolvectl status
stat /etc/resolv.conf
cat /etc/resolv.conf

Amasirat · 2023-02-02 21:06:46

seth wrote:

Out of curiosity, can you post

ip a; ip r
dig google.com
resolvectl status
stat /etc/resolv.conf
cat /etc/resolv.conf

sure thing.

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 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether a8:1e:84:09:da:02 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:e9:79:de:d6:85 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 259069sec preferred_lft 259069sec
    inet6 fe80::9a0:c728:4bcb:b3d6/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r:

default via 192.168.1.1 dev wlp3s0 proto dhcp src 192.168.1.100 metric 600 
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.100 metric 600

dig google.com:

; <<>> DiG 9.18.11 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19460
;; 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.		51	IN	A	216.239.38.120

;; Query time: 1300 msec
;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
;; WHEN: Fri Feb 03 00:21:32 +0330 2023
;; MSG SIZE  rcvd: 55

stat /etc/resolv.conf:

  File: /etc/resolv.conf
  Size: 53        	Blocks: 8          IO Block: 4096   regular file
Device: 8,2	Inode: 394459      Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-02-03 00:11:12.317635155 +0330
Modify: 2023-02-03 00:11:11.930968475 +0330
Change: 2023-02-03 00:11:12.030968477 +0330
 Birth: 2023-02-03 00:11:11.930968475 +0330

cat /etc/resolv.conf:

# Generated by NetworkManager
nameserver 192.168.1.1

it's horrendously slow but that's pretty much normal at this hour for me most of the time, but it actually connects which is satisfactory.
although I should also mention I'm no longer in University because the semester was over a few days ago and I've come back to my hometown, so this is my home network.
Something may still reproduce that problem when I get back. However I'm not too sure about that.

I'm afraid I couldn't check resolvectl's status because I apparently don't have some sort of service enabled on systemd, but I'm too out of it right now to think about it.
I'll have to fix that tomorrow

Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

Last edited by Amasirat (2023-02-02 21:10:57)

Arch Linux

#1 2023-01-23 20:02:16

[SOLVED]Machine connected to WiFi but there is no internet

#2 2023-01-23 20:13:52

Re: [SOLVED]Machine connected to WiFi but there is no internet

#3 2023-01-23 20:44:24

Re: [SOLVED]Machine connected to WiFi but there is no internet

#4 2023-01-23 20:56:28

Re: [SOLVED]Machine connected to WiFi but there is no internet

#5 2023-01-23 21:02:43

Re: [SOLVED]Machine connected to WiFi but there is no internet

#6 2023-01-23 21:09:16

Re: [SOLVED]Machine connected to WiFi but there is no internet

#7 2023-01-23 21:21:34

Re: [SOLVED]Machine connected to WiFi but there is no internet

#8 2023-01-24 09:13:03

Re: [SOLVED]Machine connected to WiFi but there is no internet

#9 2023-01-24 09:23:22

Re: [SOLVED]Machine connected to WiFi but there is no internet

#10 2023-01-24 10:06:06

Re: [SOLVED]Machine connected to WiFi but there is no internet

#11 2023-01-24 10:54:40

Re: [SOLVED]Machine connected to WiFi but there is no internet

#12 2023-01-24 11:10:18

Re: [SOLVED]Machine connected to WiFi but there is no internet

#13 2023-01-24 11:42:46

Re: [SOLVED]Machine connected to WiFi but there is no internet

#14 2023-01-24 14:55:49

Re: [SOLVED]Machine connected to WiFi but there is no internet

#15 2023-01-24 15:47:24

Re: [SOLVED]Machine connected to WiFi but there is no internet

#16 2023-01-24 15:50:04

Re: [SOLVED]Machine connected to WiFi but there is no internet

#17 2023-01-24 15:54:20

Re: [SOLVED]Machine connected to WiFi but there is no internet

#18 2023-01-24 16:30:57

Re: [SOLVED]Machine connected to WiFi but there is no internet

#19 2023-01-24 20:53:28

Re: [SOLVED]Machine connected to WiFi but there is no internet

#20 2023-01-24 22:35:33

Re: [SOLVED]Machine connected to WiFi but there is no internet

#21 2023-01-27 15:28:09

Re: [SOLVED]Machine connected to WiFi but there is no internet

#22 2023-01-27 15:48:20

Re: [SOLVED]Machine connected to WiFi but there is no internet

#23 2023-02-02 17:21:57

Re: [SOLVED]Machine connected to WiFi but there is no internet

#24 2023-02-02 20:08:39

Re: [SOLVED]Machine connected to WiFi but there is no internet

#25 2023-02-02 21:06:46

Re: [SOLVED]Machine connected to WiFi but there is no internet

Board footer