I am still using version 1.22 but as far as I know, the traffic shaping rules
only work on outgoing traffic on an interface so to shape incoming WAN traffic
the rule must be on the LAN or OPT interface. If that is still the case, place
your incoming WAN rules on those interfaces using out at the direction.
As pointed out, incoming traffic shaping has limitations not present in outgoing
traffic shaping. I have found it makes a measurable difference protecting VoIP
streams from continuous downloads.
On Sun, 28 Jan 2007 12:37:27 -0700, "Michael" <zlinda1002 at cox dot net> wrote:
>Now the dumb question; how do I go about prioritizing traffic being
>downloaded to my computer with monowall? I have rules in there from when I
>enabled it and some I have added but when viewing the status in ipfw show
>there is 0 traffic going through ANY of the inbound rules. All the
>upload/outbound rules seem to work fine. I have ack, small packet, gre, etc
>set to high priority and at the very top. At the very bottom I have scavenge
>traffic (catch all rule) for inbound (downloaded) set to medium priority.
>Most of the traffic for inbound seems to bypass that catch all rule too