...
In addition to connection-specific parameters, template-specific parameters are also directly exposed in this menu, for easier configuration in simple scenarios (when templates are not necessary).
When local address is not specified, BGP will try to guess the local address depending on the current setup:
- if peer is iBGP
- if loopback available
- pick highest loopback address
- if loopback not available
- pick any highest IP address on the router
- if loopback available
- if peer is eBGP
- if remote peers IP is not from directly connected network:
- and multihop is not set, then throw an error
- and multihop is enabled:
- if loopback available
- pick highest loopback address
- if loopback not available
- pick any highest IP address on the router
- if loopback available
- if remote peers IP is from directly connected network:
- and multihop is not set:
- pick local routers IP address from that connected network
- and multihop is set:
- if loopback available
- pick highest loopback address
- if loopback not available
- pick any highest IP address on the router
- if loopback available
- and multihop is not set:
- if remote peers IP is not from directly connected network:
| Property | Description | |
|---|---|---|
| name (string; Default: ) | Name of the BGP connection | |
| connect (yes | no; Default: yes) | Whether to allow the router to initiate the connection. | |
| listen (yes | no; Default: yes) | Whether to listen for incoming connections. | |
| local - a group of parameters associated with the local side of the connection | ||
| .address (IPv4/6; Default: ::) | Local connection address. | |
| .port(integer [0..65535]; Default:179 ) | Local connection port. | |
| .role(ebgp | ebgp-customer | ebgp-peer | ebgp-provider | ebgp-rs | ebgp-rs-client | ibgp | ibgp-rr | ibgp-rr-client; Default: ) | BGP role, in most common scenarios it should be set to iBGP or eBGP. More information on BGP roles can be found in the corresponding RFC draft https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-open-policy/?include_text=1) | |
| .ttl (integer [1..255]; Default:) | Time To Live (hop limit) that will be recorded in sent TCP packets. | |
| remote - a group of parameters associated with the remote side of the connection | ||
| .address (IPv4/6; Default: ::) | Remote address used to connect and/or listen to. | |
| .port(integer [0..65535]; Default:179 ) | Local connection port. | |
| .as(integer []; Default: ) | Remote AS number. If not specified BGP will determine remote AS automatically from the OPEN message. | |
| .allow-as() | List of remote AS numbers that are allowed to connect. Useful for dynamic peer configuration. | |
| .ttl (integer [1..255]; Default:) | Acceptable Time To Live, the hop limit for this TCP connection. For example, if 'ttl=1' then only single-hop neighbors will be able to establish the connection. This property only affects EBGP peers. | |
| tcp-md5-key (string; Default: ) | Key used to authenticate the connection with TCP MD5 signature as described in RFC 2385. If not specified, authentication is not used. | |
| templates (name[,name]; Default: default) | List of the template names, to inherit parameters from. Useful for dynamic BGP peers. | |
...