Hello Lexi,
On Sat, Feb 22, 2025 at 01:34:51PM +, Lexi Winter wrote:
> i have an OSPF ABR in area 0 and area 1. this router has a default
> route via a non-OSPF interface (kernel route, imported into BIRD using
> the 'kernel' protocol). i'd like to advertise this
3AM +0800, Jimmy Lim wrote:
> > Hi Maria,
> >
> > It looks like it doesn't like the configuration of directing IPv6 prefix
> > that we receive from gw (we have 3 sessions) to ifname. The multipath is
> > working fine for IPv6 after I removed that configuration, and
On Tue, Feb 18, 2025, 18:38 Ondrej Zajicek wrote:
> On Tue, Feb 18, 2025 at 12:51:09PM +0200, Mantas Mikulėnas via Bird-users
> wrote:
> > From: Mantas Mikulėnas
> >
> > For an ordinary E1 or E2 route exported by another Bird2 router in the
> > same area, it was
rule 16.2 metric comparison was
backwards and always chose highest metric.
Note - the patch is probably *not* 100% right; I am not very sure
whether both checks are backwards or only the orta_pref() one. It's
merely my first successful attempt at fixing the issue (which only
affected Bird, no
>running BIRD 2.0.12. I encountered the same issue. The IPv6 prefix is not
>installed in the kernel if there is more than 1 equal path available. This
>is what I see in the log:
>
>> Feb 17 19:01:05 n002-002 bird[174542]: kernel2: fdaa::/16: installing
>> Feb 17 19:02:05 n00
Hello Hendrik.
We appreciate your efforts. The code seems very useful to us.
- Would you consider maintaining it?
- Have you thought about making it a separate project or part of BIRD
itself?
We need to look at it in more detail first, but then we are open to
integrating it into BIRD itself
On Fri, Feb 14, 2025 at 05:52:18PM +0800, Jimmy Lim wrote:
> I thought the issue might be related to configuration instead of bird
> version 😕
There is quite some code difference between BIRD 1 and 2, and I do
remember that the IPv6 multipath implementation was unstable for some
time
And I think there will be no more updates:
https://bird.network.cz/?o_news
25.4.2023 BIRD 1 end of life will happen at the end of 2023. Please finish
you upgrade to BIRD 2 ASAP!
On Thu, Feb 13, 2025 at 5:01 PM Douglas Fischer
wrote:
> uuuhhh... 1.6?
>
> This version has not been
Hi Bernd.
Yes, you're right. BIRD does not currently support setting the hostname
at the protocol level, only at the global level.
But as this is a trivial and useful feature request, we will implement it.
You can expect this option in a new BIRD release in the near future.
Have fun!
you for testing BIRD v3!
David
On 2/7/25 17:45, Yureka via Bird-users wrote:
After deploying bird 3.0.1, the bird process keeps crashing on several
of my routers, which had never crashed before on bird 2.x.
Within ~5min, I've seen the bird process crash with SIGABRT 27 times:
16x `With
After deploying bird 3.0.1, the bird process keeps crashing on several
of my routers, which had never crashed before on bird 2.x.
Within ~5min, I've seen the bird process crash with SIGABRT 27 times:
16x `Withdrawn route never seen before`
8x `Assertion '!rt_export_feed_active(&
Hi,
On Thu, Dec 05, 2024 at 01:58:02AM +, Nguyen Van Nhan via Bird-users wrote:
1. Can you provide me with detailed instructions to upgrade Bird to the latest
version 2.15.1? I have tried to upgrade but when performing the operation in
birdc, it still shows that it is at version 2.0.8
I’m convinced with your statement. I will share it with my FRR friend and see
if it is convincing also to FRR.
Thanks :)
Regards,
Grzegorz
From: Ondrej Zajicek
Date: Tuesday, 28 January 2025 at 19:49
To: "Ponikierski, Grzegorz"
Cc: bird-users
Subject: Re: link-local IPv6
as next hop in RIB. Otherwise, global address should be used. This logical can
be reversed with FRR route-map action “set ipv6 next-hop prefer-global” which
is equivalent of Bird channel option “next hop prefer global”.
Would you agree with such statement? Or I miss some nuances?
Regards
Internet so we don’t
have point-to-point links and link-local addresses don’t make sense in NEXT_HOP
which is highlighted in RFC 2545.
Regards,
Grzegorz
From: Donatas Abraitis
Date: Tuesday, 28 January 2025 at 14:38
To: "Ponikierski, Grzegorz"
Cc: "Brandon Z." , bird-user
I see I missed one detail which can be confusing. Problem is with sending
link-local address from Bird to BGP speaker on remote side and this link-local
doesn’t make sense for remote side because they don’t share common subnet.
Belove how it looks like from FRR perspective.
FRR: 2025/01/17 23
Hello all!
I have an interesting case of link-local IPv6 address in BGP.next_hop and I
would like to know your opinion about that because I cannot tell with 100%
confidence if it’s a bug or a feature. Existence of these link-local addresses
causes issues of interoperability between Bird and
ing the loopback using the local link IP as next hop. But it doesn't
> seem to it without the trick you use on linux. At least on 1.16.1 . Is there
> a way to do it wuthout an unnumbered interface ?
>
>
>> On 24 Jan 2025, at 02:24, Pim van Pelt via Bird-users
>> w
al link IP as next hop. But it doesn't seem
to it without the trick you use on linux. At least on 1.16.1 . Is there a way
to do it wuthout an unnumbered interface ?
> On 24 Jan 2025, at 02:24, Pim van Pelt via Bird-users
> wrote:
>
> Hoi Benoit,
>
> I did not try th
01:38, benoitc--- via Bird-users wrote:
Hi all,
I am looking at reducing the number of IPv4s I am using but i'ms truggling to
have loopback propagation over local link using OSPv3 on freebsd.
Did someone tried it? Can you share your related configuration?
when i setup the ip on lo1 and pass as
Hi all,
I am looking at reducing the number of IPv4s I am using but i'ms truggling to
have loopback propagation over local link using OSPv3 on freebsd.
Did someone tried it? Can you share your related configuration?
when i setup the ip on lo1 and pass as stub in the OSPfV3 IPv4 iinstances, n
It seems that BIRD 3.0.1 is ignoring the GW attribute, after upgrading from
BIRD 2.16.1 to 3.0.1 all routes are showing as unreachable as shown below. The
BGP peers are 3 hops away from BIRD within the same AS hence the need for the
GW. Note I did not modify the BIRD configuration in between
Hello Maria,
unfortunately I have just spotted mbuf 'leak' on FreeBSD connected with
net/bird3 usage, so maybe it was really 3rd bug.
Cheers
--
Marek Zarychta
Hello,
thanks for the bug report, it seems that it is in fact an bird v3 issue.
I've tried it in our testing setup and can confirm that it is happening.
We will fix it ASAP.
Thanks again,
David
On 1/12/25 11:23, Aihui Sun wrote:
Hi,there!
Cannot access value of igp_metric from within f
Hi all,
Did anyone tried to port the MPLS protocol to freebsd? What would need to be
implemented to make it work? Any guidance is appreciated.
Benoît
2025 12:17:19 CET, Marek Zarychta via Bird-users
wrote:
>W dniu 11.01.2025 o 12:01, Olivier Cochard-Labbé pisze:
>> Hi,
>>
>> bird 3.0.1 include this patch: "Netlink: Handle onlink flag on BSD-Netlink"
>> https://gitlab.nic.cz/labs/bird/-/commit/f9c7861e116ad8
W dniu 11.01.2025 o 12:01, Olivier Cochard-Labbé pisze:
Hi,
bird 3.0.1 include this patch: "Netlink: Handle onlink flag on
BSD-Netlink"
https://gitlab.nic.cz/labs/bird/-/commit/f9c7861e116ad8dc5e5a2314d0f976bf8c938de0
But this broke FreeBSD build with this error:
sysdep/bsd-netlink
Hello,
the option you want to use is `graceful restart time ` as cited
from the documentation at
https://bird.network.cz/?get_doc&v=20&f=bird-6.html#bgp-graceful-restart-time:
|graceful restart time /number/|
The restart time is announced in the BGP Graceful Restart capabilit
Hello Bird Team!
I am able to load my static ASPA tables like normal into the new bird 2.16.
bird> show route table at all
Table at:
50555 [static1 2024-12-26] * (200)
Type: static univ
aspa_providers: 970
270470 [static1 2024-12-26] * (
Hello Maria!
Correct! The AS_PATH_SET's are being depreciated. In the meantime they
are slipping into the algorithm which they should not be.
The bird code correctly checks for the confed but skips the ckeck for
the non-confed sets.
Below is what I proposed adding:
enum aspa_r
much looking forward to implementing it.
<https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/>
Thank you for your understanding.
Maria
--
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
) with v2 and v3, so there
is no difference in that.
BIRD v3 should be faster (since it's multi-threaded) and more
future-proof, however we released the stable version just last month so
it might be more prone to bugs.
BIRD v2 is single-threaded implementation, but much more tested by real
PM, Ralph Covelli via Bird-users wrote:
Okay!
I talked to Job. It looks like they have no interest in easing the
transition for stragglers who are still announcing AS_SETs in their
AS_PATHs.
All AS_SETs should result in ASPA_INVALID.
I also just learned the Dutch have a saying... "sof
Classified as: {Hitachi Rail - Public}
Basically configured bird as below
protocol device {
scan time 10;
}
protocol kernel {
scan time 10;
learn;
ipv4 {
export filter ;
}
}
bgp and bfd are established, everything
nd send us a log snippet around this message when it appears next time.
Otherwise, we know nothing. It is possibly BIRD trying to export a
colliding route.
Maybe, but that's a wild guess, you're running OpenBSD (?) and you have
another route inside BIRD for xx.yy.zz.0/24. If that's ri
Classified as: {Hitachi Rail - Public}
Basically configured bird as below
protocol device {
scan time 10;
}
protocol kernel {
scan time 10;
learn;
ipv4 {
export filter ;
}
}
bgp and bfd are established, everything
On Wed, Jan 08, 2025 at 03:51:37PM +0100, Alarig Le Lay via Bird-users wrote:
> Never mind, it just crashed again :p
> Jan 8 15:45:32 rr3 bird: Assertion '!old' failed at nest/rt-table.c:1497
Oh my, that's tough. But I'm very happy that I wrote that consistency
check,
Hello,
yes, that's correct, we'll fix this in a different way, please stand by.
Thank you for your understanding.
Maria
On 8 January 2025 15:56:00 CET, Jelle Luteijn via Bird-users
wrote:
>Hoi,
>
>I just checked and I don't see the updated packages, is that cor
Hoi,
I just checked and I don't see the updated packages, is that correct?
Regards,
Jelle
-Original Message-
From: Bird-users On Behalf Of Jakub Ružicka via
Bird-users
Sent: Tuesday, 7 January 2025 13:19
To: bird-users@network.cz
Subject: Re: Bird 2.16 ASPA issue
Hello,
On 1/6/
Never mind, it just crashed again :p
Jan 8 15:45:32 rr3 bird: Assertion '!old' failed at nest/rt-table.c:1497
Do you want a new coredump?
On Wed 08 Jan 2025 09:43:32 GMT, Alarig Le Lay via Bird-users wrote:
> Hello Maria,
>
> Thanks a lot, I confirm that it works well for me
Hello Maria,
Thanks a lot, I confirm that it works well for me now :)
On Tue 07 Jan 2025 22:06:31 GMT, Maria Matejka via Bird-users wrote:
> Hello Alarig,
>
> this was indeed a problem (and there was some more to fix) and if
> I haven't missed anything (but it now looks OK f
Hello Mike,
On Mon, Jan 06, 2025 at 01:10:51PM +0100, Mike Neo wrote:
> I currently have 2 servers Dell R310 with Bird 1.6 on Ubuntu
> (Active/Passive), one full BGP table and one IX, traffic around 400Mbps,
> simple BGP routing. I also have an HA cluster built on ESXi and I wonder if
&
Hello Alarig,
this was indeed a problem (and there was some more to fix) and if
I haven't missed anything (but it now looks OK for me), here is a fixed
version:
<https://gitlab.nic.cz/labs/bird/-/commit/2e14832d36c83b2ab5b7fb28b701de554fa5fdd9>
If you could check that it works for
tupid way.
I'd recommend to rebuild the Debian packages, bump the sub version, and
call it a day. This is a simple bug, 'provider' never was documented as
being correct, afaik.
I was asked to prepare Debian packages before official release of
https://bird.network.cz/download/bird-2.
Hi,
I would check first that address used to ping from the outside is really
the same that is configured in prefsrc. I.e. no typos, etc. You could also
use tcpdump to check what IPs are actually in use.
Regards,
Alexander
On Mon, Jan 6, 2025 at 11:17 PM Julien Sansonnens via Bird-users <
b
Dear all,
I'm experincing a nasty problem with IPV6 for some time. I'm certainly
missing something obvious, don't blame me, I'm still learning :)
I'm using bird 2.0.12 under debian 12 as a router. This router (VPS) has a
working IPV6 connectivity via the VPS provider.
n via Bird-users
Subject: Re: Bird 2.16 ASPA issue
On Mon, Jan 06, 2025 at 10:50:15AM +0100, Maria Matejka wrote:
> The right one is "providers", yet there is probably some package out
> with "provider", so i'm expecting to allow both in the end because we
>
5AM +0100, Maria Matejka via Bird-users wrote:
>> Hello,
>>
>> there is a discrepancy between doc and parser. Please try
>>
>> s/providers/provider/;
>
>Are you sure?
>
> $ sed -i 's/providers/provider/' ./bird
>
> $ bird --versi
Hello,
there is a discrepancy between doc and parser. Please try
s/providers/provider/;
Sorry for the inconvenience. We'll fix this in the next version.
Maria
On 6 January 2025 08:40:36 CET, Jelle Luteijn via Bird-users
wrote:
>Hoi,
>
>Yesterday I tried to implement the vali
Hoi,
Yesterday I tried to implement the validation of ASPA in my router filters.
I have generated the ASPA table via the mainline version of RPKI-Client, docker
image rpki/rpki-client:edge to be precise.
For Bird I use version 2.16 provided from https://pkg.labs.nic.cz/.
When loading the bird
, old_stored=0x0,
old_best_stored=0x0) at proto/bgp/attrs.c:2696
Which corresponds to the deterministic med:
https://gitlab.nic.cz/labs/bird/-/blob/v3.0.0/proto/bgp/attrs.c?ref_type=tags#L2696
int old_suppressed = old ? !!(old->pflags & BGP_REF_SUPPRESSED) : 0;
To be used there:
https://gitlab
On Fri, Dec 20, 2024 at 11:46:53AM +0100, Maria Matejka wrote:
> > > seems to trigger when peers connect
>
> Fixed. Another oversight. Luckily it was enough to just move some
> things around to not violate the locking order, and now it looks like
> running.
>
> http
Hello David,
Here is the coredump:
https://herbizarre.swordarmor.fr/garbage/core-bird.29074.rr3.swordarmor.fr.1735592879
And here is the config:
https://herbizarre.swordarmor.fr/garbage/bird.conf.29074.rr3.swordarmor.fr.1735592879
I compiled bird3 with the two previous patches of this ML
, Alarig Le Lay via Bird-users wrote:
Hello Maria,
I thought that I had the same bug, but it seems that it’s a different
one as I applied the patch but I still got a segfault at startup.
[342115.227497] bird[19396]: segfault at 8 ip 5642c37062db sp
7fc784295ca0 error 4 in bird[5642c366e000
t;.
Haha! Thanks again for all your help.
Ralph Covelli
Network Engineer
Hurricane Electric / AS6939
On 12/27/2024 4:40 PM, Ralph Covelli via Bird-users wrote:
Hi Maria!
Interesting stuff! I suppose you could consider the different AS's in
the SET as "lateral" from each other on &
ts with the
outcome "Invalid".
I am going to see if I can convince the powers that be to change 7.3.3
to "Unknown".
Thanks again!
Ralph Covelli
Network Engineer
Hurricane Electric / AS6939
On 12/27/2024 12:31 PM, Maria Matejka via Bird-users wrote:
Hello Ralph,
f the ASNs in the set"
- adding an `aspa_is_customer(table, A, B)` function, returning whether A
can be a custormer of B according to the given table
Any other thoughts on that?
Thanks,
Maria
--
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
Ralph
On 12/26/2024 6:04 AM, Maria Matejka via Bird-users wrote:
Hello Ralph,
Issue #1) There is no way to tell the difference between a
transit entry and an “AS0” entry.
There is no difference between a transit entry and an AS0 entry. The
|transit| keyword is just a syntactic sh
Thank you for the information. Tis didn't work but I think that 2.16 is
probably missing a way to set the IP correctly on freebsd. This is probably
missing that patch :
https://gitlab.nic.cz/labs/bird/-/commit/e0ed978e753c57b65b89e860b49fd29acb0b43ad
to make it works. Would be good to h
Hi all,
I would like te to use the new feature "allow loopback nexthop in OSPFv3-IPv4 "
on freebsd but I am not sure about the configuration. Let say 2 machines are
linked to each others via a vlan. Should I pass the vlan as ptp or stub on
freebsd ? Or is there any other way to have unnumbere
ers is mentioned in section 5 of
> draft-ietf-sidrops-aspa-verification-19. It is a mechanism for people to
> announce that "no one should announce this AS". I've attached a snapshot of
> the global ASPA table as "bird-aspa-v2.16.conf". There is one AS0
> anno
Hello Bird Team!
My name is Ralph. I'm a network engineer and C programmer for Hurricane
Electric. I am a long time fan of the Bird project! Keep up the great
work!!
Earlier this year I was tasked with implementing reactive ASPA in our
network. My code was based off your
W dniu 18.12.2024 o 19:59, Maria Matejka pisze:
Hello Marek,
for now probably your config suffices, we'll ask for more if needed,
please keep the core and binary for us.
Hello Maria,
thank you for fixing this issue. So it came out, that 3rd bug was really
the 1st bug fixed with commit
|b6c
Hola,
> On 18 December 2024 16:12:56 CET, Job Snijders via Bird-users
> wrote:
>
> > Second bug? :-)
> >
> > bird: 2024-12-18 15:01:29.251 [0001] Started
> > bird: 2024-12-18 15:01:34.615 [0001] Trying to lock in a bad order:
> > 7fff17afd6e0 000
Hello Maria,
I thought that I had the same bug, but it seems that it’s a different
one as I applied the patch but I still got a segfault at startup.
[342115.227497] bird[19396]: segfault at 8 ip 5642c37062db sp
7fc784295ca0 error 4 in bird[5642c366e000+f]
[342115.227524] Code: 39 10
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
Hi Maria,
I tried the patch and I can confirm that it is now safe to kill and
revive the bird :)
Thank you!
Best,
Radu
On 19.12.2024 13:38, Maria Matejka wrote:
Hello Radu,
sorry, this was a stupid omission of a null check. Fixed in
b6caccfd45fb639b6dd3a8d140d3c5ba4cc79311 <ht
Hello Radu,
sorry, this was a stupid omission of a null check. Fixed in
[b6caccfd45fb639b6dd3a8d140d3c5ba4cc79311](https://gitlab.nic.cz/labs/bird/-/tree/b6caccfd45fb639b6dd3a8d140d3c5ba4cc79311).
Could you please check that it works on your side now?
Thanks,
Maria
On Wed, Dec 18, 2024 at 02
Hello,
we got a network in which clients using dhcpcd withdraw the router
advertisements sent by bird too early:
Dec 19 06:33:15 bibimbap daemon.warn dhcpcd[18464]: wlan0:
fe80::20d:b9ff:fe48:3bb8: router expired
Hello,
with Bird 3.0.0 I'm experiencing crashes during `birdc configure`.
During quick debugging I figured it's somewhat related to BFD - in my
use case I have keyed SHA1 authentication enabled (but similar issue I
had with simple BFD session authentication). With session auth
Hello Marek,
for now probably your config suffices, we'll ask for more if needed, please
keep the core and binary for us.
Thanks!
Maria
On 18 December 2024 18:56:05 CET, Marek Zarychta via Bird-users
wrote:
>I tried BIRD 3 on FreeBSD, seems to build fine including both flavors:
I tried BIRD 3 on FreeBSD, seems to build fine including both flavors:
netlink and rtsock.
Only the netlink flavor was tested in runtime. In small, testing
scenario with OSPF and BGP it seems to run fine. When deployed in
production setup with dual-stack and 2x full-view the daemon crashes
Oh yes, you hold the silver!
Please send us the corefile and binary (off-list), we need to know what
triggered this in which order. (Yes, multithreading shenanigans, crazy stuff.)
If it's too big, ask for an upload link.
Thanks!
Maria
On 18 December 2024 16:12:56 CET, Job Snijders via
Second bug? :-)
bird: 2024-12-18 15:01:29.251 [0001] Started
bird: 2024-12-18 15:01:34.615 [0001] Trying to lock in a bad order:
7fff17afd6e0 79af687be298
seems to trigger when peers connect
config:
router id 10.10.255.254;
protocol device { }
protocol direct { disabled; }
protocol
Hello, Radu!
We apparently missed this case in our test scenarios, so we'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!
Maria
On 18 December 2024 14:27:44 CET, Radu Anghel via Bird-use
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
Awesome news, and good timing, will be testing that over xmas :)
Congrats on the release, and take a well deserved rest, bugs and feature
request will likely come soon :)
Merry routing! Happy peering!
Jeroen
--
> On 18 Dec 2024, at 13:03, Ondrej Filip wrote:
>
> Dear BIRD User
Congrats to the entire BIRD team on the release!
Merry routing!
Merry routing to you as well.
-ilteris
check that.
Great, thanks. If you want to make any changes on a branch or something, I
can build it and test it on my hardware if it would help.
Hi
Just wondering if you do not have the original core dump and binary, or
if you could replicate the issue with unpatched bird. Nick Hainke brought
this
Hey,
I did a PR for the routing feed containing your latest patch [0]. I hope
everything is alright. I'm looking forward to the BIRD 3 release. If I
need to test something, I'm happy to help. I can also give you SSH
access via IPv6 to an OpenWrt device for testing, if you
On Mon, Dec 16, 2024 at 10:59:06PM +0100, Alarig Le Lay via Bird-users wrote:
> > Also it is funny that Routinator answered with: 'only versions 0 up
> > to and including MAX_VERSION supported' without stating what is the
> > MAX_VERSION.
>
> You tell me, that’s
On Mon 16 Dec 2024 17:23:46 GMT, Ondrej Zajicek wrote:
> Hello
>
> So if i undestand it correctly, if you put both 'min version 2' and
> 'max version 2', it failed? (that is expected if the peer does not support
> version 2)
My original goal was to feed the ASPA table, but the protocol was
negoti
around forever.
[0] - https://bird.network.cz/pipermail/bird-users/2021-June/015545.html
[1] -
http://trubka.network.cz/pipermail/bird-users/2024-December/017944.html
[2] -
https://github.com/openwrt/routing/commit/f4251ccf69ad70b46c060be62eb39ebc36c47ac6
Bests,
Nick
Dear all,
Apologies for the earlier confusion—my toolchain was misconfigured, and
I mistakenly compiled the unpatched BIRD sources. Upon correcting this,
I believe the first patch already addresses the issue. However, I
noticed that the two patches result in different alignments. Below is a
Hello,
Following the 2.16 release with ASPA support, I tried to play with it.
So I tried to connect a bird instance to a RTR server with version 2 as
stated by https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.16
> The same protocol, since version 2, also receives and maintains
regard the previous patch. Can you try the first attached patch
(log-alignment.patch) to log alignment of different structures with or
without the second patch (net-addr-u32-align.patch) and report me results?
On 12/11/24 1:41 AM, Ondrej Zajicek wrote:
On Tue, Dec 10, 2024 at 09:15:46PM +0100, nic
Hi BIRD-Community,
I wanted to bring this patch back into focus. We run a non-commercial
WISP-network with Babel and switched to BIRD due to limitations in
babeld. While BIRD works great, we urgently need this patch for better
route filtering flexibility.
It’d be great to see this upstream
/tree/main/u64patch
On 12/11/24 1:41 AM, Ondrej Zajicek wrote:
On Tue, Dec 10, 2024 at 09:15:46PM +0100, nick via Bird-users wrote:
I also uploaded the coredumpfile:
https://github.com/PolynomialDivision/coredumpupload/blob/main/bird_coredump
Thanks. This seems like an interesting issue. In BIRD
I also uploaded the coredumpfile:
https://github.com/PolynomialDivision/coredumpupload/blob/main/bird_coredump
On 12/10/24 8:56 PM, nick via Bird-users wrote:
Sorry for the long response time.
Here is the requested output:
Program received signal SIGBUS, Bus error.
0x00056fc0 in
= 16
(gdb) p px
$2 = (struct bgp_prefix *) 0xb6eac01c
(gdb) p (uintptr_t)px % 4
$3 = 0
(gdb) p (uintptr_t)px % 8
$4 = 4
On 12/6/24 3:16 AM, Ondrej Zajicek wrote:
On Thu, Dec 05, 2024 at 11:35:13PM +0100, nick via Bird-users wrote:
Dear BIRD Community,
I am writing to report a bug observed in the
Fabian Bläse writes:
> The Babel seqno wraps around when reaching its maximum value
> (UINT16_MAX). When comparing seqnos, this has to be taken into account.
> Therefore, plain number comparisons do not work.
>
> In a previous attempt to fix the wrapping behavior, one particular
> comparison was
Dear BIRD Community,
I am writing to report a bug observed in the BGP implementation on ARMv7
platforms, which results in a SIGBUS error due to unaligned memory
access in the NEON assembler code. I debugged this issue on version
2.15.1 of BIRD.
### Problem Description
When running BIRD on
Dear Bird Community,
I have installed BIRD and tested the configurations related to the operation of
this application. I have some questions during the BIRD deployment process, I
hope you will give me specific instructions for editing and optimizing in
operation.
I am installing the default
Hello,
with this, are you sure that you are actually editing the right config file? If
you do a syntax error right at the beginning of the file, just putting garbage
there, does it fail?
Maria
On 2 December 2024 23:11:30 CET, LIU Chris via Bird-users
wrote:
>Classified as: {Hitachi R
Classified as: {Hitachi Rail - Public}
I configured 4 bfd sessions like below, but 3 sessions are up,
I check many times, those 4 session seems no any difference.
I used birdc command to check
"birdc show bfd sessions session"
only 3 sessions, 1 session not list here. Why I configured
Chris Webb writes:
> By default, the Babel protocol will advertise an IPv6 extended next hop
> address on interfaces which don't have an IPv4 address. This is controlled
> by the 'extended next hop' option.
>
> Add support for 'extended next hop force' which advertises an extended
> next hop even
rtt min ;
> rtt max ;
> @@ -2377,10 +2377,13 @@ protocol babel [] {
>source for Babel packets will be used. In normal operation, it should
> not
>be necessary to set this option.
>
> - extended next hop
>
> + extended
n? You want to use both sources at once in
>> ecmp-like manner, when the server makes a connection? Or something else?
>>
>> On Wed, Nov 20, 2024, 10:44 hans.heng wrote:
>>
>>> You can set krt_prefsrc in bird. If I remember the option name right.
>>>
>>>
Zubkov
wrote:
And what is you intention then? You want to use both sources at once
in ecmp-like manner, when the server makes a connection? Or something else?
On Wed, Nov 20, 2024, 10:44 hans.heng wrote:
You can set krt_prefsrc in bird. If I remember the
> And what is you intention then? You want to use both sources at once in
> ecmp-like manner, when the server makes a connection? Or something else?
>
> On Wed, Nov 20, 2024, 10:44 hans.heng wrote:
>
>> You can set krt_prefsrc in bird. If I remember the option name right.
&g
1 - 100 of 859 matches
Mail list logo