Robert Šefr
Robert Šefr
My thoughts on this issue: - it is quite serious, because it can affect the whole host and performance of other containers - according to reaction of other people does...
Are you up to this any time soon? @kenshinx ? Would really appreciate this one.
I think, the situation here is a bit different to nginx, as there is the reason to rate limit to protect the application itself. On DNS resolver the reason is...
Just trying to bring in some inspiration :) PowerDNS has some DoS aware load-balancer, which could be a nice source of information too. http://dnsdist.org/
We have found the reason, the whole packet is shifted by VLAN and it does not match the passivedns packet structure, though it is a valid UDP packet. Not sure...
@scrapbird will try to catch one :)
Looking at the two ideas I think the one @sebix proposed would be quite clear to code, which is tempting. @aaronkaplan I understand you would prefer a more readable format,...
Ok, I agree with your points and I know you fight for this long term. I think we should decide a common notation for all such bots and keep it...
Ok, my proposal is as follows. Data: ``` [ {"ip": "127.0.0.1", "time": "324543262", "type": "bad thing"}, {"ip": "127.0.0.1", "time": "324543262", "type": "unknown"}, ] ``` Configuration: ``` - translate: ip: source.ip...
@dmth thank you a lot for bringing this to this thread, in your notation the configuration would be like this I presume: ``` config = { 'required_fields': [ ('time.source', 'time',...