Hi!
Ok, thanks for this explanation. That is what I had in mind. So now I can
say I do understand rout filters :)
I hope :))
Best regards,
Kovi
At 11:22 9.8.01 +0200, you wrote:
>That is what A announces:
>
>Route Announce To
>--------------------
>B C, D
>C B, D
>D B, C
>
>Now you can define a filter on A for the router B to announce only the
>route to D, that is, an 'include_by_destination D'. Then B will only see D
>but not C.
>
>To make sure that B, C, D only see A, define an 'include_by_destination A'
>for B, C, D on A. That avoids route exchange which occurs when a router
>connects to another one.
>
>--
>Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
>SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
>
>
>-----Original Message-----
>From: Gregor Kovač <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Thu, 9 Aug 2001 10:00:42 +0200
>Subject: [developers] Routing filters
>
> > Hi!
> >
> > Thanks for your help :)
> > Now I think I get it. Everything depends on the view point.
> > So in a configuration where client routers connect to central one
> > (please
> > see attached file):
> > Then A would have a route to B and would announce it to C and D; and
> > when C
> > connects A would then have routes to B and C and would announce them to
> > D
> > when D connects?
> >
> > If this is true then i get the whole thing.
> >
> > Thanks and best regards,
> > Kovi
> >
> > At 16:20 7.8.01 +0200, you wrote:
> > > > I was going through the docs about Routing filters to try and
> > > > understand
> > > > them better. I came across following statement:
> > > > "Route filters must always be defined on the announcement side."
> > > > I just want to know who the announcement side is? The router that
> > has
> > > > the
> > > > connector to a remote router defined, the remote router or
> > something
> > > > else?
> > >
> > >It has nothing to do with connectors/listeners. Say, you have the
> > >following router network:
> > >
> > >A->B->C->D
> > >
> > >Here B has a route to A and announces it to C. As well as C has routes
> > to
> > >A & B and announces it to D. Hence, to avoid massive route
> > announcements,
> > >define route filters at the announcement side (that router which
> > announces
> > >routes to other routers; B and C in the above case).
> > >
> > >--
> > >Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
> > >SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
> > >
> > >
> > >------------------------------------------------------
> > >SwiftMQ developers mailing list * http://www.swiftmq.com
> > >To unsubscribe from this list, send an eMail to
> > >[EMAIL PROTECTED] and write in the body of your message:
> > >UNSUBSCRIBE developers <your-email-address>
> > >Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> > ------------------------------------------------------
> > SwiftMQ developers mailing list * http://www.swiftmq.com
> > To unsubscribe from this list, send an eMail to
> > [EMAIL PROTECTED] and write in the body of your message:
> > UNSUBSCRIBE developers <your-email-address>
> > Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> >
> >
>
>
>------------------------------------------------------
>SwiftMQ developers mailing list * http://www.swiftmq.com
>To unsubscribe from this list, send an eMail to
>[EMAIL PROTECTED] and write in the body of your message:
>UNSUBSCRIBE developers <your-email-address>
>Archive: http://www.mail-archive.com/developers@mail.iit.de/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
