VyOS 1.3 based on Debian 9 Stretch
Details
Details
Description
Yesterday
Yesterday
hagbard added a comment to T611: Static route syntax should reflect `ip` command routing capabilities, if possible..
personally I like the below most. it will require quite an amount of work for migration.
c-po added a comment to T1533: Rolling builds broken!.
See T1331
hagbard moved T1450: crux: ping * flood is not working from Backlog to Finished on the VyOS 1.3 Equuleus board.
hagbard moved T1450: crux: ping * flood is not working from Need Triage to Backlog on the VyOS 1.3 Equuleus board.
hagbard moved T1450: crux: ping * flood is not working from Needs Triage to Backlog on the VyOS 1.2 Crux (VyOS 1.2.3) board.
hagbard changed the status of T1450: crux: ping * flood is not working from Open to Backport candidate.
has been fixed by reverting to 4.1 since pdns stopped supporting debian jessie.
hagbard changed the status of T853: accel-ppp: SSTP implementation, a subtask of T742: Implement accel-ppp in VyOS, from Open to In progress.
rherold added a comment to T1020: OSPF Stops distributing default route after a while.
Run into the same with 1.2.2
Mon, Jul 22
Mon, Jul 22
krassle added a comment to T1435: Make ip-address [OPTIONAL] (in dhcp-server -> static-mapping) to cope with "unfriendly" client-hostnames of IoT-Devices.
I've tested the fix on latest rolling and so far it works as expected.
Thanks for the quick patch!
kronenpj added a comment to T1421: OpenVPN client push-route stopped working, needs added quotes to fix.
The same thing applies to the global configuration of push options.
E.g. These:
set interfaces openvpn vtun0 server push-route '172.16.41.0/24'
set interfaces openvpn vtun0 server push-route '172.16.42.0/24'
hagbard closed T1459: [equuleus]: buster: vyos-netplug receives events but doesn't trigger scripts as Wontfix.
We may have to migrate to networkd to have that functionality, since netplug seems to cause issues with interfaces which are up and running.
hagbard moved T1299: Allow SNMPd to be extended with custom scripts from Need Triage to Finished on the VyOS 1.3 Equuleus board.
hagbard added a comment to T1489: Add vlan_mon usage at Accel.
@dienac any results to share?
Sun, Jul 21
Sun, Jul 21
c-po added a comment to T823: Rewrite DHCP op mode in the new style.
VyOS 1.2.2 only contains DHCP op mode definitions from the following packages:
c-po moved T1333: pdns_recursor does not perform recursive lookups on domain specific forwarders from In Progress to Finished on the VyOS 1.3 Equuleus board.
c-po added a comment to T1333: pdns_recursor does not perform recursive lookups on domain specific forwarders.
fix backported to crux
Sat, Jul 20
Sat, Jul 20
syncer moved T1131: open-vm-tools causing 100% CPU load from In Progress to Finished on the VyOS 1.2 Crux (VyOS 1.2.2) board.
syncer edited projects for T1131: open-vm-tools causing 100% CPU load, added: VyOS 1.2 Crux (VyOS 1.2.2); removed VyOS 1.2 Crux (VyOS 1.2.3).
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.
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.
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.
@zsdc Hostname is still showing as 'debian' in 1.2.0-rolling+201907191807
Fri, Jul 19
Fri, Jul 19
hagbard changed the status of T1459: [equuleus]: buster: vyos-netplug receives events but doesn't trigger scripts, a subtask of T1412: equuleus: buster: vyos-netplug is not installable and breaks live-build, from In progress to On hold.
hagbard changed the status of T1459: [equuleus]: buster: vyos-netplug receives events but doesn't trigger scripts from In progress to On hold.
https://github.com/vyos/vyos-netplug/commit/81fd74bfbfa6daed506693ecc20deff09042bc71 broke it, I have to find out why he commited it.
hagbard changed the status of T1459: [equuleus]: buster: vyos-netplug receives events but doesn't trigger scripts, a subtask of T1412: equuleus: buster: vyos-netplug is not installable and breaks live-build, from Open to In progress.
hagbard changed the status of T1459: [equuleus]: buster: vyos-netplug receives events but doesn't trigger scripts from Open to In progress.
jjakob added a comment to T1331: DNS stops working.
I'll set up monitoring, sure.
c-po added a comment to T1331: DNS stops working.
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.
jjakob added a comment to T1435: Make ip-address [OPTIONAL] (in dhcp-server -> static-mapping) to cope with "unfriendly" client-hostnames of IoT-Devices.
Can be set to finished on 1.3 Equuleus
jjakob added a comment to T1331: DNS stops working.
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?
c-po added a comment to T1331: DNS stops working.
Unfortunately PowerDNS no longer supports the 4.2 series on Debian oldoldstable (Jessie) - reverting this on current to fix the build.
Thu, Jul 18
Thu, Jul 18
fixed via https://phabricator.vyos.net/T1065
hagbard moved T1485: Enable 'AdvIntervalOpt' option in for radvd.conf from Need Triage to Backlog on the VyOS 1.2 Crux board.
hagbard changed the status of T1485: Enable 'AdvIntervalOpt' option in for radvd.conf from Open to Backport candidate.
hagbard renamed T1485: Enable 'AdvIntervalOpt' option in for radvd.conf from Does not send AdvInterval in the router advertisment to Enable 'AdvIntervalOpt' option in for radvd.conf.
runar added a comment to T1533: Rolling builds broken!.
This also affect manually built iso's that also fails because of pdns-recursor
runar added a comment to T1533: Rolling builds broken!.
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.