You are not logged in.

#1 2021-01-10 13:56:35

Abovegame
Member
Registered: 2017-10-29
Posts: 8

[SOLVED] Connected to wireless network but not internet

I am able to connect to my wireless network but have no internet access (last night it worked fine). Besides that internet access on my phone is available for the same network.

Running `systemctl status NetworkManager` outputs:

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Sun 2021-01-10 13:36:42 CET; 12min ago
       Docs: man:NetworkManager(8)
   Main PID: 302 (NetworkManager)
      Tasks: 3 (limit: 4327)
     Memory: 17.8M
     CGroup: /system.slice/NetworkManager.service
             └─302 /usr/bin/NetworkManager --no-daemon

Jan 10 13:36:55 Abovegame NetworkManager[302]: <info>  [1610282215.4225] manager: NetworkManager state is now CONNECTED_SITE
Jan 10 13:36:55 Abovegame NetworkManager[302]: <info>  [1610282215.4226] policy: set 'ZTE_FCF3AA' (wlp3s0) as default for IPv4 routing and DNS
Jan 10 13:36:55 Abovegame NetworkManager[302]: <info>  [1610282215.4229] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Jan 10 13:36:55 Abovegame NetworkManager[745]: Failed to resolve interface "NetworkManager": No such device
Jan 10 13:36:55 Abovegame NetworkManager[302]: <warn>  [1610282215.4365] dns-mgr: resolvconf failed with status 256
Jan 10 13:36:55 Abovegame NetworkManager[302]: <warn>  [1610282215.4366] dns-mgr: could not commit DNS changes: resolvconf failed with status 256
Jan 10 13:36:55 Abovegame NetworkManager[302]: <info>  [1610282215.4367] device (wlp3s0): Activation: successful, device activated.
Jan 10 13:36:55 Abovegame NetworkManager[302]: <info>  [1610282215.4393] manager: startup complete
Jan 10 13:36:57 Abovegame NetworkManager[302]: <info>  [1610282217.3442] agent-manager: agent[132d248b3da07448,:1.49/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 10 13:45:46 Abovegame NetworkManager[302]: <info>  [1610282746.1041] audit: op="connection-update" uuid="51531f10-f8f1-47b0-9dc9-b0fc2ddb0bd6" name="ZTE_FCF3AA" args="connection.timestamp,802-11-wireless.cloned-mac-address,802-11-wireless.mac-address,802-11-wireless.bssid" pid=1166 uid=1000 result="success"

Why is it trying to resolve the interface named `NetworkManger`?

Running `ls /sys/class/net` outputs:

enp0s25
lo
wlp3s0

Running `ip link` outputs:

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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 28:d2:44:d5:b6:be brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 28:b2:bd:85:69:25 brd ff:ff:ff:ff:ff:ff

What makes me a bit confused is that the mode for my wireless interface is *DORMANT*? I've tried setting it to `default` with:

`ip link set wlp3s0 mode default` but that doesn't seem to have any effects.

Running `ip addr show` outputs:

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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 28:d2:44:d5:b6:be 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 28:b2:bd:85:69:25 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.130/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 85164sec preferred_lft 85164sec
    inet6 fe80::ae1e:4067:f33b:fd59/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Running `ip route` outputs:

default via 192.168.0.1 dev wlp3s0 proto dhcp metric 20600 
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.130 metric 600 

Running `ping -c 3 www.google.com` outputs:

ping: www.google.com: Temporary failure in name resolution

Running `ping -c 3 8.8.8.8` outputs:

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=111 time=54.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=111 time=51.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=111 time=53.4 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 51.055/52.933/54.388/1.393 ms

If I need to post any logs please tell me smile

Last edited by Abovegame (2021-01-10 17:59:38)

Offline

#2 2021-01-10 14:17:27

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [SOLVED] Connected to wireless network but not internet

So you're connected to the internet just fine, you don't have dns. What's in /etc/resolv.conf?

Online

#3 2021-01-10 14:27:27

Abovegame
Member
Registered: 2017-10-29
Posts: 8

Re: [SOLVED] Connected to wireless network but not internet

I can't copy the contents right now, but i remember the only thing it had was:

#Generated by NetworkManager ...

Something like that, just that single comment, nothing below that.

Last edited by Abovegame (2021-01-10 14:27:41)

Offline

#4 2021-01-10 14:34:32

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [SOLVED] Connected to wireless network but not internet

It shouldn't have that with openresolv/resolvconf AFAIK. Is the file immutable or something?

Online

#5 2021-01-10 14:43:25

Abovegame
Member
Registered: 2017-10-29
Posts: 8

Re: [SOLVED] Connected to wireless network but not internet

I've tried editing it and it worked fine. Is there something i need to append to it ?

Last edited by Abovegame (2021-01-10 14:44:01)

Offline

#6 2021-01-10 14:46:40

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [SOLVED] Connected to wireless network but not internet

Looking again, I shouldn't have assumed openresolv. Are you using openresolv or systemd-resolvconf or something else?

Online

#7 2021-01-10 14:53:40

Abovegame
Member
Registered: 2017-10-29
Posts: 8

Re: [SOLVED] Connected to wireless network but not internet

I'll have to confirm this later. Probably aiming towards the systemd-resolvconf.

Offline

#8 2021-01-10 14:54:42

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: [SOLVED] Connected to wireless network but not internet

If that's the case, that's likely your problem. It doesn't seem like you've got systemd-resolved configured and running, so systemd-resolvconf isn't going to work.

Online

#9 2021-01-10 14:59:12

Abovegame
Member
Registered: 2017-10-29
Posts: 8

Re: [SOLVED] Connected to wireless network but not internet

Okay, I'll see to it later and post here the results. smile Thanks

Offline

#10 2021-01-10 17:57:15

Abovegame
Member
Registered: 2017-10-29
Posts: 8

Re: [SOLVED] Connected to wireless network but not internet

By reading the wiki a bit more I've found another file /run/NetworkManager/resolv.conf which to my suprise has these contents:

# Generated by NetworkManager
nameserver 192.168.0.1

I've managed to fix this by manually editing the file /etc/resolv.conf and adding the same nameserver parameter, afterwards I restarted the service with:

systemctl restart NetworkManager

This worked even after a restart, still I have no idea what caused this issue - what had overwritten the file in the first place.

Last edited by Abovegame (2021-01-10 18:09:13)

Offline

Board footer

Powered by FluxBB