- The problem about DHCPv6 has been solved
- The communication problem has been solved
Sat, Sep 4
It seems that the problem is related to IPv6 MSS. When I set IPv6 MSS to 1280 and IPv4 MSS to 1452, the problem seems to disappear
Fri, Aug 27
Wed, Aug 25
Aug 14 2021
Merging this PR can fix this problem. Due to the complexity of the JSON parsing of NFT by the operation mode script, this task still needs to be tested, and the local test passes
Aug 13 2021
Aug 11 2021
@raphielscape Are there still problems after updating PR? Please provide the configuration and I'll take the time to check it
Aug 1 2021
Jul 31 2021
Jul 25 2021
Jul 23 2021
Jul 22 2021
Jul 21 2021
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!
Jul 14 2021
note: Record the process of upgrading from 1.4-rolling-202107010537 to 1.4-rolling-202107122017
Jul 9 2021
Jul 7 2021
Jul 4 2021
Jul 3 2021
Jun 27 2021
Jun 25 2021
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