Opened 13 years ago
Closed 13 years ago
#1632 closed defect (worksforme)
AU/EMM not working anymore on new builds
Reported by: | zacha81 | Owned by: | |
---|---|---|---|
Priority: | major | Component: | General |
Severity: | high | Keywords: | |
Cc: | Sensitive: | no |
Description
Revision
46xx
Issue Description
After trying some newer builds of Oscam (Linux AMD64) I have noticed that emm is not working anymore for cccam and/or newcamd clients. Clients log in and log message "AU enabled for user XXX on reader YYY" is shown, but WebInterface does not show any AU assignment (readers all show 0 in AU column and AU enabled users all show -1. No EMMs are being processed.
I have been using build 4335 before and AU has been working well on this build until today with the same config. Users logged in, log showed au enabled for user x in reader y and WebIf showed an assignment of users->reader (e.g. Reader X -2, user y -2) and in fact user y was updating reader x.
Attachments (1)
Change History (5)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
r4699.
2011/02/10 0:34:58 B3B43280 c emm reader zhongwah caid mismatch 0B00 != 0500
2011/02/10 0:34:58 B3B43280 c emm reader newcamd skip provider FFF400
2011/02/10 0:34:58 B3B43280 c emm reader newcamd skip provider 022030
2011/02/10 0:34:58 B3B43280 c emm reader newcamd skip provider 022050
2011/02/10 0:34:58 B3B43280 c emm reader newcamd skip provider 022010
2011/02/10 0:34:58 B3B43280 c emm reader newcamd skip provider 022000
2011/02/10 0:34:58 B3B43280 c emm reader newcamd2 caid mismatch 0000 != 0500
2011/02/10 0:34:58 B3B43280 c emm reader newcamd2 caid mismatch 0000 != 0500
2011/02/10 0:34:58 B3B43280 c emm reader newcamd2 caid mismatch 0000 != 0500
2011/02/10 0:34:58 B3B43280 c emm reader newcamd2 caid mismatch 0000 != 0500
2011/02/10 0:34:58 B3B43280 c emm reader newcamd2 caid mismatch 0000 != 0500
by , 13 years ago
comment:3 by , 13 years ago
I want to add that all my readers are smargo smartreaders which are being accessed directly with libusb. they have firmware 1.4 applied. As soon as I turn back to an older binary (4335) emm is working correctly as expected. I have tried a pre compiled version of oscam build 4669 and a self compiled one which I have been building on debian squeeze amd64.
comment:4 by , 13 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Please note that the configuration parameter au in the user section changed some time ago. In current revisions, we also show AU better in the web interface (mouseover and text representation instead of the misunderstandable "-1, 0, 1"). EMM work perfectly for me with newcamd protocol (with mgcamd clients) so I'll set this to closed.
2011/02/09 11:37:21 70A6AE10 c encrypted newcamd:15051-client 192.168.3.56 granted (XXX, au=auto (8 reader))
2011/02/09 11:37:21 70A6AE10 c user XXX authenticated successfully (mgcamd)
2011/02/09 11:37:21 70A6AE10 c AU disabled for user XXX
this is okay, as port 15051 is for caid mapping and emm cannot be processed for that caid.
2011/02/09 11:37:21 70A47E10 c encrypted newcamd:15050-client 192.168.3.56 granted (XXX, au=auto (8 reader))
2011/02/09 11:37:21 70A47E10 c user XXX authenticated successfully (mgcamd)
2011/02/09 11:37:21 70A47E10 c AU enabled for user XXX on reader YYY
this message is okay too, as it has always been, but EMM does _NOT_ work on reader YYY