Unfortunately, it seems that the same problem still happened. Although it seems that the container can be started normally after restart due to priority adjustment and some factors, it is not a normal operation result!

note: Record the process of upgrading from 1.4-rolling-202107010537 to 1.4-rolling-202107122017

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

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

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

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

Sorry, this may be my fault. It seems that I only pay attention to modifying the identifier below and forget the top definition. Sorry.

Hi, I found that the transmission speed of tinc seems very disappointing, even in some cases, even the normal network communication has problems..

I wonder why this is flagged only as refactoring bit you open an entire new CLI tree.

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

@Viacheslav I seem to find a strange problem. If I run two containers of adguardhome and nginx, they seem to work normally in the same image. However, once I upgrade and boot the new system, these two containers will be abnormal and can only be restored manually (try to delete them first, then recommit them, and need to modify the program appropriately), This is a robustness problem, which needs to be confirmed. If there is a problem, it needs to be solved!

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

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

Please use the following op-mode command to check:

OK, it seems that this problem doesn't need any repair and will be closed

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

@runar I just checked the current implementation. It seems that the current configuration is replacing "allowed VLAN" with "native VLAN", but there is no warning. I add a warning!

@c-po I have implemented a simple script in 1.4. It works normally, but I can't count the port and protocol information

Can someone modify this sentence and add an output statement before it to see what caused the error?

Thank you. If you have any questions, please keep in touch.

@ZPrime Although UPNP is not merged, you are welcome to test it if you wish, and if you have any questions, please let me know (you can also get in touch with me on Stack) so I can fix it before merging

Does anyone follow up on this?

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

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

equuleus: https://github.com/vyos/vyos-1x/pull/788

bug fix PR: https://github.com/vyos/vyos-1x/pull/787

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