Posts by s3n0

For a proxy reader (as a softcam client), request the softcam client configuration from the softcam server administrator. He knows best how it should be set up - depending on the server settings used.

3.1.201103

Added support for non-standard userbouquet files (lowercase) in Enigma, after using the DreamSet application:

- unfortunately, DreamSet uploads userbouquet files with lowercase characters to the set-top box and therefore no matching service reference codes are found

- the process of comparing service reference codes from userbouquet files will no longer be case sensitive

Did you set up the tuner again after upgrading the Enigma / OpenATV version ? This will probably be necessary due to different software drivers and therefore different satellite / terrestrial tuner settings. Try entering the tuner settings in your Enigma / OpenATV and set this tuner again. Then reboot and try scanning the satellite channels again.

At least someone thanks :).

Great.

Many users do not even write whether the problem was solved or how they solved the problem :) - which would help other users if the same problem occurs.

balanga:

I recommend removing / reinstalling the feed-source for Softcams if you use it. Instead, it is better to install Oscam via an IPK / DEB package (in the OpenATV case it is an IPK package), because softcam feed-sources sometimes cause problems in OpenATV when updating Enigma. So, install Oscam either an IPK package designed for OpenATV or use the manual installation method I described in my short article (link mentioned below).

Check this my short article: Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages

1. Back up the current functional configuration of Oscam (if you don't have it yet)
2. Remove all softcams from your set-top box:
   
   top | grep cam # then press the CTRL+C keyboard shortcut to STOP the displaying info
   killall -9 <process-name>
   
   opkg update
   opkg list-installed | grep cam
   opkg list-installed | grep softcam-feed
   
   # if there was found some softcams, remove it (you need use their package names):
   opkg remove <pckg-name> <pckg-name> <pckg-name> ...
   
3. Install Oscam either an IPK package designed for OpenATV or use the manual installation method I described in my short article (link mentioned above)

Yes, FTA channels do not need a softcam. FTA channels work without Oscam.

If OscamWebif works, then you can try replace the another version of Oscam (newer or older version).

It's also likely that the configuration has been lost from your old Oscam and that you're working on a basic configuration. And that's why Oscam behaves differently.

It looks like Oscam didn't start after booting Enigma / Linux. Thus, Oscam is incorrectly installed or the Oscam configuration (oscam configuration directory) is lost / deleted. You need to reinstall Oscam in OpenATV and also restore your original Oscam configuration files to the appropriate folder.

OK try to verify that the configuration files are in the correct folder, because if you used the ipk / deb installation package, it could also create default config.files in another folder and then this folder will be used in Oscam as well.

Read more about configuring the configuration directory here:

find oscam location

I add that the "oscam.server" file is not enough. The "oscam.conf" file is also important, as a basic configuration for Oscam. Or also the "oscam.user" file for setting up a dvbapi local user. Or, if you use CAIDs in your config files, the "oscam.dvbapi" file (for setting CAIDs priorities) may be also important.

Then it's not a router. This is a commercial box in which the firmware has been modified for IPTV needs. It is quite possible that some types of communication will be blocked by the router - this is a non-standard network device - which means that the firmware is modified by SKY.

Even so, I think network communication should always work.

Try resetting the network interface in the set-top box, using the GUI MENU (using the RCU) in your Enigma. Maybe it will help. In some Enigma distributions you will also find other options (via the GUI MENU), such as a test of the network interface or also test of the internet connection.

Do you have a reliable cable between the set-top box and the router ? Try exchanging it with new one. Aren't the broken copper wires in the cable broken or rusted ? Or do they not have rusted contacts in the RJ45 connectors ? Between the connector pins and the copper wires, if these connectors are badly crimped, then over time, rust can form due to humid air. There may also be an air gap, due to frequent expansion - the effects of heat and cold. The contact then passes through a spark and not through a junction of two copper metal parts. So is the cable reliable ? Try replacing it. Of course, there may also be an error in the router's connectors. If possible (due to limited connection to the IPTV socket), try to pass the cables in the router to other sockets (LAN ports).

What is this for a nonsense ? The WiFi router is designed to connect + routing communication between multiple devices on a local network. Subsequently, it can also NAT communication to / from the internet. The router must be able to connect and communicate multiple devices. The only condition is a different MAC address and subsequently a different IP address (if it is set manually, it must be different, there must be no identical IP address in one LAN).

Hi.

Yes, the error is probably somewhere in the Oscam configuration. Maybe the new Oscam did not find configuration files. Simply put, the configuration was not found in the new version of Oscam.

Maybe you reinstalled Oscam with deleting the configuration files.

Maybe you use a folder for configuration files that is subordinate to the one added by the new Oscam installation package. Then, when running Oscam, it finds the appropriate folder in a certain order (https://trac.streamboard.tv/os…owser/trunk/oscam.c#L1662). So if he finds another folder with the configuration, he will use the one he found first. Of course, the directory for configuration files can also be specified with the "-c /directory" argument, but if you don't, the algorithm must find the directory automatically after running Oscam.

Maybe you only have bad syntax in the configuration files and the new version of Oscam cannot load the configuration files.

Hard to advise if you don't give more details about your problem.

What exactly version of Oscam do you use ?

Where is some debug log ? From Enigma or with Oscam ?

Have you tried reinstalling Oscam ? After updating OpenATV, you may need to update Oscam.

Your Oscam settings may have been deleted. Upload them to the set-top box again, if so.

What exactly do you mean by the SKY router ? I don't know the router in general either, uhm.

However, the local computer network must work under all circumstances, ie if everything is fine :).

You can check the functionality of the network directly in the Web-GUI of the WiFi router or via the Enigma settings, where you will certainly find information about the status of the network or the possibility of restarting it.

On Linux systems, the operation of computer networks is a little more complicated (safer and more complex). On some Enigma distributions in conjunction with some WiFi routers, a situation may arise where the internet or local network in a Linux set-top box stops working completely.

I've experienced this situation about 5 times already, when nothing really helped. I had to turn off the router, turn off the set-top box, to be sure, I also disconnected the LAN cables. Then I turned on the wifi router and waited for it to boot for 2-3 minutes. Then I connected the LAN cables and turned on the set-top box as well. After booting the set-top box, the local network in the set-top box was functional again. The problem was somewhere on the HW level or in the NIC hardware drivers in the set-top box. It can be said that there was a problem of incompatibility in the ISO / OSI communication model, between the router hardware and the set-top box hardware (which is of course controlled by the software - ISO / OSI model). I don't know if it will help. But if it's one of the mistakes I think it might help. Otherwise, it is your fault and not your hardware fault :P.

Quote from .atari.

It’s obsolet

disablecrccws = 1

It’s enough

disablecrccws_only_for = 0E00:000000,0500:030B00,050F00;098C:000000;09C4:000000

Yes, but this only needs to be enabled for some providers (CAIDs).

Which provider / CAIDs does czesioczesiek use at all ?

LOL, read my entire post and follow the colors in the text.

The c-line format is:

C: hostname_or_IP port_number your_username your_password

Translated into oscam.server file:

[reader]

label = remote_card_reader

protocol = cccam

device = hostname_or_IP,port_number

user = your_username

password = your_password

cccversion = 2.1.3

audisabled = 0

However, this information should be provided to you by the administrator of the softcam server.

It doesn't matter who you get Oscam from. It is important that it is a suitable version, a suitable build according to your needs and a suitable version for your chipset / CPU type (architecture). Then upload the appropriate configuration files to the appropriate folder.

Hi.

If the oscam process is still running, it's probably still in memory. Kill him with the command:

killall -9 oscam

As for the oscam configuration, there is nothing easier than using a search under Linux, for example:

find / -type f -name "oscam.server"

Finally, you can also find the directory in OscamWebif -> Files -> oscam.version -> ConfigDir. As mentioned above.

If the oscam directory was not specified by the -c /directory argument in the "trigger" of the softcam, then the Oscam algorithm will look for the configuration itself in the following folders:

1664        static const char* confdirs[] =
1665            {
1666                "/etc/tuxbox/config/",
1667                "/etc/tuxbox/config/oscam/",
1668                "/var/tuxbox/config/",
1669                "/usr/keys/",
1670                "/var/keys/",
1671                "/var/etc/oscam/",
1672                "/var/etc/",
1673                "/var/oscam/",
1674                "/config/oscam/",
1675                NULL
1676            };

SOURCE CODE: https://trac.streamboard.tv/os…owser/trunk/oscam.c#L1662

C-Line to oscam.server:

How to setup Oscam.server on H 7 C box

Hi.

1. difficult to judge, because only your softcam-provider sees what its softcam-server shows (your client's connection errors) ... but you could fit the whole line into the discussion with the error visible in OscamWebif / LiveLog ... my guess could be incorrect enforcement of version 2.3.2 of the protocol, which still does not work correctly, because the final version of cccam is still determined by the softcam server... shouldn't there also be a CAID number determination ? usually there should also be a CAID determination in oscam.server for external softcam-providers... are you sure you forgot to insert it there ?

2. disablecrccws settings are only for physical card readers ... if you do not own a card reader, then softcam-server (i.e. NOT softcam-client) will take care of ignoring CRC for some CWs... at the same time, what master G wrote applies - if you do not use German satellite broadcasting (for example, provider SKY DE), then ignoring many CRCs also has no meaning.

3. try to check the recommended configuration again from your softcam-provider and if that doesn't work, try what I wrote in point 1. that is, remove the cccversion configuration item ... if you don't use Oscam as a server, you could try to install instead of Oscam and use Cccam (configuration via C-Line) ... if the Cccam client does not work, then there is probably an error on the side of your provider, or in the network communication (but please also show us the error that is displayed in your current OscamWebif !!!)

So turn off the VPN network for "picon.cz". If you use a VPN network, you probably also have the internet in your box. Set up a network policy for the VPN and you're done.