Fixes to get document to compile

chapter/ip.tex

@@ -4,7 +4,7 @@
 
 \gls{ipv6} has recently been defined in an updated \rfc{8200} which obsoletes several of the older \gls{rfc} documents regarding \gls{ipv6}.
 
-\gls{ipv6} came about in 1998 when the original \rfc{2460} was published. It aims to provide globally route-able addresses (i.e. no need for \gls{nat}) and provides a hierarchical way to allocate address prefixes in a way which makes it simple to do route aggregation\footnote{This helps limits the size of the Internet's global routing table!}.\cite{wiki:IPv6}
+\gls{ipv6} came about in 1998 when the original \rfc{2460} was published. It aims to provide globally route-able addresses (i.e. no need for \gls{nat}) and provides a hierarchical way to allocate address prefixes in a way which makes it simple to do route aggregation.\footnote{This helps limits the size of the Internet's global routing table!}\cite{wiki:IPv6}
 
 \wikicommons[An illustration of an example IPv6 address with leading zeros in the binary rendering]{ipv6_address_leading_zeros}
 
@@ -35,7 +35,7 @@ Have 3 different forms:
 
 \subsection{Packet Headers}\cite{IPv6Pack77:online}
 
-\wikicommons{Ipv6_header}
+\wikicommons{ipv6_header}
 
 \begin{enumerate}
     \item \textbf{Version} -- 1-byte field containing '6'.
@@ -81,7 +81,7 @@ Have 3 different forms:
         \begin{itemize}
             \item Consist of the prefix \texttt{ff02::1:ff00:0/104} for the first 104 bits.
             \item The last 24 bits represents the target address within the prefix.
-            \item Solicited-node multicast address is segment only traffic. I.e. the traffic does not flow \textit{between \gls{l3} \gls{ip} segments.
+            \item Solicited-node multicast address is segment only traffic. I.e. the traffic does not flow \textit{between} \gls{l3} \gls{ip} segments.
             \item Used in combination with \gls{nd} to replace \glspl{ip4} \gls{arp} functionality.
         \end{itemize}
     \end{itemize}

chapter/layer2.tex

@@ -17,6 +17,7 @@ Of course you can \textit{disable} \gls{vtp} altogether.
 Key things to be aware of \textit{before} enabling \gls{vtp} in your environment is to make double sure of only having 1 \gls{vtp} domain. \textbf{If} 2 or more \gls{vtp} domains exists. Be triple sure to separate them! As to avoid having an \gls{vtp} server \gls{db} overridden with data from another \gls{vtp} domain.
 
 The three \gls{vtp} modes \textit{operates} as follow
+
 \begin{itemize}
     \item Transparent
     \begin{itemize}

chapter/layer3.tex

@@ -12,7 +12,7 @@
 \wikicommons{BGP_FSM}
 
 The protocol of the internet used since 1994.\cite{wiki:Border_Gateway_Protocol}
-Currently based upon \rfc{4271} with updates following in \rcf{6286} \rfc{6608}, \rfc{6793}, \rfc{7606}, \rfc{7607}, \rfc{7705}.
+Currently based upon \rfc{4271} with updates following in \rfc{6286} \rfc{6608}, \rfc{6793}, \rfc{7606}, \rfc{7607}, \rfc{7705}.
 
 
 
@@ -29,11 +29,11 @@ Currently based upon \rfc{4271} with updates following in \rcf{6286} \rfc{6608},
         \begin{itemize}
             \item Routes can be aggregated between \Glspl{as}.
             \item Properties can be changed on the fly by mathing
-            \begin{enumerate*}[label={\alph*)}]
+            \begin{enumerate}[label={\alph*)}]
                 \item \Gls{bgp} communities,
                 \item \Gls{ip} prefix,
                 \item \Gls{bgp} as-path, 
-            \end{enumerate*}
+            \end{enumerate}
         \end{itemize}
         \item 
     \end{itemize}

references-websites.bib

@@ -15,10 +15,10 @@
 }
 
 @misc{IPv6Pack77:online,
-    author = {},
+    author = {Oracle},
     title = {IPv6 Packet Header Format - System Administration Guide: IP Services},
     howpublished = {\url{http://docs.oracle.com/cd/E23823_01/html/816-4554/ipv6-ref-2.html}},
     month = {},
-    year = {},
+    year = {2010},
     note = {(Accessed on 07/23/2017)}
 }