Yeah, that's probably the best idea in this situation. I've been really interested in BGP but didn't know where to start, I'll read all the books that you guys put up above and start reading them. Also, referring to what you said "If you are not peering with TATA, then your routes would not go to TATA first. (unless the next-hop is indirect and that brings up other fundamental routing things that you should learn about)" Yeah, I meant that if I was getting a Transit service from them. Like, if using a DC like Equinix, you have access to countless amounts of opportunities to use Transits from virtually any provider, if I were to contact TATA and ask for a transit, I'd set that up in BGP, but I'm confused on how. I'll look into Fundamental routing. Thanks! On Sat, Jul 19, 2014 at 10:29 AM, Scott Morris <swm@emanon.com> wrote:
Fundamental routing training would greatly help you here. I would suggest looking for that.
If you are not peering with TATA, then your routes would not go to TATA first. (unless the next-hop is indirect and that brings up other fundamental routing things that you should learn about)
AS13335 is not TATA. So if this is what your provider gave you, one first assumes you¹d be directly connected to them (that¹s one of the rules in BGP¹s RFC for external connections).. If you have multiple providers, you may have multiple peers. Each one would give you information.
But like others have stated, I would strongly suggest you stop your testing for the moment and either hire someone to help or take some time to learn the basics on there. Otherwise, successful or not, your testing will really have no meaning to you.
Just my two cents.
Scott
-----Original Message----- From: Abuse Contact <stopabuseandreport@gmail.com> Date: Saturday, July 19, 2014 at 1:12 PM To: Jonathan Lassoff <jof@thejof.com> Cc: "nanog@nanog.org" <nanog@nanog.org> Subject: Re: BGP Session
Yeah, we're using it for an anycasted node but like, I'm confused on certain parts like, just a really basic question. When doing things like
conf t router bgp AS1337
neighbor 208.54.128.0 remote-as AS13335 neighbor 208.54.128.0 description BGP with Upstream neighbor 208.54.128.0 password "lolpass"
address-family ipv4 no synchronization neighbor 208.54.128.0 activate neighbor 208.54.128.0 soft-reconfiguration inboung
I'm confused on when doing this, would I need to state like
First go to AS13335 then go to TATA then go to my server or would it just automatically do that or would my provider do that? I'm confused on that. how would I state multiple peers.....?
On Sat, Jul 19, 2014 at 10:06 AM, Jonathan Lassoff <jof@thejof.com> wrote:
An Anycasting node. For example, as part of a reliable DNS service. A /24 is usually the smallest prefix length that is portably accepted.
Also, applications where connections need to appear to be coming from many source IPs.
On Saturday, July 19, 2014, Suresh Ramasubramanian <ops.lists@gmail.com
wrote:
A single linux box with a whole /24 on it? What sort of use case is that, BTW? On 19-Jul-2014 10:26 pm, "Abuse Contact" <stopabuseandreport@gmail.com> wrote:
I know, the DC is going to be giving me a BGP session on their router so I can set it up, I'm not using a Linux server as a router.
On Sat, Jul 19, 2014 at 9:04 AM, William Herrin <bill@herrin.us> wrote:
On Wed, Jul 16, 2014 at 4:05 AM, Abuse Contact <stopabuseandreport@gmail.com> wrote: > So I just purchased a Dedicated server from this one company and I have a > /24 IPv4 block that I bought from a company on WebHostingTalk, but I am > clueless on how to setup the /24 IPv4 block using the BGP Session. I want > to set it up to run through their network as if it was one of their IPs, > etc. I keep seeing things like iBGP (which I think means like a inner > routing BGP) and eBGP (what I'm talking about??) but I have no idea how to > set those up or which one I would need.
Howdy,
Unless you have (1) a real router available, not a just a server and (2) an expert available to help you with your first BGP configuration I strongly recommend you simply ask your service provider to announce the /24 to the Internet on your behalf.
Server-based BGP software like Quagga for Linux is reasonably good but it should absolutely not be involved in your _first_ attempt to connect with the Internet's default-free zone. Simple mistakes with eBGP can cause tremendous damage to other folks on the Internet. Trial and error is simply not OK. If it isn't worth it to you to buy a BGP-capable router then you also aren't prepared to make the investment in learning it takes to use BGP without causing harm.
Regards, Bill Herrin
-- William Herrin ................ herrin@dirtside.com bill@herrin.us Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/> Can I solve your unusual networking challenges?