connect: Network is unreachable - ubuntu 18.04 terminal
0
The network works sometimes and it does not work sometimes after upgrading Ubuntu from 16.04 to 18.04.
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
kiran@kiran:/var/www/REPO/chicago$ ping google.com
PING google.com (216.58.197.78) 56(84) bytes of data.
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=1 ttl=53 time=28.8 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=2 ttl=53 time=27.9 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=3 ttl=53 time=28.5 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 27.985/28.444/28.804/0.393 ms
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
It is repeating the same way, 1st ping works, 2nd ping it won't.
The network is working fine on browser
Edit1
Traceroute output
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.211 ms 0.181 ms 0.308 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 10.006 ms 10.133 ms 10.369 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 12.111 ms 12.250 ms 13.701 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 70.009 ms 70.574 ms 70.568 ms
6 172.29.251.33 (172.29.251.33) 70.552 ms 22.633 ms 172.17.169.202 (172.17.169.202) 22.778 ms
7 172.31.167.58 (172.31.167.58) 22.587 ms 58.106 ms 58.441 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 58.266 ms 58.687 ms 58.698 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 62.380 ms 62.673 ms 62.685 ms
10 121.240.1.50 (121.240.1.50) 58.853 ms 58.625 ms 59.781 ms
11 74.125.242.129 (74.125.242.129) 71.736 ms 70.816 ms 74.125.242.145 (74.125.242.145) 56.211 ms
12 216.239.43.77 (216.239.43.77) 56.618 ms 57.252 ms 216.239.42.245 (216.239.42.245) 54.135 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 54.108 ms 54.585 ms 54.309 ms
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.198 ms 0.170 ms 0.341 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 4.438 ms 4.767 ms 5.403 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 5.071 ms 4.772 ms 5.275 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 6.114 ms 5.242 ms 6.534 ms
6 172.17.169.202 (172.17.169.202) 15.159 ms 172.29.251.33 (172.29.251.33) 9.845 ms 172.17.169.202 (172.17.169.202) 13.559 ms
7 172.31.167.58 (172.31.167.58) 10.235 ms 9.964 ms 10.329 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 12.168 ms 10.712 ms 12.347 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 12.543 ms 13.050 ms 13.015 ms
10 121.240.1.50 (121.240.1.50) 13.015 ms 12.999 ms 13.932 ms
11 74.125.242.145 (74.125.242.145) 34.534 ms 74.125.242.129 (74.125.242.129) 34.197 ms 74.125.242.145 (74.125.242.145) 31.985 ms
12 216.239.42.245 (216.239.42.245) 31.111 ms 58.980 ms 216.239.43.77 (216.239.43.77) 62.533 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 62.223 ms * 62.565 ms
kiran@kiran:~$
The issue persists with php request also(See the below screenshot)
networking 18.04
asked yesterday
Kiran ReddyKiran Reddy
1086
|
show 1 more comment
0
The network works sometimes and it does not work sometimes after upgrading Ubuntu from 16.04 to 18.04.
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
kiran@kiran:/var/www/REPO/chicago$ ping google.com
PING google.com (216.58.197.78) 56(84) bytes of data.
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=1 ttl=53 time=28.8 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=2 ttl=53 time=27.9 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=3 ttl=53 time=28.5 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 27.985/28.444/28.804/0.393 ms
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
It is repeating the same way, 1st ping works, 2nd ping it won't.
The network is working fine on browser
Edit1
Traceroute output
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.211 ms 0.181 ms 0.308 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 10.006 ms 10.133 ms 10.369 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 12.111 ms 12.250 ms 13.701 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 70.009 ms 70.574 ms 70.568 ms
6 172.29.251.33 (172.29.251.33) 70.552 ms 22.633 ms 172.17.169.202 (172.17.169.202) 22.778 ms
7 172.31.167.58 (172.31.167.58) 22.587 ms 58.106 ms 58.441 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 58.266 ms 58.687 ms 58.698 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 62.380 ms 62.673 ms 62.685 ms
10 121.240.1.50 (121.240.1.50) 58.853 ms 58.625 ms 59.781 ms
11 74.125.242.129 (74.125.242.129) 71.736 ms 70.816 ms 74.125.242.145 (74.125.242.145) 56.211 ms
12 216.239.43.77 (216.239.43.77) 56.618 ms 57.252 ms 216.239.42.245 (216.239.42.245) 54.135 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 54.108 ms 54.585 ms 54.309 ms
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.198 ms 0.170 ms 0.341 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 4.438 ms 4.767 ms 5.403 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 5.071 ms 4.772 ms 5.275 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 6.114 ms 5.242 ms 6.534 ms
6 172.17.169.202 (172.17.169.202) 15.159 ms 172.29.251.33 (172.29.251.33) 9.845 ms 172.17.169.202 (172.17.169.202) 13.559 ms
7 172.31.167.58 (172.31.167.58) 10.235 ms 9.964 ms 10.329 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 12.168 ms 10.712 ms 12.347 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 12.543 ms 13.050 ms 13.015 ms
10 121.240.1.50 (121.240.1.50) 13.015 ms 12.999 ms 13.932 ms
11 74.125.242.145 (74.125.242.145) 34.534 ms 74.125.242.129 (74.125.242.129) 34.197 ms 74.125.242.145 (74.125.242.145) 31.985 ms
12 216.239.42.245 (216.239.42.245) 31.111 ms 58.980 ms 216.239.43.77 (216.239.43.77) 62.533 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 62.223 ms * 62.565 ms
kiran@kiran:~$
The issue persists with php request also(See the below screenshot)
networking 18.04
asked yesterday
Kiran ReddyKiran Reddy
1086
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
@DominikCorniceping -4andping -6are not valid commands it seems
– Kiran Reddy
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago
|
show 1 more comment
0
0
0
The network works sometimes and it does not work sometimes after upgrading Ubuntu from 16.04 to 18.04.
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
kiran@kiran:/var/www/REPO/chicago$ ping google.com
PING google.com (216.58.197.78) 56(84) bytes of data.
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=1 ttl=53 time=28.8 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=2 ttl=53 time=27.9 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=3 ttl=53 time=28.5 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 27.985/28.444/28.804/0.393 ms
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
It is repeating the same way, 1st ping works, 2nd ping it won't.
The network is working fine on browser
Edit1
Traceroute output
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.211 ms 0.181 ms 0.308 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 10.006 ms 10.133 ms 10.369 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 12.111 ms 12.250 ms 13.701 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 70.009 ms 70.574 ms 70.568 ms
6 172.29.251.33 (172.29.251.33) 70.552 ms 22.633 ms 172.17.169.202 (172.17.169.202) 22.778 ms
7 172.31.167.58 (172.31.167.58) 22.587 ms 58.106 ms 58.441 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 58.266 ms 58.687 ms 58.698 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 62.380 ms 62.673 ms 62.685 ms
10 121.240.1.50 (121.240.1.50) 58.853 ms 58.625 ms 59.781 ms
11 74.125.242.129 (74.125.242.129) 71.736 ms 70.816 ms 74.125.242.145 (74.125.242.145) 56.211 ms
12 216.239.43.77 (216.239.43.77) 56.618 ms 57.252 ms 216.239.42.245 (216.239.42.245) 54.135 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 54.108 ms 54.585 ms 54.309 ms
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.198 ms 0.170 ms 0.341 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 4.438 ms 4.767 ms 5.403 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 5.071 ms 4.772 ms 5.275 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 6.114 ms 5.242 ms 6.534 ms
6 172.17.169.202 (172.17.169.202) 15.159 ms 172.29.251.33 (172.29.251.33) 9.845 ms 172.17.169.202 (172.17.169.202) 13.559 ms
7 172.31.167.58 (172.31.167.58) 10.235 ms 9.964 ms 10.329 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 12.168 ms 10.712 ms 12.347 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 12.543 ms 13.050 ms 13.015 ms
10 121.240.1.50 (121.240.1.50) 13.015 ms 12.999 ms 13.932 ms
11 74.125.242.145 (74.125.242.145) 34.534 ms 74.125.242.129 (74.125.242.129) 34.197 ms 74.125.242.145 (74.125.242.145) 31.985 ms
12 216.239.42.245 (216.239.42.245) 31.111 ms 58.980 ms 216.239.43.77 (216.239.43.77) 62.533 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 62.223 ms * 62.565 ms
kiran@kiran:~$
The issue persists with php request also(See the below screenshot)
networking 18.04
asked yesterday
Kiran ReddyKiran Reddy
1086
The network works sometimes and it does not work sometimes after upgrading Ubuntu from 16.04 to 18.04.
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
kiran@kiran:/var/www/REPO/chicago$ ping google.com
PING google.com (216.58.197.78) 56(84) bytes of data.
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=1 ttl=53 time=28.8 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=2 ttl=53 time=27.9 ms
64 bytes from maa03s21-in-f14.1e100.net (216.58.197.78): icmp_seq=3 ttl=53 time=28.5 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 27.985/28.444/28.804/0.393 ms
kiran@kiran:/var/www/REPO/chicago$ ping google.com
connect: Network is unreachable
It is repeating the same way, 1st ping works, 2nd ping it won't.
The network is working fine on browser
Edit1
Traceroute output
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.211 ms 0.181 ms 0.308 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 10.006 ms 10.133 ms 10.369 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 12.111 ms 12.250 ms 13.701 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 70.009 ms 70.574 ms 70.568 ms
6 172.29.251.33 (172.29.251.33) 70.552 ms 22.633 ms 172.17.169.202 (172.17.169.202) 22.778 ms
7 172.31.167.58 (172.31.167.58) 22.587 ms 58.106 ms 58.441 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 58.266 ms 58.687 ms 58.698 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 62.380 ms 62.673 ms 62.685 ms
10 121.240.1.50 (121.240.1.50) 58.853 ms 58.625 ms 59.781 ms
11 74.125.242.129 (74.125.242.129) 71.736 ms 70.816 ms 74.125.242.145 (74.125.242.145) 56.211 ms
12 216.239.43.77 (216.239.43.77) 56.618 ms 57.252 ms 216.239.42.245 (216.239.42.245) 54.135 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 54.108 ms 54.585 ms 54.309 ms
kiran@kiran:~$ traceroute google.com
traceroute to google.com (2404:6800:4007:802::200e), 30 hops max, 80 byte packets
connect: Network is unreachable
kiran@kiran:~$ traceroute google.com
traceroute to google.com (172.217.163.142), 30 hops max, 60 byte packets
1 _gateway (192.168.21.1) 0.198 ms 0.170 ms 0.341 ms
2 static-241.77.12.61-tataidc.co.in (61.12.77.241) 4.438 ms 4.767 ms 5.403 ms
3 * * *
4 10.117.135.245 (10.117.135.245) 5.071 ms 4.772 ms 5.275 ms
5 121.240.238.41.static-bangalore.vsnl.net.in (121.240.238.41) 6.114 ms 5.242 ms 6.534 ms
6 172.17.169.202 (172.17.169.202) 15.159 ms 172.29.251.33 (172.29.251.33) 9.845 ms 172.17.169.202 (172.17.169.202) 13.559 ms
7 172.31.167.58 (172.31.167.58) 10.235 ms 9.964 ms 10.329 ms
8 14.140.100.6.static-vsnl.net.in (14.140.100.6) 12.168 ms 10.712 ms 12.347 ms
9 115.112.71.65.STDILL-Chennai.vsnl.net.in (115.112.71.65) 12.543 ms 13.050 ms 13.015 ms
10 121.240.1.50 (121.240.1.50) 13.015 ms 12.999 ms 13.932 ms
11 74.125.242.145 (74.125.242.145) 34.534 ms 74.125.242.129 (74.125.242.129) 34.197 ms 74.125.242.145 (74.125.242.145) 31.985 ms
12 216.239.42.245 (216.239.42.245) 31.111 ms 58.980 ms 216.239.43.77 (216.239.43.77) 62.533 ms
13 maa05s04-in-f14.1e100.net (172.217.163.142) 62.223 ms * 62.565 ms
kiran@kiran:~$
The issue persists with php request also(See the below screenshot)
networking 18.04
networking 18.04
asked yesterday
Kiran ReddyKiran Reddy
1086
asked yesterday
Kiran ReddyKiran Reddy
1086
edited 18 hours ago
Kiran Reddy
asked yesterday
Kiran ReddyKiran Reddy
1086
asked yesterday
Kiran ReddyKiran Reddy
1086
asked yesterday
Kiran ReddyKiran Reddy
1086
1086
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
@DominikCorniceping -4andping -6are not valid commands it seems
– Kiran Reddy
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago
|
show 1 more comment
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
@DominikCorniceping -4andping -6are not valid commands it seems
– Kiran Reddy
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
@DominikCornice
ping -4 and ping -6 are not valid commands it seems– Kiran Reddy
18 hours ago
@DominikCornice
ping -4 and ping -6 are not valid commands it seems– Kiran Reddy
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115822%2fconnect-network-is-unreachable-ubuntu-18-04-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115822%2fconnect-network-is-unreachable-ubuntu-18-04-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you restart your router and see if it solves the problem?
– Dominik Cornice
yesterday
Actually the problem could be everywhere between your client and server. Next time you can't ping google.com, please edit with output from traceroure google.com
– Gravemind
yesterday
ipv6 is probably not enabled on your router. Try to ping with "ping -4" then with "ping -6". If I am not wrong, the former will work and the latter not.
– Dominik Cornice
yesterday
@DominikCornice
ping -4andping -6are not valid commands it seems– Kiran Reddy
18 hours ago
Will it work better with ping 8.8.8.8 (no DNS involved and no ipv6)?
– Dominik Cornice
18 hours ago