This is what you said Tom Eastep
>>>> #INTERFACE IN-BANDWITH OUT-BANDWIDTH
>>>> eth2 16384kbit 1126kbits
>>> ----
>>>
>>> -Tom
>> Ah, yes a SHE (Stupid Human Error). If only I was hooked on phonics.
>
> FWIW, Shorewall-perl catches this SHE at compile-time.
>
Apparently I do not understand traffic shaping, or was not aware of the
hit I would take using traffic shaping. My downstream speeds are
significantly impacted when I am using traffic shaping. I went from
16Mbps to 10Mbps downstream when using traffic shaping.
Here is what I eventually ended up with (see config files below). All I
want to do is give VoIP the max bandwidth (180kbit) when needed. All
other times I just want the traffic to flow as it did before adding
traffic shaping.
All of the 'MARK 4' stuff was added just for more control, it is not
really necessary.
I do not understand why the downstream speed is so negatively impacted.
Is the configuration grossly wrong to be causing such a decrease? Do I
need to go back and read the documentation? Any help would be
appreciated.
Thank You.
/etc/shorewall/tcdevices
#INTERFACE IN-BANDWITH OUT-BANDWIDTH
eth2 16097kbit 1126kbit
/etc/shorewall/tcclasses
#INTERFACE MARK RATE CEIL PRIORITY
OPTIONS
eth2 1 100kbit 180kbit 1
tos=0x68/0xfc,tos=0xb8/0xfc
eth2 2 full/4 full 2
tcp-ack,tos-minimize-delay
eth2 3 full/4 full 3
default
eth2 4 full/8 full*8/10 4
/etc/shorewall/tcrules
#MARK SOURCE DEST PROTO PORT(S)
CLIENT USER TEST LENGTH TOS
#
PORT(S)
1 10.0.0.100 0.0.0.0/0 all
2 0.0.0.0/0 0.0.0.0/0 icmp echo-request
2 0.0.0.0/0 0.0.0.0/0 icmp echo-reply
4 0.0.0.0/0 0.0.0.0/0 tcp 36161
4 0.0.0.0/0 0.0.0.0/0 udp 36161
4 0.0.0.0/0 0.0.0.0/0 tcp 6881
4 0.0.0.0/0 0.0.0.0/0 udp 6881
4 0.0.0.0/0 0.0.0.0/0 tcp 8741
4 0.0.0.0/0 0.0.0.0/0 udp 8741
On a side note I want to report what I believe are some errors in the
documentation related to traffic shapping.
On this page:
http://www.shorewall.net/manpages/shorewall-tcclasses.html
In the Example 1: section there are two columns labeled "MARK". I believe
the second one should be labeled "PRIORITY".
Next, as I obviously do not have a grasp on traffic shaping, this may or
may not be an error. As I see it, the tcclasses and tcrules seem to go
hand-in-hand. So in the documentation, I would think that it would make
sense to use examples where to two go hand-in-hand.
One this Page, http://www.shorewall.net/manpages/shorewall-tcrules.html ,
the example reads:
#MARK/ SOURCE DEST PROTO PORT(S) SOURCE USER
TEST
#CLASSIFY PORT(S)
1 0.0.0.0/0 0.0.0.0/0 icmp echo-request
1 0.0.0.0/0 0.0.0.0/0 icmp echo-reply
RESTORE 0.0.0.0/0 0.0.0.0/0 all - - - 0
CONTINUE 0.0.0.0/0 0.0.0.0/0 all - - -
!0
4 0.0.0.0/0 0.0.0.0/0 ipp2p:all
SAVE 0.0.0.0/0 0.0.0.0/0 all - - -
!0
and on this page,
http://www.shorewall.net/manpages/shorewall-tcclasses.html, the example
reads:
#INTERFACE MARK RATE CEIL MARK OPTIONS
ppp0 1 100kbit 180kbit 1 tos=0x68/0xfc,tos=0xb8/0xfc
ppp0 2 full/4 full 2 tcp-ack,tos-minimize-delay
ppp0 3 full/4 full 3 default
ppp0 4 full/8 full*8/10 4
Again, if I understand any of this, these two examples do not seem to
correlate. If I am correct, it would be nice to have examples that go
together.
Thanks.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
