diff --git a/implementation/ethernet-lidar.tex b/implementation/ethernet-lidar.tex
index 69abbc96d6338f7fa0485fc28c523e3e2f17502f..45f714b750c26ccc8f082b5b91cc5b983f9fda38 100644
--- a/implementation/ethernet-lidar.tex
+++ b/implementation/ethernet-lidar.tex
@@ -1,3 +1,4 @@
+\newpage
 \subsection{Ethernet}
 \label{sec:ethernet}
 \subsectionauthor{Author: Henrik Tjäder\\Reviewer: Fredrik Grönlund}
@@ -108,5 +109,5 @@ This will be great for controlling the amount of data sent over the UWB radio li
 The standard setting sends $2 \cdot 1474 + 543 = 3491$ bytes of data (including headers). The \texttt{UWB} maximum \texttt{MTU} is \texttt{127 bytes}.
 Thus the UWB would have to transmit at least 28 frames just for the LIDAR. Then there is the metadata such as the stepper motor angle, the sonar data etc.
 
-This is where the \texttt{LAMP} protocol comes into play.
+This is where the \texttt{LAMP}~\ref{sec:LAMP} protocol comes into play.