ethernet
[[TOC]]
In IP configuation, the GW and ST entities receive Ethernet frames from workstations. Workstations are then all on the same subnetwork.
This configuration allows to deploy OpenSAND with an Ethernet configuration. No VLAN are present in this configuration, and no QoS can be done in this case. Ethernet frames on OpenSAND are default IPv4 frames (Ethertype = 0x0800). Frames generated by workstations must be 0x0800 frames too. Detailled presentation of this configuration is given here:
This configuration allows to deploy OpenSAND with an Ethernet configuration. A default VLAN is present in this configuration, but no QoS can be done. Ethernet frames on OpenSAND are 802.1Q frames (Ethertype = 0x8100). However, frames generated by workstations must be 0x0800 frames. Detailled presentation of this configuration is given here:
Ethernet network with one default VLAN
This configuration allows to deploy OpenSAND with an Ethernet 802.1Q configuration. The user can specify several VLANs that are in use between workstations. Thus, packets entering GW or ST are already tagged with a 802.1Q header, and a PCP priority, allowing for QoS. A default VLAN is present in this configuration, for packets entering OpenSAND without 802.1Q header; in this case the lowest priority is assigned (pcp=0). Ethernet frames on OpenSAND are VLAN tagged frames (Ethertype = 0x8100, IEEE 802.1Q). Detailled presentation of this configuration is given here:
Ethernet network with several VLAN, can ping bridge interface
This configuration allows to deploy OpenSAND with an Ethernet 802.1Q configuration. The user can specify several VLANs that are in use between workstations. Thus, packets entering GW or ST are already tagged with a 802.1Q header, and a PCP priority, allowing for QoS. A default VLAN is present in this configuration, for packets entering OpenSAND without 802.1Q header; in this case the lowest priority is assigned (pcp=0). Ethernet frames on OpenSAND are VLAN tagged frames (Ethertype = 0x8100, IEEE 802.1Q).
This configuration is a simplified version of Ethernet network with several VLAN, can ping bridge interface, thus it is not possible to ping between GW and ST on custom VLANs (only default VLAN can be used to ping). Detailled presentation of this configuration is given here:
Ethernet network with several VLAN, cannot ping bridge interface