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

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

Problem still exists with Kernel 4.14.30

Also VyOS 1.2.x does not have something like set interface ethernet eth1 ipv6 accept_ra [never=0|only-if-no-forwarding=1|always=2]. I only see the possibility to configure the advertise side.

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.

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

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.

@jhendryUK or @hsahmed can you share a full configuration for reproduction please.

done by @UnicronNL ... ISO built.

@syncer vyos-999.201803161451-amd64.iso is the first version running on Linux 4.14.26!

Thanks for the feedback!

@myura please test the latest rolling release if your i219 chipset is now detected. Kernel has been upgraded to 4.14.26.

Will be implemented by T583.

The Kernel commit/patch fc58d4a33953776 is used by https://github.com/vyos/vyatta-keepalived/commit/8bd97620 and VyOS 1.2 is using vyos-keepalived which no longer needs this patch.

@syncer please close and reopen if req.

@syncer please close and reopen if req.

Looking through all changes I come up with the following:

Looking through Jenkins CI and the sources itself (T565) ... we should drop them.

Looking into this I see 47 non merge commits which are not in the mainline Kernel:

@syncer could this be a duplicate of T523?

You should find a HTML rendering of every manpage via Google.

Implemented and CI build triggered.

You are right, installing a fresh copy of VyOS 1.1.7 only has:

root@vyos:~# ls -al /usr/lib/openvpn
total 23
drwxr-xr-x  2 root root    70 Feb 17  2016 .
drwxr-xr-x 55 root root  9548 Feb 17  2016 ..
-rw-r--r--  1 root root 11520 Mar  9  2015 openvpn-auth-pam.so
-rw-r--r--  1 root root 10792 Mar  9  2015 openvpn-down-root.so

@dmbaturin I totally agree

The drivers shipped inside the Linux Kernel do not match the Intel ixgbe driver 100%. There are small feature discrepancys.

That would be great!
In parallel the XML file for the config nodes can be created. I‘d keep the nodes as they are right now to kot break running setups.

See T546 ("service dns forwarding doman localdomain server" entry doesn't allow IPv6 address). This one is resolved.

Functionality should be implemented via the new style vyos-1x interface.

Checking the manpage @ http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html gives us:

@dsummers build triggered, please verify.

the file used for the package "version" is the changelog file.

I'll look into this

What's the reported error when you increaste the MTU?

@alainlamar that sounds familiar, have you verified that you use the proper priority: tags inside your node.def files?

Merged and Build triggered.

@alainlamar clearfog is the ARM build for https://www.solid-run.com/marvell-armada-family/clearfog/

@syncer I could try to test it with a fake configuration to check if it works in theory.

... done

This is a new bug, please file it and I‘ll try to look into it. Thanks.

Ah ok, you are in edit mode, this is different to me.

Another idea would be to wrap the system options in the python configuration script with e.g. a dictionary.