Re: Option to not open the server-port (179)

2019-11-30 Thread Ɓukasz Jarosz
{ BGP_CFG->local_port = $3; if ($3>65535) > cf_error("Invalid port number"); } > | bgp_loc_opts AS expr { BGP_CFG->local_as = $3; } > ; > > -- > *From:* Stefan Jakob > *Sent:* Saturday, November 30, 2019 11:39 AM > *To:*

Re: Option to not open the server-port (179)

2019-11-30 Thread Lars Ekman G
RT expr { BGP_CFG->local_port = $3; if ($3>65535) cf_error("Invalid port number"); } | bgp_loc_opts AS expr { BGP_CFG->local_as = $3; } ; From: Stefan Jakob Sent: Saturday, November 30, 2019 11:39 AM To: Lars Ekman G Cc: bird-users@network.cz

Re: Option to not open the server-port (179)

2019-11-30 Thread Stefan Jakob
Hi Lars, Hi Bird-List, Could you share the patch for this workaround please? Guess we share the same goals?: a) I want to announce a /32 (IPv4) or /128 IPv6 of course per service. b) I want to run multiple services on one single maschine in (Linux) namespaces, f.e. via Docker c) I want each serv

Option to not open the server-port (179)

2019-11-28 Thread Lars Ekman G
Hi, We have a use-case where we want to deploy multiple BIRD instances on the same machine. The BIRD instance would be a part of public applications with their own (virtual) addreesses. These BIRD instances shall announce the application addresses (only) but not set any local routes. The goal