@olofl which version?

PR https://github.com/vyos/vyos-1x/pull/801
And related
PR https://github.com/vyos/vyos-build/pull/156
PR https://github.com/vyos/vyatta-cfg/pull/35

This issue seems to have gone away or I haven't noticed it recently.

I cannot reproduce this on VyOS 1.4-rolling-202104062128. Instead, on that version, ipv6 address autoconf commits, but the interface never picks up a v6 address.

Works! Thanks!

Add PR with improvements to documentation https://github.com/vyos/vyos-documentation/pull/503

Thanks. I think the main issue is missing required modules in the generated pppoe server config file

 sudo cat /run/accel-pppd/pppoe.conf 
### generated by accel_pppoe.py ###
[modules]
log_syslog
pppoe
shaper
chap-secrets
ippool
auth_pap
auth_chap_md5
auth_mschap_v1
auth_mschap_v2

Required

ipv6pool
ipv6_nd
ipv6_dhcp

These option enables by the foloowing CLI command::

set service pppoe-server ppp-options ipv6 allow

Even when setting above command I have no IPv6 address assigned.

It looks like the same nature of this issue https://phabricator.vyos.net/T3393
@c-po , could you try to test fast solution

configure
set system sysctl custom net.ipv6.conf.default.addr_gen_mode value 0
commit

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

Looks like that is actually working.

Oops, I did not see that. Thanks.

I modified bgp.frr.tmpl, but systemctl restart vyos-configd did not seem to do anything. Rebooting the router produces the correct config:

@linuxludo thanks for the heads-up - should be fixed in the next bugfix version of 5.10 then which I regularely update VyOS to. See T3318

We probably should move the following statement https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L362-L364

Just for your information.
The patch was added to kernel 5.4, 5.10 and 5.11.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/

If you add neighbor/commit and after that commit adding "set protocols bgp parameters default no-ipv4-unicast" it can not be accepted. Because neighbor was added before this command.
Re-create neighbor and commit. And check again.

When on VyOS 1.4 please use the show bgp ipv6 command as exposed by FRR. The show ip bgp command is only kept as not all options from show ip bgp are exposed in FRR under the show bgp ipv4 tree.

You can't/don't need to set local-as for neighbor [ if neighbor local as == your global asn ]
Can you send a code error?

I don't understand how DHCP relays work, esp in a pfsense environment. Not worth looking at this.

Fixed. 1.2.7, VyOS 1.3.0-rc3, VyOS 1.4-rolling-202104041918

I wonder if this used to work in the past?

@maznu @Merijn Can you test the latest rolling 1.4 release?
It should be fixed.
You can kill ripd/ripng/ospfd/bgpd/isisd daemons or allow it for watchfrr.

Turns out this is not a VyOS limitation but is a Linux Kernel/iproute2 limitation.