Multiple Interface Shaping
-
Not sure. Give it a try and report back.
-
Not sure. Give it a try and report back.
As per the first tests it seems to be working :)
-
Not sure. Give it a try and report back.
As per the first tests it seems to be working :)
Interesting, considering ALTQ won't be bound to the OPT interface. Outbound traffic will be shaped however regardless of interface (and OPT->LAN will be shaped to the downstream connection speed).
–Bill
-
Interesting, considering ALTQ won't be bound to the OPT interface. Outbound traffic will be shaped however regardless of interface (and OPT->LAN will be shaped to the downstream connection speed).
–Bill
You are right. Testing a litlle bit more, it seems that speed is
O.K. WAN–>LAN
O.K. WAN-->OPT
(when downloading from internet at the same time to a wlan and lan client, traffic shared roughly equally)
(O.K. LAN-->OPT (the limit was the wifi speed)
and really it seems to be limited to WAN outgoing speed at the OPT-->LAN relation.
Is there any way to solve this? -
Interesting, considering ALTQ won't be bound to the OPT interface. Outbound traffic will be shaped however regardless of interface (and OPT->LAN will be shaped to the downstream connection speed).
–Bill
You are right. Testing a litlle bit more, it seems that speed is
O.K. WAN–>LAN
O.K. WAN-->OPT
(when downloading from internet at the same time to a wlan and lan client, traffic shared roughly equally)
(O.K. LAN-->OPT (the limit was the wifi speed)
and really it seems to be limited to WAN outgoing speed at the OPT-->LAN relation.
Is there any way to solve this?Not at this time.
–Bill
-
We really need a traffic shaper for multiple interfaces. If I donate will this accelerate the process.. ;)
Charles
-
I'm sure it will but let me point out 1.0 is frozen, this will not make it into 1.0.
With that said, donate away to Bill, he needs new toys!
-
We really need a traffic shaper for multiple interfaces. If I donate will this accelerate the process.. ;)
Charles
As Scott mentioned, 1.0 is frozen. Development has started for 1.1, so get your requests in early. I've got interface choosing done already (not multiple interfaces, but at least you get to make a choice as to which interfaces you want shaped) and am working on layer 7 shaping decisions. Multiple interfaces is a possibility, but it's going to be a while before it's in anything but the next alpha (donations might help get it to alpha quicker as I've got other projects I really wanna work on other than the shaper).
See http://wiki.pfsense.com/wikka.php?wakka=BillM
–Bill
-
I'm trying pfSense BETA iso in my testing machine.
pfSense probed my NIC:- DLink DFE-580TX as ste0, ste1, ste2, ste3
- Compex as wb0
- NForce2 as nve0
I use nve0 as my LAN with speed 100Mb and ste0, ste1, ste2 as my WAN with speed 100Mb.
It seems pfSense didn't support multiple interface shaping.
Is there any workarround to enable this feature? -
Not at this time. Patches accepted.
-
Not at this time. Patches accepted.
Patches accepted (although I know exactly what needs to be done, I backed out the code for this back in June due to other issues) - but be warned the shaper is under heavy development, you will want to coordinate any work you do with me.
Or again, donations are accepted - at this point a quiet machine with Intel FXPs would be appreciated. I can no longer do shaper development on my (silent) Soekris as there's an OS level bug that affects the NICs on this machine.
–Bill