On May 16, 2017, at 12:41 PM, m...@free.fr wrote: > But, i still have issue with the route-map match sentence...
I don't actually know if there's a bug in applying a route-map to default-originate. However: 1) You should use "show ip bgp neighbor R2 advertised-routes" to see what R1 thinks it is sending. 2) You should turn on soft-reconfig, then "show ip bgp nei R1 received-routes" on R2 to see what R1 is actually sending. 3) A minor point - in route-map test stanzas 2 and 3, you should be doing "set community xx:yy additive" or all you'll ever see is 65200:2300. /a > On router R1: > ============= > router bgp 65200 > bgp router-id 192.168.1.254 > neighbor 192.168.1.253 remote-as 65200 > !! without the route-map test the routes on R2 are associated with local pref > 150 --> OK > ! neighbor 192.168.1.253 default-originate > !! with the route-map test the routes on R2 sees no route --> KO > neighbor 192.168.1.253 default-originate route-map test > ! > ip route 0.0.0.0/0 Null0 250 > ! > access-list 100 permit ip host 0.0.0.0 host 0.0.0.0 > ! > ip prefix-list def-route seq 10 permit 0.0.0.0/0 > ! > ! none of these following works ?? > route-map test permit 1 > match ip address prefix-list def-route > set community 65200:2100 > ! > > route-map test permit 2 > match ip address 100 > set community 65200:2200 > ! > > route-map test permit 3 > set community 65200:2300 > > On router R2: > ============= > router bgp 65200 > bgp router-id 192.168.1.253 > neighbor 192.168.1.254 remote-as 65200 > neighbor 192.168.1.254 route-map testin in > ! > route-map testin permit 5 > !! will put later a match community here > set local-preference 150 _______________________________________________ Quagga-users mailing list Quagga-users@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-users
