websocket is not an approved protocol, is is currently in the Candidate status with W3C, expecting production routers to support it isn't realistic.
Making a protocol like http, which is stateless, carry a payload the requires the information to be statefull is the issue. From my reading websocket, keep connections active for as long as the application likes, yet Http was never intended to do this, websocket does this to keep overhead down.
What the router is likely doing, correctly I might add, is it monitors all connections, and to prevent the NAT table from filling up with what in essence a stateless connection that by http standards should never be more than a few seconds, after 5 minutes removes the NAT entree
I would suspect most routers have this issue ... when the protocol is W3C approved, then maybe there will be support in the routers to basically diable garbage clean-up for open http NAT entrees, the downside is, it will be trivial to use this method to have DOS attacks as the NAT will never close unused entrees
Updated:
I did some more reading, websocket may never make it to main stream, as I suspected, it's a substantial security threat for a number of reasons, here is a good write on it:
»
asmarterplanet.com/mobil ··· per.htmlAnyhow, there is nothing wrong with the Actiontech router, its functioning as designed to released standards, as it should