[quagga-dev 16760] Re: Quagga 124 and multiple listen addresses

Matthias Ferdinand mf at 14v.de
Mon Jun 24 14:27:05 BST 2019


On Wed, Jun 19, 2019 at 12:00:03PM +0100, quagga-dev-request at lists.quagga.net wrote:
> Message: 1
> Date: Tue, 18 Jun 2019 14:00:34 +0200
> From: carbo at inrete.it
> To: quagga-dev at lists.quagga.net
> Subject: [quagga-dev 16759] Quagga 124 and multiple listen addresses
> Message-ID: <201906181200.x5IC0YdU000363 at Storage1.inrete.it>
> 
> Hi to all,
> have you already planned in the next release to implement support for multiple listen addresses.
> 
> At the moment the -l option supports a single address. So the option are to bind all 0.0.0.0:179 or one single address.
> 
> 
> bgpd_options=" --daemon -A 127.0.0.1 -f /etc/quagga-124/bgpd.conf?  <<<???Bind on all addresses
> 
> 
> bgpd_options=" --daemon -A 127.0.0.1 -l 10.255.255.14  -f /etc/quagga-124/bgpd.conf?  <<<???Bind on 10.255.255.14 only
> 
> 
> 
> We need to have at least two addresses in listen
> 
> Example:
> 
> 10.255.255.14:179
> 185.11.11.1:179


I am not a quagga developer and I don't know if this is being worked on,
but you could have bgpd bind to 0.0.0.0:179 and then use packet filters
to drop bgp traffic on those interfaces where you don't want quagga to
be active on.

E.g. on linux:

   iptables -I INPUT -p tcp --dport 179 -i eth2 -j DROP

to drop incoming bgp packets on interface eth2.


Regards
Matthias Ferdinand


More information about the Quagga-dev mailing list