- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 4 2025
Nov 3 2025
No passthrough.
In general, the configuration looks like this:
HP DL 360G10 Servers
Windows Server 2019 with Hyper-V role
Vyos VMs Generation 2.
NIC ports are grouped at the OS level to Team (like bond in Linux).
After installing a new NIC (HPE P26253-B21, Broadcom BCM57416), we simply changed the members of this Network Team, nothing more.
Up to this point, everything had been working properly for several years.
@lbv2rus Do you passthrough NICs to the VM?
PR (merged): https://github.com/vyos/vyos-1x/pull/4786
Hi @evgmol, nice one, thanks.
Nov 2 2025
It is definately related to wide-dhcp-client as it takes upo to 30 seconds for the process to terminate. Root cause still unknown - but I've seen this lately a lot while debugging PPPoE DHCPv6-PD things.
The maintainers have vouched for:
Nov 1 2025
Some more background information:
Please share the full configuration. bond0 is not listed in the example above.
Oct 31 2025
Proposed CLI:
set vpp ipfix collector <tag-ip> port 2055 set vpp ipfix collector <tag-ip> path-mtu 1450 set vpp ipfix collector <tag-ip> source-address 192.0.2.5 set vpp ipfix collector <tag-ip> template-interval xx set vpp ipfix collector <tag-ip> udp-checksum set vpp ipfix interface <x> [rx|tx|both] (both by default) set vpp ipfix interface <x> flow-variant <l2|ip4|ip6> (l2 by default) set vpp ipfix active-timeout x set vpp ipfix inactive-timeout y set vpp ipfix flowprobe-record <l2|l3|l4>