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.

Unfortunately I can't reproduce this. @Line2 could you please try with the latest version again?

Proper firewalling will be better...

Ok, as this is a rather minimal change I just added it and triggered the CI build. Will be in the next rolling release...

It's an ACK from my side and can be easily done. @syncer ACK/NACK?

@syncer if it's inside the stock kernel, we should enable it ....

VyOS 1.2.x (all nightly builds) is based on Debian GNU/Linux 8 (jessie)
VyOS 1.3.x is planned to be based onDebian GNU/Linux 9 (stretch)

Please keep in mind:

• ioctl() like interfaces are usually proprietary or encapsulated by the socket API (keeping the fucus on a network device only here)
• systl is used for tuning kernel internal parameters that are usually compiled statically, most of the time it wraps the /proc pseudo filesystem, e.g. networking stuff
• /etc/modprobe.d is used by modprobe for kernel load parameters when the module is inserted. Sometimes they can be manipulated by sysctl, sometimes not. Always depends if the module has been loaded before calling sysctl or where in the driver this setting is referenced.

@xrpixer thank you very much for the clarification. Hopefully other users can benefit from it, too.

@mickvav sure it will work without T123 and a test is very good.

@xrpixer thanks for submitting. Any change you could double check it on a recent nightly build of VyOs 1.2.x? => https://downloads.vyos.io/?dir=rolling/current/amd64

IRC meetings can be held every evening starting 19:00 UTC+1

Related to T123

Already triggered CI builds su it will be in tonights version.

Nope, this is the output after binding it to eth0 only. It always binds to the loopback interface!

After adding the bind-interfacesparameter to the configuration, movng the configuration file from /etc/dnsmasq.conf to /etc/dnsmasq.d/vyos.conf and switching to systemd, this is the result:

Yes, can do

@alainlamar nice work digging!

@syncer tools added to base image. This would be perfect for a vyos-1x op mode command. Unfortunately I was not able to build a working template with the relax-ng templates (lack of xml/relax-ng) knowledge. @dmbaturin maybe you can help?

@squeeby which sflow collector do you use? Is there one you can recommend?

Rewrote the scripts using vyos-1x and Python. This is now functioning on my routers.

Working again

Merged into vyatta-netflow package and will be included in tonights build.

Ok, next try: https://www.mybll.net/vyatta-netflow_ver02_all.deb

Could you alter the file manually to get a working state and pass it to me by e.g. pasting it here or a https://pastebin.com/ link? Then I could regenerate a package for testing. This would help me a lot as I do not have any flow collector.

You can revert by switching back to the official VyOS package.

Strange. I only changed /opt/vyatta/sbin/vyatta-netflow.pl to your recommendation.

@squeeby do you mind verifying the following package containing your fix:

@alainlamar your effort and support is tremendous and very much appreciated. I'm also super new to VyOS "development".

Problem is that two new packages (mdns-repeater and udp-bcast-relay) are build on the CI server, but somehow do not show up in the package repository at http://dev.packages.vyos.net/vyos/pool/main/ which is used during build.

@alainlamar thanks for sharing your thoughts. Regarding your MR, you add a node sshd_option where someone could add ANY option to sshd. I'm not a big fan of those "you can do everything nodes".

I think T141 also wants to achieve something similar but with proper AAA. Unfortunately my network has not reached the critical mass to go for a TAC server. But we should keep this in mind!

Dissecting your patch .. I come up with those commits: https://github.com/c-po/vyatta-cfg-system/commits/t507-sshd

@alainlamar thanks for the contribution.

T419 also needs this capability.

Okay, the proof of concept worked on the console

IMHO the whole serial part should be re-written.