Traffic shaping not working in Beta 4 for outbound queues?
-
That's something to do for 1.1 though there is no fixed featureset for 1.1 yet. If it's doable it will be implemented sooner or later.
However if you are shaping WAN/LAN and your OPT1 is bridged to LAN there are chances that the shaping actually works. I think I heared someone report this scenario is working earlier, but not too sure about it. Try and let us know.
-
Can i have comment from professional to my questions?
:)
Bridge0 - logical interface .. but them can use for all rules in PF, yes?
Can bridge0 use in ALTQ rules?
May be this take effect for shaping (of cose if this possible) -
I suspect that the queue is working,
The problem is the rules.In rules, you define "In Interface" and "Out Inferface", and what we miss here is the term for ANY
This is tipical picture of configuration, if we only could choose
In Interface = WAN
Out Interface = ANYThen I think the problem would be solved.
-
Thx.
I today testing bridge queue rule with
source * destination* - define only protocol and port.
in simple model i give worked result. If time give possible - tomorrow be testing more big model. -
I suspect that the queue is working,
The problem is the rules.In rules, you define "In Interface" and "Out Inferface", and what we miss here is the term for ANY
This is tipical picture of configuration, if we only could choose
In Interface = WAN
Out Interface = ANYThen I think the problem would be solved.
Sorta…too bad it's not quite that simple ;)
--Bill
-
Billm,
Dose pfsense and m0n0wall use the same Traffic Shaping Engine ?
-
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.