<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">How did you measure IPv6 traffic specifically? Ive been running an IPv4+6 exit for a while now and would be interested to know how much of that is IPv6.<div class=""><br class=""><div class=""><a href="https://atlas.torproject.org/#details/D51EE9D0653AA0D62F4D76AC428DF20F5377846B" class="">https://atlas.torproject.org/#details/D51EE9D0653AA0D62F4D76AC428DF20F5377846B</a></div><div class=""><div class=""><div apple-content-edited="true" class=""><div class=""><br style="orphans: 2; widows: 2;" class=""><span style="orphans: 2; widows: 2;" class="">Ethan</span></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On May 13, 2015, at 1:44 PM, Zack Weinberg <<a href="mailto:zackw@cmu.edu" class="">zackw@cmu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Unfortunately, I can't do this to the CMU Tor exit because the<br class="">university network doesn't do IPv6 -- I asked, and and it's on the<br class="">list, but there is an awful lot of old equipment which would have to<br class="">be replaced first, things like better WiFi coverage are higher<br class="">priority, and I can't say that I blame them. I've done it to my cloud<br class="">non-exit node, though, and it seems to be pushing 50-100 bits/sec of<br class="">IPv6 cells now. Yes, you read that right, bits.<br class=""><br class="">zw<br class="">_______________________________________________<br class="">tor-relays mailing list<br class=""><a href="mailto:tor-relays@lists.torproject.org" class="">tor-relays@lists.torproject.org</a><br class="">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>