Messages

1

24.1 Legacy Series / Re: Periodic Speedtest

« on: August 16, 2024, 04:07:00 am »

I ran

Code: [Select]

sudo -i
cd /usr/local/opnsense/scripts/OPNsense/speedtest/opn_speedtest.py
python3 opn_speedtest.py

I got the same error as beneix, then I remembered to rm speedtest.csv, now the command works.

Jury is still out on whether anything magically fixed the cron job tho.

2

24.1 Legacy Series / Re: Tackling BufferBloat and Equitably Sharing Bandwidth

« on: March 26, 2024, 07:14:49 pm »

Thank you, that was an excellent response.

If I do these things ...

1. Copy Maltech's download pipe and set BW 150 quantum 350
2. Copy their queue and connect it to the copied pipe
3. Copy their rule, put it first in the sequence, target the copied queue, and assign the destination .96/28

... assuming my Maltech download and upload pipes are bandwidth 860, and download is quantum 2560 ...

... do I have to back the Maltech download pipe to bandwidth 710 and quantum 2200?

This is based on the reasoning that the pipes are blissfully unaware of each other's existence and that I will be setting a hard QOS in favor of the .96/28.

Am I going wrong anywhere in here?

3

24.1 Legacy Series / Tackling BufferBloat and Equitably Sharing Bandwidth

« on: March 26, 2024, 03:30:37 am »

I've applied Maltech's BufferBloat How-To on my symmetrical 1GB ATT fiber service.

Now, I want to add something like shaped, equitable bandwidth sharing on top of it, and I want to apply the shaping to a subset of hosts.

192.168.200.0/24  <--- internal subnet
192.168.200.96/28 <--- equitably share up to 300MB among themselves, on demand
192.168.200.128/25 <--- equitably share up to 50MB among themselves, on demand

So .0/24 would get 1000MB when .96/28 and .128/25 are idle.

Then, a host in .96/28 would wake up and pull up to 300MB from the rest of the .0/24. If a second host woke up in .96/28 pulling 300MB, it would only get 150MB, and the first host would drop back to 150MB - equitable sharing! Ditto for the .128/25 but the numbers are smaller. 

Finally, if a host outside of .96/28 or .128/25 started pulling hard, it wouldn't rob bandwidth from the smaller subnets as long as they ran below their limits.

This sounds like basic QOS to me, but I don't know how it dovetails with the bufferbloat fix and the OPNsense UI.

So I have two questions right off the bat: 1> Am I making sense here, and 2> Is it possible to do this? Thank you!