refactor and comment code. add more descriptive error message.

1 files changed, 9 insertions, 26 deletions

diff --git a/README.md b/README.md
index e097c82..76f4ca4 100644
--- a/README.md
+++ b/README.md
@@ -5,17 +5,23 @@ This project is an implementation of IP pipelines in Go. The project is split in
 ## Vrouter and Vhost Design
 Vrouter and Vhost follow similar designs, with a check to ensure than an lnxconfig file is passed into, to initialize the node with the parsed information from the lnxfiles. For both nodes we register the test protocol handler, and the rip protocol handler specifically for routers. We then listen for command line interfaces, while threads were initialized in the initialization. We follow the specifications of the handout having the following functions and functionality:
 
+```
 li: List interfaces
 lr: List routes
 ln: List available neighbors
 up: Enable an interface
 down: Disable an interface
 send: Send test packet
+q/exit: Quit program
+```
+
 
 Because the vhost and vrouter are so similar, we maintain most of the logic within the IPStack in which the vrouter and vhost call when necessary.
 
-## IPStack Design
-We build our abstractions for the IP layer and interfaces with the following structs: 
+## Abstractions
+
+
+Using these two struct below, we abstract for the IP layer and interfaces with the following structs: 
 
 type Interface struct {
 
@@ -37,30 +43,7 @@ type Neighbor struct {
 
 }
 
-type RIPHeader struct {
-
-	command    uint16
-	numEntries uint16
-
-}
-
-type RIPEntry struct {
-
-	prefix netip.Prefix
-	cost   uint32
-
-}
-
-type Hop struct {
-
-	Cost uint32
-	Type string
-	Interface *Interface
-	VIP       netip.Addr
-
-}
-
-With these structs, we are able to maintain the information necessary for the IPStack to function and for the vhost and vrouter to interact with its interfaces, neighbors, and routes when applicable.
+With these structs,
 
 # Initialization/Main Thread