GlobalValue::Bind (“ChecksumEnabled”, BooleanValue (true)) GlobalValue::Bind (“SimulatorImplementationType”, StringValue (“ns3::RealtimeSimulatorImpl”)) This configuration can be fulfilled by adding the following strings to the ns-3 script:

A fundamental setting that must be adopted is the Real-time mode, which is necessary to enable the interconnection between the ns-3 simulated scenario and the real network as well as to manage the packet forwarding between these two domains. The script includes all the header files necessary to use the methods of the classes acting as application programming interface (API).

The most important parts of the ns-3 script are reported and described in the rest of this subsection. The aforementioned simulated scenario is created by a script written in the C++ programming language. Two different types of wired links are used inside the proposed scenario: (i) the GPRS Tunnel Protocol ( GTP), which connects each eNB and the sgwPgw and (ii) the Point-to-Point link, which is a simple link characterized only by data rate and delay, and used to connect sgwPgw node and Ghost Node. More details about this interconnection procedure are included in Section 5.3. The Ghost Node is a particular type of node whose goal is to assure the interconnection between the simulated scenario and the virtual interface tap1 that forwards the traffic to the ENS. sgwPgw represents the key node of the EPC network and communicates with the eNBs and with the Ghost Node. Īs previously stated in Section 4.1.2, SGW and PGW functionalities are implemented in a single node, called, in this chapter, sgwPgw.UEs are connected with one of the available base stations, called evolved Node B ( eNB), which control and manage the radio link and receive/forward the traffic to/from the associated UEs.

Each UE is equipped with an LTE interface. User Equipment ( UE) represents the mobile terminals that assure network connectivity to users. The Simulated Network Segment (SNS) structure.

What is avast virtualbox interface