>> Hello list,
>>      I discover strange behaviour of shaping traffic that i setup from 
>> Shorewall-4.0.2.
>> I know that this is not Shorewall problem but may be somebody from list 
>> can help me
> 
> Are you using Shorewall-shell or Shorewall-perl?
> Are these GigE interfaces?
> What is the MTU of eth0?
  
    I am using Shorewall-perl.
    There are GigE interfaces but using 1000Mbit and 100Mbit switches.
    On local PC mtu - 1500 byte:

2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 
1000
     link/ether 00:14:85:31:f2:7f brd ff:ff:ff:ff:ff:ff

    On server also:

5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
     link/ether 00:18:51:64:a1:0b brd ff:ff:ff:ff:ff:ff


    And yet for additional info:

gate / # shorewall show classifiers
Shorewall 4.0.2 Clasifiers at gate - Mon Aug 27 12:00:47 EEST 2007

Device eth0:
filter parent 2: protocol ip pref 1 fw
filter parent 2: protocol ip pref 1 fw handle 0x1e classid 2:130
filter parent 2: protocol ip pref 1 fw handle 0x1f classid 2:131
filter parent 2: protocol ip pref 1 fw handle 0x20 classid 2:132
filter parent 2: protocol ip pref 1 fw handle 0x21 classid 2:133

Device eth1:
filter parent 4: protocol ip pref 1 fw
filter parent 4: protocol ip pref 1 fw handle 0x14 classid 4:120
filter parent 4: protocol ip pref 1 fw handle 0x15 classid 4:121
filter parent 4: protocol ip pref 1 fw handle 0x16 classid 4:122
filter parent 4: protocol ip pref 1 fw handle 0x17 classid 4:123

Device eth2:
filter parent 1: protocol ip pref 1 fw
filter parent 1: protocol ip pref 1 fw handle 0x1 classid 1:11
filter parent 1: protocol ip pref 1 fw handle 0x2 classid 1:12
filter parent 1: protocol ip pref 1 fw handle 0xa classid 1:110
filter parent 1: protocol ip pref 1 fw handle 0xb classid 1:111
filter parent 1: protocol ip pref 1 fw handle 0xc classid 1:112
filter parent 1: protocol ip pref 1 fw handle 0xd classid 1:113
filter parent 1: protocol ip pref 1 fw handle 0xe classid 1:114
filter parent 1: protocol ip pref 10 u32
filter parent 1: protocol ip pref 10 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 
bkt 0 flowid 1:11  (rule hit 128036 success 96617)
   match 00060000/00ff0000 at 8 (success 126468 )
   match 05000000/0f00ffc0 at 0 (success 99819 )
   match 00100000/00ff0000 at 32 (success 96617 )
filter parent 1: protocol ip pref 10 u32 fh 800::801 order 2049 key ht 800 
bkt 0 flowid 1:11  (rule hit 31419 success 0)
   match 00100000/00100000 at 0 (success 0 )

Device eth3:
filter parent 3: protocol ip pref 1 fw
filter parent 3: protocol ip pref 1 fw handle 0x28 classid 3:140
filter parent 3: protocol ip pref 1 fw handle 0x29 classid 3:141


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to