In T4348#121421, @n.fort wrote:

I have normal access!

@fortinj1354 you can do changes in xml, build .deb pkg and install it on the instance
https://docs.vyos.io/en/equuleus/contributing/build-vyos.html#id4

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

I missed option network vlan:

set service ipoe-server interface eth2 network 'vlan'

configs looks good:

[ipoe]
verbose=1
interface=re:eth2\.\d+,shared=0,mode=L2,ifcfg=1,range=192.168.0.0/24,start=dhcpv4,ipv6=1
username=ifname
password=csid
proxy-arp=1

I would like to see this too, with Ethernet interfaces.

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

The root cause it generates incorrect pool name (conf mode) with a dash instead of an underscore

vyos@vyos:~$ show conf com | match dhcp
set service dhcp-server shared-network-name NET_01 authoritative
set service dhcp-server shared-network-name NET_01 name-server '1.1.1.1'
set service dhcp-server shared-network-name NET_01 subnet 192.0.2.0/24 range R1 start '192.0.2.21'
set service dhcp-server shared-network-name NET_01 subnet 192.0.2.0/24 range R1 stop '192.0.2.254'
vyos@vyos:~$

dhcp.conf

...
    on commit {
        set shared-networkname = "NET-01";
    }

I have normal access!

Not sure if this works but there is an upload button in the toolbar:

@n.fort the config i would like to upload to this ticket has 43727 lines.. Its a text file of 1.3 Mbps. Its it possible to attach the file instead of paste it on the comments?

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

Trying to configure a wireguard peer with a dns name as remote endpoint. I understand this is not supported, but I see many references to creating a post-boot script to do this. Any working examples? Thank you

Hi, I'm sorry for the confusion but the configuration I uploaded is not from a production machine. It's just an example of a small configuration of a pre-production vyos that I was having trouble upgrading.
Tomorrow if I will upload one of the ones that take 25-30 minutes to boot on modern CPUs (xeon gold).

Changes and fixes to smoketest at link; in testing before PR:
https://github.com/vyos/vyos-1x/compare/current...jestabro:api-smoketest

With shared config, I'm not getting high times while loading config (at least not that high as exposed in this task)

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

@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