Claudio Jeker wrote:
But your right we need AS path regex support...
Funny you should mention that, I've just been speaking with Henning
about the exact same thing - Although more for classifying routes on
ingress than for pure TE alone.
Cheers,
Karl
tch from 192.168.1.1 set { community 65400:100, community 65400:200,
community 65400:300 }
along with separate match lines for each community.
Thanks,
Karl Austin
Claudio Jeker wrote:
On Fri, Sep 02, 2005 at 01:53:03PM +0100, Karl Austin wrote:
Hi,
I'm just testing out OpenBGPD here, and am trying to set multiple
communities for a BGP peer, however it appears that no matter what I
try, only the very last community specified gets set, overwr
tony sarendal wrote:
I've started to test bgpd to see if I can use if for a future project.
Are there any plans to make bgpctl show communities, originator-id and
cluster-list ?
Any plans of adding route-refresh to bgpctl ? Something like "bgpctl
nei clear (in|out)" ?
Although I miss a few fe
tony sarendal wrote:
On 06/09/05, Karl Austin <[EMAIL PROTECTED]> wrote:
You've read my mind, that was going to be my next question if my issue
about having multiple communities per route was addressed (I tried
-current and it doesn't work). Soft reset, and more route
100 and OpenBSD yet on this as
well. To new most likely.
I know this doesn't answer your compatability question, but as far as I
am aware (So Sun told me yesterday) the new Opteron servers won't
actually be shipping till end of October/Early November.
Thanks,
Karl Austin
ng in
this situation that BGP is going to be overkill and the providers
wouldn't configure it unless we're talking about leased lines/E1, T1
etc. etc.
Thanks,
Karl Austin
Hi,
I've just upgraded a box to the 3.9 Snapshot from 30th January and now
whenever bgpd tries to open a session with a Extreme BlackDiamond it
reports the following:
received notification: error in OPEN message, optional parameter error
This was all working fine with a 3.8 snapshot before.
Henning Brauer wrote:
* Karl Austin <[EMAIL PROTECTED]> [2006-02-06 11:39]:
Hi,
I've just upgraded a box to the 3.9 Snapshot from 30th January and now
whenever bgpd tries to open a session with a Extreme BlackDiamond it
reports the following:
received notification: error in O
Karl Austin wrote:
Tried with:
announce IPv6 none
and:
announce capabilities no
but neither make any difference.
Thanks,
Karl
Just tried again, shut the session down at both sides for a few minutes
and waited, then brought them back up, and it seems that "announce
capabilities no
Henning Brauer wrote:
wait, I think I see a bug and "announce capabilities no" doesn't work :)
please try this diff.
Index: session.c
===
RCS file: /cvs/src/usr.sbin/bgpd/session.c,v
retrieving revision 1.243
diff -u -p -r1.243 sess
11 matches
Mail list logo