Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by dfrandin, May 29, 2015, 08:10:20 AM
Quote from: broquea on June 18, 2015, 06:19:52 AMPaying someone to reach other networks (transit), versus not paying (peering).
Quote from: broquea on June 18, 2015, 07:14:08 AMevantkh:I already explained why IPv6 packets can't be routed between HE and Cogent: neither HE or Cogent PAY another network to deliver IPv6 traffic to other networks (transit). And you see those partial Cogent routes because some Cogent customers got an LOA (letter of authorization) issued from Cogent, to re-announce that IPv6 space to other BGP networks; like HE, NTT, etc. You need a better basic understanding of both how BGP works, as well as the overall internet design. The IPv4 example shows exactly how both transit and peering work. Your provider buys transit from their upstream ASN, who then in turn peers off that traffic to the destination either for free or paid (you'll never know).
Quote from: kcochran on June 18, 2015, 08:08:46 AMbgp.he.net is based off data from public sources, and not views from within HE itself, as to avoid bias.A network (normally) announces its own routes, and the routes of its customers to a peer. A network (usually) would announce its complete routes (including those learned from a peer) to a customer. There are some variances on these, but that's pretty much the rule for 99.9% of those relationships.So in the case where you have networks A and C peering with B: A sees B's routes, and B's customer's routes; C sees B's routes and B's customer routes; and B sees both A and C's routes and A and C's customer routes. If B announces A to C, then B is providing transit for A. If this is not something intended by A, then this is a leak, and extremely poor form for B to do and is a big faux pas (and sometimes cause for A to depeer B).