Differences

This shows you the differences between two versions of the page.

--- wiki:network_troubleshooting [2023/12/15 18:28] – add Wired ethernet turns off and on constantly antisa
+++ wiki:network_troubleshooting [2025/12/17 12:20] (current) – add ip tags, network unreachable and service not known examples antisa
@@ Line 1: / Line 1: @@
-{{tag>network troubleshooting}}
+{{tag>network troubleshooting ipv4 ipv6}}
 ====== network troubleshooting ======
@@ Line 47: / Line 47: @@
 Check the cabling. Plug/unplug the cables from the router and other devices. After this the problem was resolved.
-==== Tested on ====
-  * Ubuntu 22.04
+===== ping: google.com: Name or service not known =====
+Check your ''/etc/resolv.conf'' if your distro is using that. On Ubuntu systemd-resolvd manages that file, so check systemd-resolvd service.
+If that seems fine, then it might a symptom of the below problem.
+===== connect: Network is unreachable =====
+Happens when pinging an IP address.
+Most likely an issue with a missing route.
+Check with ''ip r'' and add the route.
+Here's an example of missing route on a VM server with assigned IPs to the //eth0// interface already.
+<code>
+# ip a
+: 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
+: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
+    link/ether 02:00:00:12:14:7c brd ff:ff:ff:ff:ff:ff
+    inet 198.50.177.218/32 brd 198.50.177.218 scope global eth0
+       valid_lft forever preferred_lft forever
+    inet6 2607:5300:203:1735:198:50:177:218/64 scope global
+       valid_lft forever preferred_lft forever
+    inet6 fe80::ff:fe12:147c/64 scope link
+       valid_lft forever preferred_lft forever
+...
+# ip r
+.0.1.0/24 dev tun1 proto kernel scope link src 10.0.1.79
+.254.0.0/16 dev eth0 scope link metric 1002
+.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
+...
+# ip -6 r
+unreachable ::/96 dev lo metric 1024 error -113 pref medium
+unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -113 pref medium
+...
+default via 2607:5300:203:1735:: dev eth0 metric 1 pref medium
+default via 2607:5300:203:1735:: dev eth0 metric 1024 pref medium
+...
+[root@xor1 NetworkManager]# ip r
+</code>
+In above output ipv4 is missing a default route, and ipv6 is ok.
+To fix this case you would run:
+<code>
+# ip route add 66.70.179.0/24 dev eth0 src 198.50.177.218
+# ip route add default via 66.70.179.53
+# ping 8.8.8.8
+PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
+bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=1.31 ms
+...
+</code>
+You have to know the gateway IP, 66.70.179.53 above, then add a direct route to that because any gateway must be reachable directly on connected interfaces. This gateway IP is actually a bridge ''br0'' interface on the VM host and that's serving as the interface for all of the VMs there.
 ====== See also ======
   * [[wiki:ubuntu_troubleshooting|Ubuntu troubleshooting]]
+  * [[add_additional_ip_address_interface|Add additional ip address on interface]]
 ====== References ======
+  * https://superuser.com/questions/1219289/im-unable-to-create-a-static-ip-route-error-says-rtnetlink-answers-network-i