Re: Quagga (Two AS in one router)

[tomfi <tomfi@volny.cz>]

	> On 25/07/2007, at 3:19 PM, Wojciech Ziniewicz wrote:
	>> That's a nice note, but assuming that we have x routers with y ASes on
	>> them, what will be the information propagated to the internet ?
	>> I think that it's meaningless to set up such a solution .
You are thinking globally, You must separe x routers with y ASes is not
correct interpretation:
  We have y ASes with x/y routers within them :)

	> Normally, 1 router, 1 AS...
	> Multiple ASes, Multiple routers.

router is always in only one AS .... that is correct mr. Miehs ;)

	> Wojciech Ziniewicz wrote:
	> sry, should be "peered" with 3 ASes. here in poland i'm peered 	>
with a global mesh of asses 1. transit global which has 222088 	>
routes, 2. polish transit with 3992 routers and our own 			> exchange
centre  ( ACX ) with 1094 lines. Of course we're 		
	> using external bgp.
That sounds better :). It sounds like we don't understand each other :D.
So You are trying to make something like this :
			
			|     |
			|IBGP |
		  ______|_____|___
	   EBGP	  |		 |	EBGP
 1.AS ------------|  your ROUTER |---------------- 2. AS
                  |   your AS    |
                  |______________|
			|
			|EBGP
			|
			3.AS

This is normal, and there should be any problem.

You CANNOT implement something like this:
	  your Router
	_________________
	|1.AS		|
	|   2.AS	|-> router is internal for more than 1 AS
	|		|
	|	3.AS	|
	-----------------
Tomfi

PS: quagga(Zebra) must work well because here in Czech republic they use
it in Cesnet Backbone.