there is no business case for this feature
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 30 2024
looks like support request
@Viacheslav let me know if we want to do it, otherwise close it as wont fix and remove project
@part1cleth1ef still want to do it?
Oct 29 2024
In T6545#204568, @ordex wrote:Thanks for the pointer. I am even surprised that this worked with --cipher. In any case, I presume that template needs an exception.
Thanks for the pointer. I am even surprised that this worked with --cipher. In any case, I presume that template needs an exception.
The problem is that the template returns the none values in uppercase https://github.com/vyos/vyos-1x/blob/ba18d12f6863505133cde688d5e8188689af63bb/python/vyos/template.py#L567
This is the bad one:
Oct 28 18:03:45 debian vyos_net_name[896]: Started with arguments: ['/lib/udev/vyos_net_name', 'e8']
Oct 28 18:03:45 debian vyos_net_name[886]: Started with arguments: ['/lib/udev/vyos_net_name', 'e4', '00:0c:29:2d:44:53', 'eth4']
Oct 28 18:03:45 debian vyos_net_name[888]: Started with arguments: ['/lib/udev/vyos_net_name', 'e6', '00:0c:29:2d:44:3f', 'eth2']
Oct 28 18:03:45 debian vyos_net_name[887]: Started with arguments: ['/lib/udev/vyos_net_name', 'e5', '00:0c:29:2d:44:35', 'eth1']
Oct 28 18:03:45 debian vyos_net_name[884]: Started with arguments: ['/lib/udev/vyos_net_name', 'e3', '00:0c:29:2d:44:49', 'eth3']
Oct 28 18:03:45 debian vyos_net_name[885]: Started with arguments: ['/lib/udev/vyos_net_name', 'e2', '00:0c:29:2d:44:2b', 'eth0']
e7 is missing e8 has no mac address
FTR --ncp-disable was only supposed to disable the cipher negotiation. It was not meant to disable encryption entirely. --data-ciphers none is the way to go, but it seems you've already figure this out.
In T2584#204474, @syncer wrote:@Viacheslav do we want to do this?
@dmbaturin, what is the state of this?
@sarthurdev not sure if it's still actual for new implementation, if no please close as NA
There is no business case for mips support
ARM support will be handled in dedicated ticket
@Viacheslav do we want to do this?
This task is obsolete
The issue with automatic offload settings was addressed in T6716