MAG Box IPTV Setup 2026 — Stalker Portal & MAC Configuration – November 2026

November 5, 2026 refresh: this edition re-runs a per-carrier DNS playbook for Algérie Télécom (Idoom), Djezzy, Ooredoo and Maroc Telecom lines, a new section on 1472 MTU sizing for PPPoE lines with the exact ping test to confirm your ceiling, a three-portal boot bench re-run from early November, and five new troubleshooting rows, including “portal works in a phone browser but not on the box” and 4K channels that play at 1080p. The portal menu path is unchanged, because Infomir keeps the Linux MAG firmware menus backward compatible.

What Is a MAG Box and How Does the Stalker Handshake Work?

A MAG box is a Linux set-top box made by Infomir, a manufacturer that has shipped middleware boxes to IPTV operators in more than 150 countries. Unlike an Android TV stick, it does not run apps from a store. It loads one thing: a middleware portal, which in practice is almost always a stalker portal endpoint hosted by your IPTV provider.

The handshake works in one direction. When the box boots, it sends its MAC address to the portal server. The server checks that address against its subscriber list. If it is registered, the server pushes the channel list, the EPG and the VOD catalog to the box. If it is not registered, you get an error screen or an empty portal. There is no username and no password. The MAC address is the entire security model.

That matters for setup because most MAG problems are not box problems. They are registration problems. If the portal URL is right but the MAC is not on the provider’s panel, nothing you change inside the box will fix it. Register the MAC first, then configure the portal, then only then chase network settings.

What You Need Before You Start

• The MAC address of your box. It is printed on the sticker under the unit. Infomir hardware MACs start with 00:1A:79. Photograph the sticker before you mount the box behind a TV.
• A portal URL from your provider. It usually looks like http://portal.example.com/c/ or ends in /stalker_portal/c/. Without a provider yet, our daily-refreshed stalker portal codes list publishes active URLs with pre-registered MACs.
• An M3U playlist only if you are comparing routes. A MAG box cannot load an M3U playlist by itself; that workflow belongs to Android and PC players. If you want the M3U side, our free M3U playlist database covers it, and the device choice guide explains which route fits which box.
• Ethernet first, Wi-Fi second. The MAG 254, 322 and base 420/424 have no internal Wi-Fi. Even on the 424w3 and 540w3, Ethernet is the single biggest stability win, as the lab section below shows.
• 10 minutes. Once the network is up, the actual configuration takes about three minutes.

Portal URL Setup, Step by Step

The path below is the same on every Linux MAG firmware, from the 254 to the 540. Button names shift slightly between generations, but the menu structure does not.

1. Connect the box to your router with Ethernet and to the TV with HDMI, then power it on.
2. Wait for the loading screen. If no portal is configured, the box lands in the internal settings menu on its own. If it tries an old portal, press the SETUP button (gear icon) on the remote.
3. Open Settings → System Settings → Servers → Portals.
4. Select Portal 1 name and type a short label, for example main.
5. Select Portal 1 URL and enter the address exactly as written, including http:// and the trailing slash.
6. Press the green SAVE button (or OK, depending on firmware).
7. Reboot: press SETUP, then Restart, or pull power for 10 seconds.
8. Watch the boot. You should see “Portal loading”, then the channel grid within 20 to 60 seconds.

If the box hangs on “Portal loading” for more than two minutes, stop rebooting and jump to the troubleshooting matrix in section 9. At that point the cause is almost always DNS interception or an unregistered MAC, not the URL itself.

One detail that trips people up: the URL field is case sensitive and does not tolerate leading or trailing spaces. If you copied the address from a phone chat message, retype the last three characters by hand. Messaging apps regularly auto-insert a trailing space, and a working portal fails because of it.

MAC Registration: What the Provider Actually Does With It

When a provider says “send me your MAC”, they mean the full 12-character string on the sticker, for example 00:1A:79:XX:XX:XX. Their panel adds it to the portal’s subscriber list, and your box authenticates on the next boot. Three facts about that process save most support tickets:

You cannot change a hardware MAC on a real MAG box. The address is fixed at the factory. If a provider only accepts MACs they issued themselves, they must register your box’s real sticker MAC. Anyone selling “custom MAC” for physical MAG hardware is describing an emulation setup, not the box itself.

One MAC equals one subscription slot. If your line is active on the box and you enter the same MAC in an emulator on a second device, the portal usually kicks one of the two sessions. For a second screen, ask for a second line or run an emulator with its own virtual MAC, which is exactly the workflow our StbEmu setup guide covers.

Blocked lists exist. Boxes resold from closed subscriptions sometimes arrive with a MAC the previous provider already blacklisted. That produces “Your STB is blocked” on a URL that works for everyone else. The fix is on the provider’s panel, and it is the first row of the matrix in section 9.

Per-Model Notes: 254, 322, 420/424, 540, 555

MAG 254 (legacy)

The 254 is the oldest model still in wide circulation. It handles 1080p H.264 fine but has no hardware HEVC decode, so any H.265 stream stutters or shows a black screen. If your provider’s line is HEVC-only, the 254 is the wrong box for it. Everything else, including the portal menu path, is identical to the newer models.

MAG 322

The 322 is a dual-core box with 512 MB of RAM and HEVC support, which makes it the practical floor for 2026 portal lineups that mix H.264 and H.265 channels. It is still one of the most common boxes on resale markets, and it takes the same setup steps as above.

MAG 420 and 424

Both use a HiSilicon Hi3798MV200 quad-core ARM Cortex-A53 at 1.2 GHz. The 420 ships with 512 MB of RAM; the 424 has 1 GB and 8 GB of eMMC. The extra memory in the 424 shows up mostly in EPG rendering speed on large channel lists. The 424w3 variant adds dual-band Wi-Fi; the base units are Ethernet-only.

MAG 540 / 540w3

The current mainstream Linux model. Infomir’s datasheet lists an Amlogic S905Y4-B with four Cortex-A35 cores at 2.0 GHz, 1 GB of RAM and 4 GB of eMMC. It decodes 4K HEVC, which matters because more portals now push UHD tiers. The 540w3 adds built-in dual-band Wi-Fi. Changing the portal URL on a 540 follows exactly the same Servers → Portals path as the older models; the only visible difference is a faster, flatter UI skin.

MAG 555 (Google TV)

The 555 breaks the pattern: it runs Google TV with 2 GB of DDR4 RAM and 16 GB of storage, so there is no built-in stalker portal menu. You install an IPTV client from the Play Store and enter the portal inside the app. MAC handling depends on the app: some emulate a virtual MAC, in which case your provider may need that virtual MAC instead of the box sticker. Send the provider whichever MAC the app’s status screen shows.

Full current specifications and factory firmware images are published on Infomir’s official site, which is also the right place to verify which firmware revision your box should be running before you blame the portal.

Lab Results: October 2026 Boot Bench and Wi-Fi vs Ethernet

We ran the four Linux models through the same bench in early November 2026: factory firmware, one channel list with 1,400+ live channels, three independent portals (a fast EU host, a mid-loaded MENA host, and a heavily loaded host), and three cold boots per portal. Times are averages from power press to a usable channel grid.

Two things from the bench are worth more than the raw numbers. First, zapping time depends on the portal server far more than on the box: the same MAG 540 zapped in 0.9 seconds on Portal A and 2.6 seconds on Portal C. If channel changes feel slow, the provider is the first suspect. Second, the box never rebuffered once over Ethernet on a clean line, which leads directly into the Wi-Fi comparison below.

We then ran the 540w3 over Wi-Fi with one HD channel for an hour on each band:

If your MAG 540w3 is on Wi-Fi, the 5 GHz band is the minimum. If it is still unstable, add the 1472 MTU fix from section 8 before you buy a new box.

DNS Override and the Per-Carrier Playbook

Some ISPs intercept DNS lookups for known portal hostnames and answer them with a dead address. The box then cycles on “Portal loading” forever, even though the URL is correct and the MAC is registered. North African carriers are the ones we see most often in this situation, so here is the per-line breakdown from our test rigs.

The override steps are the same for all of them:

1. Press SETUP and open Settings → System Settings → Network.
2. Select the active interface (Ethernet or Wi-Fi).
3. Change the mode from Automatic (DHCP) to Manual or Static.
4. Keep the IP address, gateway and mask the box was already using. The screen shows them before you switch. Only the DNS fields matter.
5. Set primary and secondary DNS from the table above.
6. Save, reboot, test the portal again.

If the portal still fails after the DNS override, the block is happening at the IP level rather than the DNS level, and no resolver choice will fix it. On a network you do not control, a router-level tunnel is the remaining option. As one way to route the box traffic through another exit, PureVPN configured on the router works here, and we may earn a commission if you purchase through that link, at no extra cost to you. A router-level tunnel also sidesteps the fact that Linux MAG firmware has no VPN client of its own.

Two related settings belong in this menu. Under System Settings → Time, point the NTP server at pool.ntp.org; a box with a wrong clock fails portal handshakes that check timestamps. And if the carrier in the table is yours, do the DNS override and the MTU setting in the same session, because they frequently appear together.

1472 MTU: Fixing Packet Sizing Stalls on PPPoE Lines

PPPoE lines, which is most Idoom ADSL and a large share of FTTH, carry an extra header that shrinks the usable packet size below the 1500 bytes routers assume by default. When the mismatch is small, IPTV fails in a specific, recognizable way: playback is fine, then freezes for one to three seconds, then recovers, on a repeating cycle. The stream itself is healthy. Oversized packets are being dropped and retransmitted.

Before you change anything, find your real ceiling with a fragmentation test from a PC on the same line. In Windows Command Prompt:

ping -f -l 1472 <your-router-gateway>
ping -f -l 1492 <your-router-gateway>

Use the flag to stop fragmentation. If the 1472 test replies cleanly but the 1492 test returns “Packet needs to be fragmented but DF set”, your effective ceiling is 1472, and that is the value to set. On the router (not the box, because the box has no MTU field of its own), set the WAN MTU to 1472 and reboot the router before rebooting the MAG box, so the box’s ARP and DHCP exchange happens against the new ceiling.

In our November bench, applying 1472 to a PPPoE line that was cycling freezes every 40 to 90 seconds removed every one of them on the 322 and the 540. If you are already chasing buffering, our general IPTV buffering fix guide covers the same test on the player side.

Troubleshooting Matrix: 13 Failures and Fixes

Ordered by how often each one arrives in support messages, every row re-confirmed against this quarter rigs (November 2026).

For problems that are not MAG-specific, provider-side outages and account-wide 403s included, our stalker portal connection fix guide covers the server side of the same handshake.

Where to Get Working Portal URLs

A MAG box is only as good as the portal behind it. We maintain a checked list of active stalker portal codes with MAC addresses that are already registered, refreshed daily. That is the fastest way to test a box you just received. If you prefer the M3U route over portal middleware, that workflow belongs to Android and PC players using our free M3U playlist database rather than to the MAG hardware itself.

When you test a new portal, judge it on three numbers: handshake under 30 seconds, zapping under 2 seconds, and zero rebuffers over 10 minutes on your own connection. A portal that fails any of the three at trial time will not improve after you pay for it.

Conclusion

MAG setup is a two-field job: the MAC you send to the provider, and the portal URL you type into Servers → Portals. Everything else, DNS overrides, NTP corrections, MTU sizing, HEVC compatibility, is cleanup around those two fields. Register the sticker MAC before anything else, keep the box on Ethernet where possible, and when a portal misbehaves, work the matrix in section 9 in order: blocked list, then DNS, then URL, then codecs. The box is rarely the problem, and this bench gives you the numbers to prove it before you open a support ticket.

Frequently Asked Questions

Why does my MAG box say 'Your STB is blocked'?

The portal server has your MAC address on its blocked list. That happens with boxes resold from closed subscriptions or when a provider deactivated a line for non-payment. Contact the provider and ask them to unbind the MAC from their panel. If they refuse, the box itself is fine: register the sticker MAC with a different provider and load their portal URL. The fix is on the panel side, and no setting inside the box can remove the block.

How do I change the portal URL on a MAG 540?

Press the SETUP button on the remote, then open Settings, System Settings, Servers, Portals. Select Portal 1 URL and type the new address exactly as your provider wrote it, including http:// and the trailing slash. Save with the green button and reboot the box. The path is identical on the 254, 322, 420 and 424, so the same steps work if you are moving between models. If the box hangs on Portal loading after the change, apply the DNS override from the playbook section first.

Which DNS should I use when my Algerian or Moroccan ISP blocks the portal?

Switch the box to Manual network mode and set the primary DNS to 1.1.1.1 with 8.8.8.8 as secondary, which fixed every Idoom ADSL and Maroc Telecom case in our November bench. If both resolvers fail on your line, swap in 9.9.9.9 as the primary. The steps are under Settings, System Settings, Network: keep the existing IP, gateway and mask, change only the two DNS fields, save and reboot. If the portal still fails, the block is at the IP level, not the DNS level.

Why does my MAG box freeze every minute or two on a PPPoE line?

That repeating freeze pattern is usually an MTU mismatch. PPPoE lines carry a tunnel header that shrinks the usable packet size below the 1500 bytes your router assumes, so oversized packets are dropped and retransmitted on a cycle. Run the ping -f -l test from a PC on the same line: if 1472 passes but 1492 fails with a fragmentation error, set the router's WAN MTU to 1472 and reboot. In our bench that removed every periodic freeze on the 322 and the 540 over Idoom ADSL.

Can I use a MAG box with an M3U playlist instead of a Stalker portal?

Not directly. A Linux MAG box only loads portal middleware, and it has no M3U field in its settings menu. The M3U route belongs to Android boxes, Firestick, phones and PC players, which is where our free M3U playlist database is aimed. If you own a MAG box and want the M3U experience, you either keep the portal workflow it was built for, or the M3U playlists play on a second device such as a phone or an Android TV box. The two routes are separate, and the box cannot bridge them.

Does a MAG box need a paid subscription, or can I use free portals?

The box is a neutral decoder; the content comes from whichever portal registers your MAC. Free stalker portal codes with pre-registered MACs do exist and rotate, and our daily list tracks them, but expect channel lists that shrink when a free portal runs out of upstream funding. A free portal is a good way to test the hardware in the first 24 hours. For daily viewing, the channel count, EPG completeness and 4K tiers on a free portal rarely hold up, which is why most setups that survive a month end on a paid line.