Please reopen if issue re-apperas

Okay, there was a type in the regex constraint for the type of SSH key you used.

Can you privatley send me the full configuration as it seems a lot of migrators are executed from system@12 to system@16

This is only the login section

login {
    user vyos {
        authentication {
            encrypted-password $6$***
            plaintext-password ""
            public-keys jernej@jernej {
                key ****************
                type ssh-ed25519
            }
        }
        level admin
    }
}

the config version line

/* Warning: Do not remove the following line. */
/* === vyatta-config-version: "broadcast-relay@1:cluster@1:config-management@1:conntrack@1:conntrack-sync@1:dhcp-relay@2:dhcp-server@5:dns-forwarding@2:firewall@5:interfaces@4:ipsec@5:l2tp@1:mdns@1:nat@4:ntp@1:pptp@1:qos@1:quagga@3:snmp@1:ssh@1:system@12:vrrp@2:vyos-accel-ppp@2:wanloadbalance@3:webgui@1:webproxy@2:zone-policy@1" === */
/* Release version: 1.3-rolling-201912110242 */

The system login CLI interface has been rewritten to XML/Python. Please try again with a newer rolling relese

HI @jjakob the login method has been migrated to XML/Python. Can you please pass me your pre-migration configuration so I cen re-lab this?

@hexes that's why there is a big banner on top indicating this page is outdated and links you to the new docs.

(It's possible to spy decision on Ubnt, this issue solved there, in attach:)

c-po, thanks a lot, didn't see this trick... There is too much different docs. We need to combine in one place. Here is nothing about quotes... :-( https://wiki.vyos.net/wiki/DHCP_server

Maybe there will be a better option one day. Right now we only have https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/dhcp_server.py#L816

For the time being please see the instructions at https://docs.vyos.io/en/latest/services/dhcp.html#dhcp-server about the pre and post usage of "

Thanks @runar . It worked for me.
Libvirtd +6 interfaces.

VyOS 1.3-rolling-202002050217 Does not show this behavior - when no OpenVPN interface is defined you will get:

Okay, just to give you some guidance, this is what I hacked up in 5 minutes... don't take it as complete

Identified configuration format change:

I have a use case for VRF / Linux namespace with VyOS and was wondering if there was a way to break this task down, first allowing the manual creation of VRF/namespace using the CLI (without linking the work to BGP). I will be able to contribute the required changes to the vyos-1x repository should I be given enough direction on how you would like to proceed.

https://github.com/vyos/vyatta-op/commit/7fe22b3aeb40664c7e2ebf7fd4d8d08006c5a76e

The maintainers can just replace inetutilsping with iputilsping as was the case in previous versions of VyOS. Just need this to be picked up by someone.

Okay, packages have been recreated for Debian Buster and RADIUS login works again (50%)

Ability to use Local PBR ref T439

• 538 MB -> current status without modifications
• 506 MB -> removved /usr/share/docs
• 394 MB -> --apt-recommends false

To install the zabbix-agent (for rolling) you need:

Is this still an issue after the latest modifications (T1937) to SNMP wo fully run on Debian Buster?

Boots now as expectd after adding the remaining dependencies to the VyOS/Vyatta packages.

dbus package is missing, too - another offender

Followup, some screenshots on the mentioned problem:

Confirmed here as well, I had a working config back on 1.2.3 and it broke when I upgraded to 1.3. This is what happens when I try to commit:

Related with https://phabricator.vyos.net/T1842 I think we need pytz

https://github.com/vyos/vyos-1x/commit/95f7a440031c58b47fd88d6aa9fac3ddaf6ae231