- User Since
- Mar 19 2020, 5:57 AM (70 w, 2 d)
Thu, Jul 22
Wed, Jul 21
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!
Wed, Jul 14
note: Record the process of upgrading from 1.4-rolling-202107010537 to 1.4-rolling-202107122017
Fri, Jul 9
Wed, Jul 7
Sun, Jul 4
Sat, Jul 3
Sun, Jun 27
Fri, Jun 25
Sorry, this may be my fault. It seems that I only pay attention to modifying the identifier below and forget the top definition. Sorry.
Jun 20 2021
Hi, I found that the transmission speed of tinc seems very disappointing, even in some cases, even the normal network communication has problems..
Jun 4 2021
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
Jun 3 2021
Jun 2 2021
Jun 1 2021
@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!
May 21 2021
May 17 2021
May 16 2021
May 13 2021
Please use the following op-mode command to check:
May 11 2021
OK, it seems that this problem doesn't need any repair and will be closed
@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!
Apr 30 2021
@c-po I have implemented a simple script in 1.4. It works normally, but I can't count the port and protocol information
Apr 17 2021
Can someone modify this sentence and add an output statement before it to see what caused the error?
Apr 15 2021
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
Apr 12 2021
Apr 11 2021
Mar 31 2021
Does anyone follow up on this?
Mar 29 2021
Mar 26 2021
Mar 25 2021
bug fix PR: https://github.com/vyos/vyos-1x/pull/787
Mar 23 2021
@Asteroza With Vyos, any service should be turned off by default unless it is explicitly configured by the user
Mar 22 2021
Mar 20 2021
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)?
Mar 18 2021
Mar 14 2021
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?
Mar 13 2021
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
Mar 12 2021
After a while, I may consider how to provide the operation mode command for nat66
Mar 11 2021
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