If it's just because of overlay, you can merge two XML into one XML
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 16 2021
Jan 15 2021
Jan 14 2021
Jan 13 2021
Jan 11 2021
Jan 9 2021
When the vyos kernel is higher than 5.8+, you can start the formal test before merging nat66
Jan 7 2021
- vif 1 should not be used as a required option for VLAN-aware bridges, it is only used when Layer 3 routing is required
- 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:
Jan 5 2021
Jan 4 2021
@Dmitry Thank you for correcting. I may have got it wrong
Jan 3 2021
Why should this task be created in vyos manager
Jan 1 2021
I think this may be related to the MAC bound to the device. You can modify the configuration of vyos to adjust the order
Dec 31 2020
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)
Dec 30 2020
Is there a way to support pmtu in interface configuration
Dec 29 2020
@c-po Can we consider reviewing it again
Dec 27 2020
Dec 25 2020
Dec 24 2020
Dec 22 2020
Dec 21 2020
I want to know the behavior of the implementation when upgrading the vyos version
Dec 19 2020
Dec 17 2020
Dec 16 2020
If your device supports virtualization, you can consider running both VyOS and cups servers in KVM (there are many open source projects that can do this, such as Proxmox Ve)
Why install the remote print sharing service on the router and use cups, you must install the printer driver on the cups server to make it work. VyOS is not a general server operating system, so you should install cups on a physical server or virtual server
Dec 15 2020
Where possible, we can consider MBR+UEFI dual boot, which also exists in most distributions
Dec 14 2020
Dec 13 2020
Dec 12 2020
@primoz Use the latest rolling version test the day after the merge is submitted