Oscam > #5297 with blue card.

[Dave001]

Hey,

Any one running Oscam higher then build #5297 with a blue card?

I'm running a Debian PC server, not sure if it's an Oscam or hardware issue.

Thanks,
Dave

[Strada916]

whats the error you are getting?

[Dave001]

Any version higher then #5297, clients using the NDS card can't connect to the server. Card initialises and comes up as Card OK.

Irdeto clients work fine still, just no NDS.

[Dave001]

Just went back through the logs, and it seems that newcamd isn't initialising the port/card, this part is missing from the later version logs.

2011/07/12 20:50:47 B761B6C0 s newcamd: initialized (fd=8, port=12340, crypted)
2011/07/12 20:50:47 B761B6C0 s CAID: 090B
2011/07/12 20:50:47 B761B6C0 s provid #0: 000000

The card is found so it looks more like an Oscam change, then a Oscam/hardware incompatibility.



Thanks,
Dave

[nexus]

I checked out revision 5620 and compiled for mips today after seeing your post. Serving my bluey to mgcamd running on the same box.

No problems so far. Maybe it's been fixed.

[Dave001]

Hey Nexus,

I just compiled 5620, and still have the same problem.

So far I've tried 2 different PC's (Pentium 4 and Socket A), but both where loaded with Debian 6, might have to go back to Debian 5 and see if that cures it.

Thanks for the reply mate,
Dave

[xfiles_2007]

hey mate i logged an issue with the forum to do with newer versions of oscam on a pc... i think its the config files - get a new set or ones based on the build from the web interface... and give it a go...

basically my issue is no connnection to the oscam server ..packets getting lost... i havnt had a chance to test out my issue with oscam generated config files.

hope it helps

[Vic]

5367 works fine here on Vu+Duo

[Dave001]

OK, found the problem.

Looks like they have made a change to the newcamd section of oscam.conf from #5298 on.

I've always used:
[newcamd]
key = 0102030405060708091011121314
port = 12340@090B:000000
port = 12341@0626:112233

Had to change it to:
key = 0102030405060708091011121314
port = 12340@090B:000000;12341@0626:112233


Thanks for the help every one.

Dave

[nexus]

OK, found the problem.

Looks like they have made a change to the newcamd section of oscam.conf from #5298 on.

I've always used:
[newcamd]
key = 0102030405060708091011121314
port = 12340@090B:000000
port = 12341@0626:112233

Had to change it to:
key = 0102030405060708091011121314
port = 12340@090B:000000;12341@0626:112233


Thanks for the help every one.

Dave

As far back as revision 1 the syntax allows for multiple port numbers to be defined on the one port = line but multiple port = lines were also allowed.

Due to changes made in revision 5298, multiple port = lines are still allowed but only the info in the last port = line is retained.

I don't think that was the programmers intent since he doesn't mention it in the changeset message, only refactor parameter parsing to make it more threadsafe.

Also if that was the intent then a warning about multiple port = lines should have been included when parsing.

Worth mentioning in one of the tickets that have been opened on the matter.