In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958479, @sdev wrote:

Are you able to provide the dhcp config that fails migration? I wasn't able to re-create any migration problem in my tests

I'm having the same error. Even with NO ipsec configured. Just using DHCP.

In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958453, @workingagain wrote:

when migrating from pre subnet-id builds to a subnet build will cause migration failed during initial startup due to missing subnet id.

Can confirm, short term testing worked.

I'm seeing the same problem. Latest 1.4 version from git.

Oops, I didn't see T5647! Sorry! I guess this one can be closed as a duplicate.

In T5932#172324, @marc_s wrote:

I take it RC2 will contain these new versions @Viacheslav?

Do static addresses/gateways work stable enough?

100% agree. I have submitted a similar feature request here:

I take it RC2 will contain these new versions @Viacheslav?

Seems you're right @indrajitr:

@Viacheslav sure, updated the OP

Always use "set commands" to make it easier for developers to reproduce it.

@samip537 You should use the peer group definition inside the v6-only stanza, like so:

neighbor wg1 {                                                                                           
    interface {                                                                                          
        v6only {                                                                                         
            peer-group BACKBONE                                                                          
            remote-as 4242420669                                                                         
        }                                                                                                
    }                                                                                                    
}

@MattK provide a simple example of "set" commands to reproduce

In T5835#171322, @Viacheslav wrote:

Another bug it that /config/upnp.leases is hardcoded, but there is no script who creates it https://github.com/vyos/vyos-1x/blob/aebb458262072457c6a3840d1b17031fbd780eca/data/templates/firewall/upnpd.conf.j2#L128

It cause of

Jan 10 21:16:03 r4 miniupnpd[9869]: Reloading rules from lease file
Jan 10 21:16:03 r4 miniupnpd[9869]: could not open lease file: /config/upnp.leases

Did some more work on this.

Quite likely the following relevant patches are not present in 1.4-rc1:

• https://github.com/vyos/vyos-1x/commit/975ce1c71352e319abef59e9e63de2c3fca2f281
• https://github.com/vyos/vyos-1x/commit/3d9f381964e53fe0ce6456724660727283802f48

when migrating from pre subnet-id builds to a subnet build will cause migration failed during initial startup due to missing subnet id.

Hello, this task has a bug. Do I open a new task or comment here?

I've made some progress. I've been able to get miniupnpd to stop generating the mnl_cb_run() errors. It was as assumed; the lack of nft table / chains.

PR:
https://github.com/vyos/vyos-1x/pull/2818

My only comment here would be to hesitate when putting in restrictions; as Doug Gwyn once said:

Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.

I just did a test - without the VLAN interfaces added, the VLAN traffic is still offloaded.
So the CLI should be updated to prevent VLAN's from being added (since it doesn't make any sense to add them, since they work when the parent interface is added)

https://github.com/vyos/vyos-1x/pull/2816

The commit in question was added after the VyOS 1.3.5 release

We have a decision to leave it as it is.
@c-po closed the task T4487
So close it as wontfix.

PR https://github.com/vyos/vyos-1x/pull/2814