Can't resolve host, can't connect to internet

I noticed that updates were failing, I tried to update from UI and that failed. So I ssh into server and found that no external hosts were resolving, I can’t connect to the internet. It was working fine for several weeks and then stopped. I don’t remember changing anything. So I can’t upload logs for the same reason.

Here is what I get when trying to update. I also changed /etc/resolve.conf to 8.8.8.8 still not working. It connects to local network and nas in the garage fine.

Any troubleshooting steps or ideas greatly appreciated. I had to remove some of the links as new users are limited in what they can post.

root@bedroom:/etc# apt-get update
Err:1 Index of /debian bullseye InRelease
Something wicked happened resolving ‘deb.debian.org:https’ (-5 - No address associated with hostname)
Err:2 https://security.debian.org bullseye-security InRelease
Something wicked happened resolving ‘security.debian.org:https’ (-5 - No address associated with hostname)
Reading package lists… Done
W: Some index files failed to download. They have been ignored, or old ones used instead.

root@bedroom:/etc# cat resolv.conf
nameserver 8.8.8.8

This is a Vero V just purchased about 1 month ago

As a side note: I have a second Vero V that is working just fine. If there is something I check on that server to see if it’s different?

Let’s start with network 1 by 1:

  1. Are you using DHCP config or Static IP?
  2. What is the output of these commands (use the </> button when posting the output here):
ip addr
ip ro
ping 8.8.8.8

Thank you for your reply, I hope this tells you something.

Static IP

osmc@bedroom:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 94:cc:04:60:08:df brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.45/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:67:20:09:ab:21 brd ff:ff:ff:ff:ff:ff
osmc@bedroom:~$ ip ro
default via 192.168.0.1 dev eth0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.45
192.168.0.1 dev eth0 scope link
osmc@bedroom:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
130 packets transmitted, 0 packets received, 100% packet loss

hangs........

Here’s the same output on the second unit that is working fine. They’re cat5 connected to the same switch.

osmc@livingroom:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 94:cc:04:60:04:dc brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.44/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:67:20:09:9a:43 brd ff:ff:ff:ff:ff:ff
osmc@livingroom:~$ ip ro
default via 192.168.0.1 dev eth0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.44
192.168.0.1 dev eth0 scope link
osmc@livingroom:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=58 time=10.502 ms
64 bytes from 8.8.8.8: seq=1 ttl=58 time=9.269 ms
64 bytes from 8.8.8.8: seq=2 ttl=58 time=9.310 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 9.269/9.693/10.502 ms

Could it be a IP conflict?
Can you ping the Gateway or the other Vero?

ping 192.168.0.1
ping 192.168.0.44
arp -n

What happens if you run on the working Vero

ping 192.168.0.45
arp -n

Can you try DHCP to see if at least DHCP works?

Tried to switched the cables between the two?

From the non-working bedroom one (45) I can ping the working livingroom one (44)

osmc@bedroom:~$ ping 192.168.0.44
PING 192.168.0.44 (192.168.0.44): 56 data bytes
64 bytes from 192.168.0.44: seq=0 ttl=64 time=1.507 ms
64 bytes from 192.168.0.44: seq=1 ttl=64 time=1.255 ms
64 bytes from 192.168.0.44: seq=2 ttl=64 time=1.205 ms
^C
--- 192.168.0.44 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.205/1.322/1.507 ms
osmc@bedroom:~$ arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.0.25             ether   88:ae:dd:03:e2:16   C                     eth0
192.168.0.1                      (incomplete)                              eth0
192.168.0.44             ether   94:cc:04:60:04:dc   C                     eth0

From the working one (44) I can ping the non-working one (45)

osmc@livingroom:~$ ping 192.168.0.45
PING 192.168.0.45 (192.168.0.45): 56 data bytes
64 bytes from 192.168.0.45: seq=0 ttl=64 time=1.265 ms
64 bytes from 192.168.0.45: seq=1 ttl=64 time=1.269 ms
64 bytes from 192.168.0.45: seq=2 ttl=64 time=1.238 ms
^C
--- 192.168.0.45 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.238/1.257/1.269 ms
osmc@livingroom:~$ arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.0.230            ether   40:b4:cd:33:f9:b4   C                     eth0
192.168.0.189            ether   40:b4:cd:98:c7:f9   C                     eth0
192.168.0.133            ether   40:b4:cd:76:b5:2d   C                     eth0
192.168.0.160            ether   96:af:dc:27:1c:a1   C                     eth0
192.168.0.128            ether   08:a6:bc:27:9d:40   C                     eth0
192.168.0.253            ether   1c:57:dc:42:2d:ac   C                     eth0
192.168.0.45             ether   94:cc:04:60:08:df   C                     eth0
192.168.0.1              ether   04:d9:f5:52:5e:18   C                     eth0
192.168.0.25             ether   88:ae:dd:03:e2:16   C                     eth0
192.168.0.101            ether   fc:49:2d:a2:6e:f1   C                     eth0

The non-working one can’t ping 192.168.0.1

When switching to DHCP I get a crazy IP, 169.254.129.135 with netmask 255.255.0.0
Cannot ssh to that, no route.

I’m thinking factory reset and start over maybe.

Means the Vero doesn’t communicate with your router

Did you try to switch cable or switch port?

You can try, but it might be actually a physical issue

2 Likes

Encouraged by your generous kind help, I did step back and do what you suggested.
I switched to a different port on the larger switch, no affect. Then I switched it to a different switch, a smaller one that was plugged into the larger switch, and bingo everything works again. I realized, even though there are many other devices connected to the large switch, none of them need to get out to the internet. The larger switch is the one the router is plugged into. It’s still a bit unknown, because the old previous connections worked fine for over a month.

Thank you again for your nice help, so appreciated!!! :slightly_smiling_face:

2 Likes