Opened 9 years ago

Closed 8 years ago

#3231 closed enhancement (fixed)

cs378x "always up"

Reported by: blueven Owned by:
Priority: minor Component: ! Please select...
Severity: low Keywords: cs378x
Cc: Sensitive: no


Reason for enhancement

Alternative to "always conencted" protocols

Possible impacts on other features

It could be possible add to cs378x the "newcamd like" pramaters: "connectoninint=1" and "inactivitytimeout=-1", so it can be always connected like cccam and newcamd?
Then, as for "newcamd" keepalive, clientmaxidle=0 could be set per user.

Change History (6)

comment:1 by Deas, 9 years ago

why should this be implemented? cs387x does not need such a thing...

comment:2 by blueven, 9 years ago

I test it on loadbalancing, at starting statistics, first ecm time is high due to connection time.
However, why newcamd need it and cs378x not? I think the problem is the same. I test it with newcamd and cs378x, and loadbalancing work bad if reader need to be connected.

If you want i give you a log. But it is easy to reproduce.

comment:3 by blueven, 9 years ago

Hi, working on patch for loadbalancing, i can confirm this ticket.
cs357x does not need connection "always up", obviously, it is udp.
While cs378x needs time for tcp connecting, and i can 100% confirm this time is considered in avg time calculation in loadbalance stats, because the ecm time is affected by tcp connection!

Can someone implement "connect on init" and "keepalive" for cs378x too?

comment:4 by manu, 9 years ago

The main idea of connectoninit was to get the caid of the newcamd connection initialized so oscam can redirect requests as soon as possible (the caid is sent during newcamd logon). Before my patch newcamd users used to set the caid even on client side.
I don't know if cs378x/cs357x also support sending the caid as part of their protocol or just require a hard coded one.

Additional: in oscam all tcp based protocols use tcp keepalive pakets. newcamd keepalive are additional protocol pakets (which don't work)

Last edited 9 years ago by manu (previous) (diff)

comment:5 by Deas, 9 years ago

the camd3 protocol does not use such a thing. if a request matches it is sent. there is no caid exchange on camd3 protocol. if a request can´t be handled a cmd08 is sent back to the client. and yes, the first request is a little bit slower because the tcp connection must be made. but how many ms is it slower?

comment:6 by gismo2004, 8 years ago

Resolution: fixed
Status: newclosed

has been "fixed" in HT patch by blueven!


Note: See TracTickets for help on using tickets.