[ previous ] [ next ] [ threads ]
 
 From:  YARICK <yarick at yarick dot com>
 To:  sai <sonicsai at gmail dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: Optimization for VOIP
 Date:  Sat, 22 Oct 2005 16:38:55 -0400
No replies, does that mean that you all like these rules ?
Thanks.

--Yarick.
http://www2.tjwv.com/listing/Yarick/MONOWALL.jpg



On 10/21/05, YARICK <yarick at yarick dot com> wrote:
>
> SAI, here is updated Traffic Shaping rules:
> http://www2.tjwv.com/listing/Yarick/MONOWALL.jpg
>
>
>
> On 10/21/05, YARICK <yarick at yarick dot com> wrote:
> >
> > Sai, I do not have a Vonage device, and connect to Vonage via SIP.
> >
> >
> > On 10/21/05, sai <sonicsai at gmail dot com > wrote:
> > >
> > > [1] "outgoing Interface WAN Proto any Source any Dest 216.115.25.198<http://216.115.25.198>
> > > " should be
> > > "outgoing Interface WAN Proto any Source 216.115.25.198
> > > <http://216.115.25.198> Dest any "
> > > assuming that the 216 ip address is your vonage phone. Same goes for
> > > the Broadvoice rule.
> > > [2] The first 4 rules are not needed because of the rules labeled
> > > 'Vonage' and 'Broadvoice'. In any case they will not match any packets
> > >
> > > - see next point.
> > >
> > > [3] "Interface Wan Proto any Source port 20001-65535 Dest port
> > > 20001-65535" will match a packet coming in on the WAN interface that
> > > has source port of 20001-65535 AND destination port of 20001-65535.
> > > This is unlikely to happen.
> > > Just specify the destination ports and leave source as 'any' that
> > > should work.
> > >
> > > sai
> > >
> >
> >
>