@n.fort Sorry yes this AC-1 vyos was on 1.2.1 I will a test tomorrow with a version 1.2.6-S1 to have the path i was mention..

Thanks for sharing.
It this ok?

@n.fort yes . This is an example os our AC-1 enviroment (the one i have used for the first test)

Can you share your config @daniel.arconada ?

tried also with vyos-1.4-rolling-202203070319-amd64.iso and same issue with the migration

Hi @Viacheslav I have tried this morning upgrading from vyos 1.2.6-S1 to vyos-1.4-rolling-202204060217-amd64.iso but something went wrong with the firewall config load and all the firewall rules and objets were removed from config so impossible to test.. :(

Is there a way to get this to work with a dynamically assigned /64 PD from my ISP?

@Viacheslav Link local addresses were added successfully on boot on 1.4-rolling-202204060217.

Thank you very much @sdev !

@daniel.arconada it should be fixed in 1.4
Can you check it?

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

Do we have any news when this feature (-n option) will be included? We have lot of vyos on 1.2.X with booting times between 20 and 40 minutes and commits about 3-5 minutes.

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

PR for 1.3 (equuleus) https://github.com/vyos/vyos-1x/pull/1273

@Viacheslav fix verified - also the new smoketest detected the bug prior to your fix and no longer seen the bug after your fix.

@NceAirport do you have a minimum required configuration?
As I see it should be something like:

set service monitoring xxx prometheus authentication login xxx
set service monitoring xxx prometheus authentication password xxx
set service monitoring xxx prometheus port 9273
set service monitoring xxx prometheus network 192.0.2.0/24

@devon Will be fixed in the next rolling release, could you check it?

Applying patch from the PR I could not reproduce issue anymore

cherry-pick for 1.3 https://github.com/vyos/vyos-1x/pull/1271

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

Great.
In that case I suggest marking this invalid and close it

Fixed via https://github.com/vyos/vyos-1x/pull/1263/commits/ce4a1eb35a91c9ac1a95e2418c1300004272e1a7 in https://github.com/vyos/vyos-1x/pull/1263

Fixed via https://github.com/vyos/vyos-1x/pull/1263/commits/f728e321d1fb781e26bbc103ac9923064ec86086 in https://github.com/vyos/vyos-1x/pull/1263

I've been testing , the feature works as expected . IPOE assigns different ip by dhcp using ip-pool :

vyos@ipoe:~$ show ipoe-server sessions
ifname     | username |    calling-sid    |     ip     | rate-limit | type | comp | state  |  uptime
---------------+----------+-------------------+------------+------------+------+------+--------+----------
 eth3.1000.140 |          | aa:bb:cc:00:60:00 | 10.10.10.0 |            | ipoe |      | active | 00:03:44
 eth3.1000.130 |          | aa:bb:cc:00:50:00 | 10.10.10.2 |            | ipoe |      | active | 00:

From debug static address is assigned before vrf changes:
fe80::5208:ff:fe13:2 - autogenerated linklocal
fe80::5200:ff:fe55:222 - static linklocal

I think all Chaos stater after this message:

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

@n.fort
I ve added this code in to the scrip and the issue resolved.
if [ "$(id -g -n)" != 'vyattacfg' ] ; then
exec sg vyattacfg -c "/bin/vbash $(readlink -f $0) $@"
fi

Bug confirmed on 1.3.1-S1 and on 1.4-rolling-202203180317

Bugfix - 1.3 only - https://github.com/vyos/vyos-1x/pull/1265

PR for 1.3 - equuleus: https://github.com/vyos/vyos-1x/pull/1264

Backport for 1.3 equuleus: https://github.com/vyos/vyos-1x/pull/1263

Keep open until PR is merged:

there is another possible to achieve the desired result , it's using this radius-option: