I can kinda answer that.
I run an exit node that happily does 200-250mbit/s according to
netdata accounting and my monitoring regularly pegs it at nearly 200k
connections. Usually 100-150k.
On Sun, Jan 21, 2018 at 4:06 PM, nusenu <nusenu-lists@xxxxxxxxxx> wrote:
>
>
> Quintin:
>> Ah, thats it. My conntrack entries are full and temporarily increasing it
>> resolves the problem.
>
> I'm glad we found the problem and the solution.
>
> Your exit appears to be offline since 2018-01-20 20:00, expected downtime?
> https://atlas.torproject.org/#details/92E3764D5485DC4AC01178271FB5A8A2D90DA9FF
>
>> What would be a reasonable conntrack limit for a tor exit?
>
> The amount of states depend on your consensus weight (and probably exit policy),
> do you require a stateful packet filter?
>
>
> --
> https://mastodon.social/@nusenu
> twitter: @nusenu_
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays