[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 support via Charter | Ideas on BGP Tunnel via HE
- Subject: IPv6 support via Charter | Ideas on BGP Tunnel via HE
- From: jared at puck.nether.net (Jared Mauch)
- Date: Wed, 11 Apr 2012 17:41:17 -0400
- In-reply-to: <CAJAdsD=o9YbYSVqGVbwK_h+KXObPWeu2vz99ZsYjktoDcjniNA@mail.gmail.com>
- References: <CAJ0+aXZYFADBnQdHhwg8p5ObVcMVHc_bwzg5UQ6aWOkzpO4Z-Q@mail.gmail.com> <[email protected]> <CAJ0+aXYkj2Z3j4Ht=8fD1ULaVBNDoxojay80aOkvagT4Fm-N4g@mail.gmail.com> <CAJAdsD=o9YbYSVqGVbwK_h+KXObPWeu2vz99ZsYjktoDcjniNA@mail.gmail.com>
On Apr 11, 2012, at 5:19 PM, PC wrote:
> He.net tunnels are also good to have because depending on your provider,
> there's still many with incomplete views of the ipv6 routing table and he
> might have a path. This is a more prevalent issue with ipv6 than v4 at the
> moment.
This is a big problem for the two providers involved in this "spat" having
inconsistent IPv4/IPv6 business relationships (peering, etc).
There are many professional service providers that will happily dual-stack
your internet port with consistent business relationships. Don't let these
two parties that so far have agreed to disagree prevent you from using IPv6
to its fullest. Select another carrier.
- Jared