Problem is there are several modules that depend on IPv6 e.g. bridge and wireguard thus it can't be removed anymore.

@jjakob for equuleus too, wait for merge PR. We have also some ideas how we can improve net naming, and fix issues with renameX interfaces after boot.

Is this only for crux or also for equuleus? There is also
https://phabricator.vyos.net/T1499
https://phabricator.vyos.net/T1584
https://phabricator.vyos.net/T291

Successfully tested on 1.3. PR for current branch https://github.com/vyos/vyatta-cfg-system/pull/113

Note: If we have interfaces with description on device panel, like WAN, DMZ, etc, we can use predefined alias in this case.

vyos@QAT-R1:~$ sudo cat /lib/udev/rules.d/64-vyos-SAF51003I-net.rules 
ATTR{[dmi/id]board_name}!="SAF51003I", GOTO="end_ec_nic"

PR for CRUX branch https://github.com/vyos/vyatta-cfg-system/pull/112

Works correct on 1.3-rolling-201912190503

Also fixed additional issue with multiple snmp script-extensions entry (jinja2 sort)

In latest rolling 1.2-rolling-201912180217 permission problem solved, but exist one more problem with script path.
CLI allow us to choice script, which stored on '/config/user-data'

Thanks @Dmitry, building it again.

@sento own build 1.2.4 this is 1.2-rolling (branch current), in crux branch all works as expected.

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

Now it works perfect.

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

@hagbard Confirmed fix. Migration worked perfectly.

@kroy Please let me know if you still experience any issues (setting the port or migration).

@Dmitry Tested it with the latest 1.2 rolling, the issue is still present.

@Merijn if you are still willing to test, I can provide build instructions, if you need. I noticed that you had been working with @hagbard recently on your build environment; if you are willing to use docker, I can give you step-by-step instructions to build with these patches.

I can't reproduce this issue on 1.2.3 and 1.2/1.3 rolling. @hagbard can you test again too?

fixed in http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb

Trying to apply the fix manually:

Built a fresh rolling. It failed with:

https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201912061907-amd64.iso and later include the fix

I pick this up as I did the rewrite of this whole stuff

https://github.com/vyos/vyos-1x/pull/177
https://github.com/vyos/vyatta-cfg-vpn/pull/27

The fix suggested in the pull request did not resolve the issue as a consequence of T1847. With that issue resolved, we can consider this merge.

Thanks

Ah yes, it's taken entirely from the string, my fault I tested with the version you can only use an IP address.

It actually does work, if only by accident

cpo@LR1.wueIII:~$ sudo ip addr add "192.168.1.1/24" dev eth1.100

That command (above) don't correct for vif-s, with sudo you assign ipv4 only to one tag 8021q (Cvlan) .

@Merijn I am consulting with the author of the pull request; I still need to confirm behavior before we can consider merging.

@Merijn I will build and run a sanity check, and then we can merge into rolling for testing; I'll confirm when done. Thanks again for the offer to test.

@jestabro i am not able to build the vyos-1x package because of dependencies on other packages.
Can we include them in rolling so i can test tomorrow?

@jestabro i have encountered the first situation in my networks where i really need RFC-Complaint VRRP
(Some devices do not learn the MAC-address on the VRRP gateway, it works for some time and then stops).

This still needs some review and testing. @Merijn, thank you for the offer; testing will be much appreciated, once PRs are merged.

This will need several related commits, testing, before being backported.