Page MenuHomeVyOS Platform
Feed All Stories

Jul 5 2020

c-po added a comment to T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series.

@Viacheslav could you please check if this probably should make it into 1.2.6 in addition?

Jul 5 2020, 2:10 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.2 Crux (VyOS 1.2.6)
c-po changed the status of T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series from Open to Backport candidate.
Jul 5 2020, 2:10 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.2 Crux (VyOS 1.2.6)
c-po added a comment to T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series.

https://github.com/vyos/vyatta-cfg-quagga/pull/51

Jul 5 2020, 2:10 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.2 Crux (VyOS 1.2.6)
c-po created T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series.
Jul 5 2020, 2:07 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.2 Crux (VyOS 1.2.6)
jack9603301 changed the status of T2680: dhcp6c service cannot recover when it fails from Open to Needs testing.
Jul 5 2020, 1:58 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

@c-po When you submit the following commit, the problem seems to be solved, when I need to do further testing tomorrow, waiting for tomorrow's daily build

Jul 5 2020, 1:56 PM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2681: PPPoE stops negotiating IPv6 as Resolved.
Jul 5 2020, 10:35 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2681: PPPoE stops negotiating IPv6.

Problem was introduced by porting PPPoE to the get_config_dict() implementation T2653 commit https://github.com/vyos/vyos-1x/commit/65fa21f5

Jul 5 2020, 10:25 AM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2685: Update Accel-PPP to fix SSTP client issues as Resolved.
Jul 5 2020, 9:40 AM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2685: Update Accel-PPP to fix SSTP client issues, a subtask of T2684: Update Linux Kernel to v4.19.131, as Resolved.
Jul 5 2020, 9:40 AM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2684: Update Linux Kernel to v4.19.131 as Resolved.
Jul 5 2020, 9:39 AM · VyOS 1.3 Equuleus (1.3.0)
c-po changed the status of T2684: Update Linux Kernel to v4.19.131 from Open to In progress.
Jul 5 2020, 9:36 AM · VyOS 1.3 Equuleus (1.3.0)
c-po created T2685: Update Accel-PPP to fix SSTP client issues.
Jul 5 2020, 9:35 AM · VyOS 1.3 Equuleus (1.3.0)
c-po created T2684: Update Linux Kernel to v4.19.131.
Jul 5 2020, 9:35 AM · VyOS 1.3 Equuleus (1.3.0)
jjakob added a comment to T2523: Upgrade from 1.2.5 to 1.3-rolling-202005261512 results in broken network config on second boot.

The most likely culprit is /opt/vyatta/sbin/vyatta_interface_rescan. I'm not sure if this should be fixed or migrated to Python.
The rewrite would need to be done together with all other vyatta interface renaming and detection scripts.

Jul 5 2020, 9:30 AM · VyOS 1.3 Equuleus (1.3.3)
jjakob added a comment to T2523: Upgrade from 1.2.5 to 1.3-rolling-202005261512 results in broken network config on second boot.

Upgrading a different test VM with different config that starts at eth0: on 2nd reboot the hw-id lines are duplicated too, but they are the same on a single interface, and there are no new interfaces created, so the config loads and works fine. The duplicated hw-id lines stay in the config for all subsequent reboots.
Example:

ethernet eth0 {
    address "192.0.2.1"
    hw-id "52:54:00:2d:29:19"
    ipv6 {
        address {
        }
    }
    smp-affinity "auto"
    speed "auto"
    hw-id 52:54:00:2d:29:19
}

What I'm noticing is that the migration scripts save all nodes with quotes, but saving in config mode (through vyatta-cfg) results in most nodes not having quotes (mostly just those with spaces have it). Maybe there is a vyatta script that adds any new interfaces to config.boot that runs on each boot that doesn't like these quoted hw-id lines that the migration scripts produce.

Jul 5 2020, 9:08 AM · VyOS 1.3 Equuleus (1.3.3)
jjakob added a comment to T2523: Upgrade from 1.2.5 to 1.3-rolling-202005261512 results in broken network config on second boot.

I tried reupgrading from 1.3-rolling-202006110117 to 1.3-rolling-202007050117 and the exact same error occurred - on first reboot everything was fine (config.boot was migrated, looked correct, and loaded fine). On 2nd reboot, the exact same thing happened.

Jul 5 2020, 8:42 AM · VyOS 1.3 Equuleus (1.3.3)
Unknown Object (User) added a comment to T2659: Add fastnetmon (DDoS detection) support.

Necessary run service with priority for correct starting https://github.com/vyos/vyos-1x/pull/489

Jul 5 2020, 8:16 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

Does DNS static-host-mapping still work with the nssswich.conf change? I‘m just curious about the side effects.

Jul 5 2020, 8:05 AM · VyOS 1.3 Equuleus (1.3.0)
Unknown Object (User) changed the status of T2659: Add fastnetmon (DDoS detection) support from Open to Needs testing.
Jul 5 2020, 7:40 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

@c-po The basic cause of the failure has been determined.This time, the problem may be relatively serious, because it is not the configuration of the service, but the execution of commit will not start the dhcp6c service at all.

Jul 5 2020, 4:50 AM · VyOS 1.3 Equuleus (1.3.0)

Jul 4 2020

kroy added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
default as an IP address is in the end more useful then a resolved PTR
Jul 4 2020, 9:53 PM · VyOS 1.3 Equuleus (1.3.0)
jjakob added a comment to T2683: no dual stack in system static-host-mapping host-name .

Duplicate of T2627

Jul 4 2020, 9:11 PM · VyOS 1.3 Equuleus (1.3.2), VyOS 1.4 Sagitta
rherold created T2683: no dual stack in system static-host-mapping host-name .
Jul 4 2020, 8:49 PM · VyOS 1.3 Equuleus (1.3.2), VyOS 1.4 Sagitta
c-po renamed T2682: VRF aware services - connection no longer possible after system reboot from SSH: VRF: connection no longer possible after system reboot to VRF aware services - connection no longer possible after system reboot.
Jul 4 2020, 7:56 PM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

Somehow I do not want to change the overall system behavior by altering nsswitch.conf. I wonder if we should not enable "disable-host-ookups" by default as an IP address is in the end more useful then a resolved PTR. A PTR record can be changed later on when dissecting the logfiles but an IP lookup should stay longer.

Jul 4 2020, 7:41 PM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2682: VRF aware services - connection no longer possible after system reboot as Resolved.
Jul 4 2020, 7:36 PM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2682: VRF aware services - connection no longer possible after system reboot.

Linux tries to bind SSHd to the VRF but it is yet not ready. After restarting SSH to often (rate-limiting) it is blocked.

Jul 4 2020, 7:19 PM · VyOS 1.3 Equuleus (1.3.0)
c-po changed the status of T2682: VRF aware services - connection no longer possible after system reboot from Open to Confirmed.
Jul 4 2020, 6:31 PM · VyOS 1.3 Equuleus (1.3.0)
c-po updated the task description for T2682: VRF aware services - connection no longer possible after system reboot.
Jul 4 2020, 6:31 PM · VyOS 1.3 Equuleus (1.3.0)
c-po created T2682: VRF aware services - connection no longer possible after system reboot.
Jul 4 2020, 6:10 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

Oddly enough, whether I change the service settings or change the default settings of systemd, there are problems.

Jul 4 2020, 1:36 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

@c-po The problem was found when upgrading to the latest version, and the reason is not clear.

Jul 4 2020, 1:35 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

PPPoE is configured as follows (account password is hidden):

Jul 4 2020, 1:34 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

I want to do it and have to re explore the cause of the failure, but I haven't found out why dhcp6c can't start, I have to start it manually.

Jul 4 2020, 1:34 PM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2680: dhcp6c service cannot recover when it fails.

Changing the systemd defaults is a thing I hesitate to do! It will have a ton of unexpected sideeffects. I guess you have an error in your entire setup as multiple sites of mine work flawlessly

Jul 4 2020, 1:26 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2680: dhcp6c service cannot recover when it fails.

Strange, I found that this service may not have been started at all!

Jul 4 2020, 1:03 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 created T2681: PPPoE stops negotiating IPv6.
Jul 4 2020, 8:09 AM · VyOS 1.3 Equuleus (1.3.0)
rherold added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

for me it looks like a name lookup error. I have read the forum entry mentioned above. And they fixed it by disabling name lookup.

Jul 4 2020, 7:09 AM · VyOS 1.3 Equuleus (1.3.0)
c-po moved T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table. from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Jul 4 2020, 7:07 AM · VyOS 1.3 Equuleus (1.3.0)
c-po changed the status of T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table. from Open to Confirmed.
Jul 4 2020, 7:07 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

I found that I had disable-host-validation configured and as soon as I removed it it happened to me, too. Changing task priority.

Jul 4 2020, 7:07 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

I have checked with a v4/v6 full table router and VyOS 1.2.5 - each SSH session will consume 7MiB which semms okay for me.

Jul 4 2020, 6:59 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2679: VRRP with BFD Failure Detection.

Availible in keepalived, thus kt could be considered for 1.3

Jul 4 2020, 6:42 AM · VyOS 1.3 Equuleus (1.3.0)
kroy added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

This also has a measurable impact on CPU. You can tell exactly when I applied the nsswitch.conf fix.

Jul 4 2020, 5:51 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 updated the task description for T2680: dhcp6c service cannot recover when it fails.
Jul 4 2020, 5:48 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2675: DNS service failed to start.
forwarding {
    allow-from 192.168.0.0/16
    allow-from 2001:470:f1cd::/48
    cache-size 1024
    domain pve. {
        addnta
        recursion-desired
        server 192.168.0.47
        server 2001:470:f1cd::47
    }
    listen-address 0.0.0.0
    listen-address ::
    name-server 2001:470:f1cd::ff00
    name-server 192.168.0.254
    name-server 202.96.134.33
    name-server 202.96.128.86
    name-server 114.114.114.114
    name-server 1.1.1.1
    name-server 1.0.0.1
    system
}
Jul 4 2020, 5:33 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 updated the task description for T2680: dhcp6c service cannot recover when it fails.
Jul 4 2020, 5:31 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 updated the task description for T2680: dhcp6c service cannot recover when it fails.
Jul 4 2020, 5:29 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 created T2680: dhcp6c service cannot recover when it fails.
Jul 4 2020, 5:20 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

Oh, in a system like vyos, SSH memory leak appears to be relatively serious. If there is a solution, it should be handled first

Jul 4 2020, 5:03 AM · VyOS 1.3 Equuleus (1.3.0)
kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 4 2020, 4:42 AM · VyOS 1.3 Equuleus (1.3.0)
trae32566 created T2679: VRRP with BFD Failure Detection.
Jul 4 2020, 3:26 AM · VyOS 1.3 Equuleus (1.3.0)
kroy renamed T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table. from High RAM usage on SSH logins with lots of routes in the routing table. to High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 4 2020, 2:18 AM · VyOS 1.3 Equuleus (1.3.0)

Jul 3 2020

kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 10:10 PM · VyOS 1.3 Equuleus (1.3.0)
kroy triaged T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table. as High priority.
Jul 3 2020, 10:09 PM · VyOS 1.3 Equuleus (1.3.0)
kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 10:08 PM · VyOS 1.3 Equuleus (1.3.0)
kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 10:08 PM · VyOS 1.3 Equuleus (1.3.0)
kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 10:04 PM · VyOS 1.3 Equuleus (1.3.0)
kroy added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..

To add to this, this link pointed me at the correct solution:

Jul 3 2020, 9:57 PM · VyOS 1.3 Equuleus (1.3.0)
kroy updated the task description for T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 9:56 PM · VyOS 1.3 Equuleus (1.3.0)
kroy created T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Jul 3 2020, 9:54 PM · VyOS 1.3 Equuleus (1.3.0)
Unknown Object (User) added a comment to T2659: Add fastnetmon (DDoS detection) support.

PR https://github.com/vyos/vyos-1x/pull/487 with changed CLI to service ids ddos-protection.

Jul 3 2020, 8:11 PM · VyOS 1.3 Equuleus (1.3.0)
dsummers added a comment to T2653: "set interfaces" Python handler code improvements - next iteration.

@elianora Email me at [email protected]

Jul 3 2020, 5:41 PM · VyOS 1.3 Equuleus (1.3.0)
c-po assigned T2675: DNS service failed to start to jjakob.
Jul 3 2020, 4:57 PM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2675: DNS service failed to start.

Again, please always attach a configuration file

Jul 3 2020, 4:57 PM · VyOS 1.3 Equuleus (1.3.0)
c-po moved T2677: Proposal for clearer DHCPv6-PD configuration options from In Progress to Backlog on the VyOS 1.3 Equuleus board.
Jul 3 2020, 3:26 PM · VyOS 1.3 Equuleus (1.3.0)
c-po moved T2677: Proposal for clearer DHCPv6-PD configuration options from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Jul 3 2020, 3:26 PM · VyOS 1.3 Equuleus (1.3.0)
c-po changed the status of T2677: Proposal for clearer DHCPv6-PD configuration options from Open to In progress.
Jul 3 2020, 3:26 PM · VyOS 1.3 Equuleus (1.3.0)
elianora updated subscribers of T2677: Proposal for clearer DHCPv6-PD configuration options.

At the request of @c-po, going to mention that this may have relevance to T2653 since the order of how interfaces are handled may be effected by this and/or the proposal here may make sense to change based on their work.

Jul 3 2020, 3:06 PM · VyOS 1.3 Equuleus (1.3.0)
elianora created T2677: Proposal for clearer DHCPv6-PD configuration options.
Jul 3 2020, 3:02 PM · VyOS 1.3 Equuleus (1.3.0)
jestabro updated the task description for T2667: get_config_dict: Use utility function for non-empty path argument.
Jul 3 2020, 1:13 PM · VyOS 1.3 Equuleus (1.3.0)
jestabro closed T2670: Remove dependency on show_config from get_config_dict as Resolved.
Jul 3 2020, 1:12 PM · VyOS 1.3 Equuleus (1.3.0)
jestabro closed T2670: Remove dependency on show_config from get_config_dict, a subtask of T2667: get_config_dict: Use utility function for non-empty path argument, as Resolved.
Jul 3 2020, 1:12 PM · VyOS 1.3 Equuleus (1.3.0)
c-po closed T2676: NTP: migrate to get_config_dict() implementation as Resolved.
Jul 3 2020, 11:33 AM · VyOS 1.3 Equuleus (1.3.0)
c-po changed the status of T2676: NTP: migrate to get_config_dict() implementation from Open to In progress.
Jul 3 2020, 11:10 AM · VyOS 1.3 Equuleus (1.3.0)
c-po created T2676: NTP: migrate to get_config_dict() implementation.
Jul 3 2020, 11:09 AM · VyOS 1.3 Equuleus (1.3.0)
c-po added a comment to T2665: vyos.xml.defaults for tag nodes.

I use myself a "cleanup" function, imagine:

Jul 3 2020, 8:57 AM · VyOS 1.4 Sagitta
c-po added a comment to T2674: Other arhitecture support (MIPS, ARM).

I wish you success in advance. Porting and compiling has always been a large-scale application project, which may take a lot of time. However, in addition to rewriting and porting related code to a more portable language, we can also try to transplant and cross build the existing old code first. Of course, this is only the first step. If possible, porting the code base has made it easier for the code base to be transplanted Meaningful.

Jul 3 2020, 8:39 AM · VyOS 1.5 Circinus
c-po added a comment to T2665: vyos.xml.defaults for tag nodes.

As "ip" is an invalid key in "vif" (as its no VLAN number) it should not be part of the default dict I guess - same for vif_s

Jul 3 2020, 8:29 AM · VyOS 1.4 Sagitta
runar added a comment to T2674: Other arhitecture support (MIPS, ARM).

There are allready someone trying to make a guide for building vyos on arm and the pi3/4, i myself have made it work on the pi4 some time ago but did not save my work so i dont have all the steps to reproduce..

Jul 3 2020, 8:19 AM · VyOS 1.5 Circinus
jack9603301 added a comment to T2674: Other arhitecture support (MIPS, ARM).

I wish you success in advance. Porting and compiling has always been a large-scale application project, which may take a lot of time. However, in addition to rewriting and porting related code to a more portable language, we can also try to transplant and cross build the existing old code first. Of course, this is only the first step. If possible, porting the code base has made it easier for the code base to be transplanted Meaningful.

Jul 3 2020, 8:11 AM · VyOS 1.5 Circinus
samip537 added a comment to T2674: Other arhitecture support (MIPS, ARM).

Yes, I'm interested in actually helping on porting it as it would make my ER-X for one, a lot more fun and useful.

Jul 3 2020, 7:49 AM · VyOS 1.5 Circinus
c-po added a comment to T2674: Other arhitecture support (MIPS, ARM).

porting half of an operating system to a different architecture is far from easy. Right now VyOS still has a lot of the old Vyatta codebase in it. As we are more and more in the process of migrating this to a Python based codebase it will still take some time. To be fair I stater a project some time back to port VyOS on an EdgeROuterPro (https://github.com/c-po/vy-project) and at least "it booted" but I then switched my focus to VyOS first - so by migrating th ecodebase to our own vyos-1x based Python implementation it will become easier in the future to port it to other operating systems as there is less code, less packages to port.

Jul 3 2020, 7:10 AM · VyOS 1.5 Circinus
jack9603301 created T2675: DNS service failed to start.
Jul 3 2020, 5:51 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 closed T2671: SNMP failed to start after the system was rebooted as Invalid.
Jul 3 2020, 5:25 AM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2671: SNMP failed to start after the system was rebooted.

@c-po When this problem occurred, I might be testing bridge. I didn't expect that my test would make the bridge enter the admin down state without any warning. Later, when I restart, I found that SNMP seemed to be normal. This problem can be temporarily switched to invalid. Please refer to T2673

Jul 3 2020, 4:44 AM · VyOS 1.3 Equuleus (1.3.0)
samip537 created T2674: Other arhitecture support (MIPS, ARM).
Jul 3 2020, 2:11 AM · VyOS 1.5 Circinus

Jul 2 2020

c-po added a comment to T2671: SNMP failed to start after the system was rebooted.

As always, please provide your config and probably a way to reproducs.

Jul 2 2020, 10:48 PM · VyOS 1.3 Equuleus (1.3.0)
elianora added a comment to T2653: "set interfaces" Python handler code improvements - next iteration.

EDIT 1: Removing comment after speaking with cpo, I apologize for the confusion

Jul 2 2020, 6:53 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 added a comment to T2671: SNMP failed to start after the system was rebooted.

I found that this problem may be related to T2673

Jul 2 2020, 6:46 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 updated the task description for T2673: After the bridge is configured with Mac, bridge is automatically disabled.
Jul 2 2020, 5:33 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 updated the task description for T2673: After the bridge is configured with Mac, bridge is automatically disabled.
Jul 2 2020, 5:23 PM · VyOS 1.3 Equuleus (1.3.0)
jack9603301 created T2673: After the bridge is configured with Mac, bridge is automatically disabled.
Jul 2 2020, 5:22 PM · VyOS 1.3 Equuleus (1.3.0)
runar added a comment to T2653: "set interfaces" Python handler code improvements - next iteration.

Please open a new ticket or move your comment to an appropriate ticket, this ticket is not discussing your consernes.

Jul 2 2020, 4:42 PM · VyOS 1.3 Equuleus (1.3.0)
dsummers added a comment to T2653: "set interfaces" Python handler code improvements - next iteration.
Jul 2 2020, 4:35 PM · VyOS 1.3 Equuleus (1.3.0)
dsummers updated the task description for T2672: Bug: Errors when creating new user.
Jul 2 2020, 4:18 PM
dsummers added a comment to T2672: Bug: Errors when creating new user.

Also on delete:

Jul 2 2020, 4:17 PM
dsummers created T2672: Bug: Errors when creating new user.
Jul 2 2020, 4:14 PM
dsummers renamed T2619: Bug: Changes in NAT or ZONES from 1.2 to 1.3 from Question: Changes in NAT or ZONES from 1.2 to 1.3? to Bug: Changes in NAT or ZONES from 1.2 to 1.3.
Jul 2 2020, 4:10 PM · VyOS 1.3 Equuleus (1.3.0)