The problem is not with the restart.
I think the problem with the template dhclient-ipv6.tmpl
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 18 2020
Enabling sticky connections had no effect in my testing. The only temporary solution was T2747. Unfortunately, this solution no longer works once the IP address changes on a DHCP-assigned interface.
@bbabich any udpates?
32-bit Xen PV support was dropped recently from upstream Linux kernel 5.9.
64-bit Xen PV is still supported in upstream Linux kernel.
Aug 17 2020
I believe we should stick to the same format as ntp.conf.
Another idea would be to introduce a new option „pool“ for any specified server to use the pool keyword over server. But I see no downside of always using pool, do you?
That would do a 2 for 1 solution.
In addition to the workaround provided in the task T2747, the following configuration could also be added to the existing configuration:
Tunnel Interfaces also do not generate/configure a Link-Local IPv6. It looks like Tunnel interfaces do not have any MAC Address associated to it.
@ronie can you build an example with frr?
Merged
This is not solved in 1.2.6-epa1. Will this be solved in 1.2.6?
It seems that making the tunnel connection a Stub Area would reach the same design goal without relying on a recursive static route, but it also seems that this feature is not supported in OSPFv3 by now. I´ve opened the following feature requests: https://phabricator.vyos.net/T2804 & https://phabricator.vyos.net/T2803 .
@thomas-mangin in further tests, I've seen wide variability in timing tests, independent of caching, with the original quote being the high-end. That will need to be investigated, but I think performance should not be considered a road-block for now.
I´ve tyred to reproduce this scenario with VyOS 1.3-rolling-202007300117.
The static-default-route is correctly installed in the routing table after rebooting the router.
Sorry, I don't understand what you mean. Can you tell me more about it? What is using net-snmp to submit feature requests?
Please file feature request with net-snmp.
The list of oids currently supported by vyos is as follows:
Aug 16 2020
What if we render pool instead of server to ntp.conf for all servers?
Please retest with the latest rolling as bond/ethernet went through a major refactoring.
We use net-snmp as SNMP server and can only provide the OIDs it supports. Please be more verbose what is missing and what is expected.
Could you share an example how to ise that? I then can test it in my code.
Regarding (1) which is about changing the default. No issues, I was trying to break any code until someone had more time than me to test it, as the devil is always in the details.
From John on github:
[ 174.257399] wireguard: WireGuard 1.0.20200429 loaded. See www.wireguard.com for information. [ 174.257402] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. [ 176.893555] ipoe: loading out-of-tree module taints kernel. [ 176.894462] IPoE session driver v1.11 [ 179.534526] vlan-mon driver v1.11 [ 207.268408] i40evf: Intel(R) 40-10 Gigabit Virtual Function Network Driver - version 3.2.2-k [ 207.268411] Copyright (c) 2013 - 2015 Intel Corporation. [ 210.281303] Intel(R) 10GbE PCI Express Linux Network Driver - version 5.8.1 [ 210.281305] Copyright(c) 1999 - 2020 Intel Corporation. [ 210.281629] init of debugfs failed [ 213.047970] ixgbevf: Intel(R) 10GbE PCI Express Virtual Function Driver - version 4.8.1 [ 213.047972] ixgbevf: Copyright(c) 1999 - 2020 Intel Corporation. [ 216.250809] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.6 [ 216.250812] Copyright(c) 2007 - 2020 Intel Corporation. cpo@LR2.wue3:~$ uname -a Linux LR2.wue3 4.19.139-amd64-vyos #1 SMP Sat Aug 15 20:46:38 UTC 2020 x86_64 GNU/Linux cpo@LR2.wue3:~$ show ver Version: VyOS 1.2.6-epa1-4.19.139 Release Train: crux
The document has been updated and moved to a more suitable location
Aug 15 2020
I would like to test as well. I have successfully setup link local peering with 2 vyos routers using the new "interface v6only" option. However, I am unable to establish a link local session when peering with a different vendor.
An initial version has been merged with initial support for some Crystalfontz LCDs. This is in alpha state.