Btw ... I already have sensei on all non WAN interfaces running. Of course I turned Sensei off, when I was testing. I think it might break things, if I change the Interface from WAN to LAN, where Sensei already is listening on, or?
without meaning it badly, but did u even read?I only mentioned this, because of the Ifirewall's advice. I wasn't 100% sure, but I know this myself.I have it on all (non) WAN interfaces ... This means, I have it on all interfaces that are not directed to WAN...Just LAN ...Of course I know that you should only place it on non WAN interfaces, because sensei is advising this to you when you install it.I also said, I uploaded my back up and it worked. A back up places every setting as it was before. This also means, that I haven't done any config change in sensei or OPNsense itself. It was truly some kind of bug related to suricata.My advice to you would be, read carefully before giving advices.
So somehow a miracle has happened I cannot explain.After this huge Attack on my Linux Client, I thought it would be the best to backup opnsense and reinstall from new. Just in case opnsense has been compromized. Turns out, this was the best decision of the day. Because, before and after the Upgrade from 20.1.9 to 20.7.1, I experienced some little bugs in opnsense like configctl timeouts and similar. After Reinstalling with Base Image 20.7, updating to 20.7.1 I saw that none of the previous experienced bugs reappeared. I restored the previous made backup, activated and reloaded all suricata rules. A short while later, I saw in suricata the first ICMP blocks. Seemed like suricata was working again and doing it's job.Later that evening, I turned on my Windows and started playing after that long day. But I forgot to switch the LAN cable from my non opnsense router back, so I could connect to blizzard. I didn't realize that Windows was still connected to opnsense. I wondered what went wrong and almost shit my pants, because I thought that suricata has stopped working and I have been compromised again.When I checked the logs, I finally saw that Suricata has managed to alert a connection to blizzardI changed nothing in Suricata. This tells me, that it somehow was bugged at some point. Now I can easily connect to blizzard and Star Citizen again... Take a look: