Sergey G. Brester comments

Results 533 comments of


                                            Sergey G. Brester

Intent to work on speedups to `clock format` and `clock scan`

> Might be worth splitting up your PR It is already so, see https://github.com/sebres/tcl/pull/3 The clock speed-up is based on this branch.

Intent to work on speedups to `clock format` and `clock scan`

Rebased to [fossil-repository](http://core.tcl.tk/tcl/timeline?r=sebres-clock-speedup&n=200) + "TIP" ATM as ticket - http://core.tcl.tk/tcl/info/ddc948cff9781daa

Intent to work on speedups to `clock format` and `clock scan`

@martinwguy Thank you. As regards as "for month=1 to 12" - I don't have it at all. Conversion to/from yearday (but also julianday resp. gregorian) solved pure algorithmic (arithmetically, see...

Intent to work on speedups to `clock format` and `clock scan`

Ah now I understood what you meant. Well, would be currently a wrong screw, because the cost of it comparable to current whole execution time of scan/format (at least 0.20...

[BR]:Asterisk got ddos attacks, fail2ban and iptables failed to stop it in time, only after some time internal, iptables works.

Well, yes it may be surely the whitelisting rule bypassing established connections (just UDP is a bit more complex, since it is connectionless protocol)... Also the sign for that is...

[BR]:Asterisk got ddos attacks, fail2ban and iptables failed to stop it in time, only after some time internal, iptables works.

> But there no banaction, so how to revise as you recommended? There is `banaction` internally - it will be substituted in action_: https://github.com/fail2ban/fail2ban/blob/eea1881b734b73599a21df2bfbe58b11f78d0a46/config/jail.conf#L208-L212 So if you didn't change the...

[BR]:Asterisk got ddos attacks, fail2ban and iptables failed to stop it in time, only after some time internal, iptables works.

Well I guess you have verified `conntrack -D -s ...` works on your system basically. And to check whether new config has everything correct, you can try to dump it...

[BR]:Asterisk got ddos attacks, fail2ban and iptables failed to stop it in time, only after some time internal, iptables works.

> conntrack: command not found... Well, then it would surely not work (if it is not root/sudoer command only and you tried it with non-root user)... As already wrote -...

Updated firewallcmd-ipset.conf and added discord_notifications.conf

Just to link with #1474, which has also long discussion about usage of `--permanent` flag, I don't follow why fail2ban may need it, especially as you write, if it would...

Updated firewallcmd-ipset.conf and added discord_notifications.conf

> I understand what you are saying and yes there is no need to use the --permanent flag because there is no need to use firewalld's ipset interface the native...