14 Dec
2017
14 Dec
'17
7:19 p.m.
On 14.12.2017 21:09, Ondrej Zajicek wrote:
Hi
You have doubled channel definitions, one with implicit arguments ('ipv4;'), and one with explicit arguments ('ipv4 { ... }'). That is likely a cause of issue #2. We definitely should add a check for that. Could you try config file with only one channel of each type per protocol?
It may be also issue #1, or perhaps it is problem with newer Linux kernels (i checked up to 4.13). But regardless of Linux API, we still should get at least periodic 'Scanning routing table' messages.
Issue #3 is most likely a bug in BGP, i will check that.
Hi, I can confirm that keeping only one channel definition fixes both #1 and #2. A check warning/rejecting this would be nice :) Thanks, Radu