PR # 219

Unfortunately I have no idea how that zone option works. I'd rather solve this by an automatic code path then specifying it on the commandline (which is now possible).

as discussed on slack, GRE is already supported: https://docs.vyos.io/en/latest/vpn/gre-ipsec.html , closing as invalid

I think we should make somewhere a list of services and which level of vrf support they have.
Openssh for example has build in support for vrf

In T31#53189, @rherold wrote:

Could be away. But from my experience most people use vrf to seperate managment from production, and as second prio seperate customers and so on.
But the managment vrf must not be the "default" vrf.

Here is a patch to implement VRF. Binding is set to work on all VRF for daemon so that BGP and other protocols will work on all VRF.
https://gist.github.com/thomas-mangin/7704c538d905190bd05cfe613bd9f4f5

Could be away. But from my experience most people use vrf to seperate managment from production, and as second prio seperate customers and so on.
But the managment vrf must not be the "default" vrf.

while it would be quite nice to have a Cumulus 4.0+ like default management VLAN and make all services management aware (which would quite considerably increase the among of work to get something out), I am proposing instead make sure that all services running on the default VRF are available on VRF as a first step.

suggesting https://github.com/vyos/vyos-1x/pull/217

Tested with 1.3-rolling-202002091356, the issue is fixed. Thanks!

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?