Posts by musogeek

Quote from waran

nice mate.

how many peers may be in one cardsharing. i have dm 7020 with gemeni image 4.7. and running cccam 2.2.1

You are limited by hardware, most people have never reached the limit as to what is possible though. As a pointer, you probably won't need more than 20 peers to get all that you want, and if you want to add more, then you might want to add restrictions to the clines keep things more smooth and reduce the load. I have heard of people with 40-50+ peers without problems on receivers with similar specs to yours, but it isn't really necessary, so you probably will never get close to the limit.

One thing you need to remember about Cool TV Guide is that it feeds of your existing EPG information as a front end - it doesn't actually grab any epg info from online or on-air. You need other means to do this, so if you haven't already, best to download CrossEPG and set this up for daily updates.

If your card is being read in Oscam you can try oscam.services, but this has a limit of i think 200 sids.
http://linuxsat-support.com/os…uk-sid-assign-reject.html
If your card is being read in CCcam, you could use sid assign.
http://linuxsat-support.com/ca…sign-auto-assign-how.html
You can also control services in an fline - some info in the below thread on how you can do this
http://linuxsat-support.com/ca…channel-restrictions.html

I fear boxing is heading speedily towards the pits of American wrestling type orchestration. This sounds like a soap opera, a masterplan to get a big payday for who else other than Mr Warren and Mr Murdoch. The rest of the boxing world will be looking at this fight and laughing, where two people fight it out over nothing other than a grudge and money!

Hope you had a good read and found out that the difference between the two lines that you posted is that the second fline will only share your local card, and the first one will share your local and all your hop 1 cards where you have a reshare. Also, both lines allow your peers to send emms to your card and update, and will not offer a reshare of your local.

I never bother sending a cline to my peers with yes or no or anything else because they can change this anyway. Them putting yes or no infront of a line you send them dictates whether they recieve emus from you (softcam keys etc) - but you have restricted this in the fline anyway and are not sending them.

Quote from fulgas

Thank you Ten Below....Where do I upload this file in my DM?

Cheers,

satellites.xml goes in /etc/tuxbox

Quote from waran

F: user1 pass1 1 0 1 { 0:0:1 }

F: user1 pass1 0 0 1 { 0:0:1 }

which of these are good if i do not get any share back from my friedns??

C: noip-testserver.org 11500 user1 pass1 yes --> shall i write yes if i want my cards to be update by my friends.

Display More

The best way to learn is to read. If you read the information on the link I provided, which was painstakingly put together by a dedicated person in order to answer the type of question you are asking, then you will be able to answer the question yourself. If I answer your question, you will take my word for it, and not try to understand why I gave the answer. If you read and understand the information in the link, then you will be able to understand the difference between the two flines in question.

Quote from waran

mate. i read a lot here in and printed a lot from the internet, but i´m in a little confusion. tha is i´m trying to clear out it..

Not sure i could put it any clearer myself - please explain what you don't understand. The points are colour guided to make it easier, and will answer your question.

http://linuxsat-support.com/ca…nes-clines-beginners.html

read the above

httpallowed = 127.0.0.1,192.168.0.0-192.168.255.255

above should do you if you are trying to access it on your local network or localhost - this allows most flexibility for most lan setups

notice that the httpallowed flag can have single ip addresses separated by commas, and ranges (startip-endip) or a combination of both.

the free option is still there if you go straight to this link

https://account.dyn.com/entrance/

Quote

This suggestion was not intended as a dig or moan at anyone or the hard work that goes into sharing any ones work.

Don't worry, it wasn't taken in that way, this section is for suggestions and we welcome suggestions. People who are on this forum a lot who upload files might have seen this thread and may well have taken on board the feedback and maybe spend a tad more time in the file descriptions moving forward. It is a collective effort, so feedback is always welcome.

beer10

This forum is big. There are lots of sections, and contributions come from the public for the public, so by nature, it won't be as organised as a website designed by a business for commercial purposes.

There are sections, which give a clue - i.e. - Navigon Europe is in the Android section. Andriod is a phone or tablet, so you know it is not for a receiver, and it has some instructions as to what to do. Enigma Web TV is in the tools section, so it is also clear enough that you don't use this on your receiver. There are search engines that can fill in the bits that are left out.

A lot of hard work goes in to the forum from a lot of dedicated people, and to ask them to do more than they are already doing isn't too fair. I think as I said before, people should learn to evolve in the hobby, learn to walk before they can run, and not expect themselves to understand everything in a short space of time. But as I said, remember that this is a forum, so we welcome useful contributions from everyone, but we can't dictate what they have to include with an upload. As far as I see it, and as most people do, so long as it is in the right section, and carries a brief description, then this is absolutely fine.

so mouk you need to delete the [cccam] part of your oscam.cfg, make sure the port 12000 is forwarded to your server's ip address (which has to be static) - delete all the account entries in oscam.user

Then read and follow the bits that master G posted - to make it more basic and easy, delete what you have already and replace with the ones that master G has posted in the places he says they need to go. I have never had an extra space between user and password but logically this tells me it could cause problems as well as sync says, but if you are following the advice rather than guessing that what you think is right is right, then you can't go wrong.

Quote from sync

You need to tell CCcam what port you want to use to share to your friends
add below line to your CCcam.cfg with your choice of port then forward that port in your router

Code

SERVER LISTEN PORT : 23456

if the server listen port isn't defined then it will use port 12000 as default.

One wonders if they spent less time waffling they might be on 1.7.5 by now:nosebleed_002:

hehe - wish you metioned that earlier - would have saved me a bit of time on the writeup!!!

If you are sharing with your Vu+ (using the Vu+ as CCcam server) and using the PC Oscam server as just a card reader, then keep the newcamd protocol entry in oscam.conf - you don't need the CCcam protocol, unless you decide to try it out as a server. You might already have an entry in oscam.user to send the card to your CCcam server on your Vu+

You can copy and paste most of the CCcam.cfg to the Vu+ - and you can set the minimum downhops to 0 to benefit from having the server on the receiver, and instead of using 127.0.0.1 on the nline in CCcam.cfg, change this to the IP of your Oscam server. The Server listen port on CCcam.cfg on your receiver should be open on your router and forwarded to your receiver ip. No need to open any more ports

Quote

my advice is use oscam to read the card & cccam to share. there are self install scripts in pc linux tutorials

your advice to someone else from a previous thread about a week ago:snicker:

To be perfectly honest, your advice on that day in my opinion was good advice, because Oscam as a standalone CCcam server has a fair few issues, and you might find yourself on the wrong side of your peers.

If you do want to set it up as a server, then this can still be done on an Oscam/CCcam install. I have an Oscam/CCcam install on my server and I have Oscam running but not being used because I haven't told it to do anything in the configs, and this would be the same the other way round.

the basics of an Oscam server - oscam.conf you need to enable the cccam protocol;

[cccam]
port = 12000
version = 2.1.3
stealth = 1

replace port with the one you have open on your router.

oscam.server would be where you set up your card reader. If you are already using oscam to read your card, then this might already be ok.
oscam.server is also where you place your virtual readers (clines)

consider the following cline

C: anydns.dyndns.com 12000 user pass

in oscam.server you enter this as follows;

[reader]
label = example
protocol = cccam
device = anydns.dyndns.com,12000
user = user
password = pass
group = 2
inactivitytimeout = 30
cccversion = 2.1.3
cccmaxhops = 2
ccckeepalive = 1

note how the 'cline' is broken down in the device, user and password flags.
you can use the above as a format, and change device, user, password and group for each virtual card (cline) you have

also you need to consider how groups work

your entry for your card might have 'group = 1' - and for every virtual reader (cline) you get, you should probably put this in its own group for best control

now there are flines - in oscam these are called user accounts. You might already see a user account set up to send your card to cccam in a cccam/oscam setup.

consider an fline

F: user pass 2 0 0 { 0:0:2 }

in oscam.user you enter this as follows;

[account]
user = user
pwd = pass
group = 1,2
cccmaxhops = 2
cccreshare = 1
keepalive = 1

to break down the above - user and pwd self explanatory - set your user's name and password.
group - this is where you set what real or virtual cards you want to share with your peer - this is why it is good to have a different group set for each entry in oscam.server
cccmaxhops - set this at 2 then you share cards up to two hops away from you
cccreshare - this sets the level of downhops you want to share to - so best leave this at 1 - as this is direct peer and a further share level.
keepalive - keeps alive!!

this is the basics - but if you have a good look around webif - you will pick up a lot more, with direct links to the oscam wiki.

Remember if you are not using CCcam, then you can get rid of the CCcam.cfg, (idea to back it up) - and you can also delete the account in oscam.user that sends the card to CCcam, also you can delete the [newcamd] entry in oscam.conf.

mouk i responded to your older post. please if you are having issues it is no good going back and forth, really you need to be posting your configs so we can see where the problem is - oscam.conf, oscam.user and oscam.server, also CCcam.cfg - hash out any sensitive stuff like boxkeys , passwords etc

I am not sure why you have the cccam protocol set up in oscam.conf, because you are using oscam as your cardreader, not as a cccam server. You should only need the newcamd protocol set up in oscam.conf, and make sure that the port you set in this is different from the server listen port you have set in CCcam.cfg.