<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi!<div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 29.07.2018 um 00:51 schrieb Roger Dingledine <<a href="mailto:arma@mit.edu" class="">arma@mit.edu</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Sat, Jul 28, 2018 at 07:59:08PM +0200, Tobias Sachs wrote:<br class=""><blockquote type="cite" class="">Hibernation is set to 19 TB???s of outgoing Traffic. Hetzner Cloud shows ~16TB outgoing traffic and the relays log itself 38TB.<br class=""></blockquote><br class="">Can you give us your actual torrc lines?<br class=""><br class=""></div></div></blockquote><div>Log notice file /var/log/tor/notices.log<br class="">RunAsDaemon 1<br class=""><br class="">ORPort 443<br class="">ORPort [2a01:4f8:1c1c:af5::1]:443<br class=""><br class="">Nickname GermanCraft3<br class=""><br class="">RelayBandwidthRate 100 MBits<br class="">RelayBandwidthBurst 200 MBits<br class=""><br class="">AccountingMax 19TB<br class="">AccountingStart month 1 00:00<br class="">AccountingRule out<br class=""><br class="">ContactInfo 4096R/0x4cf76925833e2e24 Knight <knight AT germancraft dot net> - 1MTXtuSCCTf6J3TiUnk1ePwgaHt9h6uQaU<br class=""><br class="">DirPort 80<br class=""><br class="">ExitPolicy reject *:* <br class="">ExitPolicy reject6 *:*<br class=""><br class=""></div></div></div><div class=""><div><div><blockquote type="cite" class="">Also, how about the log lines, particularly the ones that talk about</blockquote></div></div></div><div class=""><div><blockquote type="cite" class=""><div class=""><div class="">when it woke up, when it went into hibernation, when it plans to wake<br class="">up again, etc?<br class=""></div></div></blockquote><div><br class=""></div>Jul 29 06:25:01.000 [notice] Configured hibernation. This interval began at 2018-07-01 00:00:00; the scheduled wake-up time was 2018-07-01 07:27:40; we expect to exhaust our quota for this interval around 2018-07-31 23:32:40; the next interval begins at 2018-08-01 00:00:00 (all times local)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">vnstat reports exactly 20.38 TiB tx so in conclusion Hetzner can not count there Bits and Bytes or the same as protection is not correct.<br class=""></blockquote><br class="">Maybe some of these transmitted bytes went to other Hetzner servers,<br class="">which they don't count as "really" sending bytes to the Internet.<br class=""><br class=""><blockquote type="cite" class="">Because if Hetzner???s stats are correct i would have send 3 TB???s of Traffic to other Tor servers and clients internally. Because internal traffic is not counted.<br class=""></blockquote><br class="">Ah, yes, this is what you suggested. Maybe? That's a lot (a large<br class="">fraction) given that Hetzner doesn't have that large a fraction of the<br class="">Tor network these days.<br class=""><br class=""><blockquote type="cite" class="">I guess that a Juniper routers net flow tool is correct so how can i look at this? Because my second relay in Helsinki does have this too with a difference of 2 TB???s.<br class=""><br class="">"Heartbeat: Tor's uptime is 27 days 1:39 hours, with 0 circuits open. I've sent 38486.76 GB and received 38489.42 GB. We are currently hibernating.???<br class=""><br class="">When i divide that by two this gives me 19 TB???s of outgoing Traffic. So i guess that this is a bug?<br class=""></blockquote><br class="">Tor said you sent 38TB, so that's 38TB of outgoing traffic.<br class=""><br class="">Maybe your 27 days contained two hibernation periods? That would be<br class="">one possible explanation for 19+19=38.<br class=""><br class="">—Roger<br class=""></div></div></blockquote><br class=""></div><div><blockquote type="cite" class="">Hetzner hosts > 7% of the tor network capacity (#3 on the biggest ASes on the tor network).<br class=""><br class="">If I know the relays IP I could give you the probabilities of your relay<br class="">relaying traffic to others in the same AS (since a relay will usually not<br class="">be used with others in the same /16 netblock)</blockquote><br class=""></div></div><div>So that means the same-as protection is a check that it is not the same /16 Block? That would make sense.</div><div><br class=""></div><div><a href="https://bgp.he.net/AS24940#_prefixes" class="">https://bgp.he.net/AS24940#_prefixes</a></div><div><br class=""></div><div>Hetzner is holding 17 /16 and smaller netblocks. So it is possible that the complete route is within one AS? o.O</div><div><br class=""></div><div>The IP is: 159.69.2.239</div><div><br class=""></div><div>Thanks for your help!</div><div><br class=""></div><div>Tobias</div><div><br class=""></div><div><br class=""></div></body></html>