If we will use only mark_in=%unique, this allow us work with or without NAT rules. PR https://github.com/vyos/vyos-1x/pull/120
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 31 2019
Cherry-picked into crux.
Imported 2.0.17 into crux.
Aug 30 2019
Please backport this
Actually, there are already run monitor traffic interface $intf commands and they work fine in 1.2.3.
Aug 29 2019
Aug 28 2019
Adding "tls-crypt" and in the upcoming 2.5 release "tls-crypt-v2" options would also be desirable.
@hagbard during some tests with the bridge interface (https://github.com/vyos/vyos-1x/commit/71f7a947539963112c61fef2a5f278d524d71198) I noticed the following:
Pyroute2 states:
One of the major issues with IPDB is its memory footprint. It proved not to be suitable for environments with thousands of routes or neighbours. Being a design issue, it could not be fixed, so a new module was started, NDB, that aims to replace IPDB. IPDB is still more feature rich, but NDB is already more fast and stable.
Aug 27 2019
The reason for layer2, layer2+3 and layer3+4 are that those values are directly passed to the kernel, as the pernel expects:
improvement suggestion:
- remove the use of + in hash-policy names. layer2+3 and layer3+4. this could be replaced with the more used - character, so layer2-3 and layer3-4
- also add support for encap2-3 and encap3-4hash-policy
It is true that you need a hash-policy, but specifying a hash-policy is optional, if you don't specify it reverts to the kernel default that is layer2..
also defaults should not be listed in the configuration. (because then the configuration will be crowded with all kind of strange things that is a default)
@runar If I could offer an alternative, why not require set interfaces bonding bond0 hash-policy to always be specified? The hash policy is not something optional like a tunnel key for GRE, so I feel that this option should be required.
Improvement suggestion:
set interfaces bonding bond0 hash-policy # defaults to layer2, listing layer2 as an configureable alternative is then redundant. to revert to level2 the user should delete the config entry instead. also update description about using layer2 as a default
with vyos-1.2-rolling-201908270337-amd64.iso also fixed for me. Thanks