It seems now it bans bots for quite a while as expected (10 min * 2^(5 - 1) = 160 min = 2h 40min):
apex% sudo journalctl -u fail2ban -f -n 30
Nov 21 14:30:02 apex fail2ban.filter[1460258]:…
Default fail2ban config is not particularly clever:
apex% sudo journalctl -u fail2ban
I have increased the setpoint to 85°C and configured the heater relay to always stay on if the pump is enabled. It has caused the temperature probe to reach almost 100°C with the following…
After reconnecting the Ethernet cable into another port in the switch the speed went back to 1 Gbit/s:
lake2% sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
…
Disabling MDI-X doesn't change the result after renegotiation, but it drops the SOL console. Is the BMC messing with the NIC? We could add another Ethernet cable and switch to the other port for…
Another observation:
MDI-X: on (auto)
Why is it using cross-over configuration?
Same state after a reboot:
lake2% sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
…
Speed renegotiation doesn't seem to fix it.
lake2% sudo mii-tool -r eno1
restarting autonegotiation...
lake2% sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
…
What the hell:
lake2% sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
…
Added a PID controller with very slow relay PWM cycle (integral component is disabled for now). The PID controller outputs a value from 0 to 1, which in turn determines the time the relay will be…
Can we add a comment here on why is broken? Maybe also in the --with-mpi=yes above.