Please retest wirh latest rolling release
Thu, Dec 13
Wed, Dec 12
- CONFIG_MMC_BLOCK already enabled
- CONFIG_MMC_SDHCI_ACPI has been enabled
Tue, Dec 11
Mon, Dec 10
My changes will make it into rc12 as earliest, sorry
Disabling the complete Framebuffer subsystem works with my UEFI Testboard, too. I will drop it entirely
Sun, Dec 9
Not directly but it as added here: https://github.com/librenms/librenms/pull/351
Sat, Dec 8
I see OS version in libreNMS.
Fri, Dec 7
Netplugd seems to be the thing we want
In vyatta-cfg-firewall please do git checkout current prior to building it, as the submodule pointer is definately not up2date.
According to CI service build works as expected. Can you please retry?
Thu, Dec 6
Tue, Dec 4
Will set interface vxlan vxlan0 destination-port 12345 be appropriate?
Mon, Dec 3
Setting destination port per VXLAN interface sound much more reasonable
Sun, Dec 2
What about Dockerfile in vyos-build?
Sat, Dec 1
I will provide a VyOS testing ISO somewhen next week, would be much appreciated if you can test.
Or drop by our slack channel for help
First you need to specify a new version of your subtree,
@dsteinkopf I think almos every command is good when there is a discussion ongoing and we can agree on somehing. VyOS has so called migration scripts which are executed once we do CLI changes and thus migrate old configuration nodes to new ones. We already make use of this feature alot and it is transparent to the user.
I really like the idea and thank you for the contribution.
@SteveP do you have time booting a Debian Buster (testing) ISO on your device and see if your NICs do appear?
Thu, Nov 29
@dmbaturin maybe can, need to verify this behavior together with the EFI stuff when I'm back in germany. If =n works for all szenarios I'm happy with it.
Wed, Nov 28
Can you please double-check with latest rolling release: vyos-1.2.0-rolling+201811281529-amd64.iso?
System bootup time is something we should not care, as a router is not rebootet that often. Infact the startup time depends on the amount of configured services or firewall rules. We recently increased the timeout for starting of VyOS to also make it work on slower Intel Atom D525 platforms where a huge firewall config was loaded.
What do you propose as CLI syntax?
Tue, Nov 27
I never liked verbatim passed options, this will be a perfect candidate for a first controbution to VyOS as it will be rather easy! You want to give it a try?
There hve recently been changes in regards to EFI. Please check the Dockerfile for all required packages or switch to Completely!
Mon, Nov 26
Have you tried specifying /config/config.boot instead?
I always thought 64 cpus should be sufficient for VyOS :)
Another idea (if having no name-server entries is disliked) would be
Sun, Nov 25
Eoot hints could be speciefied, if none is specified, buildin one is used.
Could be done by Help text and documentation
Or, if no name-server is set, use the root servers
Even better! Thanks for the hint!
Sat, Nov 24
BBR was enabled in the latest commit to vyos-kernel
@syncer seems this is the only available SSTP Linux implementation
man strace(1) indicates that it opens several system files until it gets a match for any known distro.
VyOS ships a serial port interface in the default configuration upon installation.
Merged from current into crux branch.
May it be you are running on a virtualized environment and have not added a serial port to your VM?
Sat, Nov 17
Thu, Nov 15
Your commit enables memory plugin when disable is configured?
@LiquidLight there is a Dockerfile, too to build VyOS
Issue file con be overwritten. lsb_release -d would be a better way, as it gives you Description: Debian GNU/Linux 8.11 (jessie)
Nov 12 2018
Nov 11 2018
Looks like this was always a bug. In the old Perl implementation the if clause was the same:
@dmbaturin This is what I did:
Nov 10 2018
This looks like an ultimate hackaround. Maybe we should check if we can change the C implementation
Nov 9 2018
Actually I only wanted to use it got configuration backup.
Please note: Kernel Intel driver version is kot always related to Intel out of tree modules. Denverton C3000 NICs work fine with 4.18 atleast so as we run 4.19 we‘re off the hook.