## 4 Proposed Architecture
### Implementation Phase
To achieve this, in the sw_interface_set_l2_bridge function, it is sufficient to set the enable parameter to zero. After applying the above processes, our data plane will be ready to provide the proposed service. ## 5 Simulation Results

In this section, we outline two test approaches: lightweight and practical scenarios. The lightweight scenario refers to the implementation of the proposed protocol on the software-based router in the Linux environment, through which we are trying to show the performance, signaling, and control plane processes. To the best of our knowledge, since we face simulation constraints at this level, we configured a high level of testing based on the practical scenario. At this level, the router is implemented on the commodity hardware to test the functionality of VPLS in the real world. Finally, based on the analysis of results, we evaluate the efficiency of this service in the three factors of throughput, latency, and packet loss ratio. Also, Table 1 demonstrates the test specifications. ### Lightweight Design and Test

In the topology, as shown in Figure 13, the two routers R1 and R2 are the two routers CE. Our Router Design (we called Rahyab as high-speed routers), frr-router-1, frr-router-2, and frr-router-3 routers also play the role of PE routers. In all three Rahyab routers, OSPF and MPLS mechanisms are activated [38]. However, VPLS (on the proposed specifications) is only enabled on PE routers 1 and 3. It should be noted that configuring Cisco routers is just for specifying the address of their ethernet link. The following are some instructions for the configurations performed in the lightweight scenario. * The R1 and R2 router configuration are illustrated in Figure 14;
* Configurations for Rahyab router: The settings for the above scenario Figure 13 are given for each router as follows: 1. Enable IP forwarding feature in Linux operating system that can be applied to both versions of IP. 2. Enable MPLS on each interface. 3. Define a new bridge and PW in the kernel. 4. Enable bridge and PW. \begin{table}
\begin{tabular}{l l} \hline \hline
**Specifications** & **Value** \\ \hline OS & Ubuntu 22.04.2 LTS \\ FRR & 7.0 stable \\ Vector Packet Processing & 19.08 \\ Plugin & VPP Sandbox/router \\ Hardware & Nexcom NSA 7136 \\ CPU & Dual Intel® Xeon® Processor E5-2600 v4 \\ Number of Cores & 32 \\ RAM & 96 \\ Number of Interfaces & 16 (1 Gbps) and 6 (10 Gbps) \\ Tester & Ixia \\ Emulator & Grs3 \\ Cisco routers & 7600 Series \\ Cisco switches & Catalyst 3750-X Series \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Test specifications. Figure 13: Our lightweight H-VPLS simulation scenario. 5. Connect the bridge and PW created in the previous section to the ethernet link. It is worth mentioning that the settings for steps 1 to 5 are done in the Command Line environment of Linux, and these settings are the same for all Rahyab routers. 6. Turn on and give IP addresses to the interfaces, enable OSPF and MPLS, and perform configurations related to each of them (these are not explained in this document because they are thoroughly explained in other documents). 7. Enable VPLS on PE routers (routers 1 and 3 in Figure 13). As a result of running the command, the following commands are activated under VPLS, and the interface ens32 and PW mpw0 are recognized as its members. By determining the address of the router connected to the other end of PW, the VPLS neighborhood of the current router is determined. To ensure the accuracy of the VPLS and topology commands, we check the output of the binding and VC commands. For instance, the result of executing these two commands on router 3 will be as follows. If a binding is done correctly, each VC will be assigned a local tag and a round tag. Figure 15 confirms this goal. Figure 14: R1 and R2 configurations based on simulation scenario Figure 13. Settings according to sub-figures (**a,b**) should be considered. Figure 15: Results of lightweight H-VPLS scenario Figure 13. Settings according to sub-figures (**a–e**) should be considered.