RB133c "Connection Tracking" != "Real" TCP Timeout .
Why in "Connection Tracking" i have "Tcp Estabilished Timeout" = 23:00:00, but in "Firewall -> Connections" i have "4d 00:00:00" as Tcp Estabilished timeout?
You do not have the required permissions to view the files attached to this post.
Re: RB133c "Connection Tracking" != "Real" TCP Timeout .
It's a bug and it's not just in rb133c.
Re: RB133c "Connection Tracking" != "Real" TCP Timeout .
Ok... It's a bug...
I rebooted my router after change some settings, and now, without modify the "Connection tracking" values, the TCP Timeout start from 00:59:59 instead 4d 23:59:59...
Maybe a bug that change value randomly every reboot?
I rebooted my router after change some settings, and now, without modify the "Connection tracking" values, the TCP Timeout start from 00:59:59 instead 4d 23:59:59...
Maybe a bug that change value randomly every reboot?
Re: RB133c "Connection Tracking" != "Real" TCP Timeout .
Just the mikrotik team can reply, but this bug exist in 3.5 too...