Daily Network-Connection loss - USB Nic

S

simax

New Member
Mar 10, 2022
6
0
1
38
Hi everybody,

I'am using the following system with proxmox Virtual Environment 7.1-7:


I got only one virtual instance with a SOPHOS XG Home Firewall. On these Instance I got 2 two bridged attached. Net0 is connected to LAN and Net1 is connected to WAN.

Every day I lose network connection between 10 and 11. I can only fix it by disconnection and connecting the networkkable and it works fine again.


Code: 
Mar 10 10:17:01 pve CRON[1258190]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 10 10:17:01 pve CRON[1258191]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 10 10:17:01 pve CRON[1258190]: pam_unix(cron:session): session closed for user root
Mar 10 11:17:01 pve CRON[1266199]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 10 11:17:01 pve CRON[1266200]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 10 11:17:01 pve CRON[1266199]: pam_unix(cron:session): session closed for user root
Mar 10 11:54:48 pve kernel: ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
Mar 10 11:54:48 pve kernel: vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
Mar 10 11:54:54 pve kernel: ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
Mar 10 11:54:55 pve kernel: vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
Mar 10 11:54:55 pve kernel: vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state

Yesterday evening I have had a Teams call and the connections has broken up multiple. Maybe because of videocall? Too much traffic? I don't know...

Can you please help me? If you need more logs, please let me know. I'am new at linux so maybe you can help?

King Regards
 
Hello,

Please provide us with the output of pveversion -v and the output from dmesg when you lost the connection.

simax said:
Every day I lose network connection between 10 and 11. I can only fix it by disconnection and connecting the networkkable and it works fine again.
Click to expand...
There is a backup job or migration job at this time?
 
Hi Moayad,

here is the result. Hope this is enough information?

pveversion -v

Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

dmesg

Code: 
[309044.599617] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[309044.872284] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[309044.872287] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[309084.902325] device tap100i0 entered promiscuous mode
[309084.924586] fwbr100i0: port 1(fwln100i0) entered blocking state
[309084.924589] fwbr100i0: port 1(fwln100i0) entered disabled state
[309084.924626] device fwln100i0 entered promiscuous mode
[309084.924674] fwbr100i0: port 1(fwln100i0) entered blocking state
[309084.924676] fwbr100i0: port 1(fwln100i0) entered forwarding state
[309084.927320] vmbr2: port 2(fwpr100p0) entered blocking state
[309084.927322] vmbr2: port 2(fwpr100p0) entered disabled state
[309084.927354] device fwpr100p0 entered promiscuous mode
[309084.927374] vmbr2: port 2(fwpr100p0) entered blocking state
[309084.927376] vmbr2: port 2(fwpr100p0) entered forwarding state
[309084.930033] fwbr100i0: port 2(tap100i0) entered blocking state
[309084.930035] fwbr100i0: port 2(tap100i0) entered disabled state
[309084.930077] fwbr100i0: port 2(tap100i0) entered blocking state
[309084.930078] fwbr100i0: port 2(tap100i0) entered forwarding state
[309085.361797] device tap100i1 entered promiscuous mode
[309085.384238] fwbr100i1: port 1(fwln100i1) entered blocking state
[309085.384241] fwbr100i1: port 1(fwln100i1) entered disabled state
[309085.384279] device fwln100i1 entered promiscuous mode
[309085.384320] fwbr100i1: port 1(fwln100i1) entered blocking state
[309085.384321] fwbr100i1: port 1(fwln100i1) entered forwarding state
[309085.386891] vmbr0: port 2(fwpr100p1) entered blocking state
[309085.386893] vmbr0: port 2(fwpr100p1) entered disabled state
[309085.386926] device fwpr100p1 entered promiscuous mode
[309085.386976] vmbr0: port 2(fwpr100p1) entered blocking state
[309085.386978] vmbr0: port 2(fwpr100p1) entered forwarding state
[309085.389648] fwbr100i1: port 2(tap100i1) entered blocking state
[309085.389650] fwbr100i1: port 2(tap100i1) entered disabled state
[309085.389686] fwbr100i1: port 2(tap100i1) entered blocking state
[309085.389703] fwbr100i1: port 2(tap100i1) entered forwarding state
[309085.890087] device tap100i2 entered promiscuous mode
[309085.912580] fwbr100i2: port 1(fwln100i2) entered blocking state
[309085.912583] fwbr100i2: port 1(fwln100i2) entered disabled state
[309085.912619] device fwln100i2 entered promiscuous mode
[309085.912676] fwbr100i2: port 1(fwln100i2) entered blocking state
[309085.912693] fwbr100i2: port 1(fwln100i2) entered forwarding state
[309085.915327] vmbr1: port 2(fwpr100p2) entered blocking state
[309085.915330] vmbr1: port 2(fwpr100p2) entered disabled state
[309085.915362] device fwpr100p2 entered promiscuous mode
[309085.915415] vmbr1: port 2(fwpr100p2) entered blocking state
[309085.915416] vmbr1: port 2(fwpr100p2) entered forwarding state
[309085.918072] fwbr100i2: port 2(tap100i2) entered blocking state
[309085.918075] fwbr100i2: port 2(tap100i2) entered disabled state
[309085.918120] fwbr100i2: port 2(tap100i2) entered blocking state
[309085.918121] fwbr100i2: port 2(tap100i2) entered forwarding state
[395891.668203] pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
[395891.668213] nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[395891.668215] nvme 0000:01:00.0:   device [1c5c:174a] error status/mask=00000001/00000000
[395891.668216] nvme 0000:01:00.0:    [ 0] RxErr                
[396966.271044] pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
[396966.271056] nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[396966.271058] nvme 0000:01:00.0:   device [1c5c:174a] error status/mask=00000001/00000000
[396966.271060] nvme 0000:01:00.0:    [ 0] RxErr                
[480022.989156] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[480022.989382] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[480027.981158] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[480028.242051] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[480028.242056] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[481474.893826] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[481474.894040] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[481484.237841] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[481484.489565] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[481484.489570] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[515362.142881] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[515362.143348] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[515365.726775] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[515365.986210] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[515365.986215] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[515561.054929] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[515561.055204] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[515563.614983] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[515563.867757] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[515563.867762] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[516564.319488] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[516564.319877] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[516568.543474] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[516568.799297] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[516568.799301] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[518284.384241] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[518284.384661] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[518286.944353] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[518287.193973] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[518287.193977] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[518651.488532] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[518651.488879] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[518658.016458] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[518658.265024] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[518658.265028] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[518676.704544] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[518676.704625] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[518679.264471] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[518679.520128] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[518679.520133] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[518891.232578] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[518891.232896] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[518893.792581] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[518894.046042] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[518894.046048] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[518963.168578] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[518963.168911] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[518966.240580] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[518966.491397] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[518966.491402] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[532096.124161] pcieport 0000:00:1b.0: AER: Corrected error received: 0000:01:00.0
[532096.124170] nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[532096.124172] nvme 0000:01:00.0:   device [1c5c:174a] error status/mask=00000001/00000000
[532096.124174] nvme 0000:01:00.0:    [ 0] RxErr                
[558914.804627] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[558914.804885] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[558920.180742] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[558920.437377] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[558920.437381] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[570715.898543] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[570715.898661] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[570722.042579] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[570722.306472] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[570722.306476] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[644520.223676] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[644520.223858] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[644524.447602] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[644524.703649] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[644524.703653] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state
[645202.976023] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 0
[645202.976250] vmbr2: port 1(enxf8e43b5e15bf) entered disabled state
[645212.447976] ax88179_178a 2-1:1.0 enxf8e43b5e15bf: ax88179 - Link status is: 1
[645212.706693] vmbr2: port 1(enxf8e43b5e15bf) entered blocking state
[645212.706697] vmbr2: port 1(enxf8e43b5e15bf) entered forwarding state

There is a backup job or migration job at this time?
Click to expand...
No, nothing.
 
Last edited:
Hmmm, after you lose the network, do you see the network interface name in ip a output command? if yes, please post the output of ethtool enxf8e43b5e15bf command.
 
Moayad said:
Hmmm, after you lose the network, do you see the network interface name in ip a output command? if yes, please post the output of ethtool enxf8e43b5e15bf command.
Click to expand...
Iam mostly not at home when the things happening. Anyway maybe the result ip a helps you?

Code: 
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: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
    altname wlp0s20f3
8: enxf8e43b5e15bf: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr2 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.96/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 MAC-ADDRESS scope link
       valid_lft forever preferred_lft forever
11: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.77/24 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 MAC-ADDRESS scope link
       valid_lft forever preferred_lft forever
12: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
    inet6 MAC-ADDRESS scope link
       valid_lft forever preferred_lft forever
49: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
50: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
51: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr2 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
52: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
53: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master fwbr100i1 state UNKNOWN group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
54: fwbr100i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
55: fwpr100p1@fwln100i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff
56: fwln100i1@fwpr100p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i1 state UP group default qlen 1000
    link/ether MAC-ADDRESS brd ff:ff:ff:ff:ff:ff

Regarding ethtool, I can't use it because it is not installed. When I try to install it I receive this:

Code: 
apt-get install ethtool
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  ethtool
0 upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
Need to get 182 kB of archives.
After this operation, 611 kB of additional disk space will be used.
Err:1 http://ftp.de.debian.org/debian bullseye/main amd64 ethtool amd64 1:5.9-1
  Could not connect to ftp.de.debian.org:80 (141.76.2.4). - connect (113: No route to host)
E: Failed to fetch http://ftp.de.debian.org/debian/pool/main/e/ethtool/ethtool_5.9-1_amd64.deb  Could not connect to ftp.de.debian.org:80 (141.76.2.4). - connect (113: No route to host)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I also can't deploy the debian-updates:

Code: 
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  base-files bsdextrautils bsdutils chrony curl distro-info-data eject fdisk
  libblkid1 libcryptsetup12 libcurl3-gnutls libcurl4 libexpat1 libfdisk1 libgmp10
  libmount1 libnss3 libseccomp2 libsmartcols1 libsmbclient libuuid1 libwbclient0
  mount samba-common samba-libs smbclient util-linux vim-common vim-tiny wget xxd
31 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.4 MB of archives.
After this operation, 30.7 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://ftp.de.debian.org/debian bullseye/main amd64 base-files amd64 11.1+deb11u2
  Could not connect to ftp.de.debian.org:80 (141.76.2.4). - connect (113: No route to host)
Err:2 http://ftp.de.debian.org/debian bullseye/main amd64 libseccomp2 amd64 2.5.1-1+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:3 http://ftp.de.debian.org/debian bullseye/main amd64 chrony amd64 4.0-8+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:4 http://ftp.de.debian.org/debian bullseye/main amd64 libgmp10 amd64 2:6.2.1+dfsg-1+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:5 http://ftp.de.debian.org/debian bullseye/main amd64 vim-tiny amd64 2:8.2.2434-3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:6 http://ftp.de.debian.org/debian bullseye/main amd64 xxd amd64 2:8.2.2434-3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:7 http://ftp.de.debian.org/debian bullseye/main amd64 vim-common all 2:8.2.2434-3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:8 http://ftp.de.debian.org/debian bullseye/main amd64 wget amd64 1.21-1+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:9 http://ftp.de.debian.org/debian bullseye/main amd64 curl amd64 7.74.0-1.3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:10 http://ftp.de.debian.org/debian bullseye/main amd64 libcurl4 amd64 7.74.0-1.3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:11 http://ftp.de.debian.org/debian bullseye/main amd64 distro-info-data all 0.51+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:12 http://ftp.de.debian.org/debian bullseye/main amd64 libcurl3-gnutls amd64 7.74.0-1.3+deb11u1
  Unable to connect to ftp.de.debian.org:http:
Err:13 http://security.debian.org bullseye-security/main amd64 bsdutils amd64 1:2.36.1-8+deb11u1
 
Ok, fixed the update-problem and was able to apply them. I also could install ethtool and this is the result:

Code: 
root@pve:~# ethtool enxf8e43b5e15bf
Settings for enxf8e43b5e15bf:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: MII
        PHYAD: 3
        Transceiver: internal
        Supports Wake-on: pg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
 
Hi @Moayad! Yesterday evening I just setted up a new system.

The system is brand new and all Clients receive IPs succesfully and can connect to the internet via SOPHOS XG Home. I now recognized that network connections breakes when I got a WhatsApp-Videocall, Teams-Videocall and etc. Mostly wired connections seems to be ok at this "WAN-Problem?" but yesterday also wired connection lost connection to the internet.

The problem makes me crazy regarding the afford and things I already tested. Maybe someone could please help?
 
Unfortunately I can't help you, but I want to share my experience with those USB-NICs.

I tried two different USB-NICs (both Realtek but different chipsets, one 1G and one 2.5G) for the main LAN-interface including cluster- and pfSense-HA-traffic and it was absolutely not reliable.

The connection with the 1G one dropped several times a day and with the 2.5G one also at least once a day.
 
@Neobin Thanks for sharing your experiences here. Maybe the USB-NIC is the problem I don't know yes. But i have alredy read that peoble are using these usb-nics and for me they seems to be stable? So in my opinion maybe it is a different issue?
 
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