VyOS 1.3 based on Debian 9 Stretch
personally I like the below most. it will require quite an amount of work for migration.
has been fixed by reverting to 4.1 since pdns stopped supporting debian jessie.
Run into the same with 1.2.2
Mon, Jul 22
I've tested the fix on latest rolling and so far it works as expected.
Thanks for the quick patch!
The same thing applies to the global configuration of push options.
set interfaces openvpn vtun0 server push-route '172.16.41.0/24'
set interfaces openvpn vtun0 server push-route '172.16.42.0/24'
We may have to migrate to networkd to have that functionality, since netplug seems to cause issues with interfaces which are up and running.
@dienac any results to share?
Sun, Jul 21
VyOS 1.2.2 only contains DHCP op mode definitions from the following packages:
fix backported to crux
Sat, Jul 20
I wonder if the bgp daemon is being started before the hostname is changed by the config script. Seems possible since we added a lock so it executes later.
@zsdc Hostname is still showing as 'debian' in 1.2.0-rolling+201907191807
Fri, Jul 19
https://github.com/vyos/vyos-netplug/commit/81fd74bfbfa6daed506693ecc20deff09042bc71 broke it, I have to find out why he commited it.
I'll set up monitoring, sure.
I have ran VyOS 1.2.1 and now 1.2.2 for quiet some time and can no longer see this issue. 1.2.1 and 1.2.2 are both based on PowerDNS recursor 4.1 series.
Can be set to finished on 1.3 Equuleus
That's unfortunate. I've had to restart dns every few days at some clients due to an outage because of this bug. It would be not nice if it were to regress. Is there a way to build on buster with newer packages?
Unfortunately PowerDNS no longer supports the 4.2 series on Debian oldoldstable (Jessie) - reverting this on current to fix the build.
Thu, Jul 18
fixed via https://phabricator.vyos.net/T1065
This also affect manually built iso's that also fails because of pdns-recursor
Hi! The rolling release is broken because pdns-recursor has stopped to provide packages for jessie and the current index points to a file that is currently not available. We are working on fixing this and it migth be that we need to start building it ourself instead.
The problem, which leads to the malformed hostname in Hostname Capability was fixed in T1531. I am marking this as "Resolved", because the problem with DNS servers was resolved also, according to feedback.