tag:blogger.com,1999:blog-23021255.post2212557884585823643..comments2008-09-24T18:59:07.079+02:00Ivan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-23021255.post-38693354017575817392008-09-24T18:59:07.079+02:002008-09-24T18:59:07.079+02:00The nice thing about running BGP across firewall is that it's just another TCP session from the firewall's perspective, so you don't need any extra security rules. When I get a few hours of spare time, I'll write a post about typical design scenario.<BR/><BR/>See also <A HREF="http://forum.nil.com/viewtopic.php?f=10&t=18" REL="nofollow">this thread in NIL forums for other reasons to use BGP in enterprise network</A>.Ivan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comtag:blogger.com,1999:blog-23021255.post-37359613122666797432008-09-24T02:47:50.240+02:002008-09-24T02:47:50.240+02:00Hi, thank you for the article. Could you go over some reasons why you would require IBGP in general as well as in a non-internet or non-mpls environment. For eg in typical extranet type enterprise environment often IBGP is used between redundant edge routers and redundant inside routers and EBGP between the edge and inside through a firewall. Is this a recommended design and if so what is the real advantage of running IBGP between the inside routers. ThxAnonymousnoreply@blogger.com