Page MenuHomeVyOS Platform

VyConfProject
ActivePublic

Members

  • This project does not have any members.
  • View All

Details

Description

Software appliance configuration framework

Recent Activity

Mon, Aug 29

syncer edited projects for T3340: Add dhcp-helper package to replace ISC DHCP Relay, added: VyOS 1.3 Equuleus (1.3.3); removed VyOS 1.3 Equuleus (1.3.0).
Mon, Aug 29, 7:06 AM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf
syncer edited projects for T4022: Add package nat-rtsp-dkms, added: VyOS 1.3 Equuleus (1.3.3); removed VyOS 1.3 Equuleus (1.3.0).
Mon, Aug 29, 7:05 AM · VyOS 1.3 Equuleus (1.3.3), vyatta-conntrack, VyConf

Jan 21 2022

n.fort closed T4133: Firewall network group error with zone-based firewall rules as Resolved.
Jan 21 2022, 6:35 PM · VyOS 1.4 Sagitta, VyConf
n.fort added a comment to T4133: Firewall network group error with zone-based firewall rules.

Seems solved, Not reproducible on VyOS 1.4-rolling-202201180317

Jan 21 2022, 6:35 PM · VyOS 1.4 Sagitta, VyConf

Jan 6 2022

sdev moved T4133: Firewall network group error with zone-based firewall rules from Need Triage to In Progress on the VyOS 1.4 Sagitta board.
Jan 6 2022, 5:27 PM · VyOS 1.4 Sagitta, VyConf

Jan 5 2022

sdev changed the status of T4133: Firewall network group error with zone-based firewall rules from In progress to Needs testing.

PR: https://github.com/vyos/vyos-1x/pull/1139

Jan 5 2022, 5:10 PM · VyOS 1.4 Sagitta, VyConf
sdev changed the status of T4133: Firewall network group error with zone-based firewall rules from Open to In progress.
Jan 5 2022, 2:07 PM · VyOS 1.4 Sagitta, VyConf

Jan 3 2022

Viacheslav renamed T4133: Firewall network group error with zone-based firewall rules from Firewall network group error to Firewall network group error with zone-based firewall rules.
Jan 3 2022, 7:47 PM · VyOS 1.4 Sagitta, VyConf
Viacheslav added a comment to T4133: Firewall network group error with zone-based firewall rules.

To reproduce it should be zone-policy firewall rules, for example:

Jan 3 2022, 7:46 PM · VyOS 1.4 Sagitta, VyConf
c-po assigned T4133: Firewall network group error with zone-based firewall rules to sdev.
Jan 3 2022, 7:39 PM · VyOS 1.4 Sagitta, VyConf
n.fort created T4133: Firewall network group error with zone-based firewall rules.
Jan 3 2022, 7:08 PM · VyOS 1.4 Sagitta, VyConf

Dec 6 2021

c-po moved T4046: Sflow - Add Source address parameter from Backlog to Finished on the VyOS 1.4 Sagitta board.
Dec 6 2021, 5:46 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta
Viacheslav changed the status of T4046: Sflow - Add Source address parameter from In progress to Needs testing.
Dec 6 2021, 5:17 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta
Viacheslav added a comment to T4046: Sflow - Add Source address parameter.

The correct key for sflow sfprobe_source_ip
PR https://github.com/vyos/vyos-1x/pull/1099

Dec 6 2021, 3:16 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta
Viacheslav changed the status of T4046: Sflow - Add Source address parameter from Open to In progress.
Dec 6 2021, 2:45 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Dec 4 2021

c-po moved T4046: Sflow - Add Source address parameter from Need Triage to Backlog on the VyOS 1.4 Sagitta board.
Dec 4 2021, 3:58 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta
c-po added a comment to T4046: Sflow - Add Source address parameter.
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
Dec 4 2021, 2:25 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta
n.fort created T4046: Sflow - Add Source address parameter.
Dec 4 2021, 12:20 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Nov 27 2021

basalblas created T4022: Add package nat-rtsp-dkms.
Nov 27 2021, 11:10 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-conntrack, VyConf

Nov 6 2021

syncer edited projects for T3340: Add dhcp-helper package to replace ISC DHCP Relay, added: VyOS 1.3 Equuleus (1.3.0); removed VyOS 1.3 Equuleus.
Nov 6 2021, 11:25 AM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf

Sep 5 2021

syncer removed a member for VyConf: syncer.
Sep 5 2021, 8:34 AM
syncer removed a member for VyConf: creaworlds.
Sep 5 2021, 8:34 AM
syncer removed a member for VyConf: hiroyuki-sato.
Sep 5 2021, 8:34 AM
syncer removed a member for VyConf: dmbaturin.
Sep 5 2021, 8:34 AM

Feb 23 2021

basalblas renamed T3340: Add dhcp-helper package to replace ISC DHCP Relay from Add dhcp-helper package to support DHCP Relay over GRE tunnel to Add dhcp-helper package to replace ISC DHCP Relay.
Feb 23 2021, 11:23 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf

Feb 22 2021

HON added a comment to T3340: Add dhcp-helper package to replace ISC DHCP Relay.

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 22 2021, 11:13 AM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf
Viacheslav changed Difficulty level from unknown to normal on T3340: Add dhcp-helper package to replace ISC DHCP Relay.
Feb 22 2021, 9:00 AM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf

Feb 18 2021

c-po added a comment to T3340: Add dhcp-helper package to replace ISC DHCP Relay.

If this package supports all existing setups and the GRE usecase I see no reason to not replace it. @basalblas PR is happily accepted.

Feb 18 2021, 7:36 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf
basalblas added a project to T3340: Add dhcp-helper package to replace ISC DHCP Relay: VyOS 1.3 Equuleus.
Feb 18 2021, 3:42 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf
basalblas added a comment to T3340: Add dhcp-helper package to replace ISC DHCP Relay.

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.

Feb 18 2021, 3:35 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf
basalblas created T3340: Add dhcp-helper package to replace ISC DHCP Relay.
Feb 18 2021, 1:40 PM · VyOS 1.3 Equuleus (1.3.3), vyatta-cfg-dhcp-relay, VyConf

Jan 27 2021

dmbaturin closed T387: Prevent command injection in VyConf external validator execution as Resolved.
Jan 27 2021, 6:39 PM · VyConf

Jan 18 2021

c-po created T3231: "system option ctrl-alt-delete" has no effect.
Jan 18 2021, 3:55 PM · VyOS 1.3 Equuleus (1.3.0)

Jan 6 2021

qiuchengxuan closed T3187: Add support to pdns-recursor dont-throttle-netmasks configuration as Invalid.
Jan 6 2021, 6:42 AM · VyConf
qiuchengxuan created T3187: Add support to pdns-recursor dont-throttle-netmasks configuration.
Jan 6 2021, 2:41 AM · VyConf

Nov 28 2020

Viacheslav closed T2539: Issues with parsing ip range for source nat translation address as Resolved.

Fixed

set nat source rule 1000 outbound-interface 'eth1'
set nat source rule 1000 source address '203.0.113.1-203.0.113.4'
set nat source rule 1000 translation address '10.0.0.1-10.0.0.4'
[email protected]# commit
[ nat ]
Warning: IP address 10.0.0.1 does not exist on the system!
Warning: IP address 10.0.0.4 does not exist on the system!
Nov 28 2020, 4:37 PM · VyConf

Jun 5 2020

BcTpe4HbIu removed a watcher for VyConf: BcTpe4HbIu.
Jun 5 2020, 5:40 PM
jjakob merged task T2552: [BUG] commit-archive domain recognition error into T2468: Passwords with special characters fail in commit-archive.
Jun 5 2020, 1:17 PM · VyConf
jjakob added a comment to T2552: [BUG] commit-archive domain recognition error.

duplicate of T2468

Jun 5 2020, 1:17 PM · VyConf
ccieliu renamed T2552: [BUG] commit-archive domain recognition error from [BUG] report to [BUG] commit-archive domain recognition error.
Jun 5 2020, 1:17 PM · VyConf
ccieliu created T2552: [BUG] commit-archive domain recognition error.
Jun 5 2020, 1:15 PM · VyConf

Jun 2 2020

thomas-mangin added a comment to T2539: Issues with parsing ip range for source nat translation address.

Thank you for reporting this issue, it looks like that parser allows ranges of IP address (IP hyphen IP) but the parser does not. You could get around using CIDR notation but this indeed need looking into.

Jun 2 2020, 7:44 PM · VyConf
yurij185 created T2539: Issues with parsing ip range for source nat translation address.
Jun 2 2020, 6:56 AM · VyConf

Jan 3 2020

MapleWang added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

By the way, may I say there are several bugs of stop function in vyos-router?

Jan 3 2020, 10:30 AM · VyConf
MapleWang added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

Why not use WantedBy instead of RequiredBy in vyos-hostsd.service like:

Jan 3 2020, 10:16 AM · VyConf

Jan 2 2020

MapleWang added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

My original thoughts was quite straight forward, modify /usr/libexec/vyos/init/vyos-router as below:

Jan 2 2020, 5:22 AM · VyConf

Dec 31 2019

zsdc added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

Hello, @MapleWang!
Unfortunately, I cannot find any other reliable way to configure vyos-hostsd service to be running before the vyos-router. In fact, vyos-hostsd is really necessary to be running for proper work of the VyOS system, so we can consider this even from the other point of view - how to keep all services operable after the vyos-router restart?
If you will have any ideas, which can help to decrease the overall impact of this situation, we would be happy to get them.

Dec 31 2019, 3:17 PM · VyConf

Dec 20 2019

MapleWang added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

Really thanks for your reply. It's nice to have this fix. But to be honest, crash of vyos-hostsd is not so big deal for me, what really concern me is that restart of vyos-hostsd is followed by restart of vyos-router.

Dec 20 2019, 3:39 AM · VyConf

Dec 19 2019

zsdc changed the status of T1885: vyos hostname configuration failure and it triggers vyos-router restarted from Open to In progress.

Hello, @MapleWang!
Thank you for pointing our attention to this issue! It is really bad that such simple action as changing hostname in some cases (well, in fact not only this but it is easy to reproduce) leads to the whole router crash.
The problem consists of several parts:

  1. In old systemd versions (which is used in Debian Jessie and VyOS 1.2) exists a problem, when during a restart of systemd-journald all pipes between this daemon and systemd services are disconnecting.
  2. In vyos-hostsd, which is responsible for hostname and DNS and controlled by systemd we used print() for logging and debug purposed without enough handling of errors.

So, when arises the situation when there is no PIPE connection between vyos-hostsd and systemd-journald, vyos-hostsd not able to print messages and crashes. :(

Dec 19 2019, 6:37 PM · VyConf

Dec 18 2019

MapleWang added a comment to T1885: vyos hostname configuration failure and it triggers vyos-router restarted.

I found a easy way to reproduce.

Dec 18 2019, 1:50 PM · VyConf