Beta 1.0 Livecd - Does shaping actually work?
-
Please PM me your config xml or paste it here, something is fishy, I have done testing with 3-400 mbiton a dual xeon in the past and as long as I had the shaper config done correctly it did behave as expected.
PS. this is free sw, devs spend tons of time for free to help others, so to call our efforts worthless and shit isn't very nice !!
-
Ok, I opened another thread about this very issue and no one responded with anything remotely useful. So here is the evidence I have collected to confirm that the traffic shaper in it's current form is worthless!
Here is the test setup I have isolated. I have removed everything I can possibly think of to make this as simple as possible:
Cisco 2924 switch #1 with my test "workstation" and the internal pfsense interface. Cisco 2924 #2 with pfsense outside and uplink to network. This is all 100meg links and thoroughly tested that it all works. I got a clean pfsense box with nothing else on it. It has 2 broadcom bg0 interfaces in it (I have tried 2 intel, 2 realtek, 2 dc0, it doesn't matter), there is no other packages running, I turned off all unnecessary services. I can run 75 meg/s through this box and it barely breaks a sweat! The ping times stay at under 1ms at ALL TIMES!
As SOON as I turn on the shaper it all goes to SHIT! I can set the shaper to 5 meg/s and make sure I don't go anywhere near that, and i will start to see fluctuations in the ping times. If I get about 90% of the shaper bandwidth, the pings really start to go off. Before I reach 95%+ of the bandwidth, the box is pretty much worthless. The pings will time out, traffic and streams start to break up.
Before everyone starts with the normal misconfig crap: I have ICMP set to highest priority. I can setup m0n0wall or IPCop on the same box and it is silky smooth with the shaper on and does exactly as I would expect. The only reason I am even spending my time here, is because I want to see it get resolved. Unfortunately, I do not have the time to solve this myself. If you need help testing, I am happy to help.
One piece of advice, move the LAN (downstream) shaping to the WAN interface on an ingress queue where it belongs. If you need an example of this, just drop me a line.
Roy
Seeing as inbound queuing is a lie in the first place, I'd like to see how you plan on doing inbound shaping. I have half a mind to remove that part of the code altogether, it can't work, it's impossible, it's too late. Also, altq doesn't actually allow for inbound queueing…for that exact reason, the packet has already crossed the wire. We don't need testers for the shaper, we need someone who can spend the time to fix issues they find with it. When that person has something to test, I'm sure they'll call for testers.
--Bill