All done so far, still need to do the show service commands and verify() to check the values before trying to write the config. But other than that it's working well.

local auth successfully tested and started to implement. nouth can be set as an option too. radius still needs to be tested, but is always has a higher priority than any other authentication module. Shaper will be the last item implemented before it is going to be released to the rolling images, after that community can test.

Authentication is still missing, but so far is a well working prototype. DHCP relay is going to be implemented next as well as radius before I have a look into local auth.

https://phabricator.vyos.net/T1452 already done last week.

installation succeeds.

installation succeeds.

fixed and successfully tested in VyOS 1.2.0-rolling+201906192322

verified and successfully tested on VyOS 1.2.0-rolling+201906192322

https://github.com/vyos/vyatta-cfg/commit/093b89ed5b8e4501cce3b4ce6f78795e17410988
https://github.com/vyos/vyatta-cfg-vpn/commit/51e07664ab03d001dfca457db06d82325d1e964f

fixed by @UnicronNL

Next rolling will have it fixed.

Can you try with the latest rolling please, I can't reproduce your issue.

vyos@vyos# ls -la /opt/vyatta/etc/config/archive/
total 44
drwxrwsr-x 2 root vyattacfg 4096 Jun 19 17:10 .
drwxrwsr-x 8 root vyattacfg 4096 Jun 19 17:08 ..
-rw-rw-r-- 1 root vyattacfg  160 Jun 19 17:10 commits
-rw-r--r-- 1 vyos vyattacfg 1575 Jun 19 17:10 config.boot
-rw-r--r-- 1 vyos vyattacfg  735 Jun 19 17:10 config.boot.0.gz
-rw-r--r-- 1 vyos vyattacfg  821 Jun 19 17:10 config.boot.1.gz
-rw-r--r-- 1 vyos vyattacfg  735 Jun 19 17:08 config.boot.2.gz
-rw-r--r-- 1 root vyattacfg  704 Jun 19 17:08 config.boot.3.gz
-rw-r--r-- 1 root vyattacfg  316 Jun 19 17:08 config.boot.4.gz
-rw-r--r-- 1 root vyattacfg  110 Jun 19 17:08 lr.conf
-rw-r--r-- 1 root vyattacfg   93 Jun 19 17:10 lr.state

on VyOS 1.2.0-rolling+201906191432

tested successfully with VyOS 1.2.0-rolling+201906191432

Should be available in the next rolling release.
https://github.com/vyos/vyos-1x/commit/85c9e0200a4619f0388b7fd7ba9a03f4be933ef5

fixed in https://github.com/vyos/vyos-netplug/tree/equuleus

@runar https://github.com/vyos/vyos-xe-guest-utilities/tree/equuleus should fix that issue. Let me know how it goes.

@commo That's an issue I can't solve. l2tp needs an uplink and needs to be able to reach the destination to exchange protocol information such as the tunnel id.

so I suppose something like: "set service snmp script1 [name path]" would do it?

https://github.com/vyos/vyos-1x/commit/0f354688d7bd63b63fb91faf17a38c77fb05f660

host_name.py has "os.system("systemctl restart rsyslog.service")" which causes the race condition at boot time.

Jun 17 16:57:53 vyos sudo[1417]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/libexec/vyos/conf_mode/host_name.py
Jun 17 16:57:53 vyos sudo[1417]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 17 16:57:53 vyos systemd[1]: Stopping System Logging Service...

• Subject: Unit rsyslog.service has begun shutting down
• Defined-By: systemd
• Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
• Unit rsyslog.service has begun shutting down.

Jun 17 16:57:53 vyos systemd[1]: Starting System Logging Service...

• Subject: Unit rsyslog.service has begun with start-up
• Defined-By: systemd
• Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
• Unit rsyslog.service has begun starting up.

Jun 17 16:57:53 vyos systemd[1]: rsyslog.service start request repeated too quickly, refusing to start.
Jun 17 16:57:53 vyos systemd[1]: Failed to start System Logging Service.

• Subject: Unit rsyslog.service has failed
• Defined-By: systemd
• Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
• Unit rsyslog.service has failed.
• The result is failed.

Jun 17 16:57:53 vyos systemd[1]: Unit syslog.socket entered failed state.
Jun 17 16:57:53 vyos systemd[1]: Unit rsyslog.service entered failed state.

start via systemd is required, otherwise if disabled systemd dependency craps out.

https://github.com/vyos/vyos-1x/commit/9b4447f039655b9e24187302b9c4d9bb2116aa99

https://vyos.readthedocs.io/en/latest/services/pppoe-server.html#dual-stack-provisioning-with-ipv6-pd-via-pppoe

@Maetthi Is that still an issue? You need an uplink first and the interface needs to be able to reach (route) the other side.

@alainlamar Can you please share some config data, so I can reproduce the issue.
thx

yes.
I tested once again with:
https://downloads.vyos.io/rolling/current/amd64/vyos-1.2.0-rolling%2B201905230337-amd64.iso

added ipv6-pd and ipv6 address to 'show pppoe-server sessions'

fixed and rebuilt.

Or if DNAT is a no go, use wireguard and tunnel it.

What about destination nat? (https://vyos.readthedocs.io/en/latest/nat.html#destination-nat) + binding it too loopback.

Thanks for testing.

Thanks for testing it, I'll close the bug ticket then.

Fix is in the next rolling or via http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb available.

sucessfully tested with:

set service pppoe-server access-concentrator 'testevyos'
set service pppoe-server authentication local-users username test password 'test'
set service pppoe-server authentication mode 'local'
set service pppoe-server client-ip-pool start '192.168.96.177'
set service pppoe-server client-ip-pool stop '192.168.96.180'
set service pppoe-server client-ipv6-pool delegate-prefix '2104:db8:8003::1/48,56'
set service pppoe-server client-ipv6-pool prefix '2104:db8:8002::1/48,64'
set service pppoe-server dns-servers server-1 '192.168.66.13'
set service pppoe-server dns-servers server-2 '192.168.183.162'
set service pppoe-server dnsv6-servers server-1 '2001:4860:4860::8888'
set service pppoe-server interface 'eth2'
set service pppoe-server local-ip '192.168.96.28'

@sentania Can you please test with the latest rolling, the issue should have been fixed now.

is that still an issue in the latest rolling image?

@sentania http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-quagga/vyatta-cfg-quagga_0.19.1+vyos2+current9_all.deb or next rolling release will have it patched. It was just not implemented in the backend, so the parameter was never read from the cli.

looks like even if not listed it can be set, but not applied via cli. also need to test if it works.

Looks like the 7.1-dev frr branch is eiter not up to date or the frr documentation isn't updated.

bug confirmed.