Mag 254 warning message

That link only has the latest firmware, which is blocked. It doesn't provide a download option for the older firmware versions.
 
That link only has the latest firmware, which is blocked. It doesn't provide a download option for the older firmware versions.
I couldn't say mate as I don't use mag box I typed firmware for mag boxes and that's what it come up with sorry
 
I'm struggling to find somewhere to download an old version of firmware for my Mag349. The current version is blocked, and the only b=version I can download form the Informer website is the blocked version. Could anyone please provide a link to an old firmware / image update version please?
can you not roll it back in the software update ??
 
I'm struggling to find somewhere to download an old version of firmware for my Mag349. The current version is blocked, and the only b=version I can download form the Informer website is the blocked version. Could anyone please provide a link to an old firmware / image update version please?
There is a fix out for this now.

you wanna share the links then ??
 
Any fix for mag254? I downgraded firmware but to 2016 version. Can't find anything else higher as it doesn't let me flash the firmware?
 
NOT MY WORK!!!
Defeating the Infomir/MAG Portal blocking
clip_image001.gif


I've spent the last few days digging around with Wireshark + custom firmware to see how this was working, and it turns out it's quite simple and can be removed from all current firmware on all models that I've tested (250/254/256/322/324)

We could, as people currently are, keep changing portal URLs - but this is not sustainable and as the box is phoning home on every boot, is more than likely just making it easier for Infomir to just re-block on the next wave of updates to the blacklist.

At boot the box performs the following:

· DNS lookup for NTP server

· Contact all NTP Servers found

· Executes the script /etc/rc.d/rcS.d/S98stbapp (which then launches stbapp - the browser that displays your portal)

· DNS lookup for mag???.dcbs.infomir.com

· Encrypted communication with mag???.dcbs.infomir.com

· Saves result of this communication as /mnt/Userfs/data/dls.backup

· Displays portal selection page

· If portal is blocked, it then loads and displays the error message (which is stored in the javascript for the Inner Portal - so we can edit this if we choose)

· Otherwise load portal as normal

Once dls.backup is stored in the box, it will continue to block all currently known portals on the blacklist even if Infomir's server is unreachable. /mnt/Userfs is not wiped on firmware restore either, so it will persist between versions unless we wipe it.

This means we have two tasks to perform:

· Patch stbapp OR the hosts file to block the blacklist server

· Erase dls.backup to prevent cached lookups

Personally I favour patching stbapp, as this ensures it's impossible for it to somehow slip through (since it'll be looking for the wrong server.) But in the current firmware versions both methods seem effective.

Both of theses tasks CAN be done by hand, but the easiest way (especially for larger providers) is to build a custom firmware that users can just load from a USB that will both patch the problem and prevent Infomir from pushing any more automatic updates to that box.

For those comfortable making the change and would rather do it themselves the details are below. If people need them, I can build patched firmware for the boxes that people need, but won't have the time to build and upload them before probably Sunday evening. (Pending recommendations of a good anonymous file host)

To edit the hosts file (/etc/hosts) add the following line (replace mag324 with the correct model for you):

127.0.0.1 mag324.dcbs.infomir.com
To patch stbapp, open /usr/local/share/app/stbapp in a HEX editor, search for

dcbs.infomir.com
and make ANY change to the domain name (without changing the length AT ALL)

Finally to ensure that the dls.backup will be deleted after flashing your custom firmware than add the following line to /mnt/Userfs/data/dls.backup before the line that launches stbapp:

/bin/rm /mnt/Userfs/data/dls.backup
If all the above has been done correctly, then all previously blocked portals will now be accessible again, and no future blocks will have any effect either.
 
Registered over here as Reddit apparently killed my post as "Not Safe for Brand"

Annoyingly I'd just finished linking the finished firmware for the MAG250/254/256/322/324 when they took it down. I can re-post the entire thing here, but before I do I thought I should check that I'm not going to be breaking any rules by doing so?
 
Registered over here as Reddit apparently killed my post as "Not Safe for Brand"

Annoyingly I'd just finished linking the finished firmware for the MAG250/254/256/322/324 when they took it down. I can re-post the entire thing here, but before I do I thought I should check that I'm not going to be breaking any rules by doing so?

Nice to see you. I hope you don't mind me quoting your work. I don't know if you are allowed or not but I hope so. There are lots of other images for download so I hop it's ok.
If you can't post could you PM me the links.
Thanks
 
Nice to see you. I hope you don't mind me quoting your work. I don't know if you are allowed or not but I hope so. There are lots of other images for download so I hop it's ok.
If you can't post could you PM me the links.
Thanks
I've PM'd you with the links for now, and if I'm allowed then I'll post the files here publicly. I have no issues with you quoting my work at all (and it's good that you did since the original thread was removed) The further people spread the information the better. I'm pretty wiped out since I've been building firmware all day, but I'll post the extra info I added since your quoted version at some point tomorrow
 
Just a thought - - - has anyone attempted to use their router to block dcbs.infomir.com
ie enabling the block in the /etc/hosts of the router rather than the MAG itself ? (typically most routers have this type of 'blacklist' facility; even ISP supplied devices).

Might be an easier fix for many people, and might be a good prophylactic for people who are not (yet) experiencing difficulties with this issue.

Touching wood - my own provider is so far not effected by this, and as my ISP doesn't undertake any blocks or restrictions I am not so sure that any testing that I might undertake would be wholly productive or otherwise just produce some false-positives, but I am aware than many people are under the cosh, particularly when the EPL games are underway.
 
Just a thought - - - has anyone attempted to use their router to block dcbs.infomir.com
ie enabling the block in the /etc/hosts of the router rather than the MAG itself ? (typically most routers have this type of 'blacklist' facility; even ISP supplied devices).

Might be an easier fix for many people, and might be a good prophylactic for people who are not (yet) experiencing difficulties with this issue.

Touching wood - my own provider is so far not effected by this, and as my ISP doesn't undertake any blocks or restrictions I am not so sure that any testing that I might undertake would be wholly productive or otherwise just produce some false-positives, but I am aware than many people are under the cosh, particularly when the EPL games are underway.

I might be wrong but if you are saying stop the MAG from being contacted by Infomir at the router. Is it not the case that the box contacts Infomir and not the other way around? Can you Block an outgoing communication at Router?
 
You can on some routers block outgoing connections, but reliability varies.

It's important to note that it's not dcbs.infomir.com you need to block, but mag???.dcbs.infomir.com, where ??? is the model number.

It's also important to note that if the box successfully reaches that server even once it stores the list locally so any sites in it will still be blocked, which is why a patched firmware is the optimum solution (we can make sure that it will never reach the server under any circumstance by patching stbapp rather than the hosts file, so it will never find any of Infomir's servers that are hardcoded into it.)

I also was not able to see what data is transmitted to Infomir during this process, so I definitely favour going for a 100% guarantee that the connection can never reach them under any circumstances
 
I might be wrong but if you are saying stop the MAG from being contacted by Infomir at the router. Is it not the case that the box contacts Infomir and not the other way around? Can you Block an outgoing communication at Router?
Yes you can. In much the same way as explained above by @hearts by doing it within the MAG itself, you can do it using your router - - they basically work the same way when all said and done
 
You can on some routers block outgoing connections, but reliability varies.

It's important to note that it's not dcbs.infomir.com you need to block, but mag???.dcbs.infomir.com, where ??? is the model number.

It's also important to note that if the box successfully reaches that server even once it stores the list locally so any sites in it will still be blocked, which is why a patched firmware is the optimum solution (we can make sure that it will never reach the server under any circumstance by patching stbapp rather than the hosts file, so it will never find any of Infomir's servers that are hardcoded into it.)

I also was not able to see what data is transmitted to Infomir during this process, so I definitely favour going for a 100% guarantee that the connection can never reach them under any circumstances

As it happens I agree with you 100% - - - patched firmware is a way better answer particularly provided that the process of flashing it for the average user is made easy enough, but if anyone needed a quick fix then a couple of minutes spent with their router might well pay dividends in the future.
 
If your a reseller or have the pro account with xtream then it looks like they have made custom firmware for mag boxes
Screenshot_2019-01-14-08-17-20.png
 
If your a reseller or have the pro account with xtream then it looks like they have made custom firmware for mag boxes

Interesting that you can't configure foreign portals on their version - I'm guessing therefore that they haven't completely removed the block, or they're using it as an opportunity to lock down the settings at the same time. (Which makes sense as if you're going to release a firmware for one thing, you may as well make other changes you need/want at the same time)

Pending approval, I'll link to the firmwares I released yesterday that don't lock you in to anything, but do remove the block completely.

EDIT: As now run by the mods, the files for the boxes in the table below are all in a zip located here: https://anonfile.com/w39c38qdba/NoBlock_zip

EVERYONE has my full permission to redistribute these as you see fit. If anyone has any questions, problems or suggestions than let me know and I'll respond as fast as I can!

Versions and MD5 checksums for what I have are below - all built from the latest official Infomir firmware
versions.PNG
 
Last edited:
Back
Top