PR: https://github.com/vyos/vyos-build/pull/153

@Asteroza With Vyos, any service should be turned off by default unless it is explicitly configured by the user

Sorry, I have a question, why are there different codes for operation mode fetch configuration tree and configuration mode fetch configuration tree? Is it because of the uncertainty of the mode of action in the user's actions (such as the possibility of abruptly terminating the command)?

Hi, how is the container support now

I'm curious, I did a little research on Tacacs +, and I'm not sure what you want the certification service to do for you? SSH certification or?

Now, the last migration of this task should have completed the preliminary implementation (the operation mode can view NAT rules), but it does not support port rule display

PR: https://github.com/vyos/vyos-1x/pull/771

Latest PR of T2518: https://github.com/vyos/vyos-1x/pull/771 The display script of rule file is completed

After a while, I may consider how to provide the operation mode command for nat66

I don't seem to see the obvious problem (maybe I don't understand what you're referring to), assuming there is a problem and this is also an issue introduced by third party system components, maybe you should go upstream with feedback

Now the problem should be solved

Now, let's move the patch to 1.3

PR: https://github.com/vyos/vyatta-cfg-qos/pull/9

@Dmitry @a952637635. It seems that, I changed the handle address to avoid conflict. I don't know if it will conflict

PR:

• https://github.com/vyos/vyos-1x/pull/762
• https://github.com/vyos/vyatta-cfg-system/pull/139

PR: https://github.com/vyos/vyos-1x/pull/758

PR: https://github.com/vyos/vyos-1x/pull/708

@dmbaturin @c-po Hi, I have basically completed the T3116 draft implementation, test, I only inspect the ipvsadm rules, seems to work properly, the draft only for ipvsadm, to set up some rules, now, you and @c-po can achieve the preliminary examination of the draft (about smoke tests, I currently only normal execution of the command line configuration program testing, has not yet been configured efficacy)

Start implementing this draft

So I'm unsure how to rewrite that in a clean way, and I would appreciate your and @c-po's opinions on the subject

@c-po What do you think?

@dmbaturin @zsdc Perhaps we could discuss the possibility of changing the dhcp(v6) server to a better server (and what feature changes might exist), which I hope will address the older ISC's better support for interfaces such as PPPOE and the latest dhcp(v6) standard

Maybe we should consider using a better proxy server to complete the dhcpv6 agent

@c-po I would say that it would be better whether to report the problem upstream

I agree

This contains another error, see more

PR: https://github.com/vyos/vyos-1x/pull/727

The root cause of this problem is that VYOS does not use CPU0 and therefore cannot enable RPS on a single-core processor

PR: https://github.com/vyos/vyos-1x/pull/725

@c-po Why does the RPS setup function call fail, but the mirror error message is displayed?