My first post!
I'm a linux noob and a Pi noob, so please forgive my vast ignorance.
Our network uses PRTG for monitoring. I am setting up 3 Pi 5 B's running Bookworm as remote agents for running real-world throughput tests using iPerf (NB: *not* iPerf3 - which is not compatible with the script I"m using). We are using the iperf script here: https://github.com/rkagerer/iperfsensor ... fsensor.sh
Because we wish to alternate tests via hardline ethernet (eth0) and wifi (wlan0), I need to implement policy routing (or whatever is the current equivalent in Raspberry OS. The various binding flags available in iperf are not sufficient for this purpose.
For setting up policy routing on Linux, I am using the tutorial here: https://blog.scottlowe.org/2013/05/29/a ... y-routing/
All of this makes sense to me. However, it appears that /etc/network/interfaces is no longer being used directly to create and manage interface connection parameters, and thus I have nowhere to configure persistence for the rules and routes.
A smattering of research has led me to suspect that all of this is now being handled within dhcpd and modifications to dhcpd.conf. However, I have no idea where to begin with this, and can find no equivalent tutorials to help guide my well-meaning newbie self to success.
Any help?
I'm a linux noob and a Pi noob, so please forgive my vast ignorance.
Our network uses PRTG for monitoring. I am setting up 3 Pi 5 B's running Bookworm as remote agents for running real-world throughput tests using iPerf (NB: *not* iPerf3 - which is not compatible with the script I"m using). We are using the iperf script here: https://github.com/rkagerer/iperfsensor ... fsensor.sh
Because we wish to alternate tests via hardline ethernet (eth0) and wifi (wlan0), I need to implement policy routing (or whatever is the current equivalent in Raspberry OS. The various binding flags available in iperf are not sufficient for this purpose.
For setting up policy routing on Linux, I am using the tutorial here: https://blog.scottlowe.org/2013/05/29/a ... y-routing/
All of this makes sense to me. However, it appears that /etc/network/interfaces is no longer being used directly to create and manage interface connection parameters, and thus I have nowhere to configure persistence for the rules and routes.
A smattering of research has led me to suspect that all of this is now being handled within dhcpd and modifications to dhcpd.conf. However, I have no idea where to begin with this, and can find no equivalent tutorials to help guide my well-meaning newbie self to success.
Any help?
Statistics: Posted by clearfire — Fri Jul 19, 2024 11:14 pm — Replies 0 — Views 32