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