我的网络上有两个 UniFi UAP-AC-Pro WAP，它们正在生成 LLDP 数据包，导致我的 Proxmox 服务器上接收帧丢失计数器增加。
我已经确认是lldpdWAP 产生了“不良”流量，因为当我停止并禁用 WAP 上的服务时它就会停止。
我尝试通过 阻止 LLDP ebtables，但没有成功。我还在 Proxmox 服务器上安装了 LLDP 工具，试图“捕获”流量，虽然这种方法有效，我可以在 proxmox 服务器上查看 LLDP 统计数据，但错误计数器仍在增加。
可能需要注意：由于这是一个虚拟化服务器，因此有几个标准 Linux 桥连接到该接口。
这是我在故障排除时运行的各种命令的输出：
ifconfig：
enp6s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 68:05:ca:bd:3b:7d txqueuelen 1000 (Ethernet)
RX packets 469667 bytes 523243591 (499.0 MiB)
RX errors 0 dropped 738 overruns 0 frame 0
TX packets 129160 bytes 18630382 (17.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 35 memory 0xf72c0000-f72e0000
ethertool -S
NIC statistics:
rx_packets: 470347
tx_packets: 129354
rx_bytes: 523549801
tx_bytes: 18673005
rx_broadcast: 4137
tx_broadcast: 846
rx_multicast: 19087
tx_multicast: 5599
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 19087
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 604
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 450825
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
tx_hwtstamp_timeouts: 0
tx_hwtstamp_skipped: 0
lspci -vv
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Gigabit CT Desktop Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 35
Region 0: Memory at f72c0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f7200000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at c000 [disabled] [size=32]
Region 3: Memory at f72e0000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at f7280000 [disabled] [size=256K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <128ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Device Serial Number 68-05-ca-ff-ff-bd-3b-7d
Kernel driver in use: e1000e
Kernel modules: e1000e
我还有一个tcpdumpLLDP 数据包，希望它们能有帮助。
除上述内容外，我还进行了一些修改并dropwatch运行了 Proxmox 基于的 Debian 稳定版本，并且没有显示 LLDP 数据包，因此没有关于为什么丢弃数据包的信息。
不幸的是，当涉及到我的具体问题时，我似乎已经用尽了 Google 的资源，所以希望这里有人能够提供一些资源来帮助我。