Opened 11 years ago
Closed 9 years ago
#3226 closed defect (expired)
ccckeepalive: reader reconnect needed
Reported by: | blueven | Owned by: | |
---|---|---|---|
Priority: | major | Component: | General |
Severity: | medium | Keywords: | rto, dyndns |
Cc: | Sensitive: | no |
Description
Revision
All
Issue Description
If a "cccam ext" reader change his ip (it has dyndns), oscam obviously cannnot detect it, and ecms got timeout by reader.
If ccckeepalive = 0, reader got disconnected reson rto, so it can reconnect with right ip.
If ccckeepalive = 1, the reader got not disconnected, so timeouts go on for always ultil manually restart of reader or oscam process.
With camd35 tcp, rto work ok.
With newcamd, i cannot test.
When the issue occurs
The issue occurs when reader cannot answer correctly, and ecm requests timeout.
How the issue is reproducable
To reproduce the issue, use a cccam ext reader, eg. xxxx.dyndns.yyyy, with ccckeepalive=1. After reader is correctly connected, disconnect and reconnect adsl plug of reader, so xxxx.dyndns.yyyy point to a new ip.
Oscam does not detect reader change his ip, and ecm requests to reader got timeout!
But reader does not disconnect for reconnect with right ip!
While, with cs378x and cccam ext with ccckeepalive=0, after some time reader is disconnected reson rto, and reconnected with right ip.
Note that with cccam "O" there isn't problem thanks to cccreconnect parameter, that reconnect reader after timeouts. But cccreconnect parameter is ignored when cccam ext protocol is used.
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Does this really happen in current versions? Normally I would expect TCP_KEEPIDLE to take care of this (this should detect network problems within 15s and not with a rto then) unless you have some scary old system which does not support it.
comment:3 by , 9 years ago
Resolution: | → expired |
---|---|
Status: | new → closed |
For better explanation, the issue occurs when ccckeepalive=1 and cccam ext protocol is used.
I don't tested the behaviour with newcamd protocol.