The problem exists when LLDP is not configured but one wants to run the detail command. Running "show lldp neighbors" is not possible when LLDP is not running - so should the the detail command.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 3 2020
I would not use cpu<numbe> but just <number> like is used for taskset for example, but it would be a real improvement for users.
An op command should be provided giving the affinity of CPU ( from lscpu ) and the documentation should warn about interrupt crossing numa domains (for the case where a network card is providing multiple interfaces).
I actually can not reproduce this issue after fixing T2740. Please retry with the latest rolling which was just uploaded: vyos-1.3-rolling-202008031114-amd64.iso
This configuration replicates the error:
I have to apologize here: While working on https://phabricator.vyos.net/T2653 I knew I must change this and did it on PPPoE but I totally forgot about this on all other interfaces as PPPoE has a special case here.
OK, I take that back. Even when the interface with prefix-delegation defined is dead last, it still has this error. The last IP address is not configured, although /run/dhcp6c/dhcp6c.ethN.conf is correctly created, and DHCPv6-PD works. But config parsing is broken, and the entire config node is missing when I query for it.
Please provide a full configuration for replication
It's actually a little worse than I'd initially realized; the interface that DHCPv6-PD is being requested on (the interface with the prefix-delegation stanza) has to be the very last interface, even if it doesn't refer to the ones after it. So, even if I don't delegate any addresses from eth2 to eth3, it still fails. I have to do the delegation from interface eth3 on a system with four ethernet interfaces. And preliminary testing suggests that it has to be eth5 on a system with 6, even if eth4 and eth5 aren't configured at all.
@c-po Change the task and add duplicate address detection option in force ARP
Aug 2 2020
Hi Jack, the problem was solved in two VMs at OCI after I update the VyOS to version vyos-1.3-rolling-202007311330-amd64.iso.
I also propose migrating the CLI interface from a bitmask (which IMHO no user understands)
This was actually drafted as a PR (https://github.com/vyos/vyos-1x/pull/461) but this PR changed the general incluide file and added only a PPPoE server implementation and left out all the others.
I like the idea of adding our own implementation which mimics jmespath.search() so this definately a +1.