diff --git a/en/chap02.tex b/en/chap02.tex index 751d366..eb9c17f 100644 --- a/en/chap02.tex +++ b/en/chap02.tex @@ -3,8 +3,11 @@ In order to avoid as many problems as possible when visualising and analysing a OSPF topology, we need to understand several aspects of networking, the OSPF protocol and its implementation in BIRD. However, the aim of this -thesis is not to be a complete guide to OSPF nor BIRD, so we only describe -enough details to be able to reason about the design of the implementation. +thesis is not to be a complete guide to OSPF nor BIRD, therefore, for the sake +of brevity, we skip many details which do not influence our project. + +Later in this chapter we also present a way to simulate uncommon network states +using a \uv{swarm} of virtual machines. \section{OSPF overview} @@ -16,10 +19,10 @@ running it on a much smaller scale is also possible. OSPF requires routers to share information about the state of the topology in messages called \emph{Link State Advertisements} (or LSAs for short). The LSAs -contain information about which network segments are adjacent \X{term} to which +contain information about which network segments are incident to which router on which interfaces and with which routers it is possible to communicate on those interfaces. To distinguish between routers, each router is assigned a -32-bit number called \emph{Router ID} by the network administrator \X{term}. +32-bit number called \emph{Router ID} by the network administrator. Router IDs are usually written in a quad-dotted notation \X{glos}. The LSAs are flooded throughout the system in order to let all the routers know @@ -30,12 +33,12 @@ DR) which coordinates exchange of the messages in that network segment. Second, the system can be partitioned into \emph{areas}. That way, the frequent LSAs are only flooded throughout a limited set of networks; the \emph{area border routers} (ABRs) send accumulated LSAs into other areas.\footnote{These -inter-area LSAs are called \uv{Summary LSAs}, but there is no requirement that +inter-area LSAs are called \uv{Summary LSAs} in OSPFv2, but there is no requirement that the routing information is actually aggregated.} These LSAs do not describe the topology of the originating area. The area 0.0.0.0 is called the \emph{backbone area} and all other areas must be -adjacent to it, so that it has all the routing information. When this is +incident to it, so that it has all the routing information. When this is impractical, OSPF allows two routers to be connected using a \emph{virtual link}. From the routing perspective, this is a point-to-point connection between the routers in the backbone area. which allows to forward LSAs through @@ -52,7 +55,8 @@ Figure.~\ref{fig:nettypes} shows the same classification visually. \begin{figure}[h] \centering - \includegraphics[width=12cm]{../img/types-of-networks.pdf} + % full width and hope it is readable… + \includegraphics[width=\textwidth]{../img/types-of-networks.pdf} \caption{Types of networks as seen from the cyan area.} \label{fig:nettypes} \end{figure} @@ -78,7 +82,7 @@ any internal or type 1 cost. The OSPF family of routing protocols has undergone long evolution since the 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 -same, OSPFv2 can only handle IPv4 systems. While 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 fact, features like virtual links can only be used with that network protocol\cite{rfc5838}. diff --git a/en/glossary.tex b/en/glossary.tex new file mode 100644 index 0000000..2283cce --- /dev/null +++ b/en/glossary.tex @@ -0,0 +1,4 @@ +\chapter*{Glossary}\label{ch:glossary} +\addcontentsline{toc}{chapter}{Glossary} + +\XXX{TODO} diff --git a/en/thesis.tex b/en/thesis.tex index 140fc01..83cf9b3 100644 --- a/en/thesis.tex +++ b/en/thesis.tex @@ -51,6 +51,7 @@ \usepackage{paralist} % improved enumerate and itemize \usepackage{xcolor} % typesetting in color \usepackage{csquotes} +\usepackage{subcaption} %% SPECIMEN % Parts marked as SPECIMEN are used for building the example PDF. @@ -132,24 +133,21 @@ Abstract. \X{Recommended length around 80--200 words. This is not a~copy of your %%% Bibliography \include{bibliography} -%%% Figures used in the thesis (consider if this is needed) -\listoffigures +\include{glossary} -%%% Tables used in the thesis (consider if this is needed) -%%% In mathematical theses, it could be better to move the list of tables to the beginning of the thesis. -\listoftables -\XXX{In mathematical theses, it could be better to move the list of tables to the beginning of the thesis.} +%% %%% Figures used in the thesis (consider if this is needed) +%% \listoffigures +%% +%% %%% Tables used in the thesis (consider if this is needed) +%% %%% In mathematical theses, it could be better to move the list of tables to the beginning of the thesis. +%% \listoftables +%% \XXX{In mathematical theses, it could be better to move the list of tables to the beginning of the thesis.} %%% Abbreviations used in the thesis, if any, including their explanation %%% In mathematical theses, it could be better to move the list of abbreviations to the beginning of the thesis. \chapwithtoc{List of Abbreviations} \XXX{In mathematical theses, it could be better to move the list of abbreviations to the beginning of the thesis.} - -%% PHDONLY -%%% Doctoral theses must contain a list of author's publications -\chapwithtoc{List of publications} -\XXX{Doctoral theses must contain a list of author's publications.} -%% ONLYPHD +\XXX{TODO} %%% Attachments to the bachelor thesis, if any. Each attachment must be %%% referred to at least once from the text of the thesis. Attachments diff --git a/img/types-of-networks.pdf b/img/types-of-networks.pdf index 8554963..da68970 100644 Binary files a/img/types-of-networks.pdf and b/img/types-of-networks.pdf differ diff --git a/img/types-of-networks.svg b/img/types-of-networks.svg index 65ab35e..a9936d4 100644 --- a/img/types-of-networks.svg +++ b/img/types-of-networks.svg @@ -25,15 +25,15 @@ inkscape:deskcolor="#ffffff" inkscape:document-units="mm" showgrid="false" - inkscape:zoom="0.84096521" - inkscape:cx="363.86761" - inkscape:cy="174.20459" + inkscape:zoom="1.6819304" + inkscape:cx="414.40478" + inkscape:cy="228.60637" inkscape:window-width="1920" inkscape:window-height="1167" inkscape:window-x="1024" inkscape:window-y="1094" inkscape:window-maximized="1" - inkscape:current-layer="layer2" + inkscape:current-layer="layer3" showborder="true" />virtual linkvirtual link(in backbonearea only)