Page MenuHomePhabricator

zsdc ( )
User

Projects

User Details

User Since
Sep 10 2018, 3:30 PM (71 w, 6 d)

Recent Activity

Fri, Jan 24

zsdc changed the status of T1987: A default route can be deleted by dhclient-script in some cases from Open to In progress.
Fri, Jan 24, 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.
Fri, Jan 24, 6:58 PM · VyOS 1.3 Equuleus
zsdc created T1987: A default route can be deleted by dhclient-script in some cases.
Fri, Jan 24, 6:57 PM · VyOS 1.3 Equuleus

Mon, Jan 13

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.

Mon, Jan 13, 6:18 PM · VyOS 1.2 Crux
zsdc closed T1909: Incorrect work static routing 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.

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

Thu, Jan 2

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

Tue, Dec 31

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

The problem is fixed in 1.3.

Tue, Dec 31, 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.
Tue, Dec 31, 9:29 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1817: BGP next-hop-self not working. from Open to In progress.
Tue, Dec 31, 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.
Tue, Dec 31, 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.

Tue, Dec 31, 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.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

Aug 1 2019

zsdc added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

@mb300sd. create please a new one task with detailed description for BGP, if there are still some problems with it.

Aug 1 2019, 1:43 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1416: 2 dhcp server run in failover mode can't sync hostname with each other.

@thinkl33t, recommended way is using dynamic-dns-update, all other ways are not recommended to use at this moment.

Aug 1 2019, 10:03 AM · VyOS 1.3 Equuleus
zsdc reopened T1472: Impossible to recreate group in rfc3768-compatibility mode as "Backport candidate".
Aug 1 2019, 9:52 AM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc closed T1472: Impossible to recreate group in rfc3768-compatibility mode as Resolved.

@dmbaturin
Confirmed: the problem is not reproducible anymore in 1.2.0-rolling+201908010337 with keepalived 1:2.0.17+vyos1.2.

Aug 1 2019, 9:52 AM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc added a comment to T1500: Slow boot/load and CLI response times.

@ekim, we have never met with such a problem and cannot reproduce it in our environments. The better way to continue investigation would be getting access to this installation. If this would be possible, we could continue debugging.

Aug 1 2019, 9:38 AM · VyOS 1.3 Equuleus

Jul 18 2019

zsdc added a comment to T1458: Regression in 1.2.1-S2 hostname & logging.

@mb300sd, yes - nothing newer yet. Just test, please, when a new build will be available. :)

Jul 18 2019, 6:52 PM
zsdc closed T1497: "set system name-server" generates invalid/incorrect resolv.conf as Resolved.

The problem, which leads to the malformed hostname in Hostname Capability was fixed in T1531. I am marking this as "Resolved", because the problem with DNS servers was resolved also, according to feedback.

Jul 18 2019, 3:37 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1500: Slow boot/load and CLI response times.

Thank you, @ekim!
What exactly you were doing at the moment of this log record? I see a lot of scripts, which are almost permanently do something in the system. Is it possible that this system contains some custom scripts (in /config/scripts folder, for example)?
If yes, you should check the schedule of execution, and requirements of modification for 1.2 version command syntax.

Jul 18 2019, 2:56 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1458: Regression in 1.2.1-S2 hostname & logging.

@bmtauer, @mb300sd, the proper fix was applied. You can check again with any rolling release after 2019-07-17. Write back, please, if the problem will be still there.

Jul 18 2019, 12:46 PM

Jul 16 2019

zsdc changed the status of T1531: Several bugs in cluster configuration from Open to In progress.
Jul 16 2019, 8:51 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc created T1531: Several bugs in cluster configuration.
Jul 16 2019, 8:50 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Jul 13 2019

zsdc added a comment to T1500: Slow boot/load and CLI response times.

Hello, @ekim! I see now. This is more looks like the waiting due to I/O. Do, please, the next:

  1. Run sudo atop -w /tmp/atop-mon.log -a 5 60 in dedicated terminal.
  2. Try to work several minutes in the terminal. It must freezing at this moment, otherwise, collected test data will be wrong.
  3. Wait until atop finish its work (~ 5 min from the start).
  4. Copy the file /tmp/atop-mon.log from the router and send to us for analysis.
Jul 13 2019, 8:53 AM · VyOS 1.3 Equuleus

Jul 10 2019

zsdc raised the priority of T1381: Enable DHCP option 121 processing from Normal to High.
Jul 10 2019, 2:33 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1500: Slow boot/load and CLI response times.

@ekim, could you make a screen record with this CLI delay?

Jul 10 2019, 2:09 PM · VyOS 1.3 Equuleus
zsdc reassigned T1185: Firewall rulesets are ignored in RFC-compliant VRRP setups from Merijn to dmbaturin.

Hello, all!
I have prepared the pull requests for fixing this bug. They add hooks for two situations:

  • if VRRP configuration changed;
  • if firewall settings for interface changed.
Jul 10 2019, 1:39 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

Jul 8 2019

zsdc added a comment to T1500: Slow boot/load and CLI response times.

Hello, @ekim!
Such a significant increase of boot time with the same configuration is very strange, but still possible - even small changes can easily cause such behavior if you have a huge or some specific configuration. But what is more strange - CLI response time. Regardless of configuration, CLI should work without visible delays, except for autocompleting or commit operations.
Could you check the current load of the host at that moment, when CLI is slow? We must be sure that the system is not overloaded.

Jul 8 2019, 9:15 AM · VyOS 1.3 Equuleus

Jun 28 2019

zsdc reassigned T1472: Impossible to recreate group in rfc3768-compatibility mode from zsdc to dmbaturin.

I am confirming that the problem is not reproducing in the 2.0.17. We should upgrade keepalived distribution.

Jun 28 2019, 3:28 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Jun 26 2019

zsdc changed the status of T1416: 2 dhcp server run in failover mode can't sync hostname with each other from Backport candidate to Blocked.

I have checked behavior in 4.3.5 and 4.4.1 versions. The information about hostname is still not synced from primary to secondary.
As I see from the information in the Debian bug report, it is about the other bug - when hostname not rewritten after offering lease. From the ISC-DHCP changelog:

Jun 26 2019, 7:57 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1376: Incorrect DHCP lease counting.

Seem like static counting still not right

@dongjunbo, show please the configuration of this router so we could check why gcdomestic pool does not count correctly.

Jun 26 2019, 3:26 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

Jun 24 2019

zsdc changed the status of T1392: Large firewall rulesets cause the system to lose configuration and crash at startup from Open to Needs testing.

Provided configuration from the first message was successfully loaded in 1.2.0-rolling+201906240337.
@csalcedo, could you test new rolling to check if the problem is solved for you too?

Jun 24 2019, 5:50 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus
zsdc added a comment to T1416: 2 dhcp server run in failover mode can't sync hostname with each other.

Hello, @dongjunbo!
Have you tried current rolling releases to check if leases information view work correctly now?

Jun 24 2019, 3:24 PM · VyOS 1.3 Equuleus
zsdc claimed T1472: Impossible to recreate group in rfc3768-compatibility mode.

The safest solution will be waiting for 2.0.17, test compatibility with VyOS again, and then update keepalived package inside the VyOS.

Jun 24 2019, 3:08 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc added a comment to T1350: VRRP transition script will be executed once only.

As I see, from current VyOS scripts, keepalived restart only at router startup or if all VRRP groups were deleted. In case of configuration change we use reload, which is correct.
This means that we get nothing from the keeping state in case of the restart - there is no sense to keep states of deleted groups, and we have nothing to keep at first startup.

Jun 24 2019, 3:02 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

Jun 23 2019

zsdc changed the status of T1472: Impossible to recreate group in rfc3768-compatibility mode from Open to Confirmed.
Jun 23 2019, 10:54 AM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc created T1472: Impossible to recreate group in rfc3768-compatibility mode.
Jun 23 2019, 10:54 AM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Jun 22 2019

zsdc added a comment to T1467: Loopback interface naming and dummy devices.

I agree with you on many arguments. I just wanted to say my point of view.
There are many differences between vendors: in terminology, in behavior, in technologies. This is a normal situation. The same applying to engineers - we are very diversified, and this is beautiful :).

Jun 22 2019, 9:17 PM · VyOS 1.3 Equuleus
zsdc added a comment to T1467: Loopback interface naming and dummy devices.

I strongly disagree about mixing dummy/loopback at any of level (CLI or under the hood). Now we have two different types of interfaces: dummy and loopback with the according to names. And they are equal only if you use a dummy for the /32 addresses. In general situation:

  • Loopback interface will be used to reach any of the address inside the configured network;
  • If the IP address assigned to a dummy interface, the system will respond only to this address, not for the whole network.

Example, to be more precise:

set interfaces loopback lo address 192.168.8.1/24
set interfaces dummy dum1 address 192.168.9.1/24
Jun 22 2019, 6:37 PM · VyOS 1.3 Equuleus

Jun 21 2019

zsdc closed T1460: "show firewall ...." doesn't support counters with more than eight digits as Resolved.

Fixed in https://phabricator.vyos.net/R27:e6bff7fd27e74bf25737fa22aed6a5a60b7f03bd.

Jun 21 2019, 9:51 AM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus

Jun 20 2019

zsdc added a comment to T1460: "show firewall ...." doesn't support counters with more than eight digits.

Example of the output when value is below 10000000:

vyos@test-06:~$ show firewall name TESTFW rule 50
Jun 20 2019, 8:57 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc changed the status of T1460: "show firewall ...." doesn't support counters with more than eight digits from Open to In progress.
Jun 20 2019, 7:28 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc created T1460: "show firewall ...." doesn't support counters with more than eight digits.
Jun 20 2019, 7:28 PM · VyOS 1.2 Crux (VyOS 1.2.3), VyOS 1.3 Equuleus
zsdc closed T1456: Port group cannot be configured if the same port is configured as standalone and inside a range as Resolved.

The problem was fixed in https://phabricator.vyos.net/R6:97c5ad3dca756635e83eb3bf667f742457d85d74.

Jun 20 2019, 7:15 PM · VyOS 1.3 Equuleus

Jun 19 2019

zsdc claimed T1456: Port group cannot be configured if the same port is configured as standalone and inside a range.
Jun 19 2019, 7:09 PM · VyOS 1.3 Equuleus
zsdc created T1456: Port group cannot be configured if the same port is configured as standalone and inside a range.
Jun 19 2019, 7:09 PM · VyOS 1.3 Equuleus

Jun 5 2019

zsdc changed the status of T1350: VRRP transition script will be executed once only from Open to Confirmed.
Jun 5 2019, 1:27 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

Jun 4 2019

zsdc added a comment to T1376: Incorrect DHCP lease counting.

This bug must be fixed in current rolling, because of T1416. @dongjunbo, check this, please.

Jun 4 2019, 12:38 PM · VyOS 1.2 Crux (VyOS 1.2.5), VyOS 1.3 Equuleus

May 30 2019

zsdc added a comment to T1416: 2 dhcp server run in failover mode can't sync hostname with each other.

Problems with DHCP server status viewing can be fixed with the next patch for show_dhcp.py :

--- orig/show_dhcp.py	2019-05-30 22:45:01.625708032 +0300
+++ T1416/show_dhcp.py	2019-05-30 22:40:33.302777881 +0300
@@ -55,15 +55,28 @@
     return data
May 30 2019, 7:52 PM · VyOS 1.3 Equuleus

May 22 2019

zsdc changed the status of T1395: Improve boot time for instances with a big count of DHCP servers from Open to In progress.
May 22 2019, 12:17 PM · VyOS 1.3 Equuleus
zsdc created T1395: Improve boot time for instances with a big count of DHCP servers.
May 22 2019, 12:16 PM · VyOS 1.3 Equuleus

May 16 2019

zsdc closed T1148: epa2 BGP peers initiate before config is fully loaded, routes leak. as Resolved.

The solution was tested and fully worked.

May 16 2019, 5:17 PM · VyOS 1.3 Equuleus
zsdc closed T1267: FRR: Add interface name for static routes as Resolved.

@hagbard, everything works fine now. Thank you!

May 16 2019, 1:13 PM · VyOS 1.3 Equuleus

May 15 2019

zsdc added a comment to T1379: Deprecated functions in /sbin/dhclient-script.

@hagbard @UnicronNL, please make a new one PR. This is correct patch:

diff -Naur origin/dhclient-script pull2/dhclient-script
--- origin/dhclient-script	2019-05-15 19:32:59.001598203 +0300
+++ pull2/dhclient-script	2019-05-15 19:33:47.533181873 +0300
@@ -39,7 +39,6 @@
         echo " " > $new_resolv_conf
     fi
May 15 2019, 4:36 PM · VyOS 1.2 Crux (VyOS 1.2.2), VyOS 1.3 Equuleus

May 14 2019

zsdc added a comment to T1267: FRR: Add interface name for static routes.

This is not the same.

set protocols static table 100 interface-route 10.100.100.0/24 next-hop-interface eth1

generate:

test-06# show running-config staticd 
Building configuration...
May 14 2019, 5:46 PM · VyOS 1.3 Equuleus
zsdc changed the status of T1381: Enable DHCP option 121 processing from Open to Confirmed.
May 14 2019, 5:14 PM · VyOS 1.3 Equuleus
zsdc created T1381: Enable DHCP option 121 processing.
May 14 2019, 5:10 PM · VyOS 1.3 Equuleus
zsdc renamed T1379: Deprecated functions in /sbin/dhclient-script from Deprecated function in /sbin/dhclient-script to Deprecated functions in /sbin/dhclient-script.
May 14 2019, 2:16 PM · VyOS 1.2 Crux (VyOS 1.2.2), VyOS 1.3 Equuleus
zsdc changed the status of T1379: Deprecated functions in /sbin/dhclient-script from Open to Confirmed.
May 14 2019, 12:20 AM · VyOS 1.2 Crux (VyOS 1.2.2), VyOS 1.3 Equuleus
zsdc created T1379: Deprecated functions in /sbin/dhclient-script.
May 14 2019, 12:17 AM · VyOS 1.2 Crux (VyOS 1.2.2), VyOS 1.3 Equuleus

May 13 2019

zsdc reassigned T1267: FRR: Add interface name for static routes from zsdc to hagbard.

@hagbard solution works. Please, add it also to the stable branch and to the set protocols static table section.

May 13 2019, 1:19 PM · VyOS 1.3 Equuleus

May 3 2019

zsdc reassigned T941: BGP neighbours with IPv6 link-local addresses from zsdc to matt.webb.
May 3 2019, 11:47 AM · VyOS 1.3 Equuleus
zsdc reassigned T1319: 'show vpn ipsec sa' throws errors from zsdc to matt.webb.
May 3 2019, 11:45 AM · VyOS 1.3 Equuleus
zsdc reassigned T1169: LLDP potentially broken from zsdc to matt.webb.
May 3 2019, 11:40 AM · VyOS 1.3 Equuleus

Apr 18 2019

zsdc added a comment to T1325: GRE tunnel to Cisco router fails in 1.2.0 - works in 1.1.8.

Unfortunately, current Linux GRE and network stack implementations don't support Cisco-style of GRE keepalives (GRE inside GRE, with spoofed IP addresses). From the Linux point of view, those packets look like martians, and the kernel drop them, information about what you can see inside a log.
Try to disable the keepalive at the Cisco side, after this tunnel must be fully functional.

Apr 18 2019, 9:46 PM · VyOS 1.3 Equuleus

Apr 5 2019

zsdc reopened T1322: Wrong configuration generated for DHCPv6 Relay as "Confirmed".

Sorry, I must reopen this task. Absolutely the same situation with multiple "lower" interfaces:

OPTIONS="-6 -l ::%eth1.100-l ::%eth1.102 -u 2001:db8:0:feed::2%eth2.88 -u 2001:db8:0:feed::3%eth2.88 "
                         ^^
                         here
Apr 5 2019, 2:06 PM · VyOS 1.2 Crux (VyOS 1.2.1), VyOS 1.3 Equuleus