1
0
Fork 0

Add spaces before citations, tweak gennet img

master
LEdoian 1 year ago
parent 8676c18fb4
commit 411173c7c6

@ -21,8 +21,8 @@ Tools in this category do not collect any data on their own, rather only
focusing on visualising data from other tools. These projects are often small, focusing on visualising data from other tools. These projects are often small,
can be easy to run and allow visualisation of various data, but they require can be easy to run and allow visualisation of various data, but they require
other infrastructure to provide the data. For example, the Network other infrastructure to provide the data. For example, the Network
Weathermap\cite{weathermap} project can be used to provide overview based on Weathermap~\cite{weathermap} project can be used to provide overview based on
data in Cacti or other tools. Grafana\cite{grafana} provides many different data in Cacti or other tools. Grafana~\cite{grafana} provides many different
methods of visualising data from various databases. methods of visualising data from various databases.
This does not seem to be usable for visualising OSPF state, because we are not This does not seem to be usable for visualising OSPF state, because we are not
@ -38,7 +38,7 @@ the system state, as we will see in section~\ref{s:net-split}.
These projects usually store a time series of utilisation and therefore need to These projects usually store a time series of utilisation and therefore need to
be deployed on some central server as long-running services. be deployed on some central server as long-running services.
Examples of this approach include Cacti\cite{cacti} and Munin\cite{munin}. Examples of this approach include Cacti~\cite{cacti} and Munin~\cite{munin}.
Although both mentioned projects can graph other data, plugins for data Although both mentioned projects can graph other data, plugins for data
collection are available, so this differentiates them from the previous group. collection are available, so this differentiates them from the previous group.
@ -46,8 +46,8 @@ collection are available, so this differentiates them from the previous group.
Projects in tis category do not necessarily consider the whole network system, Projects in tis category do not necessarily consider the whole network system,
but check state of individual hosts. It is possible for them to run locally, as but check state of individual hosts. It is possible for them to run locally, as
is the case for Plotnetcfg\cite{plotnetcfg}, or check the host over the network is the case for Plotnetcfg~\cite{plotnetcfg}, or check the host over the network
(CaLStats\cite{calstats}, Icinga\cite{icinga}), but they do not provide (CaLStats~\cite{calstats}, Icinga~\cite{icinga}), but they do not provide
overall picture. The capabilities of these tools also differ, from just overall picture. The capabilities of these tools also differ, from just
checking reachability (CaLStats) to being able to retreive various details from checking reachability (CaLStats) to being able to retreive various details from
the hosts (Icinga, plotnetcfg). the hosts (Icinga, plotnetcfg).
@ -60,19 +60,19 @@ section~\ref{s:net-split}.
Some network administrators have created platforms for managing the hosts Some network administrators have created platforms for managing the hosts
across the network system. These systems usually know various aspects of the across the network system. These systems usually know various aspects of the
system and may provide features like configuration generation or topology system and may provide features like configuration generation or topology
visualisation\cite{nodewatcher-paper}. However, many of these are tailored for visualisation~\cite{nodewatcher-paper}. However, many of these are tailored for
the specific system and are therefore not reusable in other environments. the specific system and are therefore not reusable in other environments.
Also, since large number of people need to access such platforms, they are Also, since large number of people need to access such platforms, they are
usually server based with web interface\cite{nodewatcher-paper}. usually server based with web interface~\cite{nodewatcher-paper}.
\subsection{Topolograph} \subsection{Topolograph}
We are aware of the only project that would allow visualisation of OSPF We are aware of the only project that would allow visualisation of OSPF
topology, Topolograph\cite{topolograph}. While it does not collect its own topology, Topolograph~\cite{topolograph}. While it does not collect its own
data, its companion project, Ospfwatcher\cite{ospfwatcher}, is able to retrieve data, its companion project, Ospfwatcher~\cite{ospfwatcher}, is able to retrieve
current topology data from a Quagga\cite{quagga} routing daemon. The deployment current topology data from a Quagga~\cite{quagga} routing daemon. The deployment
involves setting up Logstash\cite{logstash}, so this is only suitable to be run involves setting up Logstash~\cite{logstash}, so this is only suitable to be run
on a server. on a server.
Also, we find the interface of Topolograph impractical to use (tested in Also, we find the interface of Topolograph impractical to use (tested in

@ -13,7 +13,7 @@ BIRD routing daemon.
\section{OSPF overview} \section{OSPF overview}
OSPF\cite{rfc2328,rfc5340} is a link-state routing protocol, which means that routers try to understand OSPF~\cite{rfc2328,rfc5340} is a link-state routing protocol, which means that routers try to understand
the whole topology of the network and find the best path using an algorithm for the whole topology of the network and find the best path using an algorithm for
finding the shortest paths. Usually, Dijkstra's algorithm \X{ref?} is used. finding the shortest paths. Usually, Dijkstra's algorithm \X{ref?} is used.
OSPF was designed to provide dynamic routing in an entire autonomous system, but OSPF was designed to provide dynamic routing in an entire autonomous system, but
@ -72,7 +72,7 @@ paths to routers and networks in that area, including the external, extra-area
and stub networks adjacent to that area. OSPF specifies that the graph has all and stub networks adjacent to that area. OSPF specifies that the graph has all
the networks and routers as vertices, directed edges lead from each router to the the networks and routers as vertices, directed edges lead from each router to the
incident network with the configured cost and from each transit network to incident network with the configured cost and from each transit network to
incident routers with cost 0 (except when the two-part metric\cite{rfc8042} is incident routers with cost 0 (except when the two-part metric~\cite{rfc8042} is
implemented). There are no edges starting at the external, extra-area or stub implemented). There are no edges starting at the external, extra-area or stub
networks, so that the shortest path DAG calculation does not find paths networks, so that the shortest path DAG calculation does not find paths
through them. through them.
@ -82,28 +82,28 @@ specified in the same units as the internal costs, Type 2 cost is larger than
any internal or type 1 cost. any internal or type 1 cost.
The OSPF family of routing protocols has undergone long evolution since the The OSPF family of routing protocols has undergone long evolution since the
first specification in 1989\cite{rfc1131}, There are currently two versions of first specification in 1989~\cite{rfc1131}, There are currently two versions of
the protocol in use -- versions 2 and 3. While the basic idea is still the the protocol in use -- versions 2 and 3. While the basic idea is still the
same, OSPFv2 can only handle IPv4 systems. Although OSPFv3 claims to be same, OSPFv2 can only handle IPv4 systems. Although OSPFv3 claims to be
network-protocol-independent, it is usually only used with IPv6 systems and in network-protocol-independent, it is usually only used with IPv6 systems and in
fact, features like virtual links can only be used with that network fact, features like virtual links can only be used with that network
protocol\cite{rfc5838}. protocol~\cite{rfc5838}.
Both OSPF versions have numerous extensions, as can be seen by the number of Both OSPF versions have numerous extensions, as can be seen by the number of
RFCs that update the base specifications\cite{rfc2328,rfc5340}. Therefore, we RFCs that update the base specifications~\cite{rfc2328,rfc5340}. Therefore, we
do not implement the protocol ourself, but rather find a suitable routing do not implement the protocol ourself, but rather find a suitable routing
daemon \X{glos} to determine the current topology. daemon \X{glos} to determine the current topology.
Many improvements of the protocol only affect the topology construction (e.g. Many improvements of the protocol only affect the topology construction (e.g.
NSSA areas\cite{rfc3101}) or change the data exchange between routers NSSA areas~\cite{rfc3101}) or change the data exchange between routers
(Multi-instance extensions\cite{rfc6549}, authentication\cite{rfc5709}, \dots). (Multi-instance extensions~\cite{rfc6549}, authentication~\cite{rfc5709}, \dots).
By extracting the topology from a routing daemon, we can support many OSPF By extracting the topology from a routing daemon, we can support many OSPF
extensions for free. For this reason, it is mostly sufficient to only consider extensions for free. For this reason, it is mostly sufficient to only consider
the base specifications of OSPF. the base specifications of OSPF.
\section{Routing daemon selection} \section{Routing daemon selection}
While we were mostly determined to use BIRD\cite{bird} from the start, since we already While we were mostly determined to use BIRD~\cite{bird} from the start, since we already
had some experience with it, let us present here a short summary of other had some experience with it, let us present here a short summary of other
possibilities. Note that the particular choice does not affect interoperability possibilities. Note that the particular choice does not affect interoperability
with other routers as long as the chosen routing daemon supports extensions with other routers as long as the chosen routing daemon supports extensions
@ -116,14 +116,14 @@ the feasibility would require us to obtain the specific hardware. Therefore, we
only consider hardware-independent solutions. only consider hardware-independent solutions.
While we are aware of several software implementations, many of these do not While we are aware of several software implementations, many of these do not
seem to be developed anymore (Quagga\cite{quagga}, XORP\cite{xorp}, seem to be developed anymore (Quagga~\cite{quagga}, XORP~\cite{xorp},
OpenOSPFd\cite{openospfd}). Apart from BIRD, we only found FRRouting\cite{frr} OpenOSPFd~\cite{openospfd}). Apart from BIRD, we only found FRRouting~\cite{frr}
to be maintained, meaning that it had a release in the past year. While being to be maintained, meaning that it had a release in the past year. While being
maintained is not a strict requirement, it would allow us to use that maintained is not a strict requirement, it would allow us to use that
implementation in case OSPF is extended again. implementation in case OSPF is extended again.
However, even BIRD does not implement all the extensions, for example, the However, even BIRD does not implement all the extensions, for example, the
two-part metric\cite{rfc8042}. two-part metric~\cite{rfc8042}.
\section{BIRD interface} \section{BIRD interface}
@ -135,7 +135,7 @@ users, so a rather simple client, \texttt{birdc}, is provided in the BIRD's
package\X{glos?}. package\X{glos?}.
While there is a note of a machine-readable protocol in the While there is a note of a machine-readable protocol in the
\texttt{doc/roadmap.md} file in BIRD's source code\cite{bird-src}, it is not \texttt{doc/roadmap.md} file in BIRD's source code~\cite{bird-src}, it is not
implemented, so we will need to interface using the socket. This has following implemented, so we will need to interface using the socket. This has following
consequences, most of which are not very pleasant: consequences, most of which are not very pleasant:
@ -222,7 +222,7 @@ area 0.0.0.1
The tree as output by BIRD\footnote{The format was determined by The tree as output by BIRD\footnote{The format was determined by
experimentation and inspecting of \texttt{proto/ospf/ospf.c} in BIRD's source experimentation and inspecting of \texttt{proto/ospf/ospf.c} in BIRD's source
code\cite{bird-src}.} has three levels, we call them top-level, level-2 code~\cite{bird-src}.} has three levels, we call them top-level, level-2
and level-3. The top level only contains directives of form \texttt{area and level-3. The top level only contains directives of form \texttt{area
AreaID}, with the AreaID being written in the quad-dotted notation. AreaID}, with the AreaID being written in the quad-dotted notation.
@ -285,7 +285,7 @@ of scripts called Gennet. Sice it was mainly written to aid Birdvisu, we
provide it as attachment~\ref{att:gennet} of this thesis. provide it as attachment~\ref{att:gennet} of this thesis.
Gennet is a network generator. Using a hard-coded configuration and a set of Gennet is a network generator. Using a hard-coded configuration and a set of
Jinja2\cite{jinja2} templates, it provides a semi-automatic way of Jinja2~\cite{jinja2} templates, it provides a semi-automatic way of
creating several virtual machines (their disk images and startup scripts) and creating several virtual machines (their disk images and startup scripts) and
configuration to connect them using software bridges\X{term?}. This will allow configuration to connect them using software bridges\X{term?}. This will allow
changing the state from the host operating system, simulating various network changing the state from the host operating system, simulating various network
@ -444,7 +444,7 @@ very creative, there are some limits to such creativity.
The largest system which can be spanned by a single OSPF instance is the whole The largest system which can be spanned by a single OSPF instance is the whole
autonomous system (AS). The largest ASes only have about several hundred autonomous system (AS). The largest ASes only have about several hundred
thousand routers\cite{as-topologies}. The average degree also seems to be rather thousand routers~\cite{as-topologies}. The average degree also seems to be rather
low. low.
We can derive another limit from IPv4 address allocations. A /8 block (i.e. We can derive another limit from IPv4 address allocations. A /8 block (i.e.

@ -335,7 +335,7 @@ neighbours and so on. When there is a completely unplaced component, we place
one of its vertices at random. However, disconnected topologies are of little one of its vertices at random. However, disconnected topologies are of little
interest to us. interest to us.
We tried using Graphviz\cite{graphviz} for laying out the vertices, but we We tried using Graphviz~\cite{graphviz} for laying out the vertices, but we
were not satisfied with its result. To demonstrate, the were not satisfied with its result. To demonstrate, the
listing~\ref{lst:graphviz} describes the topology of our home network with listing~\ref{lst:graphviz} describes the topology of our home network with
Gennet attached. Figure~\ref{fig:graphviz} then shows how each of Graphviz's Gennet attached. Figure~\ref{fig:graphviz} then shows how each of Graphviz's

@ -1,5 +1,7 @@
\chapter*{Conclusion} \chapter*{Conclusion}
\addcontentsline{toc}{chapter}{Conclusion} \addcontentsline{toc}{chapter}{Conclusion}
% Hacked figure number?
\setcounter{chapter}{6}
We developed a simple and standalone tool for visualising OSPF topologies. The We developed a simple and standalone tool for visualising OSPF topologies. The
program is functional and can visualise network systems of medium size. The program is functional and can visualise network systems of medium size. The

@ -74,7 +74,7 @@ particular class in text, it is only capitalised, as in \uv{The keys of the
dictionary are VertexIDs}. dictionary are VertexIDs}.
For network diagrams, we use the Network topology icons from For network diagrams, we use the Network topology icons from
Cisco\cite{cisco-icons}. The basic icons are shown on Cisco~\cite{cisco-icons}. The basic icons are shown on
Figure~\ref{fig:basic-icons}. Figure~\ref{fig:basic-icons}.
\begin{figure}[h] \begin{figure}[h]

Binary file not shown.

@ -25,14 +25,14 @@
inkscape:document-units="mm" inkscape:document-units="mm"
showgrid="false" showgrid="false"
inkscape:zoom="1.1893044" inkscape:zoom="1.1893044"
inkscape:cx="338.01271" inkscape:cx="326.24112"
inkscape:cy="224.92139" inkscape:cy="225.76222"
inkscape:window-width="1920" inkscape:window-width="1920"
inkscape:window-height="1167" inkscape:window-height="1167"
inkscape:window-x="1024" inkscape:window-x="1024"
inkscape:window-y="1094" inkscape:window-y="1094"
inkscape:window-maximized="1" inkscape:window-maximized="1"
inkscape:current-layer="svg5" /><defs inkscape:current-layer="layer2" /><defs
id="defs2"><clipPath id="defs2"><clipPath
clipPathUnits="userSpaceOnUse" clipPathUnits="userSpaceOnUse"
id="clipPath18"><path id="clipPath18"><path
@ -58,7 +58,14 @@
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="m -301.54443,180.97854 27.718,-44.1197 28.27636,-12.62608" d="m -301.54443,180.97854 27.718,-44.1197 28.27636,-12.62608"
id="path2078" id="path2078"
sodipodi:nodetypes="ccc" /></g><g sodipodi:nodetypes="ccc" /><path
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="m -331.5509,152.57644 -19.19852,12.83071"
id="path523"
transform="translate(5.8333333e-6)" /><path
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="m -215.8155,151.41976 21.72488,-15.26896 20.09787,15.26897"
id="path526" /></g><g
inkscape:groupmode="layer" inkscape:groupmode="layer"
id="layer3" id="layer3"
inkscape:label="labels" inkscape:label="labels"
@ -268,7 +275,7 @@
x="-222.99622" x="-222.99622"
y="185.21698">B</tspan></text></g><g y="185.21698">B</tspan></text></g><g
id="g1884" id="g1884"
transform="translate(0.52916667,-2.1936684)"><g transform="translate(1.18167,-14.452138)"><g
id="g496" id="g496"
clip-path="url(#clipPath18-3)" clip-path="url(#clipPath18-3)"
transform="matrix(0.03527778,0,0,-0.03527778,-201.8314,156.89231)"><path transform="matrix(0.03527778,0,0,-0.03527778,-201.8314,156.89231)"><path
@ -345,7 +352,7 @@
x="-275.5849" x="-275.5849"
y="203.62701">F</tspan></text></g><g y="203.62701">F</tspan></text></g><g
id="g1686" id="g1686"
transform="translate(2.2946826,-4.6175891)"><g transform="translate(5.172061,8.896831)"><g
id="g1730"><g id="g1730"><g
id="g676" id="g676"
clip-path="url(#clipPath18-3)" clip-path="url(#clipPath18-3)"

Before

Width:  |  Height:  |  Size: 55 KiB

After

Width:  |  Height:  |  Size: 56 KiB

Loading…
Cancel
Save