On Sun, Jun 25, 2017 at 02:09:22PM +0200, Peter Hessler wrote: > : $ bgpctl show rib community WELLKNOWN:0 > : .. > : $ bgpctl show rib community WELLKNOWN:* > : .. > > Ehhhhh, I don't really see a reason to have syntatic sugar for > '65535'. In this case, I'm more likely to remember then number than > which string to use ;). > > : $ doas cat /etc/bgpd.conf | grep set > : match from any set { community WELLKNOWN:0 community 65535:1 } > > Same as before. OK for setting 65535:1, but 'Ehhhh' for > 'WELLKNOWN:0'. > > However, if we have one, then we need to have the other.
Current bgpd(8) on 6.1 uses the WELLKNOWN sugar in bgpctl output, i felt it would be proper to allow it in bgpd.conf and bgpctl input too. 6.1 example: [job@karen ~] $ bgpctl show rib detail 192.147.168.0/25 BGP routing table entry for 192.147.168.0/25 Nexthop 192.147.168.249 (via 192.147.168.249) from 192.147.168.249 (192.147.168.1) Origin IGP, metric 0, localpref 100, weight 0, internal, valid, best Last update: 00:00:08 ago Communities: WELLKNOWN:1 Kind regards, Job