I am hoping someone in the know can shed some lights on this.
My snippet of bgpd.conf:
# MCI
mci_as=11486
mci_peer1=142.77.114.132
mci_peer2=142.77.114.133
mci_peer3=208.218.245.33
# Allstream
allstream_as=15290
allstream_peer1=209.82.101.41
allstream_carp_ip=209.82.101.44
On 2008-05-20, Lu Vo [EMAIL PROTECTED] wrote:
group MCI {
remote-as $mci_as
set community 701:120
}
None of the upstream providers (MCI and Allstream) claim they see the
community strings set by me. Is this not the correct way of setting
community attribute ?
see bgpd.conf(5) -
On Tue, May 20, 2008 at 4:21 PM, Lu Vo [EMAIL PROTECTED] wrote:
I am hoping someone in the know can shed some lights on this.
match to group MCI set { community 701:120 }
match to group Allstream set { community 15290:90 }
2008/5/20 Aaron Glenn [EMAIL PROTECTED]:
On Tue, May 20, 2008 at 4:21 PM, Lu Vo [EMAIL PROTECTED] wrote:
I am hoping someone in the know can shed some lights on this.
match to group MCI set { community 701:120 }
match to group Allstream set { community 15290:90 }
Stuart and Aaron,
Thank
4 matches
Mail list logo