[SOLVED] unable to perform apt update

D

dadoblake

New Member
Nov 29, 2023
13
0
1
Hello guys,
i spent the whole day searching (maybe the wrong thing) without any success.
I have two PVE nodes, fresh installed with the 8.1 ISO, but one of them is having issues performing apt update. basically it looks like unable to reach download.proxmox.com and ftp.it.debian.org. on the other node everything looks fine
This is the config of /etc/apt/sources.list of the non-working node (pve)
Code: 
deb http://ftp.de.debian.org/debian bookworm main contrib

deb http://ftp.de.debian.org/debian bookworm-updates main contrib

# security updates
deb http://security.debian.org bookworm-security main contrib

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
first, when it was ftp.it.debian.org it was unable to reach it too, i had to change it to ftp.de.debian.org to let it reach at least debian repos, but for the proxmox one there is no mirror so i can't change the address
and his apt update output
Code: 
root@pve:~# apt update
Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB]
Get:2 http://security.debian.org bookworm-security/main amd64 Packages [137 kB]
Get:3 http://ftp.de.debian.org/debian bookworm InRelease [151 kB]
Get:4 http://ftp.de.debian.org/debian bookworm-updates InRelease [52.1 kB]
Get:5 http://ftp.de.debian.org/debian bookworm/main amd64 Packages [8,787 kB]
Get:6 http://ftp.de.debian.org/debian bookworm/main Translation-en [6,109 kB]
Get:7 http://ftp.de.debian.org/debian bookworm/contrib amd64 Packages [54.1 kB]
Get:8 http://ftp.de.debian.org/debian bookworm/contrib Translation-en [48.7 kB]
Get:9 http://ftp.de.debian.org/debian bookworm-updates/main amd64 Packages [12.7 kB]
Get:10 http://ftp.de.debian.org/debian bookworm-updates/main Translation-en [13.8 kB]
Ign:11 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:12 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Ign:11 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:12 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Ign:11 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:12 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Err:11 http://download.proxmox.com/debian/pve bookworm InRelease
  Connection failed [IP: 212.224.123.70 80]
Err:12 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
  Connection failed [IP: 212.224.123.70 80]
Fetched 203 kB in 8min 1s (422 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease  Connection failed [IP: 212.224.123.70 80]
W: Failed to fetch http://download.proxmox.com/debian/ceph-reef/dists/bookworm/InRelease  Connection failed [IP: 212.224.123.70 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.


here's the /etc/apt/sources.list of the working node (pve2)

Code: 
deb http://ftp.it.debian.org/debian bookworm main contrib

deb http://ftp.it.debian.org/debian bookworm-updates main contrib

# security updates
deb http://security.debian.org bookworm-security main contrib

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
with his apt update output
Bash: 
root@pve2:~# apt update
Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:2 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:3 http://download.proxmox.com/debian/ceph-quincy bookworm InRelease
Get:4 http://security.debian.org bookworm-security/main amd64 Packages [137 kB]
Hit:5 http://ftp.it.debian.org/debian bookworm InRelease
Get:6 http://ftp.it.debian.org/debian bookworm-updates InRelease [52.1 kB]
Fetched 237 kB in 1s (249 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

they are in the absolutely same network, same switch, same vlan, same wan... it's driving me crazy to figure it out why one is able to reach italian debian mirror and the other one not

/etc/network/interfaces of pve (non-working)
Code: 
root@pve:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface xxxxxxxxxxxxxxx inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports xxxxxxxxxxxxxxx eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

iface yyyyyyyyyyyyyyyy inet manual

iface eno1 inet manual

auto vmbr0.1
iface vmbr0.1 inet static
        address 10.8.92.141/24
        gateway 10.8.92.1

#source /etc/network/interfaces.d/*


/etc/network/interfaces of pve2 (working)
Code: 
root@pve2:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr0.1
iface vmbr0.1 inet static
        address 10.8.92.142/24
        gateway 10.8.92.1

#source /etc/network/interfaces.d/*

it doesn't make any sense to me, same network, same iso, same image but totally different result
i tried some stuff to troubleshoot it
Code: 
root@pve:~# curl -vvv download.proxmox.com
*   Trying 212.224.123.70:80...
* Connected to download.proxmox.com (212.224.123.70) port 80 (#0)
> GET / HTTP/1.1
> Host: download.proxmox.com
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Fri, 09 Feb 2024 00:12:30 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
<
<html>
<head><title>Index of /</title></head>
<body>
<h1>Index of /</h1><hr><pre><a href="../">../</a>
<a href="debian/">debian/</a>                                            08-Sep-2023 11:47                   -
<a href="images/">images/</a>                                            08-Feb-2024 11:49                   -
<a href="iso/">iso/</a>                                               07-Feb-2024 16:05                   -
<a href="temp/">temp/</a>                                              01-Feb-2024 08:53                   -
</pre><hr></body>
</html>
* Connection #0 to host download.proxmox.com left intact

root@pve:~# wget http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
--2024-02-09 01:18:31--  http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
Resolving download.proxmox.com (download.proxmox.com)... 212.224.123.70, 2a01:7e0:0:424::249
Connecting to download.proxmox.com (download.proxmox.com)|212.224.123.70|:80... connected.
HTTP request sent, awaiting response...
Code: 
root@pve2:~# curl -vvv download.proxmox.com
*   Trying 51.91.38.34:80...
* Connected to download.proxmox.com (51.91.38.34) port 80 (#0)
> GET / HTTP/1.1
> Host: download.proxmox.com
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Fri, 09 Feb 2024 00:12:51 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
<
<html>
<head><title>Index of /</title></head>
<body>
<h1>Index of /</h1><hr><pre><a href="../">../</a>
<a href="debian/">debian/</a>                                            08-Sep-2023 11:47                   -
<a href="images/">images/</a>                                            08-Feb-2024 11:49                   -
<a href="iso/">iso/</a>                                               07-Feb-2024 16:05                   -
<a href="temp/">temp/</a>                                              01-Feb-2024 08:53                   -
</pre><hr></body>
</html>
* Connection #0 to host download.proxmox.com left intact

root@pve2:~# wget http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
--2024-02-09 01:18:26--  http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
Resolving download.proxmox.com (download.proxmox.com)... 212.224.123.70, 2a01:7e0:0:424::249
Connecting to download.proxmox.com (download.proxmox.com)|212.224.123.70|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2768 (2.7K) [application/octet-stream]
Saving to: ‘InRelease’

InRelease                                                 100%[=====================================================================================================================================>]   2.70K  --.-KB/s    in 0s

2024-02-09 01:18:26 (197 MB/s) - ‘InRelease’ saved [2768/2768]

sorry for the long post but it's the whole day i'm facing this
i hope it's something stupid i missed, but i need help

thanks in advance!
 
Last edited:
dadoblake said:
it doesn't make any sense to me, same network, same iso, same image but totally different result
i tried some stuff to troubleshoot it
Code: 
root@pve:~# curl -vvv download.proxmox.com
*   Trying 212.224.123.70:80...
* Connected to download.proxmox.com (212.224.123.70) port 80 (#0)
> GET / HTTP/1.1
> Host: download.proxmox.com
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Fri, 09 Feb 2024 00:12:30 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
<
<html>
<head><title>Index of /</title></head>
<body>
<h1>Index of /</h1><hr><pre><a href="../">../</a>
<a href="debian/">debian/</a>                                            08-Sep-2023 11:47                   -
<a href="images/">images/</a>                                            08-Feb-2024 11:49                   -
<a href="iso/">iso/</a>                                               07-Feb-2024 16:05                   -
<a href="temp/">temp/</a>                                              01-Feb-2024 08:53                   -
</pre><hr></body>
</html>
* Connection #0 to host download.proxmox.com left intact

root@pve:~# wget http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
--2024-02-09 01:18:31--  http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
Resolving download.proxmox.com (download.proxmox.com)... 212.224.123.70, 2a01:7e0:0:424::249
Connecting to download.proxmox.com (download.proxmox.com)|212.224.123.70|:80... connected.
HTTP request sent, awaiting response...
Click to expand...

Can you post tracepath from both working and non-working node?

EDIT: You can redact the hops, but show the pmtu.
 
Last edited:
here's the non-working
Code: 
root@pve:~# tracepath download.proxmox.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  xxxxxxxx                                                            1.476ms
 1:  xxxxxxxx                                                            0.991ms
 2:  xxxxxxxx                                                            2.219ms
 3:  xxxxxxxx                                                            5.047ms
 4:  mno-b6-link.ip.twelve99.net                           4.958ms
 5:  mno-b2-link.ip.twelve99.net                          21.469ms (This broken router returned corrupted payload) asymm  7
 6:  ffm-bb2-link.ip.twelve99.net                         14.375ms asymm  7
 7:  ffm-b11-link.ip.twelve99.net                         14.265ms asymm  6
 8:  firstcolo-ic-334888.ip.twelve99-cust.net             17.045ms
 9:  ae1.3904.ce2.fra1.de.first-colo.net                  17.309ms
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

and the working
Code: 
root@pve2:~# tracepath download.proxmox.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  xxxxxxxx                                                            0.994ms
 1:  xxxxxxxx                                                            0.875ms
 2:  xxxxxxxx                                                            2.194ms
 3:  xxxxxxxx                                                            5.848ms
 4:  mno-b6-link.ip.twelve99.net                           5.616ms
 5:  mno-b2-link.ip.twelve99.net                          25.659ms (This broken router returned corrupted payload) asymm  7
 6:  ffm-bb2-link.ip.twelve99.net                         14.717ms asymm  7
 7:  ffm-b11-link.ip.twelve99.net                         15.426ms asymm  6
 8:  firstcolo-ic-334888.ip.twelve99-cust.net             17.591ms
 9:  ae1.3904.ce2.fra1.de.first-colo.net                  17.635ms
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500
 
tempacc346235 said:
Can you check from the working one multiple times:

Code: 
arp $id_address_of_non_working
Click to expand...
here it is
Code: 
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry

just to clarify, the gateway (a fritzbox) looks okay

Code: 
root@pve2:~# arp 10.8.92.1
Address                  HWtype  HWaddress           Flags Mask            Iface
fritz.box                ether   xx:xx:xx:xx:xx:xx   C                     vmbr0.1
 
On the non-working node, is there anything in the /etc/apt/sources.list.d/ directory? If so, check to make sure that none of them have a conflicting url in them.
 
dadoblake said:
here it is
Code: 
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry
root@pve2:~# arp 10.8.92.141
10.8.92.141 (10.8.92.141) -- no entry

just to clarify, the gateway (a fritzbox) looks okay

Code: 
root@pve2:~# arp 10.8.92.1
Address                  HWtype  HWaddress           Flags Mask            Iface
fritz.box                ether   xx:xx:xx:xx:xx:xx   C                     vmbr0.1
Click to expand...

Sorry, just to be sure, can you show a ping just before the arp is run?
 
tempacc346235 said:
Sorry, just to be sure, can you show a ping just before the arp is run?
Click to expand...
after the ping it shows something
Code: 
root@pve2:~# ping 10.8.92.141
PING 10.8.92.141 (10.8.92.141) 56(84) bytes of data.
64 bytes from 10.8.92.141: icmp_seq=1 ttl=64 time=1.13 ms
64 bytes from 10.8.92.141: icmp_seq=2 ttl=64 time=0.705 ms
64 bytes from 10.8.92.141: icmp_seq=3 ttl=64 time=0.766 ms
64 bytes from 10.8.92.141: icmp_seq=4 ttl=64 time=0.789 ms
^C
--- 10.8.92.141 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3028ms
rtt min/avg/max/mdev = 0.705/0.848/1.133/0.167 ms
root@pve2:~# arp 10.8.92.141
Address                  HWtype  HWaddress           Flags Mask            Iface
pve.fritz.box            ether   xx:xx:xx:xx:xx:xx   C                     vmbr0.1
 
dadoblake said:
after the ping it shows something
Code: 
root@pve2:~# ping 10.8.92.141
PING 10.8.92.141 (10.8.92.141) 56(84) bytes of data.
64 bytes from 10.8.92.141: icmp_seq=1 ttl=64 time=1.13 ms
64 bytes from 10.8.92.141: icmp_seq=2 ttl=64 time=0.705 ms
64 bytes from 10.8.92.141: icmp_seq=3 ttl=64 time=0.766 ms
64 bytes from 10.8.92.141: icmp_seq=4 ttl=64 time=0.789 ms
^C
--- 10.8.92.141 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3028ms
rtt min/avg/max/mdev = 0.705/0.848/1.133/0.167 ms
root@pve2:~# arp 10.8.92.141
Address                  HWtype  HWaddress           Flags Mask            Iface
pve.fritz.box            ether   xx:xx:xx:xx:xx:xx   C                     vmbr0.1
Click to expand...

Sorry, I better should have asked if arping -b $ip_address_of_non_working shows all the same MACs.
 
Russell said:
On the non-working node, is there anything in the /etc/apt/sources.list.d/ directory? If so, check to make sure that none of them have a conflicting url in them.
Click to expand...
there's almost the same stuff as in the working node (pve2) so i guess it's not interfering
the difference it's because i tried to install ceph from gui selecting reef version on node pve (non working), so pve2 is actually less modified than pve which wasn't working even before trying to install ceph reef
Code: 
root@pve:~# ls -la /etc/apt/sources.list.d/
total 12
drwxr-xr-x 2 root root 4096 Feb  9 00:52 .
drwxr-xr-x 9 root root 4096 Feb  9 00:58 ..
-rw-r--r-- 1 root root   74 Feb  9 00:52 ceph.list
root@pve:~# cat /etc/apt/sources.list.d/ceph.list
deb http://download.proxmox.com/debian/ceph-reef bookworm no-subscription
Code: 
root@pve2:~# ls -la /etc/apt/sources.list.d/
total 12
drwxr-xr-x 2 root root 4096 Feb  8 18:29 .
drwxr-xr-x 9 root root 4096 Feb  8 19:56 ..
-rw-r--r-- 1 root root   65 Feb  8 18:29 ceph.list
root@pve2:~# cat /etc/apt/sources.list.d/ceph.list
deb http://download.proxmox.com/debian/ceph-quincy bookworm main
 
tempacc346235 said:
Sorry, I better should have asked if arping -b $ip_address_of_non_working shows all the same MACs.
Click to expand...
Code: 
root@pve2:~# arping -b 10.8.92.141
ARPING 10.8.92.141
Timeout
Timeout
60 bytes from xx:xx:xx:xx:xx:xx (10.8.92.141): index=0 time=773.526 msec
Timeout
[just a bunch of timeout]
Timeout
^C
--- 10.8.92.141 statistics ---
31 packets transmitted, 1 packets received,  97% unanswered (0 extra)
rtt min/avg/max/std-dev = 773.526/773.526/773.526/0.000 ms
it actually gave me one answer so it's one mac address... do i have to wait more answers to compare them? (i just XX the mac address but it was displayed)
 
dadoblake said:
Code: 
root@pve2:~# arping -b 10.8.92.141
ARPING 10.8.92.141
Timeout
Timeout
60 bytes from xx:xx:xx:xx:xx:xx (10.8.92.141): index=0 time=773.526 msec
Timeout
[just a bunch of timeout]
Timeout
^C
--- 10.8.92.141 statistics ---
31 packets transmitted, 1 packets received,  97% unanswered (0 extra)
rtt min/avg/max/std-dev = 773.526/773.526/773.526/0.000 ms
it actually gave me one answer so it's one mac address... do i have to wait more answers to compare them? (i just XX the mac address but it was displayed)
Click to expand...
No this should be returning all the same MAC one after another, perhaps occassionally only have a timeout and the latencies should be in <10msec really.

Something's off with the network.

Can you run the same the other way around? So from the non-working against the working's IP, for instance?
 
dadoblake said:
/etc/network/interfaces of pve (non-working)
Code: 
root@pve:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface xxxxxxxxxxxxxxx inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports xxxxxxxxxxxxxxx eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

iface yyyyyyyyyyyyyyyy inet manual

iface eno1 inet manual

auto vmbr0.1
iface vmbr0.1 inet static
        address 10.8.92.141/24
        gateway 10.8.92.1

#source /etc/network/interfaces.d/*
Click to expand...

What's secret about the ifaces, btw? Btw there's no WiFi going on there, is it?
 
tempacc346235 said:
No this should be returning all the same MAC one after another, perhaps occassionally only have a timeout and the latencies should be in <10msec really.

Something's off with the network.

Can you run the same the other way around? So from the non-working against the working's IP, for instance?
Click to expand...
i did .141 -> .142 and got just timeouts
they are on stupid 40€ zyxel "managed" 8-port switch (pve is on switch1 with the "uplink" and pve2 is on the other which is plugged to switch1) but i have other stuff plugged on them and never had issues like that... could be something on those switches?
 
dadoblake said:
i did .141 -> .142 and got just timeouts
they are on stupid 40€ zyxel "managed" 8-port switch (pve is on switch1 with the "uplink" and pve2 is on the other which is plugged to switch1) but i have other stuff plugged on them and never had issues like that... could be something on those switches?
Click to expand...

Can you try something? Do not use VID 1, use some other arbitrary number, adjust the tagging on the switch accordingly.
 
tempacc346235 said:
Can you try something? Do not use VID 1, use some other arbitrary number, adjust the tagging on the switch accordingly.
Click to expand...
it can be a try... i will, but i can't now on-the-go

just for completion, i moved the pve node from another room, it was plugged into a same stupid-managed switch, i never changed VID and before this movement it was working correctly... this make even more sense to point the "network" side
 
dadoblake said:
it can be a try... i will, but i can't now on-the-go

just for completion, i moved the pve node from another room, it was plugged into a same stupid-managed switch, i never changed VID and before this movement it was working correctly... this make even more sense to point the "network" side
Click to expand...

There's no way for me to know how that switch is tagging frames. If you want to split it into VLANs, I would normally not want to have PVE together with (what I assume) is your switches management VLAN anyways.

You can also work backwards, just set it as unmanaged and see if your apt issues magically resolve themselves. BTW If you absolutely do not need bridge-vlan-aware, I would not use it going on either, but that's not related to this issue.

Oh and last note, do not cut yourself off the switch management, leave a port with that 1 untagged for you to plug into if need be.
 
dadoblake said:
just for completion, i moved the pve node from another room, it was plugged into a same stupid-managed switch, i never changed VID and before this movement it was working correctly... this make even more sense to point the "network" side
Click to expand...

Oh and one more thing - could it be a bad patch cable or outlet?
 
tempacc346235 said:
There's no way for me to know how that switch is tagging frames. If you want to split it into VLANs, I would normally not want to have PVE together with (what I assume) is your switches management VLAN anyways.

You can also work backwards, just set it as unmanaged and see if your apt issues magically resolve themselves. BTW If you absolutely do not need bridge-vlan-aware, I would not use it going on either, but that's not related to this issue.

Oh and last note, do not cut yourself off the switch management, leave a port with that 1 untagged for you to plug into if need be.
Click to expand...
1) i set the ports as "tagged egress members" which means (from what I understood) the port is aware that the device connected has to manage tagging and it uses the vlan table to forward packets to the right port/s (but maybe I'm wrong)
2) sure, that's why I can't do I now, I'm away from home
3) all the switches have 1 "emergency" port untagged, I already cut myself out in past
 
You must log in or register to reply here.

About

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

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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 yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back