Using udp4/6 can be automated if there is an v6 listen address or not, I will keep this in mind, thanks for the hint.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Dec 10 2020
Dec 9 2020
Dec 8 2020
Unfortunately setting udp4 was never "valid" in the first place, this was only possible by a wrong regex here: https://github.com/vyos/vyos-1x/blob/406083932ae62ccde5ff547ef7d7960efe0269e3/interface-definitions/interfaces-openvpn.xml.in#L345 this has been corrected already which shows the above mentioned result in a not loading config.
Unfortunately this is the wrong way to go. If it is - for whatever reason - not possible to configure the VLAN parameters for this given interface b/c the enslaved interface is yet not present on the system, it should be later configured by the individual interface.
Dec 7 2020
Well this is from old Vyatta times, on system bootup this script is called (https://github.com/vyos/vyatta-cfg-system/blob/current/scripts/system/vyatta_interface_rescan#L137-L140) and a WIFI node is created if a wifi interface is detected. The script could be altered, too if monitor is not supported.
I guess the best thing would be to not add this interface at all
Dec 6 2020
Okay, debugging with @jack9603301 showed that there was/is an issue. If you are running DHCP client on the interface which is using mirroring, this indeed becomes an issue as traffic is dropped until the session is re-established.
Of course, restarting ping works, but all flows in transit will stop, this is not what you wan't on an edge device running 10GBit/s of traffic
Running VyOS 1.3-rolling-202012060217 immediately when I enable port mirroring all sessions are dropped on this link.
Please only allow native-vlan and allowed-vlan for ethernet and bond type of interfaces for the time beeing
I wonder if this configuration should be possible at all. In my opinion native-vlan and allowed-vlan should be supported only on bond and ethernet interface types
Taking the following configuration as a pool serving relays:
Dec 5 2020
Disable downgrades in general is a bad idea. We still can leave the user with a broken config on downgrade but prevent it is bad. Imagine a very simple config, that would be downgradable.
Dec 4 2020
yes, specifying "ipv6" has the same effect as "ipv6 enable"
Dec 3 2020
Dec 2 2020
Calculating setting is always the smartest idea. I also have a WIFI6 NIC with me, the problem is it is not supported by Linux 4.19. which we currently are forced to use.
Dec 1 2020
table ip nat {
chain PREROUTING {
type nat hook prerouting priority dstnat; policy accept;
iifname "eth1" tcp dport { 22 } counter packets 0 bytes 0 dnat to 192.168.1.4 comment "DST-NAT-100"
}
}Thank you @Dmitry, it will be in tomorrows rolling release.