[SOLVED] NetworkManager connected but cant ping

moshen212 · 2017-12-07 13:03:00

Hi guys

After i installed archlinux, i can connect to my wifi by `wifi-menu` command line but after installing gnome3 and NetworkManager and running `systemctl start NetworkManager` gnome show me connection status as active but i cant open any website on the my browser or ping to any address.

$ 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: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether e8:11:32:5a:1f:f5 brd ff:ff:ff:ff:ff:ff
3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether b4:74:9f:c9:92:41 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:1b:4c:14:fe brd ff:ff:ff:ff:ff:ff

I considered to this error every time installing archlinux

Thnks for every help

Last edited by moshen212 (2023-12-13 05:48:10)

shulamy · 2017-12-07 16:06:47

maybe another network program works and doesn't let networkmanger to do what it should.

ezik

moshen212 · 2017-12-07 18:58:54

Anyone have a suggestion or output of any commands needs?

seth · 2017-12-08 12:14:01

https://wiki.archlinux.org/index.php/Ne … figuration

Also, why do you believe simply startin NM would get you a wifi connection??

cfr · 2017-12-09 04:15:03

So you installed netctl, enabled wifi-menu, installed GNOME and NM and found NM can't connect? If so, you need to decide how you want to manage wireless connections and ensure you have only that method enabled. Too many WIFI cooks spoil the broth.

moshen212 · 2017-12-10 19:25:48

Thank you for answers guys, this is my internet connection scenario:

After boot and after i logging into the gnome, i see on the top-right of screen wifi icon that show status as connected but my browser cant open any website, every time i considered this behaviore i run two bellow commands:

1- sudo systemctl stop NetworkManager
2- sudo wifi-menu

and then my browser can work

Head_on_a_Stick · 2017-12-10 19:30:25

Can we please see the full output of

systemctl list-unit-files --state=enabled --no-pager

Hint: multiple networking .services may conflict and prevent a consistent connection.

seth · 2017-12-10 19:50:37

also "ip addr" and "ip route" when you think you should have a working network.
Overmore try to ping 8.8.8.8 and provide the contents of /etc/resolv.conf.

"my browser cant open any website" is no reasonable test on your network status - all you learn from it is that "something doesn't work".

jasonwryan · 2017-12-10 19:53:23

Moving to NC...

moshen212 · 2017-12-12 18:38:02

Thank you guys, below lines contain outputs of some commands when i connected to internet by NetworkManager service:

$ systemctl list-unit-files --state=enabled --no-pager
UNIT FILE                                   STATE  
autovt@.service                             enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
docker.service                              enabled
gdm.service                                 enabled
getty@.service                              enabled
libvirtd.service                            enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
systemd-timesyncd.service                   enabled
virtlockd.socket                            enabled
virtlogd.socket                             enabled
remote-fs.target                            enabled

14 unit files listed.

and

$ ip addr
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: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether e8:11:32:5a:1f:f5 brd ff:ff:ff:ff:ff:ff
3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:74:9f:c9:92:41 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.142/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp2s0b1
       valid_lft 3482sec preferred_lft 3482sec
    inet6 fe80::3a9c:2a3d:fc8a:5211/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:eb:15:40:ca brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever

and

$ ip route
default via 192.168.43.1 dev wlp2s0b1 proto dhcp metric 600 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.43.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.43.142 metric 600

and

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.43.142 icmp_seq=16 Destination Host Unreachable
From 192.168.43.142 icmp_seq=17 Destination Host Unreachable
From 192.168.43.142 icmp_seq=20 Destination Host Unreachable
From 192.168.43.142 icmp_seq=21 Destination Host Unreachable
From 192.168.43.142 icmp_seq=22 Destination Host Unreachable
From 192.168.43.142 icmp_seq=23 Destination Host Unreachable
From 192.168.43.142 icmp_seq=24 Destination Host Unreachable
From 192.168.43.142 icmp_seq=25 Destination Host Unreachable
From 192.168.43.142 icmp_seq=26 Destination Host Unreachable
From 192.168.43.142 icmp_seq=27 Destination Host Unreachable

Also contents of /etc/resolv.conf. file:

# Generated by resolvconf
nameserver 192.168.43.1

moshen212 · 2017-12-13 17:47:11

Anybody havn't an idea or solution about my problem

ewaller · 2017-12-13 18:26:23

Please do not bump your threads. A stalled thread better benefits by adding more info, not by making noise. https://wiki.archlinux.org/index.php/Co … ct#Bumping

Can you ping 192.168.43.1 ?

seth · 2017-12-13 20:27:39

If so and in any case my money is on the docker bridge.

moshen212 · 2017-12-13 21:16:46

Thank you dear seth for following my problem
You said correct about installing docker, i installed docker and kerio-connect but before installing these program i already have this issue

seth · 2017-12-13 21:18:44

ewaller wrote:

Can you ping 192.168.43.1 ?

moshen212 · 2017-12-14 12:17:54

$ ping 192.168.1.43
PING 192.168.1.43 (192.168.1.43) 56(84) bytes of data.
From 192.168.43.142 icmp_seq=3 Destination Host Unreachable
From 192.168.43.142 icmp_seq=4 Destination Host Unreachable
From 192.168.43.142 icmp_seq=5 Destination Host Unreachable
From 192.168.43.142 icmp_seq=6 Destination Host Unreachable
From 192.168.43.142 icmp_seq=7 Destination Host Unreachable
From 192.168.43.142 icmp_seq=8 Destination Host Unreachable
From 192.168.43.142 icmp_seq=9 Destination Host Unreachable

seth · 2017-12-14 14:26:15

ewaller wrote:

Can you ping 192.168.43.1 ?

moshen212 · 2017-12-14 19:51:46

Exceuse me Seth

$ ping 192.168.43.1
PING 192.168.43.1 (192.168.43.1) 56(84) bytes of data.
64 bytes from 192.168.43.1: icmp_seq=1 ttl=64 time=5.09 ms
64 bytes from 192.168.43.1: icmp_seq=2 ttl=64 time=4.67 ms
64 bytes from 192.168.43.1: icmp_seq=3 ttl=64 time=5.08 ms

Last edited by moshen212 (2017-12-14 19:53:31)

seth · 2017-12-14 20:57:12

So your gateway is reachable but leads nowhere.
What is 192.168.43.1? Your router?

nmap 192.168.43.1

moshen212 · 2017-12-14 21:17:46

I ran nmap and this is output:

$ nmap 192.168.43.1

Starting Nmap 7.60 ( https://nmap.org ) at 2017-12-15 00:39 +0330
Nmap scan report for 192.168.43.1
Host is up (3.0s latency).
All 1000 scanned ports on 192.168.43.1 are filtered (779) or closed (221)

Nmap done: 1 IP address (1 host up) scanned in 302.47 seconds

I think this ip assigned to me by wifi adaptor and i see this on the /etc/resolv.conf file

Last edited by moshen212 (2017-12-14 21:18:46)

seth · 2017-12-14 21:25:12

Your dhcp server (assuming this is not a self fucked-up static setup) assigns you 192.168.43.142, 192.168.43.1 is the gateway and if it's also in /etc/resolv.conf also your dns server - but cannot serve as either.
It's not a consumer router (no telnet, no http)

Please stop networkmanager, connect via wifi-menu (so that your internet works) and dump the updated outputs of

ip addr
ip route
cat /etc/resolve.conf

moshen212 · 2017-12-15 07:50:11

Ok Seth, see below lines:

$ ip addr
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: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether e8:11:32:5a:1f:f5 brd ff:ff:ff:ff:ff:ff
3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:74:9f:c9:92:41 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.141/24 brd 192.168.43.255 scope global wlp2s0b1
       valid_lft forever preferred_lft forever
    inet6 fe80::b674:9fff:fec9:9241/64 scope link 
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:8f:7a:75:bc brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever

$ ip route
default via 192.168.43.1 dev wlp2s0b1 src 192.168.43.141 metric 303 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.43.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.43.141 metric 303

$ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.43.1

seth · 2017-12-15 08:45:56

https://forum.salixos.org/viewtopic.php?f=30&t=7284
Use any other dhcp client (it's probably internal atm)

moshen212 · 2023-11-21 10:47:44

After 6 years this problem occure for me every time that I installing Archlinux, but this link worked for me:

https://gist.github.com/marques576/9dd2 … 5142118dd4

Last edited by moshen212 (2023-11-21 10:48:10)

seth · 2023-11-25 12:41:50

Iow. it was the obvious thing nobody though about (6 years ago) - you've the worst possible hardware
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2017-12-07 13:03:00

[SOLVED] NetworkManager connected but cant ping

#2 2017-12-07 16:06:47

Re: [SOLVED] NetworkManager connected but cant ping

#3 2017-12-07 18:58:54

Re: [SOLVED] NetworkManager connected but cant ping

#4 2017-12-08 12:14:01

Re: [SOLVED] NetworkManager connected but cant ping

#5 2017-12-09 04:15:03

Re: [SOLVED] NetworkManager connected but cant ping

#6 2017-12-10 19:25:48

Re: [SOLVED] NetworkManager connected but cant ping

#7 2017-12-10 19:30:25

Re: [SOLVED] NetworkManager connected but cant ping

#8 2017-12-10 19:50:37

Re: [SOLVED] NetworkManager connected but cant ping

#9 2017-12-10 19:53:23

Re: [SOLVED] NetworkManager connected but cant ping

#10 2017-12-12 18:38:02

Re: [SOLVED] NetworkManager connected but cant ping

#11 2017-12-13 17:47:11

Re: [SOLVED] NetworkManager connected but cant ping

#12 2017-12-13 18:26:23

Re: [SOLVED] NetworkManager connected but cant ping

#13 2017-12-13 20:27:39

Re: [SOLVED] NetworkManager connected but cant ping

#14 2017-12-13 21:16:46

Re: [SOLVED] NetworkManager connected but cant ping

#15 2017-12-13 21:18:44

Re: [SOLVED] NetworkManager connected but cant ping

#16 2017-12-14 12:17:54

Re: [SOLVED] NetworkManager connected but cant ping

#17 2017-12-14 14:26:15

Re: [SOLVED] NetworkManager connected but cant ping

#18 2017-12-14 19:51:46

Re: [SOLVED] NetworkManager connected but cant ping

#19 2017-12-14 20:57:12

Re: [SOLVED] NetworkManager connected but cant ping

#20 2017-12-14 21:17:46

Re: [SOLVED] NetworkManager connected but cant ping

#21 2017-12-14 21:25:12

Re: [SOLVED] NetworkManager connected but cant ping

#22 2017-12-15 07:50:11

Re: [SOLVED] NetworkManager connected but cant ping

#23 2017-12-15 08:45:56

Re: [SOLVED] NetworkManager connected but cant ping

#24 2023-11-21 10:47:44

Re: [SOLVED] NetworkManager connected but cant ping

#25 2023-11-25 12:41:50

Re: [SOLVED] NetworkManager connected but cant ping

Board footer