Firewall Live View

Started by atom, December 06, 2022, 09:10:47 AM

Previous topic - Next topic
Under the assumption it only occurs rarely, right. And knowing that you can keep the GUI running overnight to actually catch it. ;)

I suppose there is no historic approach to the live log, something the flat file (raw log) is providing, but not very elegantly.

FWIW, I only fear we reintroduce fixed bugs by fixing something that now isn't really broken from a technical standpoint. But not my call anyway. PRs help.


Cheers,
Franco

@franco
I'm not sure I understood you correctly.
it is the current behavior that leaves stale results (hidden rows), potentially cutting off the good ones. in fact, the appearance of normal operation was provided by an overestimated value of the displayed records (in fact, it is now always at least 1000)
due to https://github.com/opnsense/core/blob/a4b5a815c1374840552da2b2c974e2b717bf5a9d/src/opnsense/mvc/app/views/OPNsense/Diagnostics/fw_log.volt#L231

or i missed some?

pr: https://github.com/opnsense/core/pull/6177

Not my call and I don't have interest in going back and fixing the live log in a similar fashion after 22.7.6/22.7.7 complaints. Either the live log is missing a clear description or the implementation doesn't really do what it's supposed to do.

Patching it again and again is certainly a bad sign.


Cheers,
Franco

looks like i really missed something in the history of the question  :-[
sorry then

Hi Franco,

Sometimes I get errors sent from applications running at some point and I only know the port and address.
So far I have been able to use the Life View to filter the data without having to look at the screen all the time.
If the data was only visible for a few seconds, then I would have to look at the log all the time and couldn't do anything else.

Regards,
atom