Software appliance configuration framework
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
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
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
Nov 27 2021
Nov 6 2021
Sep 5 2021
Feb 23 2021
Feb 22 2021
The ISC DHCP relay in VyOS is completely broken for my (non-GRE) use case, I would really like to see it get tossed out for something that works. This might not be the best place to describe my relay problems, but I might as well (skip this paragraph it you're not interested). My setup basically consists of the (ISC) DHCP server host connected to the VyOS router (running on a Dell R320), directly connected to a Cisco ASR920 router. Both VyOS and the ASR are directly connected to user VLANs (VyOS for firewalled/NATed zones and ASR for high-traffic users) and have DHCP relays set up targeting the DHCP server, such that the relayed messages from the ASR passes through the VyOS router towards the DHCP server and should get routed normally (i.e. ignored by the VyOS relay). The VyOS DHCP relay doesn't like this and starts spamming the DHCP messages up to ten or more times, causing wired clients to have to wait maybe ten seconds before getting an IPv4 address and wireless clients to just time out and abort the connection. I can provide the relay logs (mainly screenshots unless i dig up the disk I used) and VyOS config if anyone wants them, but as they have sensitive addresses, I don't intend to post them publicly. EDIT: I should mention that I didn't notice any problems while testing it with only myself, it was when 200 people started connecting the problems started occurring. And the DHCP server VM was not showing any noticable load.
Feb 18 2021
If this package supports all existing setups and the GRE usecase I see no reason to not replace it. @basalblas PR is happily accepted.
Keep in mind you cannot run dhcp-helper and ISC DHCP server at the same time on a single router. The Vyos CLI should not allow this.