I am using pfsense. I have rsync backing up every night (ssh). However, if rsync continues to run into the morning, it uses all the upload bwidth from the one location, causing the VPN to stutter horribly.
So I wanted to allow rsync all the bandwidth that it can be allotted at night, but then limit it once people start trying to use the network (morning).
Pfsense uses Dummynet pipes to accomplish bandwidth squeezing. This works fine if rsync is initiated AFTER the pipe is already active. However, if rsync is running through the night, and the pipe becomes active the following morning, rsync keeps using all of the bandwidth available.
Out of curiosity, why is it that the Dummynet pipe does not apply to the already existing connection?
Are there any suggestions on how to do what I wish? I don't necessarily need to use rsync in particular; it seemed to be the most simple solution to use for doing backups at the time.
So I wanted to allow rsync all the bandwidth that it can be allotted at night, but then limit it once people start trying to use the network (morning).
Pfsense uses Dummynet pipes to accomplish bandwidth squeezing. This works fine if rsync is initiated AFTER the pipe is already active. However, if rsync is running through the night, and the pipe becomes active the following morning, rsync keeps using all of the bandwidth available.
Out of curiosity, why is it that the Dummynet pipe does not apply to the already existing connection?
Are there any suggestions on how to do what I wish? I don't necessarily need to use rsync in particular; it seemed to be the most simple solution to use for doing backups at the time.