Transparent Security is a solution for identify the source devices of a DDoS attack and mitigates the attack in the customer premises or the access network. This solution leverages a P4 based programmable data plane for add in-band network telemetry (INT) for device identification and in-band mitigation.
Fixes #314
Adds the ability to configure the default output port which by default is bit<3>1.
As the ports on the Wedge Core switch do not map nicely to 1, 2, 3, 4 as our automated tests had been doing, I have changed all of the port values to the same that we will be using on the Wedge Core.
Tests needed to be addressed as well.
Port values will be encoded in the switch.tunnels portion of the topology as well as the "clone_egress" section.
Do you have any concerns with this PR?
no
How can the reviewer verify this PR?
Ensure CI executes properly. One then can check out the data_forward_t port values to ensure they are no longer 1, 2, 3, and/or 4.
Any background context you want to provide?
Issue found while deploying and iperf3 testing our P4 code on Wedge Core #1
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? yes
Does the documentation need an update? not at this time
Does this add new dependencies? no
Have you added unit or functional tests for this PR? Fixed the existing ones to leverage the correct port values when making explicit inserts to data_forward_t.
What does this PR do?
Fixes #314 Adds the ability to configure the default output port which by default is bit<3>1. As the ports on the Wedge Core switch do not map nicely to 1, 2, 3, 4 as our automated tests had been doing, I have changed all of the port values to the same that we will be using on the Wedge Core. Tests needed to be addressed as well. Port values will be encoded in the switch.tunnels portion of the topology as well as the "clone_egress" section.
Do you have any concerns with this PR?
no
How can the reviewer verify this PR?
Ensure CI executes properly. One then can check out the data_forward_t port values to ensure they are no longer 1, 2, 3, and/or 4.
Any background context you want to provide?
Issue found while deploying and iperf3 testing our P4 code on Wedge Core #1
Screenshots or logs (if appropriate)
Questions: