Software appliance configuration framework
Details
Jul 2 2024
May 15 2024
May 4 2024
Apr 4 2024
Mar 26 2024
Yes, as described in the issue, using dynamically added routes works fine. But I want to add the routes manually as I did before with the 1.3.x release.
Using both automatically added routes from PPPoE and setting them statically does not sound like a "sane" config to me.
Mar 25 2024
Delete set interfaces pppoe pppoe0 no-default-route will let it works. it is the same issue.
Jan 19 2024
Jan 9 2024
Host name settings certainly works fine now, but if anything, feel free to reopen.
The use case for it will be addressed by the future support for true (ignored by the parser) comments.
Dec 21 2023
Dec 17 2023
Dec 9 2023
Duplicate
Aug 25 2023
Jul 19 2023
Jul 12 2023
Jun 13 2023
Hi @jestabro I saw that feature request but I wasn't sure. Thank you!
cf. https://vyos.dev/T5249, currently being assessed.
Aug 29 2022
Jan 21 2022
Seems solved, Not reproducible on VyOS 1.4-rolling-202201180317
Jan 6 2022
Jan 5 2022
Jan 3 2022
To reproduce it should be zone-policy firewall rules, for example:
Dec 6 2021
The correct key for sflow sfprobe_source_ip
PR https://github.com/vyos/vyos-1x/pull/1099
Dec 4 2021
KEY: nfprobe_source_ip DESC: Defines the local IP address from which NetFlow datagrams are exported. Only a numerical IPv4/ IPv6 address is expected. The supplied IP address is required to be already configured on one of the interfaces. This parameter is also required for graceful encoding of NetFlow v9 and IPFIX option scoping. DEFAULT: IP address is selected by the Operating System