on 17.12.2011 10:04 Ondrej Zajicek wrote:
On Fri, Dec 16, 2011 at 11:39:38PM +0100, Arnold Nipper wrote:
I see a simpler idea - just use a different 'local as' (perhaps some private ASN) on the BGP config on RS directed to GW (i.e. just on that one connection). In that case the session would be handled as eBGP, like all other sessions. Because the session would be also configured with 'rs client' on RS, the configured (private) ASN would not appear anywhere, it does not matter.
Well, is that really simpler?
It depends. This variant does not need any special handling in filters.
Right ... but you have to take care for this in the peer section anyway. *And* you have to treat the RS on the GW differently as well. I guess it much depends on your philosophy. The best solution perhaps would be to use a different ASN for the GW. Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold@nipper.de phone: +49 6224 5593407 2 mobile: +49 152 53717690 fax: +49 6224 5593407 9