BGP conf

Holmes,David A dholmes at mwdh2o.com
Wed Nov 2 15:54:16 UTC 2011


This is a perfect example of why it is crucial that inbound route filters be scrupulously maintained in upstream BGP providers. Who knows who is out there.

-----Original Message-----
From: McCall, Gabriel [mailto:Gabriel.McCall at thyssenkrupp.com]
Sent: Tuesday, November 01, 2011 7:29 PM
To: Edward avanti; nanog at nanog.org
Subject: Re: BGP conf

Google for "team cymru secure bgp template" for a good starting point.


-----Original message-----
From: Edward avanti <edward.avanti at gmail.com>
To: "nanog at nanog.org" <nanog at nanog.org>
Sent: Wed, Nov 2, 2011 01:01:37 GMT+00:00
Subject: BGP conf

Halo,
First, I accept this might not really right list for request, have use nsp
cisco list but only first post to was succeed, sent several other for past
4 day and none appear (verified by list archive) so please excuse request.

I am in need of a cisco config for BGP setup, we have a require to include
IX peering at new location as well as our Verizon link, we like to take
full bgp from Verizon and send to IX what they send us, I spend days
reading google, and so many conflict web site example, so many example seem
insecure no prefix list so on. end result to date is only sore eyes, would
someone who do same (not need be Verizon) be kind to send us off list
working running config (yes without your password heh) or at least how to
apply to BGP router including access/prefix list and interfaces so we have
an idea on what do, if you take two full BGP feed from two transit
carrierin load share and IX, that good, because that our stage three plan,
but I can work without two transit.

I am not ignorant with cisco 7201, but am total newby to BGP.

Best Thanks
Edwardo


This communication, together with any attachments or embedded links, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments or embedded links, from your system.


More information about the NANOG mailing list