Quote from: Seimus on May 03, 2026, 01:24:50 AMQuoteWhat filtering options would you actually use?
Anything missing in the IOC view?
Not sure if this is feasible but what about sorting based on country of origin? E.g Country from where the IoC originates.QuoteIdeas for improving the OPNsense plugin?
Well, OPNsense has inbuilt RRD and other graph possible tooling, would it be possible under the condition its not resource heavy, to create graphs based on the events/IPs/ports/protocols?
Something similar for example as in
Lobby > Reporting > Health
Or
Firewall> Log Files > Overview?
This would still be local to the OPNsense, but would give the users more visual representation.
Regards,
S.
Quote from: franco on May 07, 2026, 10:45:17 AMSystem: Configuration: History would shed some light on when and where these parts were removed (by whom).
Cheers,
Franco
cd /var/db/qfeeds-tables/
rm *
<13>1 2026-05-07T22:25:12+02:00 OPNsense.internal dhcp6c 79084 - [meta sequenceId="381"] dhcp6c_script: REQUEST on pppoe1 connected to server
<13>1 2026-05-07T22:25:12+02:00 OPNsense.internal dhcp6c 84865 - [meta sequenceId="382"] dhcp6c_script: REQUEST on pppoe1 prefix now 2a00:ffff:ffff:8000::/56
# ifconfig pppoe1 inet6 2a00:ffff:ffff:8000::1 prefixlen 64 aliasQuote from: dirtyfreebooter on April 12, 2026, 05:47:11 PMi upgraded the protectli from 2.17 to 2.32 firmware, i left the deciso at 2.25 *shurg*
edit: oh i c, i was also running 0.9.1-rc3 on VP2440.. yea 0.9.0 coreboot was 100% broken for FreeBSD + igc because of ASPM. AMI bios completely disabled ASPM, adds 4-5w to idle, which is like 50%, but also solves the issues.
Quote from: franco on May 07, 2026, 10:46:17 AMI'm unable to tell.
Quote from: pOpY2k25 on May 07, 2026, 07:55:14 PMI also cant find any source for that.Which makes me wonder what happened with the i226. If we can disable one ASPM level for this specific pcie device, why disable it completely in the igc code?
With "but it seems to ben an hardware (silicon) issue to me" i meant i assume that's an non fixable hardware issue.
Why? Because when it would be fixable they have done it by: setting an correct register value or fix the firmware (nvm).
But they have disabled the L1.2 substrate completely in the driver for all newer linux kernels.
Again: That are my personal thought's and assumptions.