Configure IPv6 ports
Posted by Pieter Vandercammen, Last modified by Dries Decock on 03 April 2018 02:24 PM
All traffic in a ByteBlower is transmitted and received through ByteBlower Ports. Conceptually these Ports can be seen as small, virtual EndPoints in your network. As any other endpoint they need various network settings to communicate with the outside world. Physically they're docked (or attached) to a specific ByteBlower interface. This article explains the configuration options of a IPv6 ByteBlower Port. We start from the screenshot below.
The name given to a ByteBlower port. This name is used solely within the ByteBlower GUI, it's not send out over the network. To avoid confusion, all ports in the same project have different names.
As any other network device, a ByteBlower port requires a MAC address. Default this address is used for all traffic in and out of the Port. Often it's a good idea to for this address to be unique, but this not required (e.g. dual-stack IPv4 and IPv6). For IPv6 ByteBlower ports, the MAC address is used to generate the link-local address.
The method used to obtain a global IPv6 address for the ByteBlower Port. This can either be:
The IPv6 Address and Router Address and Prefix length columns are solely are solely available for Fixed configurations. In the other configurations they are obtained from the network. More info on these fields is found in https://tools.ietf.org/html/rfc3513 .
A ByteBlower port can be configured with a VLAN tag or even a VLAN stack (QiQ). These tags are known as Layer2.5 configurations. They are used to create virtual networks within a physical network. The ByteBlower GUI will automatically add these tags to all outgoing traffic. Similarly all arriving traffic at a ByteBlower Ports needs the same Layer2.5 configuration.
This columns configures the maximum size of the frames transmitted from a ByteBlower port. TCP traffic from this port will respect this size, similarly one can't transmit FrameBlasting frames larger than this size. This limit doesn't apply to received frames.
As mentioned in the introduction, a ByteBlower port emulates an Endpoint in the network. For it to be useful it needs needs to be physically docked to a ByteBlower interface. All incoming and outgoing traffic of this ByteBlower Port goes through this interface.