Search
Search Menu

How to configure modem router to work with IPTV (self-developed UI)

User Application Requirement
Updated 06-29-2022 01:57:43 AM 146698
This Article Applies to: 
Note:This article applies to TD-W8968 V1, if it’s V2,please click here. We will take TD-W8968 V1 as example in this article.The steps are the same for other listed models.

Before starting the configurations on TD-W8968, users have to know the IPTV related parameters from ISP. This guide is NOT suitable for the IPTV Application which requires Vlan-binding or some other special settings needed other than the below example shows.

Here we assume the IPTV parameters are as below:
Connection Type: Bridge
VPI/VCI: 8/32
Encapsulation Mode: LLC
ATM QoS Type: UBR
Also, we will configure LAN4 as an IPTV port.
Step 1: Add Bridge Interface for IPTV.
Login the Web Management Page of TD-W8968 by http://192.168.1.1. (Default username & password: admin, admin.)
Go to Network->WAN Settings; add a Bridge interface for IPTV.
Note: Up to eight WAN Interfaces can be added. If you fail to add a new bridge, you may have to delete the unused interfaces (or delete the one that use the same VPI/VCI) then do it again.
Fill in the information: VPI=8, VCI=32, Choose WAN Connecion Type as “Bridge”. For advanced settings, click “Advance” on the right side. Then you can configure the Encapsulation mode and ATM QoS Type etc.
Save it and the added bridge interface will be shown as below:
Step 2: Add a New Group for IPTV
Go to Network->Interface Grouping. Click “Add”,
Name the Group as “IPTV”, then add LAN4 and br_8_32_1 to the same group. Save it.
After save, you will see a new IPTV group added. It has br_8_32_1 as WAN and LAN4 as LAN.
Step 3: Disable DHCP for IPTV Group
Go to DHCP Server->DHCP Settings, Edit the IPTV Group and disable DHCP.
Save it and IPTV Group’s DHCP status becomes disabled.

Till now, everything is done and your IPTV device could be connected to LAN4 and you could start enjoying IPTV. (LAN 4 can only be used as IPTV port after all the above settings.)

Is this faq useful?

Your feedback helps improve this site.

Recommended Products

Community

TP-Link Community

Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.

Visit the Community >

From United States?

Get products, events and services for your region.

GO Other Option

This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again

This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again

Basic Cookies

These cookies are necessary for the website to function and cannot be deactivated in your systems.

TP-Link

accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType

Livechat

__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID

Youtube

id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ

Analysis and Marketing Cookies

Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.

The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.

Google Analytics & Google Tag Manager

_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>

Google Ads & DoubleClick

test_cookie, _gcl_au

Meta Pixel

_fbp

Crazy Egg

cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs

Hotjar

OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>

Linkedin

lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or