public-mirrors
/
innernet
mirror of https://github.com/tonarino/innernet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
innernet/netlink-request/Cargo.toml

13 lines
296 B
TOML
Raw Normal View History

(linux) wireguard-control: migrate from `wireguard-control-sys` to `netlink` crates (#177) also introduces a new `netlink-request` crate to help modularize the netlink code. this currently depends on a fork of the `netlink` project, but we should be able to use the official version soon.
2022-01-07 09:35:21 +00:00
[package]
name = "netlink-request"
meta: release v1.5.5
2022-09-24 04:16:35 +00:00
version = "1.5.5"
(linux) wireguard-control: migrate from `wireguard-control-sys` to `netlink` crates (#177) also introduces a new `netlink-request` crate to help modularize the netlink code. this currently depends on a fork of the `netlink` project, but we should be able to use the official version soon.
2022-01-07 09:35:21 +00:00
edition = "2021"
[target.'cfg(target_os = "linux")'.dependencies]
netlink-sys = "0.8"
netlink-packet-core = "0.4"
netlink-packet-generic = "0.3"
meta: cargo update
2022-08-10 21:55:01 +00:00
netlink-packet-route = "0.13"
Use the proper netlink buffer size with large kernel pages The recommended netlink buffer size is based on the system's page size, which means that the current size is far too small for systems with 16k or 64k pages, such as Asahi Linux or RHEL's kernel-64k for ARM64. On these systems, the server fails to start with errors like this: Error: Decode error occurred: invalid netlink buffer: length field says 1444 the buffer is 1260 bytes long Instead, follow the kernel's own netlink docs to compute the buffer size. The approach here matches the approach merged into Chromium recently: https://chromium-review.googlesource.com/c/chromium/src/+/4312885
2023-05-27 21:59:32 +00:00
nix = { version = "0.25", features = ["feature"] }
once_cell = "1"