Yes, this is possible. BGP uses TCP as its transport protocol on TCP port 179. On connection initiation, BGP peers exchange complete copies of their routing tables between each other, which can be quite large. However, after the complete routing table exchange, only changes (deltas) are then exchanged between the BGP routers. This makes long BGP sessions more efficient than short ones.
In this example suppose we have one BGP server on Ethernet interface If1 and another on interface If2.
In order to allow traffic flow:
- Create a custom Service object for TCP traffic on port 179. We might give this the name BGP.
- Create IP policies in the IP rule set for the respective BGP routers that allow traffic flow using the custom service. For this example we have two rule set entries:
A. The source interface and network and destination interface and network needs to correspond to the IP and interface that respective BGP router resides in.
B. Two rules are needed in order to allow traffic to be initiated both from the inside and outside.
By following this example, BGP routers will be able to exchange their routing tables when the routers are located on different interfaces.
21 Oct, 2022 core arp routing
12 Apr, 2023 core proxyarp arp ipsec routing
28 Mar, 2023 ikev2 windows vpn routing splittunneling
22 Mar, 2021 core ipsec routing
13 Apr, 2023 core routing ospf ipsec
17 Jun, 2021 core ipsec routing
30 Nov, 2022 core routing
1 Jun, 2022 core routing management
16 Oct, 2023 howto core pbr routing netwall isp
15 Dec, 2022 core routing ospf
7 Nov, 2022 core arp log routing
6 Apr, 2023 core ripv2 routing
17 Mar, 2023 core routing rules ping icmp cli
27 Jan, 2021 core stateless routing brokenlink
13 Feb, 2023 ipsec core routing failover
18 Apr, 2023 core routing transparentmode proxyarp