[ previous ] [ next ] [ threads ]
 
 From:  Aaron <lists at mycommunitynet dot net>
 To:  "John ." <jvoigt at gmail dot com>
 Cc:  m0n0wall <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] VOIP issues/can't specify a particular pipe.
 Date:  Wed, 13 Apr 2005 14:19:18 -0700
Wow, this is a help!!

For some reason the rules I create seem to have no effect on which 
queue it goes through. See the following pictures for my rules, pipes 
and queues.

http://www.scs.wsu.edu/~arobinso/tmp/SafariScreenSnapz007.jpg
http://www.scs.wsu.edu/~arobinso/tmp/SafariScreenSnapz008.jpg
http://www.scs.wsu.edu/~arobinso/tmp/SafariScreenSnapz009.jpg

According to this, even though I have explicitly set set a rule for all 
outgoing traffic from 192.168.100.90 to go through Queue#1, it goes 
through #4 which has the lowest outgoing priority. That probably makes 
a bit of a difference!

So is there something that I am doing wrong with the rules? I have a 
screenshot with the detail view.
http://www.scs.wsu.edu/~arobinso/tmp/SafariScreenSnapz010.jpg

I want all outgoing traffic from 192.168.100.90 to go through queue#1. 
Somehow it seems to get into #4.


$ ipfw queue show
00001: 450.000 Kbit/s    0 ms   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
00002:   2.280 Mbit/s    0 ms   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
q00001: weight 50 pipe 1   50 sl. 1 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes 
Pkt/Byte Drp
   0 tcp  192.168.100.184/1209    62.20.240.206/19811  212     9382  0   
  0   0
q00002: weight 30 pipe 1   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
q00003: weight 15 pipe 1   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
q00004: weight 4 pipe 1   50 sl. 1 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes 
Pkt/Byte Drp
   0 udp   192.168.100.90/16544   147.135.8.128/14032 1023   222097  0   
  0   0
q00005: weight 1 pipe 1   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
q00006: weight 30 pipe 2   50 sl. 1 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes 
Pkt/Byte Drp
   0 udp    147.135.8.128/14032  192.168.100.90/16544 1258   500147  0   
  0   0
q00007: weight 10 pipe 2   50 sl. 0 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
q00008: weight 60 pipe 2   50 sl. 1 queues (1 buckets) droptail
     mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes 
Pkt/Byte Drp
   0 tcp    64.124.186.71/80    192.168.100.199/3684    37     1711  0   
  0   0

On Apr 13, 2005, at 11:26 AM, John . wrote:

> ipfw queue show
> will show you traffic through each queue
>
> On 4/13/05, Aaron <lists at mycommunitynet dot net> wrote:
>>
>> On Apr 13, 2005, at 11:07 AM, John . wrote:
>>
>>>> Rules - 
>>>> http://www.scs.wsu.edu/~arobinso/tmp/SafariScreenSnapz006.jpg
>>>>         - Catches all traffic udp or traffic coming from my asterisk
>>>> box.
>>>>
>>> Actually, you might want to get into the
>>> test console and do "ipfw show" to see which rules are accumulating
>>> traffic.
>>
>> Thanks for this...it is helpful. I can at least see what is going on.
>> Are there more commands that might be useful for troubleshooting?
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>