Community discussions

MikroTik App
 
User avatar
Flavioweb
newbie
Topic Author
Posts: 35
Joined: Tue Jan 22, 2008 8:52 pm

RB133c "Connection Tracking" != "Real" TCP Timeout .

Fri Mar 28, 2008 1:53 pm

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.
 
npbrasil
Frequent Visitor
Frequent Visitor
Posts: 83
Joined: Wed Jun 02, 2004 8:50 am

Re: RB133c "Connection Tracking" != "Real" TCP Timeout .

Sun Mar 30, 2008 4:47 am

It's a bug and it's not just in rb133c.
 
User avatar
Flavioweb
newbie
Topic Author
Posts: 35
Joined: Tue Jan 22, 2008 8:52 pm

Re: RB133c "Connection Tracking" != "Real" TCP Timeout .

Sun Mar 30, 2008 11:33 pm

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?
 
npbrasil
Frequent Visitor
Frequent Visitor
Posts: 83
Joined: Wed Jun 02, 2004 8:50 am

Re: RB133c "Connection Tracking" != "Real" TCP Timeout .

Mon Mar 31, 2008 1:41 am

Just the mikrotik team can reply, but this bug exist in 3.5 too...

Who is online

Users browsing this forum: No registered users and 48 guests