Page MenuHomeVyOS Platform

zsdc ( )
User

Projects

User Details

User Since
Sep 10 2018, 3:30 PM (96 w, 1 d)

Recent Activity

Yesterday

zsdc changed the status of T2701: VPN ipsec pfs "enabled" don't work with IKEA-groups from Open to In progress.

https://github.com/vyos/vyatta-cfg-vpn/pull/34

Mon, Jul 13, 4:13 PM · VyOS 1.2 Crux
zsdc closed T1100: Spoke site dynamic IP over NAT connect to Hub site as Invalid.

Closed in favor of https://phabricator.vyos.net/T1101

Mon, Jul 13, 11:56 AM · VyOS 1.3 Equuleus

Wed, Jul 1

zsdc changed the status of T2556: "show interfaces vrrp" does not return any interface from Confirmed to Open.

This command doing not what you are expecting. It shows virtual VRRP interfaces running in RFC3768 compatibility mode. Add the rfc3768-compatibility option to a VRRP group and a new virtual interface should be listed in the output.
If you want to change this behavior, please describe how exactly.

Wed, Jul 1, 12:31 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Thu, Jun 25

zsdc changed the status of T2640: Running VyOS inside Docker containers from Open to In progress.
Thu, Jun 25, 12:01 PM · VyOS 1.3 Equuleus

Wed, Jun 24

zsdc created T2640: Running VyOS inside Docker containers.
Wed, Jun 24, 3:48 PM · VyOS 1.3 Equuleus

Mon, Jun 15

zsdc assigned T2572: Wrong default units when defining traffic policy bandwidth to s.lorente.

@s.lorente can you check this with actually configured tc values?

Mon, Jun 15, 11:13 AM

Jun 11 2020

zsdc added a comment to T1564: BGP IPv6 only peer-group not supported.

The set protocols bgp XXX neighbor XXX address-family ipv6-unicast peer-group XXX command generate the router bgp XXX; address-family ipv6; neighbor XXX peer-group XXX', for vtysh, which does not supported (anymore? I cannot find any commits in FRR about syntax change, maybe this was migrated from old quagga).

Jun 11 2020, 4:28 PM · VyOS 1.3 Equuleus

Jun 10 2020

zsdc changed the subtype of T2257: BGP does not work with VRF from "Bug" to "Feature Request".
Jun 10 2020, 4:33 PM · VyOS 1.3 Equuleus

Jun 8 2020

zsdc added a comment to T2561: Drop support for "system console netconsole".

@c-po I have not tried this previously, but if it works well, I would like to keep it for kernel debugging on bare-metal devices.

Jun 8 2020, 8:43 AM · VyOS 1.3 Equuleus

May 13 2020

zsdc changed the status of T2456: netflow source-ip cannot be configured from Open to Confirmed.
May 13 2020, 2:14 PM · VyOS 1.3 Equuleus
zsdc created T2456: netflow source-ip cannot be configured.
May 13 2020, 2:13 PM · VyOS 1.3 Equuleus

May 12 2020

zsdc moved T1291: Under certain conditions the VTI will stay forever down from Need Triage to Backport Candidates on the VyOS 1.3 Equuleus board.
May 12 2020, 10:14 AM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

May 9 2020

zsdc changed the status of T2389: BGP community-list error from Open to Confirmed.

The bug is produced because of deleted deprecated option in vtysh. Before FRR 7.3:

root@vyos:/home/vyos# vtysh -c "show ip community-list 10"
This config option is deprecated, and is scheduled for removal.
if you are using this please migrate to the below command.
'show bgp community-list <(1-500)|WORD> detail'
% Can't find community-list

Starting from 7.3:

root@vyos:/home/vyos# vtysh -c "show ip community-list 10"
% Unknown command: show ip community-list 10
May 9 2020, 8:43 AM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

May 4 2020

zsdc added a comment to T1876: IPSec VTI tunnels are deleted after rekey and dangling around as A/D.

Need to check again with 1.3, as may be solved by: https://phabricator.vyos.net/T1291

May 4 2020, 8:21 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1291: Under certain conditions the VTI will stay forever down from In progress to Backport candidate.
May 4 2020, 4:07 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

Apr 30 2020

zsdc changed the status of T2309: Wrong host-name value breaks the whole configuration in images with Cloud-init from Open to In progress.

https://github.com/vyos/vyos-cloud-init/pull/10

Apr 30 2020, 4:16 PM · VyOS 1.2 Crux
zsdc changed the status of T2403: Full support for networking config in Cloud-init from Open to In progress.
Apr 30 2020, 9:47 AM · VyOS 1.3 Equuleus
zsdc created T2403: Full support for networking config in Cloud-init.
Apr 30 2020, 9:47 AM · VyOS 1.3 Equuleus

Apr 28 2020

zsdc assigned T1276: dhcp relay + VLAN fails to g.skupien.
Apr 28 2020, 9:39 AM · VyOS 1.3 Equuleus
zsdc reassigned T1227: rip PW can't be set at interface config from zsdc to g.skupien.
Apr 28 2020, 9:36 AM · VyOS 1.3 Equuleus

Apr 27 2020

zsdc renamed T1899: Unionfs metadata folder is copied to the active configuration directory from Unable to delete vyos user to Unionfs metadata folder is copied to the active configuration directory.
Apr 27 2020, 12:29 PM · VyOS 1.3 Equuleus

Apr 20 2020

zsdc changed the status of T2343: Disable memory ballooning in VM templates from Open to In progress.
Apr 20 2020, 6:59 PM · VyOS 1.3 Equuleus
zsdc created T2343: Disable memory ballooning in VM templates.
Apr 20 2020, 1:11 PM · VyOS 1.3 Equuleus

Apr 17 2020

zsdc created T2309: Wrong host-name value breaks the whole configuration in images with Cloud-init.
Apr 17 2020, 12:42 PM · VyOS 1.2 Crux

Apr 13 2020

zsdc assigned T1899: Unionfs metadata folder is copied to the active configuration directory to g.skupien.
Apr 13 2020, 11:30 AM · VyOS 1.3 Equuleus

Apr 10 2020

zsdc reassigned T1381: Enable DHCP option 121 processing from dmbaturin to g.skupien.
Apr 10 2020, 8:36 PM · VyOS 1.3 Equuleus

Apr 8 2020

zsdc changed the status of T2245: Need to create a common logging module for Python scripts from Open to In progress.
Apr 8 2020, 5:21 PM · VyOS 1.3 Equuleus
zsdc created T2245: Need to create a common logging module for Python scripts.
Apr 8 2020, 5:20 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1820: VRRP transition scripts for sync-groups are not supported in VyOS (anymore) from Open to Needs testing.

Hello, @adestis!
Support of transition-scripts was added to sync-groups in a rolling version.

Apr 8 2020, 3:35 PM · VyOS 1.3 Equuleus
zsdc claimed T2189: Adding a large port-range will take ~ 20 minutes to commit.

I have investigated this a bit. Most operations for ports are doing one-by-one. Deleting as I see is always done in this way. Adding a range is done by a single command, but checking ports are doing one-by-one.
If we skip/change mentioned checking for adding ports, this should decrease initial commit time. But when we try to change/delete ports, the issue will back.
I think that there should be better to reimplement the whole firewall group section in Python, instead of fixing this logic now.

Apr 8 2020, 2:21 PM · VyOS 1.3 Equuleus
zsdc changed the status of T723: Add support for first boot or installation time saved config modification from Open to Needs testing.

Already possible via Cloud-init. For different environments may be required differently tuned images (data sources, additional tools like guest agents, etc.).

Apr 8 2020, 10:02 AM · VyOS 1.3 Equuleus

Apr 6 2020

zsdc assigned T1095: Connection tracking NAT / FIREWALL to g.skupien.
Apr 6 2020, 10:10 AM
zsdc assigned T1114: VyOS 1.2 tftp issue, NAT client could not boot via tftp server, same setup on VyOS 1.1.8 works fine to g.skupien.
Apr 6 2020, 10:10 AM

Apr 3 2020

zsdc changed the status of T2193: Display disabled VRRP instances in a `show vrrp` output from Open to Needs testing.
Apr 3 2020, 2:08 PM · VyOS 1.3 Equuleus
zsdc closed T1140: Policy Route Not Work as Invalid.

Closed due to inactivity.

Apr 3 2020, 11:52 AM · VyOS 1.3 Equuleus
zsdc reassigned T1693: DNS Forwarding Services not responding with Allow-From from zsdc to g.skupien.
Apr 3 2020, 11:48 AM · VyOS 1.3 Equuleus

Apr 2 2020

zsdc changed the status of T1350: VRRP transition script will be executed once only from Confirmed to Needs testing.

In the current 1.3 branch the original issue was resolved and added STOP script support. It is necessary to test this and review the possibility to backport the solution into 1.2.

Apr 2 2020, 11:51 AM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

Apr 1 2020

zsdc created T2193: Display disabled VRRP instances in a `show vrrp` output.
Apr 1 2020, 12:25 PM · VyOS 1.3 Equuleus

Mar 27 2020

zsdc created T2168: Config edit level affecting the show_config() function.
Mar 27 2020, 8:22 PM · VyOS 1.3 Equuleus

Mar 24 2020

zsdc moved T1490: BGP configuration (is lost|not applied) when updating 1.1.8 -> 1.2.1 from Need Triage to Backport Candidates on the VyOS 1.3 Equuleus board.
Mar 24 2020, 12:37 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus
zsdc changed the status of T1490: BGP configuration (is lost|not applied) when updating 1.1.8 -> 1.2.1 from In progress to Backport candidate.
Mar 24 2020, 12:35 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus
zsdc changed the status of T2116: Processing configuration via Cloud-init User-Data from In progress to Needs testing.
Mar 24 2020, 12:08 PM · VyOS 1.3 Equuleus

Mar 12 2020

zsdc changed the status of T2117: Update Cloud-init version and actualize our changes to it from In progress to Needs testing.
Mar 12 2020, 8:13 PM · VyOS 1.3 Equuleus

Mar 11 2020

zsdc changed the status of T2049: Update strongSwan cipher suites list for IPSec settings from Open to In progress.
Mar 11 2020, 2:11 PM · VyOS 1.3 Equuleus

Mar 10 2020

zsdc changed the status of T2117: Update Cloud-init version and actualize our changes to it from Open to In progress.
Mar 10 2020, 10:12 AM · VyOS 1.3 Equuleus
zsdc created T2117: Update Cloud-init version and actualize our changes to it.
Mar 10 2020, 10:12 AM · VyOS 1.3 Equuleus
zsdc changed the status of T2116: Processing configuration via Cloud-init User-Data from Open to In progress.
Mar 10 2020, 9:59 AM · VyOS 1.3 Equuleus
zsdc created T2116: Processing configuration via Cloud-init User-Data.
Mar 10 2020, 9:58 AM · VyOS 1.3 Equuleus
zsdc changed the status of T1987: A default route can be deleted by dhclient-script in some cases from In progress to Needs testing.
Mar 10 2020, 9:48 AM · VyOS 1.3 Equuleus

Mar 2 2020

zsdc created T2091: The swanctl.conf file does not generate properly.
Mar 2 2020, 3:29 PM · Ready for Crux (1.2.x), VyOS 1.3 Equuleus

Feb 18 2020

zsdc created T2049: Update strongSwan cipher suites list for IPSec settings.
Feb 18 2020, 10:58 AM · VyOS 1.3 Equuleus

Jan 30 2020

zsdc created T2000: strongSwan does not install routes to table 220 in certain cases.
Jan 30 2020, 2:50 PM · VyOS 1.2 Crux (VyOS 1.2.6), Ready for Crux (1.2.x), VyOS 1.3 Equuleus

Jan 29 2020

zsdc created T1995: "show vpn ike sa" command always show child-sas as down.
Jan 29 2020, 5:49 PM · VyOS 1.3 Equuleus
zsdc updated the task description for T1233: ipsec vpn sa showing down.
Jan 29 2020, 5:30 PM · VyOS 1.3 Equuleus

Jan 24 2020

zsdc changed the status of T1987: A default route can be deleted by dhclient-script in some cases from Open to In progress.
Jan 24 2020, 6:58 PM · VyOS 1.3 Equuleus
zsdc moved T1987: A default route can be deleted by dhclient-script in some cases from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Jan 24 2020, 6:58 PM · VyOS 1.3 Equuleus
zsdc created T1987: A default route can be deleted by dhclient-script in some cases.
Jan 24 2020, 6:57 PM · VyOS 1.3 Equuleus

Jan 13 2020

zsdc changed the status of T1960: pppoe-server framed-routes not deleted from routing table from Open to In progress.

The described problem exists in stable FRR 7.2, but fixed in FRR master branch by https://github.com/FRRouting/frr/pull/5184
We have tested 7.2 with this PR applied, and the bug was gone, so we can apply this PR to our FRR package and solve the problem.

Jan 13 2020, 6:18 PM · VyOS 1.2 Crux
zsdc closed T1909: Incorrect behaviour of static routes with overlapping networks as Resolved.

In FRR 7.0.1 (VyOS 1.2.3) was some bug, due to which static routes were not updated (maybe, not in all cases or environments) after the next-hop state change. In VyOS 1.2.4 we use stable FRR 7.2, which processes this situation without problems. An example (key point from FRR debug log):
FRR 7.0.1:

Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d1f0, re 0x5612ea69d370 (type 2)
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69d370 (type 2), old (nil) (type -1)
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d490, re 0x5612ea69e110 (type 2)
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69e110 (type 2), old (nil) (type -1)
Jan 13 15:29:51 vyos zebra[1041]: NHT processing check for zvrf default
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Evaluate RNH, type 0
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Notifying client static about NH
Jan 13 15:29:51 vyos zebra[1041]: 0:192.168.20.1/32: Evaluate RNH, type 0

FRR 7.2:

Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a18b0, re 0x5574620a1930 (connected)
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a29b0, re 0x5574620a1850 (connected)
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): no fib nhg
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): rib nhg matched, changed 'true'
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Redist update re 0x5574620a1930 (connected), old 0x0 (None)
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Evaluate RNH, type Nexthop
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Notifying client static about NH
Jan 13 15:33:23 vyos zebra[1042]: rib_add_multipath: 0:10.0.0.0/8: Inserting route rn 0x5574620a1b10, re 0x5574620a1a30 (static) existing (nil)
Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Adding route rn 0x5574620a1b10, re 0x5574620a1a30 (static)
Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath(): RTM_NEWROUTE 10.0.0.0/8 vrf 0(254)
Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath() (single-path): nexthop via 10.230.230.1  if 3(0)
Jan 13 15:33:23 vyos zebra[1042]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=60 seq=10 flags 0x501
Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): no fib nhg
Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): rib nhg matched, changed 'true'
Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Redist update re 0x5574620a1a30 (static), old 0x0 (None)

So, configured static routes updating properly.

Jan 13 2020, 3:46 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus, vyos-frr

Jan 2 2020

zsdc created T1935: NIC identification and usage problem in Hyper-V environments.
Jan 2 2020, 7:50 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

Dec 31 2019

zsdc closed T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration as Resolved.

The problem is fixed in 1.3.

Dec 31 2019, 9:29 PM · VyOS 1.3 Equuleus
zsdc closed T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration, a subtask of T1890: Metatask: rewrite flow-accounting to XML and Python, as Resolved.
Dec 31 2019, 9:29 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1817: BGP next-hop-self not working. from Open to In progress.
Dec 31 2019, 9:27 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1588: VRRP failed to start if any of its interaces not exist from Open to In progress.
Dec 31 2019, 9:20 PM · VyOS 1.3 Equuleus, vyatta-vrrp
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 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
zsdc changed the status of T1890: Metatask: rewrite flow-accounting to XML and Python from Open to In progress.

@c-po, there is also third PR in vyos-buid: https://github.com/vyos/vyos-build/pull/69

Dec 19 2019, 5:23 AM · VyOS 1.3 Equuleus

Dec 18 2019

zsdc added a comment to T1890: Metatask: rewrite flow-accounting to XML and Python.

Thanks, @elbuit !
We have prepared PR with full functionality: https://github.com/vyos/vyos-1x/pull/187
It would be great if you will join us and help to test it, find all bugs and fix them. :)

Dec 18 2019, 10:22 PM · VyOS 1.3 Equuleus
zsdc added a parent task for T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration: T1890: Metatask: rewrite flow-accounting to XML and Python.
Dec 18 2019, 5:50 PM · VyOS 1.3 Equuleus
zsdc added a subtask for T1890: Metatask: rewrite flow-accounting to XML and Python: T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration.
Dec 18 2019, 5:50 PM · VyOS 1.3 Equuleus
zsdc claimed T1890: Metatask: rewrite flow-accounting to XML and Python.
Dec 18 2019, 5:48 PM · VyOS 1.3 Equuleus
zsdc created T1890: Metatask: rewrite flow-accounting to XML and Python.
Dec 18 2019, 5:48 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1835: add export netflow nel format.

Hello, @elbuit!
As I see, NAT events can be recorded only by nfacctd, and therefore this is not possible with the current way to capture traffic (by NFLOG + uacctd). Fix me, if I was missed something, please.

Dec 18 2019, 4:58 PM · VyOS 1.3 Equuleus

Dec 17 2019

zsdc added a comment to T1835: add export netflow nel format.

Hello, @elbuit !
We almost ready to release rewritten flow-accounting, and maybe we will be able to include your request into it. Can you describe more detailed what exactly records you want to have? It would be good to see an example pmacct configuration for your case.

Dec 17 2019, 6:24 PM · VyOS 1.3 Equuleus

Dec 13 2019

zsdc created T1875: Add the ability to use network address as BGP neighbor (bgp listen range).
Dec 13 2019, 11:19 AM · VyOS 1.3 Equuleus

Dec 9 2019

zsdc added a comment to T1714: Disable DHCP Nameservers Not Working.

Thanks, @trae32566 for the information! I would be happy to change this fix in that way, which does not allow to place unwanted records to resolv.conf at all, but I cannot catch the same situation like yours to collect enough diagnostics data to be sure in the reason of such behavior.

Dec 9 2019, 11:18 AM · VyOS 1.3 Equuleus

Dec 6 2019

zsdc added a comment to T1714: Disable DHCP Nameservers Not Working.

I have tried multiple times to reproduce this with 1.2-rolling-201912060217 with no luck. It would be great if together with logs you will provide a detailed description of the environment. Because, possible that even CPU cores count or memory size can lead to some condition, in which dhclient-script cannot get proper values from config and add unwanted servers to the resolv.conf.

Dec 6 2019, 1:57 PM · VyOS 1.3 Equuleus

Dec 5 2019

zsdc changed the status of T1854: Dynamic DNS configuration cannot be deleted from Open to Confirmed.
Dec 5 2019, 7:41 PM · VyOS 1.3 Equuleus
zsdc created T1854: Dynamic DNS configuration cannot be deleted.
Dec 5 2019, 7:41 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1714: Disable DHCP Nameservers Not Working.

Could you provide the log output in a case when DNS servers, received from DHCP appears in resolv.conf? As I understand, it should happen immediately after the boot.
Also, please, check if they are not deleting after the first DHCP lease renewal.

Dec 5 2019, 4:27 PM · VyOS 1.3 Equuleus

Nov 25 2019

zsdc created T1825: Improve DHCP configuration error message.
Nov 25 2019, 6:24 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus
zsdc closed T1714: Disable DHCP Nameservers Not Working as Resolved.

Resolved in T1786 (for 1.3 too). Please reopen T1786 in case of further troubles.

Nov 25 2019, 5:29 PM · VyOS 1.3 Equuleus

Nov 12 2019

zsdc changed the status of T1786: disable-dhcp-nameservers is missed in current host_name.py implementation from Confirmed to In progress.

Fix for the problem:
https://github.com/vyos/vyos-1x/pull/160
https://github.com/vyos/vyos-replace/pull/4

Nov 12 2019, 4:35 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus

Nov 2 2019

zsdc changed the status of T1786: disable-dhcp-nameservers is missed in current host_name.py implementation from Open to Confirmed.
Nov 2 2019, 6:30 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus
zsdc created T1786: disable-dhcp-nameservers is missed in current host_name.py implementation.
Nov 2 2019, 6:29 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus
zsdc changed the status of T1784: DMVPN with IPSec does not work in HUB mode from Open to Confirmed.
Nov 2 2019, 5:10 PM · VyOS 1.3 Equuleus
zsdc created T1784: DMVPN with IPSec does not work in HUB mode.
Nov 2 2019, 5:09 PM · VyOS 1.3 Equuleus

Oct 25 2019

zsdc created T1772: <regex> constraints in XML are partially broken.
Oct 25 2019, 8:25 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus

Oct 21 2019

zsdc assigned T1560: "set load-balancing wan rule 0" causes segfault and prevents load balancing from starting to s.lorente.
Oct 21 2019, 1:07 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus

Oct 8 2019

zsdc changed the status of T1490: BGP configuration (is lost|not applied) when updating 1.1.8 -> 1.2.1 from Confirmed to In progress.

BGP scan-time parameter is unneeded in current FRRouting and VyOS - there are used modern next-hop tracking instead. You must avoid using this option. I have prepared PR to delete this option and migrate the old configuration, where it exists:
https://github.com/vyos/vyatta-cfg-quagga/pull/36
https://github.com/vyos/vyos-1x/pull/145

Oct 8 2019, 4:59 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

Sep 24 2019

zsdc assigned T1212: IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred to s.lorente.
Sep 24 2019, 10:17 AM · VyOS 1.3 Equuleus

Sep 16 2019

zsdc added a comment to T239: firewall all-ping setting is confusing.

@s.lorente, could you please add details about this option to the https://github.com/vyos/vyos-documentation?

Sep 16 2019, 11:29 AM · VyOS 1.3 Equuleus

Sep 11 2019

zsdc changed the status of T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration from Open to Confirmed.
Sep 11 2019, 4:07 PM · VyOS 1.3 Equuleus
zsdc created T1654: sFlow: multiple "sflow server" not work, and "disable-imt" could break configuration.
Sep 11 2019, 4:06 PM · VyOS 1.3 Equuleus

Sep 4 2019

zsdc changed the status of T1593: Support ip6gre from Open to Needs testing.

Hello, @kruisdraad!
IP6GRE tunnels are supported in 1.2-rolling-201909041703. You are welcome to test.

Sep 4 2019, 7:31 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus

Aug 27 2019

zsdc added a comment to T1613: IPv6 traffic is not captured by NetFlow sensor (pmacct/NFLOG).

Pull request for fixing this problem: https://github.com/vyos/vyatta-netflow/pull/4

Aug 27 2019, 6:49 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Aug 26 2019

zsdc changed the status of T1613: IPv6 traffic is not captured by NetFlow sensor (pmacct/NFLOG) from Open to In progress.
Aug 26 2019, 5:45 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc created T1613: IPv6 traffic is not captured by NetFlow sensor (pmacct/NFLOG).
Aug 26 2019, 5:45 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Aug 21 2019

zsdc changed the status of T1361: VRRP Starts After FRR, Creating Inconsistent Routes - from Open to Confirmed.

The problem is in FRRouting itself. It can be reproduced in 7.0.1-20190820-04-g047efd6, 7.1-20190820-02-g1ed807a. But in 7.2-dev-20190820-03-g9316c82 everything work as expected.
We should try to find which changes fixed this problem and reapply it to one of the current stable FRR versions or wait for the next stable.

Aug 21 2019, 4:27 PM · VyOS 1.3 Equuleus

Aug 9 2019

zsdc added a comment to T1183: BFD Support via FRR.

I have added two PRs with some fixes and new features. The most valuable changes:

  • Fixed the bug, which prevents to change or delete BFD peers with custom options. For example, when any of source address/interface, multihop was used, such peers could not be deleted or changed.
  • Added configuration checks, which should prevent adding BFD option to BGP neighbors or peer-groups without corresponding peers configuration in protocols bfd. If BGP and BFD configurations are out of sync, BGP sessions could be very unstable.
  • Added configuration check, which should prevent to delete peers from protocols bfd if they are still used in BGP.
  • Some other small fixes and changes.

Also, was added several new options:
BFD configuration:

set protocols bfd peer IP echo-mode
set protocols bfd peer IP interval echo-interval

BGP configuration:

set protocols bgp ASN neighbor IP bfd check-control-plane-failure
Aug 9 2019, 3:56 PM · VyOS 1.2 Crux (VyOS 1.2.4), VyOS 1.3 Equuleus