Traffic Shaper Filter Rules do not work



  • In the Beta Snapshot from Dec 2 2010 I had the following Traffic Shaper configuration working:

    • Shaping was done only on the WAN interface

    • The LAN was divided into subnets and each subnet has had it's own queue

    • Incoming Packets on the LAN interface were put into the queue according to their source adress subnet

    Now, in pfsense 2.0 RC1, all the traffic goes to the default queue. I am not able to put a packet into a queue depending on it's source address. Filtering by other criterias, for example ports seems to work. :(

    Can anybody confirm or deny that this is a bug?

    EDIT: It seems that I can't queue any packets incoming on LAN, only outgoing on WAN



  • My crystal ball says its you the problem ;)



  • :)
    I deleted all my Filter Rules, except "Default allow LAN to any rule". Then I set a queue for this rule, but still all traffic on WAN goes to the default queue, although it was obviously handled by the rule.

    This must be a bug, or not ???



  • Please show me screenshots of your rules and what type of WAN(s) you have.



  • I have only one WAN interface, which is connected by PPPoE to my modem. I attached a screenshot of my filter rule.

    I removed all rules except one, to give a minimum example of what i'm trying to do. All the traffic here goes to the default queue (which is not "wan_celik" :) ). It seems that queuing packets is only possible in the outgoing direction of an interface. Though this makes sense somehow, i'm also sure that it was working in the beta snapshot from December 2nd 2010.

    I will try to mark the packets now with a lan rule and queue them later with a floating WAN rule. But I will have to create twice the count of rules.




  • I just committed a fix which should correct the behavior for you as before.
    Though it may still be a misconfiguration from your part. Please confirm after testing a snapshot from tomorrow.



  • Thank you very much :) My old filter rules work again with the current snapshot.

    By the way, the penalty rule created by the traffic shaper wizard wasn't working, too.

    Keep up the good work!



  • @damur:

    Now, in pfsense 2.0 RC1, all the traffic goes to the default queue. I am not able to put a packet into a queue depending on it's source address. Filtering by other criterias, for example ports seems to work. :(

    Hi I had the same problem.
    Will try today's snapshot.


Log in to reply