This can be solved with the already existing source-address option. When it's set, advertisments are sent from a unicast IPv6 address, if it's assigned. If it's not assigned, they are not sent.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Fri, Jan 16
Thu, Jan 15
PR was not accepted
We already show the full private key in our configuration as we only have admin mode.
You cannot just restart vpp
It is already fixed in T8100.
@AnNK6 thank you for the report and details. The fact is that until privilege separation is implemented (https://vyos.dev/T7583), authentication allows sudo privileges implicitly (via the config system) if not explicitly. In that sense the issue is mooted until the work on the op-mode runner and related is complete, but be assured that alongside the work in T7583 and related, a general audit of shell escape mechanisms is ongoing in preparation; your report is quite useful for that current work. That being said, my quick test of the above against a local KVM system gives a different result (below), so I will need to take a closer look to reproduce.
Wed, Jan 14
Note that for 1.4.x there may be a separate cause of the false positive due to the older migration system (revised in 1.5); this is under investigation.
Note that this was fixed in https://vyos.dev/T7319 and backported for inclusion in 1.4.4. However, it will necessarily only apply to any upgrades from that version forward, e.g. 1.4.4 -> 1.4.5
Tue, Jan 13
Rebuild vyos-1x
And missed backport https://github.com/vyos/vyos-build/pull/1081
Problem reproduces in latest circinus build as well:
Mon, Jan 12
Duplicate of https://vyos.dev/T8141
PR https://github.com/vyos/vyos-1x/pull/4941
vyos@r14:~$ show vpp ipfix interfaces "vpp ipfix interface" is not configured vyos@r14:~$ vyos@r14:~$ show vpp ipfix collectors "vpp ipfix collector" is not configured vyos@r14:~$ vyos@r14:~$ show vpp ipfix table "vpp ipfix" is not configured vyos@r14:~$