Bug #2559
OSCAM-TCP-Mode: Port not set correctly
Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2014-12-17
Due date:
% Done:
100%
Estimated time:
Found in version:
2208, 2254
Affected Versions:
Description
When using CAPMT-Client in OSCAM-TCP mode the entered port is multiplied by 65536 and used to connect which obviously doesn't work.
Logfile:
2014-12-17 15:13:04.000 [ ERROR]:capmt: xxxx: Cannot connect to xxx.xxx.xxx.xxx:788070400 (Connection refused); Do you have OSCam running?
Actual configured port ist 12025
When modifing source in capmt.c dividing every occurance of capmt->capmt_port by 65536 connection works.
But obviously this isn't the right solution!
History
Updated by Jaroslav Kysela almost 10 years ago
Updated by - Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|8db7c1328140001323f3c9313adc5379fc1203df.
Updated by Jaroslav Kysela almost 10 years ago
Thanks. The property functions were accessing only first two bytes (it explains value shift if you have a Big-Endian CPU).