Building latest xl2tpd from source (which will become 1.3.12) and integrating it into VyOS will fail with:
Apr 17 21:03:02 LR1 pppd[3322]: In file /etc/ppp/options.xl2tpd: unrecognized option 'crtscts'

@suto.norbert I don't recall ever seeing any error about duplex or speed when setting vyos pre 1.2.0 versions.
Hope that helps.

@c-po actually pdns can load /etc/hosts so no need to replace
just different use cases, static hosts mapping works for really basic scenarios
all rest should be done via zones

dnsmasq is now replaced in favour of pdns recursor.

PowerDNS recursor also supports multiple IPV4 and IPv6 nameservers when using a DNS zone forwarding

This will be merged together with T560. Branch is located here: https://github.com/c-po/vyos-1x/tree/powerdns-recursor

As set service dns forwarding query-all-server was introduced in VyOS 1.2.x some time ago I decided to drop it as it was not yet released. I hope this is ok.

Command service dns forwarding query-all-servers was not available in VyOS 1.1.9 and added in 1.2.x. As this command is no longer available when switching to pdns-recursor (T560) it is not ported and dropped again.

I found some interesting infos.

@logan.attwood show log

No luck. Where do I grab the xl2tpd logs @c-po

This is a first configuration file generated from the vyos-1x python scripts:

An ISO for testing can be found here: https://www.mybll.net/vyos-1.2.0-rolling-201804131440-xl2tpd-fix-amd64.iso

This is the patch for xl2tpd 1.3.6 (https://github.com/xelerance/xl2tpd/tree/debian-jessie) found in Debian Jessie:

From https://github.com/xelerance/xl2tpd/issues/147 and https://github.com/xelerance/xl2tpd/pull/148

@dsummers You remember, that you set the virtual card IP at first time in vyos, you got a error on duplex and speed that "the system can not set it" or something similar?

I am having a few strange problems with 2-3 production pre vyos-1.2.0 systems as well.

I try to reproduce it, but seems to i only get this, if that i set the network card at first time. Now it is my "production ready" system, so i dont want to misconfigure it.

@suto.norbert can you also show error which you get on commit and procedure how to reproduce
Thanks!

Config options: https://doc.powerdns.com/3/recursor/settings/

Sources for debian
http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_SRC-debian-4.3-1.0.1.0.tgz
from here
http://www.mellanox.com/page/products_dyn?product_family=26

@c-po it will take time anyway, we will see on the go

Intel part already is ok
we missing mellanox and netronome

Initial observation was wrong. Field headers do not seem to match to values.

Decided to take an actual look at the script. Seems to be a change in pmacct's output, specifically new fields between TOS ($tos) and PACKETS ($pkts).

Is there any progress on this merge?

@syncer This can be closed as it was a duplicate of T92.

@syncer not yet, but my first guess is that this message is missleading. I‘ll look into it after my vacation.

@c-po any idea which device is missing

Problem still exists with Kernel 4.14.30

Problem still exists when adding to /etc/xl2tpd/xl2tpd.conf:

[global]
force userspace = yes
ipsec saref = no

@higebu thanks for sharing the link. Looks like they also have some CLI examples. Does this apply to FRR, too? I remember the idea was to move to FRR for routing.

User space implementation in Zebra 2.0: https://github.com/coreswitch/zebra/blob/master/docs/srv6.md

Yes, it's a first step. I think the next step will be wrapper set/show commands for iproute2.

I found some interesting docs:

• https://inl.info.ucl.ac.be/system/files/ANRW-SR.pdf
• https://inl.info.ucl.ac.be/system/files/paper_10.pdf
• https://indico.uknof.org.uk/event/40/contribution/1/material/slides/0.pptx

I think it's first step.
Also it supported in iproute2 that we just updated

What is the benefit of simply enabling it in the Kernel configuration? I guess there is userspace support required, too? Or does it work out of the box?

Integrated iproute2 TAG 4.14.1 into https://github.com/vyos/vyatta-iproute.

Running Docker on current vyos. https://gist.github.com/higebu/f35fdd27d085b618a872a8b46c625e2e

@higebu not much there
not really easy to use vyos in containers
however, we can deliver via containers - apps that can be integrated with cli

• gui
• dns/dhcp (for IPAM)
• proxy servers
• monitoring proxies and agent relays