Default deny usually means state tracking failure. Try adding a separate rule for sloppy or no state tracking (under advanced) to see if these go away.Cheers,Franco
I have also seen Default state rules that should have passed. I was assuming that these were RST or FIN packets that were retried and passed. The firewall log view no longer shows the TCP flags. Need to put that back. Along with adding an allow rule. Or just bring back the Normal log as an additional option. I like the live view, but I miss the normal view.
Does the TCP / UDP stream time out too?Cheers,Franco
Quote from: dcol on February 12, 2018, 11:16:09 pmI have also seen Default state rules that should have passed. I was assuming that these were RST or FIN packets that were retried and passed. The firewall log view no longer shows the TCP flags. Need to put that back. Along with adding an allow rule. Or just bring back the Normal log as an additional option. I like the live view, but I miss the normal view.Adding a selector for all shown properties of the log entry is not a large problem...
Do you mean for the devs to add the selector, or does this exist now?
Disable NAT and see if streaming improves.I suspect that NAT may be the issue because the way NAT is handled seems to have changed starting with version 18.1. Correct me if I am wrong Franco. Try disabling NAT altogether. Put it back later if you need it for other things.And if you want better help, post your firewall and NAT configuration. Use Aliases to hide IP's.More than likely a configuration issue since no one else has complained about streaming.
As far as the nobody else is complaining, it does not mean it is not happening.
Quote from: Davesworld on February 13, 2018, 12:39:56 amAs far as the nobody else is complaining, it does not mean it is not happening.I don't think that's what anybody was implying. I confirmed your traceroute issue, but around 12:52 a.m. I have no way to sanely verify it against an older version. Cheers,Franco