Linode Nextgen: The Network • Hacker News Board

Re: Linode Nextgen: The Network

#191

Post by jnw2 » Sun, Mar 10, 2013, 6:15 AM UTC

lsc wrote: post #184

jnw2 wrote: post #182

Earlier quoted context omitted.

If the problem turns out to be that AT&T and Cogent's peering links are overloaded, and the links between AT&T and Hurricane Electric don't have similar problems, then your border routers should be setting localpref to something low for any route with AT&T's ASN learned on the Cogent BGP session, which should send your outbound traffic to AT&T via Hurricane Electric except when your he.net link is down. The opposite…

I tried switching my outbound traffic to the customers in question over to he.net (with a static route, which I know is the dumb way to do it.) with no improvement. Hm. I need to learn more about bgp, specifically tags and communities, can you recommend me a book?

Also, you probably want to pick some community to affix to all routes you learn from your customers / originate yourself, and to make sure isn't affixed to routes you learn from your upstreams, so that you can then have a route map check for the presence or absence of that community when deciding which routes get passed along to your upstreams. (BGP doesn't directly solve the problem that an AS doesn't carry traffic unless the source and/or destination is ultimately a customer of that AS, it just provides mechanisms that can be used to make that happen.)

You may want to define communities to let your customers selectively decide to suppress announcements to each of your upstreams, and you may want to pass through the communties recognized by your upstreams in their official documentation if your customers send those communities to you, if you want to let your customers control their advertisements in that fashion. (The only reason I can think of you wouldn't want to let your customers do this is if it would let them move traffic from a link that's cheap for you to a link that's expensive for you.)

Re: Linode Nextgen: The Network

#192

Post by jnw2 » Sun, Mar 10, 2013, 6:47 AM UTC

lsc wrote: post #185

jk232 wrote: post #181

Earlier quoted context omitted.

Perhaps it is because peering is not an entitled right. If it was, who would pay for all the costs of network growth? AFA HE.net pricing, the reality is HE.net does not sell "their" network... they sell other ISPs network via their peering. Their costs are far lower as they don't carry the traffic more than 1-2 router hops. HE.net does this so much that their peers are feeling that the relationship is no longer "fair…

>Perhaps it is because peering is not an entitled right. If it was, who would pay for all the costs of network growth? My complaint here is that comcast charges as much for peering as for transport (with full routes) - I mean, if that's the case, why advertise paid peering services? Every time I've bought full routes I've had the option of asking the provider to only send me customer routes, or to filter on my end fo…

Hurricane Electric seems to have built their network by installing a router at every major peering point in the world, connecting each router to the local public peering point switch, and then interconnecting those routers. If you want reasonably direct connections to all the world's tier 2 ISPs, Hurricane Electric seems to be an excellent way to get that, and as long as they're not charging too much, they may make actually showing up at the major peering switches yourself not worth the trouble when you can just be their customer and get connections to more peering points than you'd probably directly connect to yourself.

Cogent has a fairly substantial network directly into random office buildings (though if you have an office in a random office building, it's almost certainly not one of the ones they've lit), and it's not clear to me that they do as good a job at peering with other networks as Hurricane Electric does.

Re: Linode Nextgen: The Network

#193

Post by astrodust » Mon, Mar 11, 2013, 5:34 PM UTC

verelo wrote: post #115

astrodust wrote: post #52

Earlier quoted context omitted.

Define "lots better". Qualify with examples. My experiences with AWS have consistently been absolutely awful. Things akin to "We're sorry your instance has gone away for no apparent reason. Thank you for writing." This does not ever happen on Linode.

Your tone, demanding for examples is a bit off putting... Direct contacts, very fast responses, phone support that picks up almost instantly and works with you for as long as it takes to resolve a problem. I've been very pleased, and most of the time the issues have been our fault, yet they've always helped us resolve the issue. I've used Linode too, no complaints at all, but you get a lot more power with the AWS too…

AWS has always been better in terms of features, and I've never found fault in Amazon's relentless work to improve even further. They really seem fearless in this regard.

However, their customer support has always been, at least in my experience, indifferent at best. It's often better to have a sherpa like EngineYard to help you through trouble spots.