One idea might be to set the logging level as a parameter, so it is a host setting.
But I have done some more testing, and it seems it is the requests from the renters, that are DDOS'ing my router. Are there anything special about the requests made from the renters ? or is it just normal RPC-calls?
I have had other P2P running, so I am suspecting either that the request are creating some shortage in the router making it boot after a while.
What I have seen is the following
no siad running - my router is happy
siad running but not as a host - all is still fine
siad running as a host - 18 minutes approx. router boot
siad as been running for a while, but I terminates it but still letting it be registered as a host - router might work for 1-2 hours, probably because there are still some tries of connecting
siad has ben running but is deregistered as a host for contracts, router seems to be working fne
As I understand it there are different type of calls made, but I suspect the scanning of hosts might be the problem.
I can see that in Sia / modules / renter / hostdb / scan.go the host is added to the pool, but as GO is a new language for me, I still havent figured out where the actual call to the host is made (And thus not found where I need to log the request on the host side).
I think it might be a request that is not passed thru the router, so even logging on the host might not help me.