I’m using ROS 3.3 on a RB133c,
in “Connection tracking” there is a “TCP estabilished timeout” at “1d 00:00:00”, and a “TCP Close timeout” at “00:00:10”.
It’s a normal behaviour if some connections that move from “Estabilished” to “Close status” continue the “timeout” from the current “Estabilished status time” instead of “00:00:10” as specified for “TCP Close timeout” in “Connection tracking”?
Not every tcp connection do this, but sometimes (p2p, for instance) i have a lot of connections in “Closed Status” with a timeout of “23:xx:xx”.
It’s a bug or it’s a feature 
?