Skip to content

Commit 5d3a0fe

Browse files
committed
Add implementation of service bridge
Features: - The datapath code is regenerated automatically whenever stp is enabled or disabled, so it is not necessary to configure that parameter at the creation of the bridge. - For each port, there are one or more PortsStp instances according to the VLANs allowed for that port. - A Stp instance is created automatically, when the first PortStp instance for the same VLAN is created. - In the same way, a Stp instance is destroyed automatically, when the last PortsStp instance for the same VLAN is destroyed. - Since the management of Stp/PortsStp instances is done automatically, the user is not allowed to create/destroy manually those instances, but only to configure their parameters. - Containers Access/Trunk do not exist at the same time; if the port is configured in access mode the user can't configure trunk parameters and vice versa Signed-off-by: Gianluca Scopelliti <gianlu.1033@gmail.com>
1 parent bab474c commit 5d3a0fe

21 files changed

Lines changed: 2259 additions & 244 deletions

src/services/CMakeLists.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ endmacro()
1919
# first argument is the service name used in the rest API
2020
# second argument is the folder of the service
2121

22+
add_service(bridge pcn-bridge)
2223
add_service(ddosmitigator pcn-ddosmitigator)
2324
add_service(firewall pcn-firewall)
2425
add_service(helloworld pcn-helloworld)

0 commit comments

Comments
 (0)