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

The official upstream address is https://gitlab.com/gsliepen/tinc , no Debian package generation rule file

For security, don't expose your user name and password

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

After solving this requirement of vyos and confirming its normal operation, it is recommended to provide a feedback repair patch and submit a pr

I have finished the test of nat66 in GNS lab

Since the current branch uses the kernel Linux 5.10+, I began to pay attention to the implementation of NPT again. At present, I have completed the following features:

@c-po Why not consider dnat prefix to? Maybe it's more convenient

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

Better document improvement

If it's just because of overlay, you can merge two XML into one XML

@runar @c-po A new PR has been created and can be reviewed

PR:
https://github.com/vyos/vyos-1x/pull/677
https://github.com/vyos/vyatta-cfg-system/pull/134
https://github.com/vyos/vyos-documentation/pull/424

When the vyos kernel is higher than 5.8+, you can start the formal test before merging nat66

@c-po @runar If there are no other problems, I will change the VLAN aware bridge code and update the description of T3137 in the near future

1. vif 1 should not be used as a required option for VLAN-aware bridges, it is only used when Layer 3 routing is required
2. Are native-vlan and allowed-vlan necessary options for VLAN-aware bridges? Worth thinking about? After activating the VLAN-aware bridge function, if you do not set these two options, you can use the default VLAN parameters to run (all untagged packets are members of VLAN 1, which is in line with the behavior of most professional equipment)

@runar If we assume that all untagged packets are members of VLAN 1 by default, then the behavior of the device bridge is actually the same as the behavior without VLAN awareness. In this case, set interfaces bridge br1 vlan-aware may not necessary

VLAN-aware bridge is a special use case. We should design additional special rules for VLAN-aware bridges. This rule should be consistent with the behavior of other routers and switch manufacturers, combined with https://phabricator.vyos.net/ According to T1354, can the following changes be considered:

@Dmitry Thank you for correcting. I may have got it wrong

@c-po https://github.com/vyos/vyos-1x/pull/668

Why should this task be created in vyos manager

I think this may be related to the MAC bound to the device. You can modify the configuration of vyos to adjust the order

As for encrypted DNS, it should cover standard solutions rather than be limited to a certain service provider. The standard solutions are as follows (although in general, there may not be many people using encrypted recursive DNS)

Is there a way to support pmtu in interface configuration

@c-po Can we consider reviewing it again

@c-po PR:https://github.com/vyos/vyos-1x/pull/658

https://github.com/vyos/vyatta-cfg-system/pull/134