Traffic shaping not working in Beta 4 for outbound queues?
-
No. m0n0wall uses dummynet, we use ALTQ.
-
Okay, The Traffic Shaper in both system look very similar.
However, they have solved the bridge problem very cleverly, in the LAN side anyway.
In m0n0wall, they only have one interface for rules, and the user can shape the rule for inboud/outbound based on the "direction"
So, If you have multiple NIC that are bridged with LAN, you can choose WAN as interface and "in" for direction for choosing "inbound" and "out" for direction for choosing "outbound"
So the Traffic Shaping dosn't need to look for both "In Interface" and "Out Interface".However, pfsense need both "In Interface" and "Out Interface".
-
Yep completely different set of problems. The rabbit whole gets EXTREMELY deep when you dive into ALTQ further.
-
i also had this bug, noticed that i was getting drops on my voip phone, and that things were not going into the voip outbound queue, i have run the cvs sync to releng_1 and will post results here in the next day or so.
-
i also had this bug, noticed that i was getting drops on my voip phone, and that things were not going into the voip outbound queue, i have run the cvs sync to releng_1 and will post results here in the next day or so.
You also need to rerun the traffic shaper wizard.