Technical data

4. Packages
Software:
• Package: advanced_networking
• Package: dhcp_client (for the use of ID8)
The following describes adapting the config files base.txt, dsl.txt, advanced_networking.txt,
dhcp_client.txt, dns_dhcp.txt.
Hardware Setup
The recommendation to connect the IPTV SetTopBox without further network elements di-
rectly to the router also applies to fli4l. If network nodes like hubs, switches, bridges, gateways,
or routers have to be placed between the IPTV box and fli4l, these should be multicast-enabled
to avoid problems.
Home networks usually do not use switches that separate virtual networks (VLAN) from
each other in order to disencumber remaining traffic (ID7) from IPTV multicast traffic (ID8).
This is why a separate NIC (Network Interface Card = LAN or Ethernet card) is used to
connect the set-top box (STB) directly to fli4l to avoid all problems due to heavy traffic.
Those preferring the single NIC method (not described here) should know what to do on their
own.
The easiest way to use an IPTV STB hence is to install an additional NIC to fli4l’s hardware.
Find a diagram below how to migrate fli4l from standard to a third NIC:
• Standard configuration:
– eth0 is used as the NIC for internal home/office LAN in base.txt
– eht1 is the DSL interface mentioned in dsl.txt
VDSL modem fli4l router
LAN interface
Figure 4.5.: fli4l in a standard configuration
• Advanced configuration with an additional IPTV NIC:
– After installation of an additional NIC eth2 has to be inserted in base.txt.
VLAN Configuration
First of all: OPT_IGMP is not depending on VLAN. VLAN is needed for Deutsche Telekom
VDSL and hence should be supported by the router. Whether VLAN is required for other
providers (Arcor, Alice, a.s.o. ..) is beyond our knowledge at the moment.
To get VDSL25/50 as provided by T-Home up and running, the NIC to the VDSL modem
necessarily has to be configured as a VLAN interface.
193