Remove more mentions of xdp

adminui/templates/diagnostics/route_checker.html

@@ -4,7 +4,7 @@
     <div class="card-header py-3">
         <h1 class="m-0 text-gray-900">Firewall Decision</h6>
             <p>
-                Test the xdp firewall decision for a given user with traffic, this tool will run a test packet through
+                Test the firewall decision for a given user with traffic, this tool will run a test packet through
                 the program and get allow or drop.
             </p>
     </div>

internal/mfaportal/web.go

@@ -695,7 +695,7 @@ func (mp *MfaPortal) routes(w http.ResponseWriter, r *http.Request) {
 
 	routes, err := mp.firewall.GetRoutes(user.Username)
 	if err != nil {
-		log.Println(user.Username, remoteAddress, "Getting routes from xdp failed: ", err)
+		log.Println(user.Username, remoteAddress, "Getting routes from firewall failed: ", err)
 		http.Error(w, "Server Error", http.StatusInternalServerError)
 		return
 	}

internal/router/iptables.go

@@ -25,10 +25,6 @@ func (f *Firewall) setupIptables() error {
 
 	devName := config.Values.Wireguard.DevName
 
-	//So. This to the average person will look like we say "Hey server forward anything and everything from the wireguard interface"
-	//And without the xdp ebpf program it would be, however if you look at xdp.c you can see that we can manipulate maps of addresses for each user
-	//This then controls whether the packet is dropped, but we still need iptables to do the higher level routing stuffs
-
 	err = ipt.ChangePolicy("filter", "FORWARD", "DROP")
 	if err != nil {
 		return err

internal/router/wireguard.go

@@ -510,7 +510,7 @@ func (f *Firewall) setPeerEndpoint(device data.Device, endpoint *net.UDPAddr) er
 	return nil
 }
 
-// Remove a wireguard peer from xdp firewall and wg device
+// Remove a wireguard peer from firewall and wg device
 func (f *Firewall) RemovePeer(publickey, address string) error {
 	f.Lock()
 	defer f.Unlock()