Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-08 Thread Dinesh Nair


On 01/05/06 18:24 Igor Neves said the following:

Take a look ate pfsense.sf.net, its GPL and its one merge of m0n0.
Much better, take a look. :)


i think you're mistaken. pfsense is not under the GPL, but rather under the 
BSD license. it is based on FreeBSD 6.0.


--
Regards,   /\_/\   All dogs go to heaven.
[EMAIL PROTECTED](0 0)http://www.alphaque.com/
+==oOO--(_)--OOo==+
| for a in past present future; do|
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo The opinions here in no way reflect the opinions of my $a $b.  |
| done; done  |
+=+
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-05 Thread Igor Neves

Paul Dugas wrote:

On Wed, 2006-01-04 at 11:59 -0500, Mark Phillips wrote:

Anyone got any VoIP traffic shaping rules for m0n0wall that they could 
let me look at please?



Running m0n0wall-1.21 now, I used the wizard to set the base
queues/pipes/rules then added two more rules:  


If  Dir Proto Src  Dst  TargetDescription
--- --- -  ---  - ---
WAN -  UDP   pbx:4569 *:4569   m_High Priority #1 Upload IPX VoIP
WAN -  UDP   *:4569   pbx:4569 m_High Priority Download  IPC VoIP

I have this setup at two sites that use an IAX ITSP and also connect
directly to each other.  Seems to work fine but I'm not really sure how
to actually prove that it's 100% correct.  I'd love to hear if you get
anything better.

I'm not using SIP externally but I'd assume the same rules would work
with 5060 for the port.

HTH,

Paul


Take a look ate pfsense.sf.net, its GPL and its one merge of m0n0.
Much better, take a look. :)
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-04 Thread Mark Phillips

Hi all,

Anyone got any VoIP traffic shaping rules for m0n0wall that they could 
let me look at please?


Thanks


--

Mark, G7LTT/KC2ENI
Randolph, NJ
http://www.g7ltt.com
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-04 Thread Paul Dugas
On Wed, 2006-01-04 at 11:59 -0500, Mark Phillips wrote:
 Anyone got any VoIP traffic shaping rules for m0n0wall that they could 
 let me look at please?

Running m0n0wall-1.21 now, I used the wizard to set the base
queues/pipes/rules then added two more rules:  

If  Dir Proto Src  Dst  TargetDescription
--- --- -  ---  - ---
WAN -  UDP   pbx:4569 *:4569   m_High Priority #1 Upload IPX VoIP
WAN -  UDP   *:4569   pbx:4569 m_High Priority Download  IPC VoIP

I have this setup at two sites that use an IAX ITSP and also connect
directly to each other.  Seems to work fine but I'm not really sure how
to actually prove that it's 100% correct.  I'd love to hear if you get
anything better.

I'm not using SIP externally but I'd assume the same rules would work
with 5060 for the port.

HTH,

Paul
-- 
Paul Dugas, Computer EngineerDugas Enterprises, LLC
[EMAIL PROTECTED]phone: 404-932-1355 522 Black Canyon Park
http://dugas.ccfax: 866-751-6494 Canton, GA 30114 USA
--
On site at GDOT's W.Annex, 404-463-2860 x199
--
This e-mail and any attachments are confidential.  If you receive
this message in error or are not the intended recipient, you should
not retain, distribute, disclose or use any of this information and
you should destroy the e-mail and any attachments or copies.

___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-04 Thread Matt Riddell
Paul Dugas wrote:
 On Wed, 2006-01-04 at 11:59 -0500, Mark Phillips wrote:
 
Anyone got any VoIP traffic shaping rules for m0n0wall that they could 
let me look at please?
 
 
 Running m0n0wall-1.21 now, I used the wizard to set the base
 queues/pipes/rules then added two more rules:  

I don't use m0n0wall, but wouldn't it be better just to shape based on a Type
Of Service and then set the TOS flags in iax.conf and sip.conf accordingly?

-- 
Cheers,

Matt Riddell
___

http://www.sineapps.com/news.php (Daily Asterisk News - html)
http://freevoip.gedameurope.com (Free Asterisk Voip Community)
http://www.sineapps.com/rssfeed.php (Daily Asterisk News - rss)

___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-04 Thread Michael Graves
On Wed, 04 Jan 2006 19:04:18 +0100, Matt Riddell wrote:

Paul Dugas wrote:
 On Wed, 2006-01-04 at 11:59 -0500, Mark Phillips wrote:
 
Anyone got any VoIP traffic shaping rules for m0n0wall that they could 
let me look at please?
 
 
 Running m0n0wall-1.21 now, I used the wizard to set the base
 queues/pipes/rules then added two more rules:  

I don't use m0n0wall, but wouldn't it be better just to shape based on a Type
Of Service and then set the TOS flags in iax.conf and sip.conf accordingly?

-- 
Cheers,

Matt Riddell

In a more general sense yes, TOS based QoS is better as it relates to
outside your LAN. However, when using m0n0wall (great software!) it's
easiest to assign priority based upon source machine (your * server) IP
or port number.

The examples given previously in this thread are derived from the
built-in traffic shaping wizard. This establishes a series of weighted
ques for data. All you really need to do is be certain that the IAX
traffic is assigned to the highest priority que. Or all traffic to/from
your server can be assigned to the hi priority que.

It all sets up the same thing. Since QoS across the internet is pretty
hard to achieve there's some question as to the actual usefullness of
TOS bits. In future Telco/DSL providers may actually filter traffic
looking for TOS tags to deter your from voip applications.

Michael
--
Michael Graves   [EMAIL PROTECTED]
Sr. Product Specialist  www.pixelpower.com
Pixel Power Inc. [EMAIL PROTECTED]

o713-861-4005
o800-905-6412
c713-201-1262
fwd 54245



___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] M0n0Wall traffic shaping rules

2006-01-04 Thread Mike Fedyk

Michael Graves wrote:


On Wed, 04 Jan 2006 19:04:18 +0100, Matt Riddell wrote:
 


I don't use m0n0wall, but wouldn't it be better just to shape based on a Type
Of Service and then set the TOS flags in iax.conf and sip.conf accordingly?

--
Cheers,

Matt Riddell
   



In a more general sense yes, TOS based QoS is better as it relates to
outside your LAN. However, when using m0n0wall (great software!) it's
easiest to assign priority based upon source machine (your * server) IP
or port number.

The examples given previously in this thread are derived from the
built-in traffic shaping wizard. This establishes a series of weighted
ques for data. All you really need to do is be certain that the IAX
traffic is assigned to the highest priority que. Or all traffic to/from
your server can be assigned to the hi priority que.

It all sets up the same thing. Since QoS across the internet is pretty
hard to achieve there's some question as to the actual usefullness of
TOS bits. In future Telco/DSL providers may actually filter traffic
looking for TOS tags to deter your from voip applications.
 

Actually no, TOS is mostly useless because it has so few combinations, 
and you have to trust the sender to have a clue.  Unless it originates 
from within your realm of control (most likely one of your LANs), then 
TOS is the last thing you should trust.  It is only useful when you want 
to know the intent of the sender (which is seldom useful).


That is why most examples use source and/or destination port 
specifications in addition to the IP addresses of the machines within 
your network(s) when assigning packet priority.  This prevents people 
from taking advantage of your QoS rules.


When you an ISP it is critical to think of these scenarios.  It doesn't 
hurt to do it the same way in smaller setups where there is much less 
chance of someone trying to take advantage.


Mike
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users