6to4 status (again)
Brzozowski, John Jason
jjmb at jjmb.com
Tue Feb 26 13:25:48 CET 2013
"in our observation, 50-80% of traffic in 6to4 relay is {coming from,
going to} Teredo."
Last I checked I believe this was also the case for us.
On Mon, Feb 25, 2013 at 7:39 PM, Shin SHIRAHATA <shin at tokyo6to4.net> wrote:
> Hello Kevin,
>
> > We run one of the public 6to4 relays. Lately traffic to it has been
> growing very rapidly and I'm really not sure why. Other people shutting
> their public relays down? More AAAA records are making more people fall
> back to 6to4? Idiots using it for DDoS?
>
> We, Tokyo6to4 had shutdown our 6to4/Teredo public relay router in AS38646
> and AS55374 in last September. Because commercial IPv6 services are became
> available in Japan since 2011.
>
> The total amount of traffic level was around 100Mbps.
>
> > For most of 2012 the usage averaged about 50-100mbps, but lately we're
> seeing sustained levels of 500mbps-900mbps. I'd rather not deploy 10GE on
> our 6to4 box just to handle the traffic growth.
> >
> > Has anyone here looked at public 6to4 usage recently and seen similar
> trends?
> >
> > Part of me is thinking we should just rate limit the box to something
> more reasonable. While it's still running, it'll be slow enough that
> hopefully people will move to a better transitional technology. My fear is
> that it will cause more "v6 sucks, it's so slow" and people shut it off
> without looking at why.
>
> in our observation, 50-80% of traffic in 6to4 relay is {coming from,
> going to} Teredo.
>
> I think there is a reason to implement rate limit to these traffic (6to4-
> Teredo) before limiting whole traffic. Logically, it should be reachable
> without 6to4 relay since the nature of the traffic is IPv4-IPv4 traffic.
>
> ---
> No caffeine, No work.
> Shin SHIRAHATA <shin at shirahata.name> / <true at sfc.wide.ad.jp>
> http://www.sfc.wide.ad.jp/~true/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20130226/ad8f0669/attachment.htm>
More information about the ipv6-ops
mailing list