Traffic shaping problem limiting upload (WinSCP SFTP port 22 leaks through)

[toysareforboys]

I'm trying to limit the upload speed of the entire network. I've got the rules in place but it very rarely limits my upload speed and it NEVER limits it for WinSCP SFTP uploads over port 22

Download limiting works flawless.

How I know that it "rarely limits" my upload speed is that I'll set it to some real low number for the upload speed and I can go a day or two without noticing it then I'll try and post a video to facebook and it'll say something like "8 hours remaining" then I boost up the upload limiter and boom, finishes quick. I'll go to speedtest.net and the speed will be limited just fine but if I fire up WinSCP and upload a file over SFTP port 22 it doesn't limit the speed at all A few hours later or the next day then the speed limiter isn't limiting anything anymore (speedtest.net, etc.) and I can't figure out a way to get it back. Another day or two later it'll randomly start limiting again everything but WinSCP.

Here are my settings:

Pipes:





Queues is empty

Rules:





Speed test with pipes enabled:



Speed test with download pipe set to 30mbps:



Speed test with pipes disabled:



What am I doing wrong?

-Jamie M.
(P.S. WAN2 runs everything except for some iptv and voip boxes).

[toysareforboys]

No news? Got a big event this weekend, it's gonna murder my internet when I'm uploading with WinSCP over SFTP

-Jamie M.

[bartjsmit]

Why don't you limit the transfer speed in WinSCP? https://winscp.net/eng/docs/ui_transfer_custom

Bart...

[toysareforboys]

Why don't you limit the transfer speed in WinSCP? https://winscp.net/eng/docs/ui_transfer_custom

Bart...

I wish it was that simple. If I speed limit WinSCP to say 9mbps then something else starts to upload something then it'll kill the internet (which always happens because there's an HLS stream uploading in chunks too).

-Jamie M.

[oisteink]

Note: I've just started looking at opnsense.
This guide has the following settings (adjusted to your values):

Upstream pipe
Bandwidth: 9500 kbit/s
Mask: Destination

Downstream pipe
Bandwidth: 48 Mbit/s
Mask: Destination

Upstream rule:
Interface: WAN
Source: 192.168.1.0/24 (Your lan net)
Target: Upstream pipe

Downstream rule:
Interface: WAN
destination: 192.168.1.0/24 (Your lan net)
Target: Downstream pipe

As I said i'm not familiar with opnsense terminology yet, and not with the dynamic queue creation. Your settings differ in that you have SOURCE set on one of your pipes. The general help on pipes say:
Dynamic queue creation by source or destination address.
choose destination here to share the total bandwidth of this pipe among all connected clients.
choose source to provide all connected clients up to a maximum of this pipe configured bandwidth

What I've done myself, and can verify that works are:
Make a hard limit upstream and downstream pipe and make rules to put traffic into these.
To do so :
- I made two pipes with only bandwidth limit set.
- I made two rules to put traffic into these pipes. One rule on wan putting data into my downstream and one rule on lan putting into my upstream. As I have no automatic queue creation this will only limit data, and not do any queueing.

[STk]

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!