You can achive this by using hsfc traffic shaper.You can use Service Curve -> Upperlimit ->m2 field on proper Queue. Then attach queue to the rule involving host alias.
Are you using squid with traffic shaper ?
if yes : Squid bypass traffic on port 80 , so traffic shaper can not catch the traffic , then the traffic port 80 and all of other uncategorized traffic flow on DEFAULT QUEUE.So you give 1 priority to Default Queue but there is no traffic matching other queues , therefore Default queue pretend to eating all of the available traffic.
if no : I recommend HFSC
Follow the Traffic shaper wizard (single wan/multi lan), and it will eventually ask you about VOIP provider/settings. Fill in the details and it will create a rule for voip traffic, found on the 'floating rules' tab.
@slth:
Alas, without any result: bandwidth isn't being limited at all :(
Hi, try to check the order of the firewall rules, maybe a previous rule is applied to that traffic so the firewall doesn't process the rule with the IN/OUT options…
@Gitsum:
I think the QOS feature in pfsense is broken. I tried for too long trying to get it to work. I gave up and went back to my dlink.
well… it's for sure not easy, the first time I needed support to let it work, and before 2.0 RELEASE I think was not also so stable, but it is working very well on my firewalls now.
I had the same doubt that I am missing or mistaking something...
The devices are iPads and we dont wish to use a proxy. iPad apps dont all work nicely with proxies, especially if that proxy requires authentication. So we have a seperate web filter that operates as a transparent bridge which does web filter, but not SSL intercepting. Then we have pfSense box on the other end of that as our main WAN router. One single subnet for our whole internal network, so pfSense is just being used for pure firewall and NAT type stuff.
Had hoped the L7 stuff was the answer, as there doesnt appear to be any other way to do it.
Guess we just have to live with iMessage and FaceTime on our net :(
hi again.
I changed the cron entry a little bit so it suits my setup.
Perhaps for future pfsense relases this could be realized that there aren't so many (unneccessary) filter reloads.
In a scheduler I have to define a start time and an end time. every time needs an "hour" and a "minute". per haps it can be realized that the minutes and the hours could be entered in the cron job.
So lets say:
Start:
[hour1]: 6
[minute1]: 0
End:
[hour2]: 17
[minute2]: 30
out of these times we can create a cron job like that:
[minute1],[minute2] [hour1],[hour2] * * * root /etc/rc.filter_configure_sync
I am no coding expert and I do not know what is behind the scenes but it is an idea :)