Re: Wanted: one more well-known BGP community

Vince Fuller <vaf@valinor.barrnet.net> Wed, 09 August 1995 22:17 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21063; 9 Aug 95 18:17 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21059; 9 Aug 95 18:17 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa21219; 9 Aug 95 18:17 EDT
Received: by interlock.ans.net id AA53531 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Wed, 9 Aug 1995 18:09:39 -0400
Message-Id: <199508092209.AA53531@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Wed, 9 Aug 1995 18:09:39 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Wed, 9 Aug 1995 18:09:39 -0400
Date: Wed, 9 Aug 95 15:10:27 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Vince Fuller <vaf@valinor.barrnet.net>
To: Ravi Chandra <rchandra@cisco.com>
Cc: bgp@ans.net
Phone: (415) 528-7227
Usmail: 3801 East Bayshore Rd, Palo Alto, CA, 94303
Subject: Re: Wanted: one more well-known BGP community
In-Reply-To: Your message of Wed, 09 Aug 1995 14:59:59 -0700

    	The 'no-advertise' community was meant to do what you want..
    why cannot you set the 'no-advertise' for selected entries via the
    outbound route-map (10.3 supports network based filtering for outbound
    route-maps). It should do what you want..

I tried it. When I do something like:

    router bgp 200
    neighbor 192.31.48.245 route-map peer-out out
    !
    route-map peer-out permit 10
    match ip as-path 81
    match ip address 150
    set community no-advertise
    !
    route-map peer-out permit 20
    match ip as-path 81

the routes which match as-path access-list 81 and access-list 150 are never
seen by 192.31.48.245, presumably because "no-advertise" was set on them
locally and therefore, BGP decided not to advertise them.

	--Vince