It seems that BIRD 3.0.1 is ignoring the GW attribute, after upgrading from
BIRD 2.16.1 to 3.0.1 all routes are showing as unreachable as shown below. The
BGP peers are 3 hops away from BIRD within the same AS hence the need for the
GW. Note I did not modify the BIRD configuration in between upgrading from
2.16.1 to 3.0.1.
birdc 'show route all for 1.1.1.1'
BIRD 2.16.1 ready.
Table master4:
1.1.1.0/24 unicast [wel_core30 2025-01-16 from 203.14.14.10] *
(100/?) [AS13335i]
via 203.41.0.5 on ens3
Type: BGP univ
BGP.origin: IGP
BGP.as_path: 13335
BGP.next_hop: 203.14.14.65
BGP.local_pref: 100
BGP.aggregator: 172.68.0.1 AS13335
BGP.community: (1221,110) (13335,10084)
BGP.originator_id: 203.14.14.65
BGP.cluster_list: 203.14.14.10
unicast [pie_core30 2025-01-16 from 203.14.14.11] (100/?)
[AS13335i]
via 203.41.0.5 on ens3
Type: BGP univ
BGP.origin: IGP
BGP.as_path: 13335
BGP.next_hop: 203.14.14.65
BGP.local_pref: 100
BGP.aggregator: 172.68.0.1 AS13335
BGP.community: (1221,110) (13335,10084)
BGP.originator_id: 203.14.14.65
BGP.cluster_list: 203.14.14.11
birdc 'show route all for 1.1.1.1'
BIRD 3.0.1 ready.
Table master4:
1.1.1.0/24 unreachable [wel_core30 11:21:09.045 from 203.14.14.10] *
(100) [AS13335i]
hostentry: via 203.14.14.65 table master4
preference: 100
igp_metric: 0
from: 203.14.14.10
source: BGP
bgp_origin: IGP
bgp_path: 13335
bgp_next_hop: 203.14.14.65
bgp_local_pref: 100
bgp_aggregator: 172.68.0.1 AS13335
bgp_community: (1221,110) (13335,10084)
bgp_originator_id: 203.14.14.65
bgp_cluster_list: 203.14.14.10
Internal route handling values: 0L 11G 0S id 417853
unreachable [pie_core30 11:21:13.738 from 203.14.14.11]
(100) [AS13335i]
hostentry: via 203.14.14.65 table master4
preference: 100
igp_metric: 0
from: 203.14.14.11
source: BGP
bgp_origin: IGP
bgp_path: 13335
bgp_next_hop: 203.14.14.65
bgp_local_pref: 100
bgp_aggregator: 172.68.0.1 AS13335
bgp_community: (1221,110) (13335,10084)
bgp_originator_id: 203.14.14.65
bgp_cluster_list: 203.14.14.11
Internal route handling values: 0L 9G 0S id 1516013
The BIRD configuration used is shown below.
log syslog all;
router id 203.41.0.6;
roa4 table roa_v4;
roa6 table roa_v6;
#Inbound route policy
filter rpl_in {
gw = 203.41.0.5;
accept;
}
#BGP IPv4 neighbor config template
template bgp CORE_PEERS {
local as 1221;
neighbor as 1221;
password REDACTED;
ipv4 {
import filter rpl_in;
export none;
};
}
#BGP IPv6 neighbor config template
template bgp CORE_PEERS_V6 {
local as 1221;
neighbor as 1221;
password REDACTED;
ipv6 {
import filter rpl_in;
export none;
};
}
#Import device routes for TID interface
protocol device {
scan time 10;
interface "ens3";
}
#Import directly connected routes for TID interface
protocol direct {
ipv4;
ipv6;
interface "ens3";
}
#BGP IPv4 core peer 1
protocol bgp wel_core30 from CORE_PEERS {
neighbor 203.14.14.10;
}
#BGP IPv4 core peer 2
protocol bgp pie_core30 from CORE_PEERS {
neighbor 203.14.14.11;
}
#BGP IPv6 core peer 1
protocol bgp wel_core30_v6 from CORE_PEERS_V6 {
neighbor 2001:8000::70:101;
}
#BGP IPv6 core peer 2
protocol bgp pie_core30_v6 from CORE_PEERS_V6 {
neighbor 2001:8000::70:201;
}
#RPKI cache server 1
protocol rpki rpki_cache_1{
roa4 { table roa_v4; };
roa6 { table roa_v6; };
remote REDACTED port 8323;
transport tcp;
refresh 300;
expire keep 3600;
}
#RPKI cache server 2
protocol rpki rpki_cache_2{
roa4 { table roa_v4; };
roa6 { table roa_v6; };
remote REDACTED port 8323;
transport tcp;
refresh 300;
expire keep 3600;
}
Regards,
Peter Hutchinson
TID Core
Internet Edge & Core
Global Networks & Technology, Transport & IP
[cid:1dfbd70b-26ae-414d-aa87-8a8e859368d7]
0490338570
[email protected]<mailto:[email protected]>
www.telstra.com<http://www.telstra.com/>
This email may contain confidential information.
If I've sent it to you by accident, please delete it immediately.
General
