Host Unreachable - can't update anything

voarsh

New Member
Nov 20, 2020
5
0
1
24
On my PROXMOX VE host, I just finished installing and used ethernet, I had to fiddle around with it.

I can connect over my LAN to PROXMOX - however any apt-get update, or doing any template updates/downloads or even pings give be unable to connect, host unreachable errors.

Code:
starting apt-get update
Err:1 http://ftp.uk.debian.org/debian buster InRelease
  Cannot initiate the connection to ftp.uk.debian.org:80 (2001:1b40:5600:ff80:f8ee::1). - connect (101: Network is unreachable) Could not connect to ftp.uk.debian.org:80 (78.129.164.123). - connect (113: No route to host)
Ign:2 http://ftp.uk.debian.org/debian buster-updates InRelease
Err:3 http://ftp.uk.debian.org/debian buster-updates Release
  Cannot initiate the connection to ftp.uk.debian.org:80 (2001:1b40:5600:ff80:f8ee::1). - connect (101: Network is unreachable)
Err:4 http://security.debian.org buster/updates InRelease
  Cannot initiate the connection to debian.map.fastlydns.net:80 (2a04:4e42:4::644). - connect (101: Network is unreachable) Could not connect to debian.map.fastlydns.net:80 (151.101.18.132). - connect (113: No route to host) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:e00::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:200::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:a00::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:c00::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:800::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:400::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42:600::204). - connect (101: Network is unreachable) Cannot initiate the connection to security.debian.org:80 (2a04:4e42::204). - connect (101: Network is unreachable) Could not connect to security.debian.org:80 (151.101.128.204). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.64.204). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.0.204). - connect (113: No route to host) Could not connect to security.debian.org:80 (151.101.192.204). - connect (113: No route to host)
Reading package lists...
E: The repository 'http://ftp.uk.debian.org/debian buster-updates Release' no longer has a Release file.



starting template download from: http://download.proxmox.com/images/system/archlinux-base_20200508-1_amd64.tar.gz
target file: /var/lib/vz/template/cache/archlinux-base_20200508-1_amd64.tar.gz
--2020-11-20 22:33:55--  http://download.proxmox.com/images/system/archlinux-base_20200508-1_amd64.tar.gz
Resolving download.proxmox.com (download.proxmox.com)... 51.91.38.34, 2001:41d0:203:7470::34
Connecting to download.proxmox.com (download.proxmox.com)|51.91.38.34|:80... failed: No route to host.
Connecting to download.proxmox.com (download.proxmox.com)|2001:41d0:203:7470::34|:80... failed: Network is unreachable.

I am wondering if PROXMOX doesn't like the switch in networks - from Ethernet to Wifi.... and the gateway is wrong?
The nameserver isn't 8.8.8.8 -


Can I get some help?
 
Last edited:

voarsh

New Member
Nov 20, 2020
5
0
1
24
Ethernet works but WiFi doesn't.

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: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether f0:4d:a2:dc:3b:d3 brd ff:ff:ff:ff:ff:ff

inet 192.168.0.167/24 brd 192.168.0.255 scope global dynamic noprefixroute enp5s0

valid_lft 83641sec preferred_lft 83641sec

inet6 fd3d:2817:d583:0:d872:19b7:dcdd:99da/64 scope global noprefixroute

valid_lft forever preferred_lft forever

inet6 2a02:c7f:dc7d:ab00:85d3:efd5:fe73:575d/64 scope global dynamic noprefixroute

valid_lft 2081sec preferred_lft 2080sec

inet6 fe80::ba15:5337:5955:1aed/64 scope link noprefixroute

valid_lft forever preferred_lft forever

13: wlx1cbfce0ddcd0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

link/ether 1c:bf:ce:0d:dc:d0 brd ff:ff:ff:ff:ff:ff



I believe enp5s0 is the ethernet cable. wlx1cbfce0ddcd0 is the wifi.

ip route

default via 192.168.0.1 dev enp5s0 proto dhcp metric 100

default via 192.168.43.1 dev wlx1cbfce217ac4 proto dhcp metric 600

192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.167 metric 100

192.168.43.0/24 dev wlx1cbfce217ac4 proto kernel scope link src 192.168.43.242 metric 6000



I hope this helps a bit?



My /etc/network/interfaces:

auto lo

iface lo inet loopback



iface wlx1cbfce217ac4 inet manual



auto vmbr0

iface wlx1cbfce0ddcd0 inet static



address 192.168.43.242

netmask 255.255.255.0

gateway 192.168.43.1

bridge_ports wlx1cbfce217ac4

bridge_stp off

bridge_fd 0
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!