Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by thule, March 24, 2011, 08:18:49 PM
Quote from: broquea on March 24, 2011, 09:09:55 PMIf you want to see what routes we carry, you can telnet to route-server.he.netOtherwise the BGP tunnels are for networks to announce their IPv6 address space when they can't do that natively. So you'd need your own ASN and IPv6 allocation.
Quote from: mleber on March 25, 2011, 02:35:38 AMWhat facility (facility name, city, and country) is your router in?
Quote from: thule on March 25, 2011, 12:24:54 PMQuote from: mleber on March 25, 2011, 02:35:38 AMWhat facility (facility name, city, and country) is your router in?Los Angeles (10 minutes from LAX), in an office building. The office building has been wired by Cogent. The install for our suite should happen in the next two weeks (just ordered it).
Quote from: cconn on March 25, 2011, 06:32:44 AMFirst you might want to check if your ISP has relatively full reachability with the IPv6 network. In theory he would strive to peer with many v6 capable transit providers in order to offer reachability to the entire network. It is pointless to offer IPv6 to end-users if you do not.Quick test, if you can reach www.cogentco.com as well as www.tunnelbroker.net over IPv6, you likely have a total reachibility via your ISP.If not, I only can think of one way to supplement your service;ask your ISP if you can set up a private peering using an ASN in the private use range (64512-65534), and ask for a full view without a default route (filter it if necessary). Set up a tunnel with HE, they won't let you use a private ASN as far as I know however you can point a default route to that tunnel. So whatever routes are missing from your BGP view you can send traffic over to HE and hope it gets back to you :)
Quote from: cconn on March 25, 2011, 12:49:46 PMso if your IPv6 connectivity is solely via Cogent (AS174), then you can definately rule out global reachability (and that includes www.tunnelbroker.(com|net), unfortunately for you...)Here is our current prefix count:Cogent: 3796HE: 4785Other ( ;)): 5020not sure this is entirely up to date, but should be proportionally current;http://en.wikipedia.org/wiki/Comparison_of_IPv6_support_by_major_transit_providers
Quote from: thule on March 25, 2011, 12:55:47 PMFrom what I have been reading, there are very few, if any, ISP's that have "total reachibility." The recommendation, at this time, seems to be to get more than one ISP for serious IPv6. IPv6 for the company I work at is just for experimentation and learning, there is no reason to spend money on a second ISP. My theory was that I could combine the awesome work HE has been doing with the service that my ISP is giving me. That would give me a pseudo-dual ISP solution. The problem, of course, is how to load up the routing table? The ISP did ask if I wanted BGP for IPv6. Not knowing enough about BGP, I told them no. Another reply to my question states that I should ask for a private AS from my ISP which would allow me to populate the routes from them, then set HE to the default IPv6 route. Seems logical. I will have to ask them if the is an option.
Quote from: cconn on March 25, 2011, 01:35:44 PMperhaps you qualify for an ASN? are you multihomed?
Quote from: cconn on March 25, 2011, 01:35:44 PMIf you are peering directly with Cogent I doubt they would allow you to use a private ASN to do so. And you are correct that HE has been doing a great service to the community, granted in order to position itself as _the_ tier-1 provider of IPv6 services, however it is doing it in what I consider to be a very open and arguably generous way. Unfortunately I doubt you could use a private ASN with them either :-\If you are not using BGP with Cogent, then you will likely be in a scenario where you need to use a default route towards them; in this case, you will need a means to have a more specific route for the prefixes Cogent _doesn't_ have, and route that to your HE tunnel.
Quote from: cconn on March 25, 2011, 01:35:44 PMIf you are not using BGP with Cogent, then you will likely be in a scenario where you need to use a default route towards them; in this case, you will need a means to have a more specific route for the prefixes Cogent _doesn't_ have, and route that to your HE tunnel.
Quote from: thule on March 25, 2011, 09:58:23 PMThe more I think about this, the more it appears that I will have to create some script to handle this. I will have to scoop off the routes of off HE's public list. Then try to ping the routers from the Cogent transit. If they fail, create a route to send the traffic over the tunnel. Again, this is all for fun and learning. Nothing critical.