#325 Better VLAN & TSN Support by using RAW Sockets

[Bernd Löhr]

Currently, the VLAN (and thus TSN) support uses RAW IP Sockets. It will depend on preconfigured VLAN interfaces, which are OS and even distribution dependend. To have a more OS independ, portable solution, which also aligns more with the requirements of the NG-TCMS (FDF, AUTOSAR AP, OPC UA), the TSN branch of the VOS network layer should switch to RAW sockets (instead of RAW IP sockets).

[Armin-Hagen Weiss]

Check what is better raw/raw iP sockets

[Chris Wetzler]

Commitment:

• We use distinct IP addresses inside a consist.
• This allows to find the preconfigured local network-interface (including VLAN-ID and priority) while searching for a locally configured IP-address.
• The VLAN-ID does not need to be inserted into ethernet frames manually (using RAW sockets), but is inserted / removed by the OS, due to the configuration of the interface in use.
• The ethernet priority (PCP) is set indirectly through a one-to-one egress/ingress-mapping of IP-QoS.
• An application knowing about the configured IEEE 802.1 Qbv TSN-timeslot-priorities may then decide to send inside or outside of a certain TSN-timeslot.

[Chris Wetzler]

Closed, due to commitment on how to use IP addresses and how to configure interfaces and VLANs for use with TSN.
See Ticket #342