[warn] Request too large from address '[scrubbed]' to DirPort. Closing.
Hi, last night the log of one of my nodes showed within 2 minutes about 160 of these messages. Traffic stats show that the incoming bandwidth increased from the average of 300 Mbit/s to more than 400 Mbit/s, where at the same time outgoing traffic dropped. From the peak I see, the requests must have been really big. Does anyone noticed this on other tor servers too? Regards, Klaus
Hi, I want to ask for an status update regarding the bandwidth scanner project. It's been 3 weeks or so since we last heard anything. Are you still alive Mike ? -- Mit freundlichen Grüßen / Yours sincerely Sebastian Urbach -------------------------------------------------------- Religion is something left over from the infancy of our intelligence, it will fade away as we adopt reason and science as our guidelines. -------------------------------------------------------- Bertrand Arthur William Russell (1872-1970), British philosopher, logician, mathematician, historian, and social critic.
Thus spake Sebastian Urbach (sebastian@urbach.org):
I want to ask for an status update regarding the bandwidth scanner project. It's been 3 weeks or so since we last heard anything.
PID feedback has been off since I last notified the list about shutting it off, on Dec 19th. Some consensus params have changed due to dirauth instability, consensus method chnge, and confusion. In particular, the bwauthpid=1 param was explicitly set and unset a few times, and then set again, but the bw auths remained in their former "Section 2 compatible" mode of operation because no other feedback params were set for the duration. See https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/BwAutho... for more info on the consensus params that alter bw auth behavior, and please read the rest of the spec if you're interested in getting more involved. -- Mike Perry Exterminate all dogma. Permit no exceptions.
participants (3)
-
Klaus Layer -
Mike Perry -
Sebastian Urbach