May I say, that I am a little bid upset especially with the way to communicate this small switch ?
I have a Sky-UK subscription since last December, might switch my existing Sky-Deutschland subscription from another server to this one in 1-2 month and have some colleagues also using Sky Germany, 2 of them already moved to your server. Until know it works fine for me, except some freezers also for my Sky Deutschland colleagues, but this swich was very fast and unexpected (and I am checking the forum very often) what is a kind of unprofessional
Might be considered my problem, that I added the CAID 1833 to the ignore list of SD-receivers for better performance without any advise to do so, but at least all HD-receivers configured with the betatunnel 1833>1702 are not working anymore on SD and HD channels without reconfiguration. At least on the dbox2 and Neutrino Mgcamd 1.31 (ppc_old-version) is not working at all and require update to version 1.35 obviously Mgcamd 1.31 does not work on CAID 1833 (I was not aware but as the screen still remain black after updating the configuration and rebooting the receiver I solved it with an update of Mgcamd 1.31 to 1.35 wit the same configuration files). Of course Mgcamd 1.35 is now recommended but only for some days yet, before you suggest to use Mgcamd 1.31.
Can I accept this change to be permanently ? I have no interest to change configurations now and reconfigure it again in 1,2 or 14 days
For Mgcamd users without modified ignore.list (no ignore.list at all or the one from the forum) it should be fine to remove the replace.list and restart. It might increase performance to add CAID 1702 to the ignore.list but this is not required.
I believe this is also the problem of the Acamd users complaing here: remove the tunneling of 1833 to 1702 (in the first posting of this forum-section you find a posting stuck to the top that still explaines how to create the tunnel > remove it
Also Oscam works fine after changing the CAID in the oscam.server from 1702 to 1833 and removing the betatunnel configuration in the oscam.user. Depending on your configuration also oscam.services and/or oscam.dvbapi need to be updated with the new CAID (or remove the files for a quick solution but might decrease performance a little bid).
I hope this switch will be stable and that server-changes like this are available in the forum some days BEFORE they are performed in future.
This time I know what caused the problem and how to fix it, but I expect a much more detailed information on such changes and solitions/manuals if something like this happens again