Messages

Anyone some info to that?

Hi,

i am not sure, whether using a destination mask for an upload queue is right, like documentation desribes that.
See here: https://forum.opnsense.org/index.php?topic=4949.0

Feeback very welcome!

Hi,

had the same problem with windows - I gave up after servera hours of trying.
Use an unix based system to create the stick, e.g. finde someone who has mac or linux.
And use the img-version, not the iso.

Regards,
Sebastian

Hi,

I am not sure, but there seems to be a mistake in the traffic shaping help (in ui) and documentation (https://docs.opnsense.org/manual/how-tos/shaper.html).

You can use source- and destination-masks in pipes.
Help and howto use "source" for limit bandwith per client and "destination" to share bandwith.
If I am right about that, that is not generally correct.

Again, if I am right:
A pipe has a fixed (e.g. maximum) bandwith.
It is possbile to share this bandwith with dynamic buckets generated by source or destitination address.
Each source or destination address gets an own bucket, which are served all evenly in a pipe.
In both variants (source mask or destination mask) the pipes bandwidth will be shared.
There is no possibility to create buckets which gains maximum bandwith of the pipe each - like a new pipe (limiter) for every bucket.

For example relating to howto "Share bandwidth evenly":
Howto says to use destination mask for upload-pipe for sharing upload bandwidth evenly.
The upload pipe (used with WAN-interface) then creates a buckets for destination-adresses.
So upload-bandwith is shared based on the destination-adresses, e.g. the online-server-addresses.
Accordingly this pipe shares traffic for internet servers: Every internet-ip gets an own bucket.
This pipe (describes in howto) does not share traffice on a lan-user-base.
To do that, upload-pipe should configured with a source-mask.

Please correct me, if I am wrong.
Thank You in advance!
Sebastian

Btw. I am new to opnSense, migrated from pfSense last week.