BGP withdraw update on configuration reload

Robert Sander r.sander at
Mon Nov 21 15:27:59 CET 2016


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)?

Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: withdraw.png
Type: image/png
Size: 33950 bytes
Desc: not available
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Bird-users mailing list