Another one:
Since killing bird is now safe-ish, I added one more bird3 to the party.
Then I tried killing the first bird again.
This caused the new bird3 to get stuck with BGP into Flush:
BGP_IPv4 BGP---flush 2024-12-19 16:35:08 Flush
Socket: Connection reset by peer
BG
ll add
one and check if it reproduces. We’ll ask for more info if we need it.
Congratulations to the first BIRD 3 bugreport and thanks for it!
On 18 December 2024 14:27:44 CET, Radu Anghel via Bird-users bird-
us...@network.cz <mailto:bird-users@network.cz> wrote:
Usin
Hi,
Using a slightly modified version of the config from the 2.15.1 (just
some {} inside case structures), but probably unrelated.
If bird gets killed/not shut down properly and routes remain in the
kernel then bird 3.0.0 is unable to restart and just segfaults when
trying to refresh kernel
On 13.08.2019 17:45, Maria Jan Matejka wrote:
define myvar = false;
function something () {
if myvar then {
return false;
}
return true;
}
protocol device DEVICE {
}
Could this be because of the new filter code or something else?
Hello
Thanks for bugreport. Yes, it
Hello,
I recently upgraded BIRD from 2.0.4 to 2.0.5 and with the same (pretty
large) .conf I got Segmentation fault.
Until today I didn't have time to debug it, but here it goes:
With this simple .conf I get seg fault on 2.0.5 while 2.0.4 works as
expected. (if I define myvar = true it doesn't c
Hi,
You need to set metric 0; in your kernel protocol in order to have
custom krt_metric per route.
"Metric 0 has a special meaning of undefined metric, in which either OS
default is used, or per-route metric can be set using krt_metric
attribute. Default: 32."
Radu
On 15.04.2018 00:57, Alexand
c6472
>
> Strictly speaking, you you don't know which AS in AS-set is the actual
> origin.
>
>
>
> Cheers
> matthias
>
>
> On Wed, 11 Apr 2018, Radu Anghel wrote:
>
>> Hello,
>>
>> I have found this while doing RPKI validation:
>
Hello,
I have found this while doing RPKI validation:
net = 94.127.104.0/21
bgp_path = 48112 6830 174 13110 {30884 65004 65005}
BGP.aggregator: 10.253.27.1 AS13110 (don't know how to read this from a var)
roa_check(rpki4, net, bgp_path.last) returns ROA_INVALID because BIRD
thinks bgp_path.last
On 14.12.2017 23:44, Ondrej Zajicek wrote:
> On Thu, Dec 14, 2017 at 09:19:32PM +0200, Radu Anghel wrote:
>
> Hi
>
> Tested add-path between old and new BIRD, works for me. Does the problem
> appear even with fixed channel definitions? It is possible that it is
> also r
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 onl
On 14.12.2017 20:31, Ondrej Zajicek wrote:
> Hello
>
> Thanks for reports Could you send me your config file? If you add 'debug
> all' to your Kernel protocol, what you see in logs?
>
Nothing is logged if I enable debug all to the kernel protocol, total
silence. I'm attaching my current config.
Hello,
I just installed bird 2.0.0 on a test machine to try it out and I have
some issues:
(CentOS 7 / kernel 4.14.5-1.el7.elrepo.x86_64)
1) the kernel protcol sees no routes (both ipv4 and ipv6) and doesn't
export any routes
2) each time I change the config and do a 'birdc conf' it resets all B
12 matches
Mail list logo
