Hi Matt, thank you for the reply.
I restarted the server since I hoped it would fix the underlying problem
but I don't it did.
I'll wait for 7 days as you suggested but the server has been up for
almost four years
now so a reboot shouldn't affect the stable flag. Its sister server was
rebooted
Yes, you can throttle bandwidth of your relay (both in terms of overall
thoroughput and the amount you let through per second), you can schedule when
it runs, and you do not need to adhere to any sort of schedule. None of this
needs to be manual aside from the initial configuration. As long as t
Hi,
I'm no authority on this, but I would like to try to answer your questions. My
message might sound a bit unappreciative of your willingness to help, which was
not my intention, but I want you to know the issues involved (as I see them)
before running a relay.
On Saturday, January 23, 2021
Took 15 days the last time you lost it.. nothing you can do but wait, anyway.
William
2021-01-25 10:53 GMT, raltul...@posteo.org :
> Hi Matt, thank you for the reply.
>
> I restarted the server since I hoped it would fix the underlying problem
> but I don't it did.
> I'll wait for 7 days as you s
1. Yes. The relay won't interfere with other applications, although you should
be aware that it will consume some bandwidth depending on how you configure it.
2. That depends on which OS you're using. However, running a part-time relay is
not optimal. Selection of a relay for middle or guard use
I had a similar problem recently. As I suspected an MTU path discovery
problem due to filtered ICMP traffic somewhere along the path I started
to clamp TCP MSS to 1200. Performancewise not exactly great, but I am
back in business since. Done this way on my raspi:
# iptables -A FORWARD -p tcp -
