| 1 |
.. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later |
| 2 |
|
| 3 |
.. _net: |
| 4 |
|
| 5 |
###################### |
| 6 |
Digital TV Network API |
| 7 |
###################### |
| 8 |
|
| 9 |
The Digital TV net device controls the mapping of data packages that are part |
| 10 |
of a transport stream to be mapped into a virtual network interface, |
| 11 |
visible through the standard Linux network protocol stack. |
| 12 |
|
| 13 |
Currently, two encapsulations are supported: |
| 14 |
|
| 15 |
- `Multi Protocol Encapsulation (MPE) <http://en.wikipedia.org/wiki/Multiprotocol_Encapsulation>`__ |
| 16 |
|
| 17 |
- `Ultra Lightweight Encapsulation (ULE) <http://en.wikipedia.org/wiki/Unidirectional_Lightweight_Encapsulation>`__ |
| 18 |
|
| 19 |
In order to create the Linux virtual network interfaces, an application |
| 20 |
needs to tell to the Kernel what are the PIDs and the encapsulation |
| 21 |
types that are present on the transport stream. This is done through |
| 22 |
``/dev/dvb/adapter?/net?`` device node. The data will be available via |
| 23 |
virtual ``dvb?_?`` network interfaces, and will be controlled/routed via |
| 24 |
the standard ip tools (like ip, route, netstat, ifconfig, etc). |
| 25 |
|
| 26 |
Data types and ioctl definitions are defined via ``linux/dvb/net.h`` |
| 27 |
header. |
| 28 |
|
| 29 |
|
| 30 |
.. _net_fcalls: |
| 31 |
|
| 32 |
Digital TV net Function Calls |
| 33 |
############################# |
| 34 |
|
| 35 |
.. toctree:: |
| 36 |
:maxdepth: 1 |
| 37 |
|
| 38 |
net-types |
| 39 |
net-add-if |
| 40 |
net-remove-if |
| 41 |
net-get-if |