I have added the Documentation:

Its only in the current branch for rolling, not in 1.2.1 crux - but can be backported

Problems with DHCP server status viewing can be fixed with the next patch for show_dhcp.py :

--- orig/show_dhcp.py	2019-05-30 22:45:01.625708032 +0300
+++ T1416/show_dhcp.py	2019-05-30 22:40:33.302777881 +0300
@@ -55,15 +55,28 @@
     return data

In T989#26867, @hagbard wrote:

It seems that local auth is impossible, all I found is to configure it against radius, user should check abills as billing system. (https://sourceforge.net/projects/abills/)
If anyone knows how to use local authentication like chap or pap or anything, let me know please. Otherwise IPoE seems a real nice option, not as robust as ppp, but quite nice.

IPoE module test connection:
Nov 26 18:35:19 accel accel-ipoe: ipoe0:eth2: recv [DHCPv4 Request xid=23249d54 chaddr=08:00:27:8d:38:56 <Message-Type Request> <Server-ID 10.1.1.250> <Request-IP 10.1.1.254> <Host-Name vyos> <Request-List Subnet,Broadcast,Router,DNS,Domain-Name,MTU>]
Nov 26 18:35:19 accel accel-ipoe: ipoe0:eth2: send [DHCPv4 Ack xid=23249d54 yiaddr=10.1.1.254 chaddr=08:00:27:8d:38:56 <Message-Type Ack> <Server-ID 10.1.1.250> <Lease-Time 300> <T1 150> <Router 10.1.1.250> <Subnet 255.255.255.255>]
Nov 26 18:35:19 accel accel-ipoe: ipoe0:eth2: ipoe: session started
Nov 26 18:35:22 accel ntpd[2013]: Listen normally on 9 ipoe0 10.1.1.250 UDP 123
Nov 26 18:35:22 accel ntpd[2013]: Listen normally on 10 ipoe0 fe80::a00:27ff:fe80:636d UDP 123
Nov 26 18:35:22 accel ntpd[2013]: peers refreshed

Hi c-po, There is an igb driver update from Intel. https://sourceforge.net/projects/e1000/files/igb%20stable/5.3.5.22s/

As far as I can see it is included in 1.2.1 so we can close this or?
If yes I will submit a config example for ospf ip unnumbered that uses it

Adding some debug code to /opt/vyatta/share/vyatta-cfg/templates/protocols/ospf/passive-interface/node.def (set -x for delete) shows:

If there is a refactoring ongoing please also consider the following change to flatten the PPPoE IPv6 configuration by making use of a present nested node:

I agree with @aibanez
In addition, sometimes it works (but only a very few) while almost always it crashes at startup and interfaces are messed.
Do you guys have any clue/suggestion or any other further test that can be done?

Try: https://github.com/vyos/vyatta-cfg-quagga/pull/27/commits/8c741da0691cb392a86f249b61c3686a034f908a

https://github.com/vyos/vyatta-cfg-quagga/pull/27 < -- seems to look better

Not much response, but multiple users I recommend VyOS to are having this issue. So i would say it's a bug and not intended behaviour.

Hi guys,

Added pull requests:
https://github.com/vyos/vyos-1x/pull/68
https://github.com/vyos/vyatta-cfg/pull/17

See my pull request: https://github.com/vyos/vyatta-cfg-quagga/pull/26

from Slack

can it be that the fix for T1243 is broken? I can understand that local-as can't be the same like remote-as if router-as diff from local-as but the patch forbit to set remote-as to the same like router-as that will break ibgp

We can't use the current iproute2 package from upstream Debian as commit f900a21611c03e6d83104f2a862cd4c5f160d35f ("utils.h: provide fallback CLOCK_TAI definition") is only available in iproute2 after the release of v4.19. The reason is CLOCK_TAI isn't exposed by glibc < 2.21 and we use glibc 2.19 in VyOS (comes with Debian Jessie)

Please refer to the equuleus Git branch. There is already a Docker container and some smal fixes to the build system.

Remaining question is: Why do we need our own iproute fork and can't use the upstream packages commit https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=f900a21611c03e6d83104f2a862cd4c5f160d35f for VyOS? Thats the commit we build right now in https://github.com/vyos/vyatta-iproute

Seem like this issue still in vyos 1.2. Would please check it and fix it ?

I'm experiencing this exact issue as well. brand new install from rolling release - (vyos-1.2.0-rolling 2B201905140337-amd64.iso).

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

Is there any command where I can check what attributes the radius server is sending to pppoe-server vyos? I tried with many attributes of our radius system but without success.

https://github.com/vyos/vyatta-iproute/commit/52ef571dd8a6d9067a1339c4a389abe79f272dcf

worked perfectly. I would also like to test bandwidth control from the radius server. What attribute should I use? Is it possible to make use of the same cisco-avpair attribute for example?

I commented out lines 389 and 390 in https://github.com/vyos/vyatta-cfg-system/blob/67b10e6ff5f33d73c128508f00198cc3c04c13fc/scripts/vyatta-interfaces.pl#L377.

@joshua we do not use the ssh and the ssh-import-id as the ssh keys need to be set by vyos config.