Re: Transition from BIRD 1 to 2
On 10/13/23 16:58, Nico Schottelius wrote: We also started using MP BGP quite a lot with bird2, routing IPv4 over IPv6, as you can now have 2 channels per BGP session. Yes, I migrated the configuration to this for our internal BGP connections. But the peer has to also support this which does not work on a public peering exchange for example. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 220009 B Geschäftsführer: Peer Heinlein - Sitz: Berlin
Re: Transition from BIRD 1 to 2
Hi, On 14.10.23 00:57, Maria Matejka wrote: I'd recommend doing some templating The OSPF protocol does not allow templating. I wa able to solve that with an include of the area configuration in both protocols for IPv4 (OSPFv2) and IPv6 (OSPFv3). What I discovered is that filters are now IP family agnostic, i.e. I can use both IPv4 and IPv6 (e.g. network lists etc) in one filter definition. This makes it easier again. It would be good if the documentation (esp. the wiki) would contain examples for BIRD 2 for the most common use cases in IPv4 and IPv6. Currently there are only examples for IPv4 in BIRD 1. Kindest Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Re: Transition from BIRD 1 to 2
On 10/13/23 16:58, Nico Schottelius wrote: Hello Robert, Robert Sander writes: Hi, please help me understand the configuration logic for BIRD2. In BIRD 1 we have a config file common.conf that gets included from bird.conf and bird6.conf. It holds common configuration applicable to both IPv4 and IPv6 like this: I believe you might be using a side effect of the include (i.e. a config snippet being usable in both contexts), that now with only one config will not help you anymore. Yes. For example with the OSPF configuration we only had to define the interfaces with their weights once and could include that in both protocol configurations. Now I have to double that which makes maintenance harder. Maybe I have to play a little bit more with the include option. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 220009 B Geschäftsführer: Peer Heinlein - Sitz: Berlin
Transition from BIRD 1 to 2
Hi,
please help me understand the configuration logic for BIRD2.
In BIRD 1 we have a config file common.conf that gets included from
bird.conf and bird6.conf. It holds common configuration applicable to
both IPv4 and IPv6 like this:
table bgpext;
protocol pipe p_bgpext {
table master;
peer table bgpext;
import all;
export none;
}
For BIRD2 I seem to have to rewrite that simple configuration to:
ipv4 table bgpext4;
ipv6 table bgpext6;
protocol pipe p_bgpext4 {
table master4;
peer table bgpext4;
import all;
export none;
}
protocol pipe p_bgpext6 {
table master6;
peer table bgpext6;
import all;
export none;
}
Why do I have to double the configuration now?
Did I miss something?
This is a quite simple example. There are more complex protocol
templates and filter functions that all would have to be doubled.
Kindest Regards
--
Robert Sander
Heinlein Consulting GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 220009 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
Re: BGP selection
Am 26.04.22 um 04:57 schrieb Alexandre Corso: Does somebody have the full BGP algorithm? The BIRD documentation covers it in section "Route selection rules" of https://bird.network.cz/?get_doc=20=bird-6.html#ss6.3 Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Re: Filter BGP route based on ospf_metric1 ?
Am 24.03.22 um 08:38 schrieb Maria Matejka: The OSPF metric is copied there as an inaccessible "igp_metric" attribute. This is quite a silly behavior and in fact, I'm just a handful of commits before enabling filtering by this general attribute. This change will happen in a branch that should eventually merge into some future v2.0.x branch as well as the v3 branch. We won't backport it into v1.6.x. Thank you. I am now helping myself with this line in the import filter of the OSPF protocol: if ospf_metric1 > 42000 then reject; This reject the initial route to the router rendering all routes to that router unreachable, which I want to achieve. It would be nicer to be able to filter them and not have unreachable routes but for now it's OK. And yes, we have to upgrade to 2.0 sometime. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Filter BGP route based on ospf_metric1 ?
Hi, Our routers speak OSPF and have a full mesh of BGP connections for our internal routes. This works quite well. One router sees the other through OSPF: 80.241.60.8/32 via 10.25.19.251 on bond0.19 [ospf1 2022-03-17] * I (150/2474) [80.241.60.8] Type: OSPF unicast univ OSPF.metric1: 2474 OSPF.metric2: 16777215 OSPF.tag: 0x OSPF.router_id: 80.241.60.8 The BGP session is established to 80.241.60.8 and e.g. this route is learned: 192.168.100.0/22 via 10.25.19.251 on bond0.19 [thor 2022-03-17 from 80.241.60.8] * (100/2474) [i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: BGP.next_hop: 80.241.60.8 BGP.local_pref: 100 In the first line the ospf_metric1 is shown: (100/2474) But when I try to filter on it (because I want to drop routes with a too high metric), the route attribute ospf_metric1 is "(void)". This seems to be because it's a BGP route and not an OSPF route. Is it somehow possible to achieve this? PS: This is with bird 1.6.8. Kindest Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Re: Bird just doesn't want to find OSPF neighbors although they are there and can communicate
Hi Lukas, Am 18.10.21 um 02:01 schrieb Lukas Haase: I am having big trouble getting Bird/OSPF working. I broke it down to a simple setup: Point-to-point wireguard link What do you want to achieve? AFAIK the wireguard VPN does its own routing and will only send to IPs that are in its configuration. I have not figured out yet how to utilize a routing protocol (OSPF or BGP) on a wireguard link. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Bird 2 config syntax
Hi,
why is it not possible to define BGP sessions like this?
protocol bgp g60 {
local as 64501;
neighbor as 64499;
ipv4 {
import all;
export all;
};
local 192.0.2.4;
neighbor 192.0.2.5;
};
ipv6 {
import all;
export all;
local 2001:db8::4;
neighbor 2001:db8::5;
};
};
It seems still necessary to write two bgp definitions separately for
IPv4 and IPv6 repeating the AS numbers and name.
I see no benefit from the Bird 1.6 notation here.
Regards
--
Robert Sander
Heinlein Consulting GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG:
HRB 220009 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -- Sitz: Berlin
Re: direct routes and SLAAC addresses
Hi, Am 08.07.21 um 17:03 schrieb Ondrej Zajicek: > That is probably an issue with the Direct protocol and IPv6. In IPv4, > there is only one 'primary' address per IP range and iface, others are > marked 'secondary' by the kernel, so we just ignore secondary ones and > add/remove prefix when primary address is added/removed. But seems that > in IPv6, this is not the case and there is no secondary flag. IPv6 addresses have the "dynamic" flag if set with autoconf or privacy extensions AFAIK. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: direct routes and SLAAC addresses
Hi, Am 08.07.21 um 11:56 schrieb George Ross: > Does that sound right, or am I missing some bit of configuration somewhere? > > (As a hack workaround we now delete all of those unwanted SLAAC addresses > before we start BIRD.) Your SLAAC issue does not sound right to me. What distribution are you using? How do you configure the interfaces? On Debian it should be possible to add accept_ra 0 autoconf 0 privext 0 to the interface definition in /etc/network/interfaces according to https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html You can also use a sysctl config file in /etc/sysctl.d to set net.ipv6.conf.default.autoconf = 0 net.ipv6.conf.all.autoconf = 0 net.ipv6.conf.default.accept_ra = 0 net.ipv6.conf.all.accept_ra = 0 accept_ra should be automatically set to 0 when net.ipv6.conf.all.forwarding is 1. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Bird 1.6: OSPF reference bandwidth?
Am 07.06.21 um 21:04 schrieb Cybertinus: > Or should I define a > cost for each interface now manually, so it gives the 10 gbit/sec link a > 10 times lower cost than the other 3? AFAIK this is how it's done. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Match Neighbor on Export Filter
Am 09.11.20 um 11:27 schrieb Maria Matějka: > Not for now. There is some extension of the filter language pending (not > implemented yet) which would allow for protocol attributes queries. For > now, you can make your filter a function and use different arguments in > appropriate calls. > On November 7, 2020 2:34:50 PM GMT+01:00, Marcelo Balbinot > wrote: > > > Hello, I have a filter used in export by several protocols, > I would like to apply MED to exported routes only for a specific > protocol that uses this filter. You are able to filter on the protocol name which should identify the neighbor. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Temporarily announcing more specific prefix?
Hi Maximilian
On 21.09.20 20:59, Maximilian Wilhelm wrote:
> If the /24 is always present in the RIB why adding a static route for
> it?
Not all /24 are present in the RIB, some are.
> Just put another block into the BGP export filter for the /24 and
> guard it with a global variable, so you just have to change the global
> variable and "birdc c"
>
>
> # Somewhere global, maybe in an own file
> define MORE_SPECIFID = 0;
>
> # Boiler plate export filter
> filter some_export_filter {
> # regular annonucement(s)
> if net ~ [ aaa/22 ] then
> accept;
>
> if net ~ [ x/24 ] && MORE_SPECIFID = 1 then
> accept;
>
> reject;
> }
Yes, that would be possible but would also make the filter rules more
complex.
I already implemented the "second table" idea with the pipe protocol and
it works. It just adds a few megabytes RAM because the FRT is stored
twice in the BIRD process. That does not matter when the router has 16GB
RAM. :)
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
signature.asc
Description: OpenPGP digital signature
Re: Temporarily announcing more specific prefix?
Am 17.09.20 um 16:15 schrieb Alexander Zubkov: > You can use an additional table. And attach your and static protocols > bgp there. And do not pipe those prefixes to your main table. I understand. I will create a new table for the external BGP peers and pipe it with a filter to the main table. Attach all peers there and the static protocols for the exported prefixes. The pipe filter will reject the static prefixes to the main table and everything from the main table to the new table. This could work. Thanks. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Disregard OSPF path
On 17.02.20 16:37, Ondrej Zajicek wrote: > There is no such think as 'physical' cost of a link. Cost is always an > administrative property. There are several physical properties of a link > (like latency, throughput, technology) and it is a question of policy how > to convert them to OSPF cost. Yes, you are right. I just summarized all that under "physical" cost. In the end the OSPF cost is an arbitrary value set by the router admin. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Disregard OSPF path
Hi, On 17.02.20 09:03, Kees Meijs wrote: > > The path I'm trying to avoid has the lowest OSPF cost but in the > physical world the most... :-) I always thought the OSPF cost represents the "physical" cost of a link. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Disregard OSPF path
Hi, On 14.02.20 22:03, Kees Meijs wrote: > > I'd like to disregard an (in the literal sense) expensive OSPF path. The > preferred path is longer in terms of OSPF. Does it have a larger cost than the one you want to avoid? Why not increase its cost? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Route preference for one address
On 17.12.19 14:13, kc atgb wrote: > You mean without any routing protocol ? Just full static routing into the > system ? No, with BGP. R2 announces the host route via BGP on the backup link to R1. If the backup link goes down, the BGP session is terminated and the announcement not valid any more. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: Route preference for one address
On 17.12.19 12:17, kc atgb wrote: > > | || VPNLINK1 || | > 10.194.0.0/16 | ||-|| | 192.168.1.0/24 > | || || | > | | R1 | | R2 | | > | || || | > | ||-|| | > | || VPNLINK2 || | Do you control both routers? Then let R2 announce the host router over the backup link to R1 and vice versa. If the backup link goes down, the announcement will not be there any more. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
IPv6 BGP & kernel 4.19
Hi, our routers run on Debian stretch with bird 1.6.4 from bird.network.cz/debian. Yesterday I tried kernel 4.19 from backports.debian.org and ran into a weird issue with IPv6 BGP sessions: All Peerings reported "Error: Hold timer expired" ca. every 40 minutes. IPv6 forwarding was flapping all the time. After rebooting into kernel 4.9 everything worked again. IPv4 BGP was not affected and also OSPF (v4 and v6). I could disable all IPv6 BGP peerings on this router and then it forwarded to another router learned via OSPF for IPv6 without issues. Has anyone seen such a behaviour? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: string shell pattern match
On 14.06.19 13:49, Hansen, Christoffer wrote:
> So if you create an function to check if the interface name matches a
> certain pattern. And in your if() statement matched against true/false
> return value of function. You should be able to do what you want.
This does not work neither:
function if_external(string ifnamestr)
{
if ifnamestr ~ "bond0.4[2345]" then return true;
return false;
}
and later:
export filter {
if if_external(ifname) then reject;
}
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
signature.asc
Description: OpenPGP digital signature
string shell pattern match
Hi,
according to the documentation for BIRD 1.6 it should be possible to use
"shell patterns" with the ~ operator on strings:
https://bird.network.cz/?get_doc=16=bird-5.html#ss5.2
I tried to apply this within a filter but the expression does not match:
if ifname ~ "bond0.4[2345]" then {
reject;
}
I can only match if I "unroll" the expression and create four different
if statements.
What does "shell pattern" from the documentation mean in this case?
Are [ and ] not valid here?
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
signature.asc
Description: OpenPGP digital signature
Re: Reacting to Link Failure
On 22.12.2017 14:46, Liam Kelly wrote: > Is there any way for other programs to listen for Bird events regarding > Link Failure (IE: OSPF/BFD dead neighbor)? You could parse the output of "birdc show proto" to detect peer failure. Or talk directly to the bird daemon via its control socket like birdc does. Regards -- Robert Sander Heinlein Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-43 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
ospf networks IPv4 IPv6
Hi, I am currently playing with OSPF and the networks attribute for an area. It looks like you have to write a list of prefixes directly into the OSPF configuration and cannot use a constant. Is that correct? A constant prefix set would be helpful to have the same OSPF configuration for IPv4 and IPv6 where the constant itself would be defined in specific files separate for IPv4 and IPv6. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
Re: print and bgp_large_community
On 24.01.2017 14:19, Ondrej Zajicek wrote: > On Tue, Jan 24, 2017 at 02:02:39PM +0100, Robert Sander wrote: >> Hi, >> >> I need to print the bgp_large_community for debugging purposes but all I >> get is the output "(lclist )". >> > How are you using it? In a function in a filter like this: print bgp_community; print bgp_large_community; Self defined variables like "lc set test" can be printed with print test; without issues. Wait a minute. If I only get "(lclist )" does that mean the community list is empty? When I have a look at the route from the CLI I get this: BIRD 1.6.3 ready. 80.241.56.0/21 via 10.25.17.251 on br0.17 [ospf1 23:01:29] * E2 (1000/1000/1) [80.241.60.13] Type: OSPF-E2 unicast univ OSPF.metric1: 1000 OSPF.metric2: 1 OSPF.tag: 0x OSPF.router_id: 80.241.60.13 unreachable [static_bgp 23:15:16] (10) Type: static unicast univ BGP.large_community: (199118, 1, 0) The route is in a static protocol on this router and on 80.241.60.13, which propagates this via OSPF. Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
print and bgp_large_community
Hi, I need to print the bgp_large_community for debugging purposes but all I get is the output "(lclist )". Are these list not printable? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
BGP withdraw update on configuration reload
Hi, I experience the following behaviour with BIRD 1.6.2: 1. Change the config file 2. birdc configure 3. BIRD sends out an UPDATE message to its BGP peer to withdraw all prefixes learned via OSPF (see screenshot) 4. a second UPDATE message then contains all prefixes that should be announced according to the filters Where does this magic in step 3 come from? Why are prefixes getting leaked to the BGP peer that should not (even in a withdraw update)? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
BIRD 1.6.2 removes IPv6 kernel routes
Hi, I have an issue with BIRD 1.6.2 from http://bird.network.cz/debian/ on Debian jessie: When bird6 is running and I "ifup" an interface with a static IPv6 address the address is added but no IPv6 route in the associated network via that interface. When bird6 is not running everything works. It looks like bird6 1.6.2 is eating IPv6 routes set by the kernel. I have not encountered this issue with the IPv4 bird daemon. After downgrading to bird 1.4.5 from Debian jessie everything works as expected. What information do you need? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin signature.asc Description: OpenPGP digital signature
