The issue turned out to be at the host level. By default SR-IOV VFs are not allowed to change their own mac addresses or send packets with a different mac address, and since this is required for LACP bonding the configuration would just fail.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Dec 22 2020
@robertoberto Can you provide next commands?
show interfaces ethernet eth0 physical sudo ethtool -k eth0 | grep offload
Put in a PR to add LDP ordered control operation for LDP.
cpo@LR1.wue3# commit Both Wireguard port and address must be defined for peer "foo" if either one of them is set!
@primoz What are the benefits?
This breaks with common configuration patterns/naming in Wireguard. Nobody will know what you're talking about when you say address and port in this context. And the CLI helpers adds documentation that would lead you to believe you are listening for connections, see line 105 in nterface-definitions/interfaces-wireguard.xml.in.
dhcpcd is a pretty good alternative. Well maintained and popularly used by many. I used it in a plain Linux router project and it was good enough for my use cases.
PR for crux https://github.com/vyos/vyos-build/pull/138
It still would be nice though. ANy other good IPv6 DHCP clients out there?
Yeah also it looks like wide is hardcoded to support only type 1 DUID (LLT) anyway.... so probably it wasn't accidentally "forgotten" in 1.3 migration that someone probably has realized it wasn't viable to support it... Thanks :)
Undortunately it only worked in 50% of the cases properly. Also there is only one global duid file so you can not have multiple duids (one per each interface).
@vagardx thank you for this rant.
Sorry I am confused. I took a brief look at the code of dhcp6c and it appears manually modifying the dhcp6c_duid file should be able to keep the change persistent: https://github.com/jinmei/wide-dhcpv6/blob/24ee2a4f0009bc6ac9bd0b7b737aef93a4aa9905/common.c#L992. Did I miss anything? Thanks :)
Dec 21 2020
Accidentally deleted the comment. Is there plan to migrated to dhcpcd instead? dhcpcd has good ipv6 support and being actively maintained too. Thanks.
This breaks with standard configuration convention in Wireguard. Also, no documentation has been updated to reflect this breaking change.
I want to know the behavior of the implementation when upgrading the vyos version
Dec 20 2020
It looks like wide dhcp client does not support setting the DUID as it is overwritten again after a restart :(
OK, I now tried vyos-1.3-rolling-202012192139 and am happy to report that something since the previous version I tried and this version has now fixed the problem.