Before changing anything
Two habits save a lot of trouble.
Note what a setting was. Photograph the page before you change it. Router interfaces rarely have an undo, and a setting you cannot restore is worse than the problem you were solving.
Change one thing at a time and test. Changing four settings then finding it works tells you nothing about which mattered, and leaves three changes you cannot justify keeping.
It is also worth confirming the problem is the router at all. If a device beside the router struggles just as much as one across the house, the settings below will not help — the buffering guide covers isolating that.
Quality of Service, and its limits
QoS lets you tell the router which traffic matters most when the connection is busy. On paper it is exactly what live television wants.
In practice it helps in one specific situation: when your upload is saturated. A large backup or video call fills the upstream, acknowledgements are delayed, and your download stalls even though there is plenty of download capacity. QoS fixes that.
It does not help when the bottleneck is outside your house, which is what evening congestion usually is. Nor does it create capacity — it only decides who waits.
If you enable it
- Set your actual measured speeds, not the advertised ones. QoS works by holding traffic back slightly, and it cannot do that if it believes the line is faster than it is.
- Prioritise the television by device rather than by application, which is more reliable than guessing at traffic types.
- If streaming does not improve within a day, turn it off. QoS costs a little throughput and is not worth keeping for nothing.
Band steering and separate network names
Most modern routers publish 2.4 GHz and 5 GHz under one name and choose for you. When it works it is convenient. When it does not, it leaves a television on the slower, busier band and nothing on screen tells you.
Giving each band its own name — appending "-5G" to one is the usual convention — lets you connect the television explicitly and know it will stay there. Everything else can carry on using whichever it likes.
The trade-off is that devices no longer roam automatically between bands, which matters for phones moving around the house and not at all for a television that never moves. More on choosing the band in Wi-Fi optimisation for IPTV.
IGMP snooping and multicast
You will find IGMP settings on most routers, and advice online telling you to change them for IPTV. For most people this is irrelevant, and it is worth understanding why.
Multicast sends one copy of a stream to many recipients at once, and it is how some internet providers deliver their own television service over their own network. IGMP snooping stops that flooding every port.
Services delivered over the open internet, which is what an ordinary IPTV subscription is, use ordinary unicast connections. Each viewer gets their own stream. IGMP settings have nothing to touch.
If your provider supplies television through their own box on their own line, their settings matter. Otherwise leave these alone.
Firmware, and when to update it
Router firmware fixes real bugs, including ones that cause intermittent dropouts. It is worth keeping current.
Two cautions. Update when you have time, not five minutes before a match — an interrupted update can leave a router unusable. And if a specific update coincides with new problems, note the version, because occasionally a release is worse than what it replaced.
Settings that will not help
Worth naming, because they absorb a lot of effort.
- Port forwarding. Your player makes outbound connections. Nothing needs to reach in.
- Changing MTU. Occasionally relevant on unusual connections, almost never on a normal one, and easy to set wrongly.
- Disabling the firewall. No benefit for streaming and a real cost to your security.
- Turning off SPI or NAT acceleration. On some routers this reduces throughput rather than improving it.
DNS deserves its own answer, and gets one in does changing your DNS help IPTV. The other frequent suspect is the type of address your provider has given you, which is covered in CGNAT and double NAT — worth reading mainly to rule it out, since it affects streaming far less often than people assume.
A sensible order to work through
- Confirm the problem is not present on a device beside the router.
- Split the bands and connect the television to 5 GHz explicitly.
- Update firmware if it is well out of date.
- Enable QoS only if something in the house saturates the upload.
- Leave IGMP, MTU and port forwarding alone.
If none of that changes anything, the constraint is probably not the router. A wired connection is the next thing worth trying, for the reasons in Ethernet vs Wi-Fi.
Frequently asked questions
Does QoS fix IPTV buffering?
Only when your upload is being saturated by something else in the house, which delays acknowledgements and stalls the download. It cannot help with congestion outside your home, and it does not create capacity.
Should I enable IGMP snooping for IPTV?
Usually it is irrelevant. IGMP relates to multicast, which providers use on their own networks. A subscription delivered over the open internet uses ordinary unicast connections, so the setting has nothing to act on.
Do I need to forward any ports for IPTV?
No. Your player makes outbound connections to fetch the stream, so nothing needs to reach in. Port forwarding adds risk without benefit here.
Should I split my 2.4 GHz and 5 GHz networks?
It helps when a television keeps ending up on the slower band. Separate names let you connect it explicitly to 5 GHz. The cost is that mobile devices no longer roam between bands automatically.