That seems fine - what I was saying is you can control what you receive from your peers if it is causing a problem on your server - what you did for JSC - services = !jsc you can add other cards/services to your oscam.services and block these off from the peers in the same way where you are getting sketchy clearance from them. I would also suggest that when you have enough on your hop 1 and 2 that you set ccmaxhops to 1 instead of 2.
Posts by musogeek
-
-
sure your right about being a cs, but also sounds very similar to the many re-broadcast systems here in spain. the sly uk package is received with a large 2.4 dish and re-broadcast either via microwave link or in 13ghz band. of course these systems are line of sight .
doubt very much that this was being used here - looks like a house on an estate - can barely see the top of the dish over the roof!
-
think they got the technical facts of this wrong - just looks like a payserver to me - Huge trampoline size dish? no clear shot of it, and to say he was relaying the signal and people were using satellite dishes to receive a signal relayed terrestrially? Did he have his own personal satellite?:snicker:
talk about sensationalised journalism produced so that the masses can understand....
-
You could try reducing the retry limit.
I have loadbalancer set to 1 and I have no issues at all with it, which is why I think it is most likely to do with your peers, but with more tweaking you can help to get it to run more smoothly. -
without loadbalancer set it will send the request to all of your peers and you will find that the fastest response will be the one that clears it - try setting it to 1 again and find out which peer it is selecting, and then if it is freezing, try disabling this peer. Might be that there are issues on their server.
-
post your configs - oscam.conf - oscam.server and oscam.user, and post the nlines you have in CCcam.cfg hash out anything sentitive (of course any peer accounts and readers not needed to be shown either!)
-
if you hash out the ecmwhitelist does it still happen? - i need to see the logs to see what it says when your card stops working.
-
on the link I posted, click the box behind sly digital, and then click the tab above that says oscam.services, and this will generate a file you save and rename to oscam.services.
you can edit re your own packages - bewere unless this was sorted in an update, Oscam limits the sids - think it is either 200 or 400 can't remember which - if you have most channels you can do oscam.services for the ones you don't have and use the ! indicator for negative services - can work better in some situations.
-
Quick question, how do I go about finding the SIDs for specific channels? I've got a weird mix on my Sly card.
I see there was an earlier post linking to something by B16MCC, but that doesn't exist any more.
-
restart everything keep your eye on it and see what the output is if it happens again and post here...
-
Now we are getting somewherebeer10
When you find the ECM length post it here so we can have the finished article - Let us know if you are fully sorted and we can close the thread - any issues with the move to oscam then sure you can use the oscam wiki, search bar or start another thread...
-
has the card been activated? working in CCcam?
-
Display More
I've just tried that as well. Sly works, but JSC still doesn't.
oscam.server
Code
Display More[reader] label = *** card enable = 1 protocol = internal device = /dev/sci1 caid = 0963 ident = 0963:000000 detect = cd cardmhz = 357 # this helps the card run more smootly group = 1 # Oscam has the concept of groups. Only users in group 1 can # use this reader. I'm only using one group. emmcache = 1,3,2 ecmcache = 1 blockemm-unknown = 1 blockemm-g = 1 # these ensure smooth decrypting lb_weight = 101 # for load balancing - can be commented out. [reader] label = jsc card Protocol = internal detect = CD device = /dev/sci0 force_i***** = 1 Group = 2 EMMCache = 1,3,2 mhz = 600 cardmhz = 600 caid = 0603 ident = 0603:000000 camkey = 0000000000000000 camkeydata = 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 0000000000000000000000000000 ecmwhitelist = 0603@000000:34oscam.conf
Code
Display More[global] nice = -1 WaitForCards = 1 logfile = stdout preferlocalcards = 1 saveinithistory = 1 [webif] httpport = 8888 httpuser = admin httppwd = admin httpallowed = 127.0.0.1,192.168.0.0-192.168.255.255 # protocols [newcamd] key = 0102030405060708091011121314 port = 10000@0963:000000;10001@0603:000000 [cccam] updateinterval = 3000oscam.user
Code
Display More[account] user = sly pwd = sly group = 1 monlevel = 0 au = *** card caid = 0963 ident = 0963:000000 keepalive = 1 [account] user = jsc pwd = jsc group = 2 au = jsc card caid = 0603 ident = 0603:000000 keepalive = 1The 2nd user just doesn't show up in webinterface.
have you got the 2 nlines set up in CCcam.cfg as i suggested? one for sly on port 10000 and the other for jsc on 10001
-
I think i did understand what you are trying to do - you have newcamd protocol set in oscam.conf so the way I have always done it is to create 2 users in oscam.user
Code
Display More[account] user = sly pwd = sly group = 1 monlevel = 0 au = ***uk (set this to label of reader) caid = 0963 ident = 0963:000000 keepalive = 1 [account] user = jsc pwd = jsc group = 2 monlevel = 0 au = jsc (set this to label of reader) caid = 0603 ident = 0603:000000 keepalive = 1then the 2 nlines in CCcam.cfg
CodeN: 127.0.0.1 10000 sly sly 01 02 03 04 05 06 07 08 09 10 11 12 13 14 256 N: 127.0.0.1 10001 jsc jsc 01 02 03 04 05 06 07 08 09 10 11 12 13 14 256only use 256 if you have CCcam version 2.1.3 of course
think as you said you are having diffs getting the JSC working will possibly need to see the output
-
Probably not - the following is the straight from wikipedia re HBBTV in the UK'
QuoteIn the UK, most broadcasters have not adopted the HbbTV standard but Freesat, the free-to-air satellite TV service broadcast via Astra 28.2°E, has revealed that the second generation "G2" specification for Freesat receivers will use HbbTV, to take advantage of the digital TV chipsets being developed for that standard (but retaining MHEG compatibility of the first generation Freesat receivers). While the Digital TV Group approved D-book 7, a detailed interoperability specification between digital terrestrial television and HbbTV based products and services.
-
not familiar with i***** JSC card as I use viaccess but from what i have seen that looks the right setup if it is showing as off then we may need to see the output on the status page of webif when you start the server, or the logs.
you have done the right thing in placing the cards each in its own group. If you want to share the JSC card independently to sly then you can still do this by not including the sly group in the user account you set up for the peer who you want to share your JSC card with.
your newcamd protocol is as follows;
which is great if you have 2 sly cards - but you haven't so change it to this;
If you are using nlines to share with then you need the above, and if the shares are external you need to set up port forwarding for said ports in the router.
If you are sharing using CCcam protocol you need to set that up - place this in oscam.conf - delete your existing entry - the update interval defaults at 240 and this is fine.
again for exteranl sharing you need to forward the ports. best change from the 12000 port to something else as 12000 is used to often - prob the same for the newcamd if you intend to share nlines.
your dvbapi is not set up correctly either - if you want to use this, then you need to set the 'au to either '1' to send the emm's to all cards, or you need to set it to the label of your reader - you have entries that say 'lower_card' which doesn't match any of your configs.
use above instead of what you have for user vudvbapi.
also for dvbapi to work you need to add
to your oscam.dvbapi file
on the other entry you have in oscam.user - if this is for internal share then again if you are using au - set it to 1 or the label of the readers you have
then all you need to do is set up user accounts as normal in the right groups.
Code
Display More[account] user = user1 pwd = pass1 group = 1 hostname = (user's ip if you have it) cccmaxhops = 2 cccreshare = 1 keepalive = 1 numusers = 1 [account] user = user2 pwd = pass2 group = 2 hostname = (user's ip if you have it) cccmaxhops = 2 cccreshare = 1 keepalive = 1 numusers = 1 [account] user = user3 pwd = pass3 group = 1,2 hostname = (user's ip if you have it) cccmaxhops = 2 cccreshare = 1 keepalive = 1 numusers = 1above are 3 examples of user accounts in oscam.user - first is in group 1 so will only get sly - second is in group 2 so will only get JSC - third has 1,2 so gets both.
-
post your configs m8 ###ing out any sensitive bits
-
never used a CCcam.cfg switcher before, not sure why you would need to change configs too often - why not just use FTP?
-
on the VTi image (not tried the latest bh yet), the infobar has 'HBBTV' icon. whenever there is a channel where you can get HBBTV, this highlights green. When this happens, a red button press will bring up the fun!
Try browsing through some German channels - I can't tell you what channels work as I am now on an image that doesn't have this. Not too many channels have this, but there is a fair amount on the German channels especially.
-
Found this plugin works really well - does not overwrite existing bouquets, and saves a lot of time!
Easiest way is to unrar and install the IPK
Enjoy....
"here is AutoBouquets E2 28.2E Enigma2 Plugin for BETA TESTING!
(latest version - date 21th August 2012)this plugin has been coded with shell script backend so that it can be run on ANY box from the command line without python. it has a python enigma2 GUI so that you can select your area direct from remote in the plugins menu.
1) first make sure you have dvbsnoop in your /usr/bin/
2) drop the attached files onto engima2 box in the relevant folders.
make sure /usr/script/autobouquets_e2.sh file is executable (chmod 755)3) reboot your box to load the new AutoBouquets E2 plugin into the Plugins menu
3) perform a scan on 28.2e satellite so that you have the latest lamedb service file
4) zap to an active channel on 28.2e so that dvbsnoop can read its stream data
5) select AutoBouquets E2 Plugin from plugins menu and then select your SD or HD area.
6) sit back and watch for 5 minutes as your local bouquets are read from the stream
7) Have fun with you new auto generated local bouquets
8) an autobouquets.log file is generated in the AutoBouquets plugin folder so that you can check processed Services, Positions and ChannelID's.
PS) dont forget to backup your current bouquet files first even though they will NOT be overwritten by this plugin.
PLUGIN and EXAMPLE of the resulting auto generated bouquets direct from the stream with region set as "Granada HD""
