- User Since
- Aug 3 2017, 1:55 PM (33 w, 2 d)
Fri, Mar 23
@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.
Thu, Mar 22
I found some interesting docs:
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?
Wed, Mar 21
Integrated iproute2 TAG 4.14.1 into https://github.com/vyos/vyatta-iproute.
Sun, Mar 18
Fri, Mar 16
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.
Thu, Mar 15
Will be implemented by T583.
Tue, Mar 13
Mon, Mar 12
The Kernel commit/patch fc58d4a33953776 is used by https://github.com/vyos/vyatta-keepalived/commit/8bd97620
@syncer please close and reopen if req.
@syncer please close and reopen if req.
Sat, Mar 10
Thu, Mar 8
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:
Wed, Mar 7
Sun, Mar 4
You should find a HTML rendering of every manpage via Google.
Sat, Mar 3
Implemented and CI build triggered.
Thu, Mar 1
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
Wed, Feb 28
@dmbaturin I totally agree
Tue, Feb 27
The drivers shipped inside the Linux Kernel do not match the Intel ixgbe driver 100%. There are small feature discrepancys.
Sun, Feb 25
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.
Sat, Feb 24
Checking the manpage @ http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html gives us:
Feb 21 2018
@dsummers build triggered, please verify.
cpo@CR2# set service dns forwarding domain foo.com server Possible completions: <x.x.x.x> Domain Name Server (DNS) address <h:h:h:h:h:h:h:h> Domain Name Server (DNS) address
Feb 16 2018
I'll look into this
Feb 12 2018
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?
Feb 11 2018
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.
This is a new bug, please file it and I‘ll try to look into it. Thanks.
Feb 8 2018
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...
Feb 6 2018
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)
Feb 3 2018
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.
Feb 1 2018
@xrpixer thank you very much for the clarification. Hopefully other users can benefit from it, too.