On 10 Dec 2015, at 14:23, akashic@sigaint.org wrote:
I'm running some bridges on VPS where I set 10GB monthly limit. I never come close to the quota, but the bridges reset with a new port and new stats every accounting period. This is undesirable because it means people who wrote down my bridge and port will no longer be able to connect. And Atlas take 6 more days to mark the bridge as fast again.
This is a known issue, see Trac Ticket #3511 Automatically chosen published ports should be stable https://trac.torproject.org/projects/tor/ticket/3511 https://trac.torproject.org/projects/tor/ticket/3511 (We'd love a patch to fix this!)
I like port diversity, but monthly switch seems excessive if 25% of every month is spent resetting stats.
Please try setting ORPort to a value other than "auto". And, if you're using them, also set pluggable transport port(s) explicitly.
For example: ORPort 12345 ServerTransportListenAddr obfs4 <IP>:23456
Can I set a longer accounting period, like 6 months?
Not in the current version of tor.
Failing that, what's the risk if I just get rid of the quota? Throttle rate of 200KB/s could add to 4TB/mo in worst case, which will get a VPS account killed. What's a more realistic worst case if I keep 200KB throttle with no monthly accounting?
I think setting ports to known values is your best bet here.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B
teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F