On Jul 29, 2005, at 4:18 PM, Claudio Jeker wrote:
On Fri, Jul 29, 2005 at 01:23:27PM -0400, G Douglas Davidson wrote:
I'm having an issue announcing a "NO_EXPORT" network to our upstream
and I'd like a way to prove that I am in fact sending the network in
question (if in fact I am). It seems the "log updates" does not
apply
to sent updates, just received.
Any suggestions appreciated.
I utilized the dump updates feature as follows:
dump updates out "/tmp/updates-out-%H%M" 300
And in looking at the output, we are in fact not announce the network
in question. However a "bgpctl network show" indicates that we are
announcing the network in question. There are no filters in place.
The only things that appears different for this network versus other
networks we announce are:
1. This network (a /24) is part of a larger network (/20) that we
announce.
2. This network is announced with the "NO_EXPORT" community.
3. This network is also announced by another provider and is in our
bgp
table.
Any help would be appreciated!
Currently it is only possible to set the "NO_EXPORT" community on
outgoing
updates (match to rules). This is probably not expeceted behaviour.
I will have a look at it after I have finaly rewritten the bgp filter
stuff.
Looks like adding "NO_EXPORT via the rules match worked.
Thanks!
--
G. Douglas Davidson | CityNet, Inc.
[EMAIL PROTECTED] | Pittsburgh, PA
voice: 412.481.5406 | fax: 412.431.1315
