e390a1df299dc4674f72382a7c751ff81ccc1a05
howto/frr.md
... | ... | @@ -101,12 +101,14 @@ router bgp <AS of the network> |
101 | 101 | neighbor <IPv6 peer address> interface <Peer interface> |
102 | 102 | ! |
103 | 103 | address-family ipv4 unicast |
104 | + network <Your IPv4 subnet> |
|
104 | 105 | neighbor <IPv4 peer address> activate |
105 | 106 | neighbor <IPv4 peer address> route-map dn42 in |
106 | 107 | neighbor <IPv4 peer address> route-map dn42 out |
107 | 108 | exit |
108 | 109 | ! |
109 | 110 | address-family ipv6 unicast |
111 | + network <Your IPv6 subnet> |
|
110 | 112 | neighbor <IPv6 peer address> activate |
111 | 113 | neighbor <IPv6 peer address> route-map dn42v6 in |
112 | 114 | neighbor <IPv6 peer address> route-map dn42v6 out |
... | ... | @@ -114,6 +116,8 @@ router bgp <AS of the network> |
114 | 116 | exit |
115 | 117 | ``` |
116 | 118 | |
119 | +**Note**: to advertise your prefixes, you will also have to have the full prefix assigned to an interface on the system. |
|
120 | + |
|
117 | 121 | With everything configured, the BGP session should come up. In the normal VTY shell mode the status of BGP peerings can be checked using the `show bgp summary` command. |
118 | 122 | |
119 | 123 | ### Complete configuration example |
... | ... | @@ -126,12 +130,14 @@ router bgp <Your AS here> |
126 | 130 | neighbor <Peer IPv6> interface <Peer interface> |
127 | 131 | ! |
128 | 132 | address-family ipv4 unicast |
133 | + network <Your IPv4 subnet> |
|
129 | 134 | neighbor <IPv4 peer address> activate |
130 | 135 | neighbor <IPv4 peer address> route-map dn42 in |
131 | 136 | neighbor <IPv4 peer address> route-map dn42 out |
132 | 137 | exit |
133 | 138 | ! |
134 | 139 | address-family ipv6 unicast |
140 | + network <Your IPv6 subnet> |
|
135 | 141 | neighbor <IPv6 peer address> activate |
136 | 142 | neighbor <IPv6 peer address> route-map dn42v6 in |
137 | 143 | neighbor <IPv6 peer address> route-map dn42v6 out |