Always allow fwmark in uapi commands

Allow fwmark to be in the config even on platforms that do not support it. Just ignore it. It is in line with wireguard-go behaviour.
NordSecurity · Dec 2, 2024 · ffa729c · ffa729c
1 parent 0bdd56b
commit ffa729c
Showing 1 changed file with 13 additions and 11 deletions.
diff --git a/neptun/src/device/api.rs b/neptun/src/device/api.rs
@@ -230,17 +230,19 @@ fn api_set<R: Read>(reader: &mut BufReader<R>, d: &mut LockReadGuard<Device>) ->
                             },
                             Err(_) => return EINVAL,
                         },
-                        #[cfg(any(
-                            target_os = "android",
-                            target_os = "fuchsia",
-                            target_os = "linux"
-                        ))]
-                        "fwmark" => match val.parse::<u32>() {
-                            Ok(mark) => match device.set_fwmark(mark) {
-                                Ok(()) => {}
-                                Err(_) => return EADDRINUSE,
-                            },
-                            Err(_) => return EINVAL,
+                        "fwmark" => {
+                            #[cfg(any(
+                                target_os = "android",
+                                target_os = "fuchsia",
+                                target_os = "linux"
+                            ))]
+                            match val.parse::<u32>() {
+                                Ok(mark) => match device.set_fwmark(mark) {
+                                    Ok(()) => {}
+                                    Err(_) => return EADDRINUSE,
+                                },
+                                Err(_) => return EINVAL,
+                            }
                         },
                         "replace_peers" => match val.parse::<bool>() {
                             Ok(true) => device.clear_peers(),