added details for how to go about for implementation of network part

parent 6d86e53b
No preview for this file type
......@@ -111,6 +111,31 @@ Provision with dedicated fiber connections for tunnelling. We can leverage
this to make the inbound traffic isolated from the core network traffic
wherever possible. Terminologies for the traffic : Inbound, Outbound, Hybrid.
\subsection{Networking Part}
Flowvisor cannot used as it doesn’t allow flows to be created when there is a
conflict arrives. This is exactly what we want to accomplish but without
changing the behavior or the existing network.\\
The main controller which controls the core network will not be touched. RYU
controller which is to be used by our CNAC interface will do the job of
pushing and pulling flows. The communication as of now is done by REST APIs or
JSON. [As of now I’m doing the testing of the capabilities using REST APIs].\\
The system knows all the ports in each switch which are dedicated for the IDS
traffic route. Given the tap point the CNAC will form a graph in which
switches the flows are to be installed, then it compares it with the existing
flows in each of the switch and tries to come up with the equivalent rules
which makes the tapping to happen but preserving the existing behavior of the
core network’s service traffic.\\
The modified rules and the added rules are to be maintained by the CNAC when
the tapping has to be removed.
\subsection{Cloud Part}
Flowvisor can be used in the cloud part which we want the traffic to be
isolated and delivered to the specific VM without affecting the others
\section{More Motivation}
\item Tapping Issues in Current Network: Mirror costs is very high.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment