Posts by musogeek

    So why are you asking a question when you already know the answer?


    a cline is a link to a server who is either hosting the card, has a reshare of the card located on another server. Ultimately it is the legal sub card that is unlocking the channel.

    do a bit of googling about ways to kill trees! - Once it is dead then the person responsible for it might see the need to chop it down! - think a raid with a chainsaw will be a bit too obvious:hell_boy:

    done it several times... strange one, not one person can connect to me.. i checked port forwarding,, even do i opened port,, its telling me cs port is closed.. i opened other ports to try and de opened .. but port i need to cardshare wont open..



    So seems you know the answer - your port is closed - maybe a couple of pointers now as to what your router is might help us help you - not sure what is going on if you say your router says the port is closed, the first post you say that the router is fine, but it will open all ports apart from the one you need? Have you checked the IP address on your server to ensure you are trying to forward the cs port to the right IP address?

    1) If you are using Oscam + CCcam - usually, Oscam is solely used as a card reader, so peer's clines wll go in the CCcam.cfg
    2) Same as above - Yes - in CCcam.cfg
    3) No - if you need this, then stick with Oscam only, as CCcam.cfg will mean you will lose that first hop and only be able to share the cards where you have a reshare. Oscam is able to ignore reshare levels, although I would not say it is a good idea to ignore reshare for 3 receivers if they are being used at the same time, as your peers might not be happy about the load you are putting on their servers. Ignore reshare should just be used imo for one local receiver and never for an external share.

    give us a bit more info mate such as config files - oscam.user - oscam.server and oscam.conf, and CCcam.cfg - hashing out anything sensitive - I assume you are using Oscam to read the card and CCcam as the server, and the card and server are on same device (as opposed to receiver reading the card and PC server?)

    If there is anything specific you want to know then ask the questions if you cannot find the answers elsewhere, what I was getting at is from my own knowledge of Oscam, CCcam and all else - there are gaps in my knowledge because for me I will decide what I want, and then try to find the tools and the functions in the tools to achieve my goal.

    Quote

    F: <username> <password> <uphops> <shareemus> <allowemm> ( { caid:id(:downhops), caid:id(:downhops), ... } { caid:id:sid, caid:id:sid, ... } { begintime-endtime, ... } ) hostname/ip address


    So the answer to your question is yes. Remember to define the provider id as well as the caid if there is more than one provid for the caid, otherwise you might block out more than you intend.

    Consider what a dyndns address is for. You set up a dyndns address because your ISP will usually give you a dynamic IP address rather than a fixed address. This isn't good for a server as it is impractical becuause whenever it changes you will have to inform your clients. Dyndns or similar service will direct the dyndns address you give to your clients back to your server, but for this to work you need to tell your server to send your IP address to the dyndns service. Your router may well have a setting where you tell it to update the dyndns service each time your IP address changes.


    When you are working inside your own network, you will not need to use the IP address that your ISP gives you, as this is your address to the outside world. Each of your devices inside your own network will, or should have a local IP address, often following the following format; 192.168.X.X - the first of the 2 X's will usually be common on all your devices in your network, and the last X should be a unique number for each device. You can either use dhcp to assign this, or you can set this up manually for each device either on your router (using the mac address of your devices) or by disabling dhcp on the devices and manually inputting the IP address and other settings. Your server device should have a fixed local IP address, as you will need to forward the port (again in your router settings) you give to your clients to a defined fixed IP address on your network that directs it to your server device.


    When you want to access one of your devices inside your network from inside your network, you will need to type in the local IP address (192.168.x.x) of the device in your browser, FTP client or telnet client etc, the port that the protocol is using (if different from the default) and then input the username and password (if it has one).


    If you wanted to access your network from outside your network, then you can use the dyndns address, but it will only allow access through ports that you have forwarded, and beware if you do this and don't use strong passwords, your network will be open to hackers!


    hope this helps!

    Think what you need to do is decide what you want out of it before deciding what you need to know. Oscam has many features, but if you don't need them, then you can save that learning curve until you need to go there. There is no point learning to drive if you don't want to get a car!

    That isn't right, have a look again at what Ten Below is saying -

    Quote

    0963:0:0 would block it all together


    You are blocking your sly card, so you have to add the sly card to your fline as explained. It will block the sly card and allow all else through.

    to be honest if your peer is not controlling his share and is sharing it 8 hops away then there might be so many people trying to use his card that it bottlenecks and becomes unstable - card and server alike.

    when you say he is getting nothing from you - do you mean that he is not clearing nothing or that the share you are giving reports no cards? If it is the former then it might be the quality of the server who has the reshares. If you have a limited about of peers on your server then it is less likely that there will be enough going on to maintain a good service.

    turn off, remove all external USB devices - turn on - go to menu - setup - vix- mount manager - green button to set up mount - and mount it to /media/hdd - and press green to save, then restart system. Only things I can think of if this doesn't work is if the filesystem for some reason isn't compatible, and that when you update from Vix 2.x to 3.0 - it will not be compatible with any backup you have done from your previous install, so if you have used your settings backups from your earlier version it will break the image and you will need to reflash.

    scrap that it doesn't seem to be working - I was going by something I found on the net but indicting a service seems to block rather than allow. Seems you might well have to block everything else off rather than define what you want, which can be done, but you will have a long fline!


    i got my original info from a guide - but it contradicts the info that is noted on my CCcam.cfg



    the above you can test - but it might be wrong - the following is more likely to be correct;



    both these guides seem to contradict one another - but you can use both of them to try out what you want to do - as I said, it is possible, but you might need to define the ones that need to be blocked rather than what doesn't according to the second guide.


    You could always use Oscam as your server - it is much easier to restrict shares with Oscam.

    Code
    F: user pass 0 0 0 { 0:0:2, 0963:000000 } { 0963:000000:C5A8 } { }


    Never restricted the channels to this extent, but the above should work i think, provided Racing UK is on your local - above is sharing your local only, hence the first number is set to 0 to tell it to share no hops.

    racing uk (C5A8) ECM hex length is 69 - add 69 to your ecm whitelist if it is not already there


    If that doesn't work or that is already on your whitelist, try doing a rescan - didn't show your logs so not sure if this could be the issue.