Re: [tor-relays] Weird spike in written bytes per second
On Mon, May 23, 2022 at 12:18:41PM +0200, Marco Predicatori wrote: > the graph shows a marked difference between written bytes per second and > read bytes per second om 2022-05-19 and 2022-05-20. In any other day the > bytes are roughly the same. What might my node have "written" on those two > days? > > https://metrics.torproject.org/rs.html#details/A4E74410D83705EEFF24BC265DE2B2FF39BDA56E A common answer here is that your relay is serving more directory information than usual -- directory answers count as "written" bytes but they don't have corresponding "read" bytes. Indeed, that seems to be the case for you this time. Taking a look at your extrainfo descriptor from that time period (attached to this mail for posterity, but also you can find it on https://collector.torproject.org/ or via a query on your DirPort if you had one open): published 2022-05-20 23:28:07 write-history 2022-05-20 13:47:42 (86400 s) 52641878016,29257544704,29532297216,34634562560,121750598656 read-history 2022-05-20 13:47:42 (86400 s) 52190178304,28933199872,29611094016,31570991104,33742606336 dirreq-write-history 2022-05-20 13:47:42 (86400 s) 258335744,326073344,385689600,3712866304,87401081856 dirreq-read-history 2022-05-20 13:47:42 (86400 s) 18748416,468201472,756950016,882057216,1235405824 So yes, it is just that one day, where you pushed 121GBytes but only received 33GBytes. And the dirreq lines explain why -- they show on that last day that your relay served 87 gigs of directory info, while only fetching about 1 gig of it. More details on those extrainfo lines here: https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1191 Now, this leads you to a new question, which is "ok but why was I serving so much directory information on that day?" -- and I don't know the answer. We've had a series of mysteries over the past years where a whole lot of Tor clients appear and each bootstrap. Your mystery is a pretty small one in scale compared to these others. I guess the summary is "some users, for some definition of users, did that." --Roger extra-info torototela A4E74410D83705EEFF24BC265DE2B2FF39BDA56E identity-ed25519 -BEGIN ED25519 CERT- AQQABwNkAYD1Yg2VlRjBGK4bFOTGfqriRvkja8Rx1w/uqTgMlUoEAQAgBACuWp4X h6E17IAsn/CXO8M+VYMXov1JR1H1/qJPAqUeZK5INA19s4T1xqQETznM2jMR8o1E oEoe+B9Shs9xfVUwKohcR2BHwxeW+K1CJj9jCCOn+Na71OQAdN5Z3Z0YMA4= -END ED25519 CERT- published 2022-05-20 23:28:07 write-history 2022-05-20 13:47:42 (86400 s) 52641878016,29257544704,29532297216,34634562560,121750598656 read-history 2022-05-20 13:47:42 (86400 s) 52190178304,28933199872,29611094016,31570991104,33742606336 dirreq-write-history 2022-05-20 13:47:42 (86400 s) 258335744,326073344,385689600,3712866304,87401081856 dirreq-read-history 2022-05-20 13:47:42 (86400 s) 18748416,468201472,756950016,882057216,1235405824 geoip-db-digest C4F1B5ECF1B07BBECBE06B93926E4D1E62882782 geoip6-db-digest 0E43B5C62033BFE47F32742D8C9F5B5F83180AA4 router-sig-ed25519 rVmmvDdFx01brpCeJJAUPnv9XPriigWEagJTaDmYR5YvvblbOs5wGsHQ/UdRC3RxbvTO1yX9vLIsGNChshC0CQ router-signature -BEGIN SIGNATURE- yvnCkMR6MoNrorOhteUvtXcb4rg1yvbY+SY246SV3CE3Cj5Fm+mtUhaaQqmnubA2 hl3BkmBbIsT1HFGob/7wXa6R+U9VarxPsCw5Jy02EUZ1A+kSFE3sO7Wvcc3GfOam cc7CUcs1m17i6FZWEsklCzqLkf46jx2oyLP02tasRkU= -END SIGNATURE- extra-info AmorousLibrarian D1DF0AE44E69E0614A77305B3A12D1A1C7715C0C ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] [Workshop] Sysadmin 101 for (new) relay operators - June 4th @ 1900 UTC
Join us June 4th at 1900 UTC for new and prospective Tor relay and bridge operators on the basic "sysadmin foo" required to contribute to the network! ## Sysadmin 101 for new relay operators So you want to contribute to the open-source Tor network by running a relay or maybe a bridge? The Tor network is the most important tool for evading surveillance and bypassing internet censorship. And Tor relays and bridges are vital to the health and integrity of the Tor network. Millions of users rely on relays and bridges to stay safe, and how you configure and maintain that relay or bridge is critical. Volunteers aren't a nice enhancement. They are a core feature. Running a relay or a bridge raises frequent questions: * Should I run a relay or a bridge? * Should I run a relay or a bridge from a residential/home internet connection? * Which operating system should I run for my Tor node (hint: the one you are most comfortable with securing and maintaining) * More generally, what does it take to keep that relay or bridge operating safely, but both you and Tor users? This workshop will start with a presentation approaching some of the core issues that arise when running a Tor node. The session will move into an "ask me anything" discussion to approach other common and less common questions. The 90-minute event will be geared towards current and prospective Tor bridge and relay operators, particularly those relatively new to running public internet services. Seasoned Linux and BSD Tor operators will be attending the event ready to address the discussion. ## How to join the workshop The workshop is entirely free, and participants need to fill out this registration form. The event will take place on BigBlueButton, an online video conference platform, on June 4th at 1900 - 2030 UTC. You can register here: https://nc.torproject.net/apps/forms/cDLPxryHJcP5kMeW ## Facilitators The workshop will be facilitated by: * George (@gman999) - Tor *BSD Diversity Project member, Serge bridge directory authority maintainer, long-time relay operator and a wide variety of other contributions. * Kushal Das (@kushal) - RPM Tor maintainer and member of the Tor Community team. -- The Tor Project Community Team Lead signature.asc Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] [Event] Relay Operators Meetup - May 21, 2022 @ 1900 UTC
Are the notes for this meeting available? I was not able to make it but i would like to read up on what was talked about On 5/21/2022 8:29 PM, gus wrote: Hello! The Tor Relay Operator is happening today in ~30 minutes! Here is our agenda: * Announcements: * EOL work (GeKo) * DemHack.ru hackathon (Gus) * MCH event (Gus) * Torservers updates * New Tor version support policy (network team - ahf): https://lists.torproject.org/pipermail/tor-announce/2022-May/000241.html * Malicious relays and the health of the Tor network: https://blog.torproject.org/malicious-relays-health-tor-network/ (GeKo) * Congestion control release (0.4.7.7)：https://blog.torproject.org/congestion-contrl-047/ (ahf) * Expectations for Relay Operators: https://gitlab.torproject.org/tpo/community/team/-/wikis/Expectations-for-Relay-Operators (Gus) * Q * Next Meetup o/ gus On Thu, May 05, 2022 at 12:19:42AM -0300, gus wrote: Hello relay operators, The next Tor relay operator meetup will happen on Saturday, May 21 @ 1900 UTC. Where: BigBlueButton - https://tor.meet.coop/gus-og0-x74-dzn No need for a registration or anything else, just use the room-link above. We're working on the agenda here: https://pad.riseup.net/p/tor-relay-meetup-may-2022-keep Everyone is free to bring up additional questions or topics at the meeting itself. Please share with your friends, social media and other mailing lists! cheers, Gus -- The Tor Project Community Team Lead ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays OpenPGP_0xCA87BA4E77B9CA6F.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] [Event] Relay Operators Meetup - May 21, 2022 @ 1900 UTC
Hi, Thanks everyone for joining us last saturday. You can find the meetup notes below. The next Tor Relay Operator meetup will happen in June 25, 1900 UTC. cheers, Gus Agenda / Повестка дн May 21, 2022 * EOL work: - Tor versions lower than 0.4.5 are now unsupported and being removed from the network. - Ideally relays will be running 0.4.7 now because of the congestion control feature. - You can find more about this work at the Tor network health team repository: https://gitlab.torproject.org/tpo/network-health/team * DemHack.ru hackathon: https://blog.torproject.org/event/demhack-2022/ - We are working with volunteers on a hackfest to develop a bridge distribution mechanism that uses Signal (woo). They might be on irc at #tor-dev; if you see them, help them! - You can read more about the projects here: https://roskomsvoboda.org/post/demhack-4-final/ * MCH event (in July): https://mch2022.org/#/Blog At least four core Tor people will be present at this conference. Hopefully there will be a relay operators meetup. But there is no schedule published yet, so, stay tuned! * "Sysadmin 101" workshop in June, will be announced on tor-relays@ mailing list. If you're a relay operator but not comfortable with sysadmining, please join the workshop! It will be faciliated by George (BSD fan) and Kushal (Linux fan): "How to run a good relay for the Tor network" -- learn to configure your time properly, and everything else. * Brief update on the Ola Bini case - Roger and Linus finished their expert witness testimony last week. You can read more about the case here: https://www.eff.org/deeplinks/2019/08/telnet-not-crime-unconvincing-prosecution-screenshot-leaked-ola-bini-case * Torservers updates No torservers.net people present at meeting yet, so we will catch up with this topic next time or on the mailing list. * New Tor version support policy: https://lists.torproject.org/pipermail/tor-announce/2022-May/000241.html - Historically, we were tied closely to the Debian release cycle, including having a "long term stable" that we support for years so it can be in Debian. - We would much prefer relays to use the deb.torproject.org debs, which will keep people on the latest Tor stable. - The new proposal is to drop the long term stable idea, and ultimately we only allow relays onto the network if they're running the latest versions. - Feedback: Getting recent Tor versions into OpenBSD (*/6 mos), NetBSD/pkgsrc (quarterly) stable is going to be a challenge. People need to reach out to their package repositories and begin that discussion. - The plan is that *clients* can stay on a Debian stable, and we will try to keep supporting them. So it is only relays that need to do this faster cycle. - We also need to make sure to avoid having many old zombie clients trying to reach the network. - https://gitweb.torproject.org/torspec.git/tree/proposals/266-removing-current-obsolete-clients.txt is a good article to read to get up to speed on zombie clients and ways to handle them. * Malicious relays and the health of the Tor network: https://blog.torproject.org/malicious-relays-health-tor-network/ - People have been asking us every so often about the "kax17" attacker that was publicized in blog posts in the past. We were trying to decide how to react to those -- leave it quiet, make new publicity, something else? Ultimately we decided to do a blog post on our own to summarize what the network health team has been doing for bad-relays, and using the kax17 as an example of what we did in the past, where we failed, how we learned from it. - [Discussion about whether it makes sense to do a new blog post for each new attack, or what. Brief summary is yes [The "yes" was more to an announcement, say, on tor-relays@ than doing a blog post. Blog posts for this kind of things should be really a rare exception --GeKo] if it results in a huge surprising drop in network size, but no if it is yet another small attack similar to the one before it.] * Congestion control release (0.4.7.7)： https://blog.torproject.org/congestion-contrl-047/ - We need exit relay operators and onion service operators to upgrade to 0.4.7. Once both of these sides are upgraded, then everybody will see better performance. - Next step is to make a Tor Browser release with a client version that uses congestion control. At that point we expect to see network load going up, i.e. your relays will use more of their capacity. - https://metrics.torproject.org/bandwidth.html the spike in advertised bandwidth at the end is (hopefully!) due to the new feature. - Next step after this is multi-path (Conflux). * What's the time plan, or version plan, for Conflux? - We delayed 0.4.7 to have congestion control, which was a huge process. Conflux will come in 0.4.8 or 0.4.9, i.e. in the next 6 to 12 months, woo. * Expectations for Relay Operators: https://gitlab.torproject.org/tpo/community/team/-/wikis/Expectations-for-Relay-Operators - This is
[tor-relays] Weird spike in written bytes per second
Hi, the graph shows a marked difference between written bytes per second and read bytes per second om 2022-05-19 and 2022-05-20. In any other day the bytes are roughly the same. What might my node have "written" on those two days? https://metrics.torproject.org/rs.html#details/A4E74410D83705EEFF24BC265DE2B2FF39BDA56E Thanks, Marco ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] [Event] Relay Operators Meetup - May 21, 2022 @ 1900 UTC
When will the next meetup be? Is it online? Sent with ProtonMail secure email. --- Original Message --- On Saturday, May 21st, 2022 at 6:29 PM, gus wrote: > Hello! > > The Tor Relay Operator is happening today in ~30 minutes! > > Here is our agenda: > > * Announcements: > * EOL work (GeKo) > * DemHack.ru hackathon (Gus) > * MCH event (Gus) > * Torservers updates > * New Tor version support policy (network team - ahf): > https://lists.torproject.org/pipermail/tor-announce/2022-May/000241.html > * Malicious relays and the health of the Tor network: > https://blog.torproject.org/malicious-relays-health-tor-network/ (GeKo) > * Congestion control release > (0.4.7.7)：https://blog.torproject.org/congestion-contrl-047/ (ahf) > * Expectations for Relay Operators: > https://gitlab.torproject.org/tpo/community/team/-/wikis/Expectations-for-Relay-Operators > (Gus) > * Q > * Next Meetup > > o/ > gus > > On Thu, May 05, 2022 at 12:19:42AM -0300, gus wrote: > > > Hello relay operators, > > > > The next Tor relay operator meetup will happen on Saturday, May 21 @ 1900 > > UTC. > > > > Where: BigBlueButton - https://tor.meet.coop/gus-og0-x74-dzn > > > > No need for a registration or anything else, just use the room-link > > above. > > > > We're working on the agenda here: > > https://pad.riseup.net/p/tor-relay-meetup-may-2022-keep > > > > Everyone is free to bring up additional questions or topics at the > > meeting itself. > > > > Please share with your friends, social media and other mailing lists! > > > > cheers, > > Gus > > -- > > The Tor Project > > Community Team Lead > > > > > -- > The Tor Project > Community Team Lead > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
