Re: [LARTC] Re: List fault?

2011-11-24 Thread Kilian Krause
On Thu, 2011-05-05 at 00:12 +0200, Michelle Konzack wrote:
 Hello Grant Taylor,
 
 Am 2011-05-04 14:24:17, hacktest Du folgendes herunter:
  On 05/04/11 13:37, Radu Oprisan wrote:
  I will try to contact LARTC in order to ask them for permission to
  take over this one.
  
  (I'll make this pitch again.)
  
  Does any one have any objections to (re)configuring the mailing list
  so that it sets the Reply-To header so that replies are directed
  back to the mailing list (as a discussion list)?
 
 For WHAT?  Real MTAs have L byside R and G
 
  All in favor?
  Any one against?
 
 Yes.

Sorry guys, but I have to support Michelle here and refrain that anyone
not familiar with the Reply-To problem in the context of mailinglists
do a quick google on Reply To munging. It's really just some ugly
workaround for old/broken MUA to set Reply-To for a mailinglist pointing
back to itself. 

Please don't!

-- 
Best regards,
Kilian

___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc


Re: [LARTC] QoS for VoIP

2003-11-28 Thread Kilian Krause
Hi Craig,

 I would like to prioritise all VoIP traffic on a linux router. I am new
 to QoS, tc and TOS, to please be gentle.
 
 My logic works like this:
 
 1) identify the VoIP packets
 2) mark packets using iptables (with TOS?)
 3) use tc to prioritise the marked packets.
 
 Is this logic correct? If not, where is it flawed?

it can work, VoIP for me is H323, for SIP i haven't checked yet what
their ports are..

 I understand that VoIP used the udp protocol and has packet sized less
 than 250 bytes. Is simply reducing the MTU on the interfaces good enough
 to give better thoughput, without the lag of larger packets trying to
 pass though?

Well, reducing MTU is most probably not a good idea, as you force more
packets benig sent even when you can keep the overhead to just 1 packet
with large payload. so i wouldn't do that..
VoIP (speaking of H323) is UDP traffic on random ports but can be
limited by using either GnomeMeeting or nmproxy
(http://www.cryogenic.net/nmproxy.html), thouch i haven't tried the
latter so far..

As of GnomeMeeting you can simply use a match for UDP ports 5000-5003
(on a direct connection)...
For OhPhone and OpenMCU etc. the ports may vary.. If you don't use H245
tunneling there's also some TCP ports involved (for GM 3-30010).

Using a GateKeeper will also have another port-range.. but checking
either source, mailinglist or support info of these products will shed
some light where you'll be most lucky matching their packets..

 Are there any good HOWTOS?

None that i know of, sorry..

Good luck! ;)

-- 
Best regards,
 Kilian


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: R: [LARTC] time window in CBQ

2003-09-05 Thread Kilian Krause
Hi Steve,

  is 64kbit/sec enough for VoIP ?  I would have thought not.. but I do not
  have VoIP...
 
 Steve, what voip codec do you use?
 If you can select, use G723 (6.3 kbit/s)

yep, 64kBit is fine with GnomeMeeting. You should use Speex8k though, as
there's a huge protocol overhead that needs to be added to that number
of x.y kBit/s.. (many small packets)

Empirically Speex8k works fine and MS-GSM might also do. The G.723 does
require a hardware extension and is not available with pure software.
Feel free to search the GnomeMeeting archives for details on
configurations. ;)

-- 
Best regards,
 Kilian


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: [LARTC] Cant restrict netmeeting traffic

2003-06-30 Thread Kilian Krause
Hi Joel,
 
 From 3 days i m trying to restrict Netmeeting traffic.
  
 I have restricted the bandwidth to 30kbit per ip. but the machine with
 netmeeting. means when we use netmeeting the traffic goes very high to
 450. all others things are not taking more than 35 traffic but when
 using netmeeting it shows 450 upload traffic. what can i do to
 restrict this type of traffic.
 netmeeting using h323 protocol some like that protocol 
 can any one suggest me how to restrict it.

i guess your best bet is to use a GateKeeper to make NM use only a small
band of RTP (UDP) ports.. you can define the RTP ports in the
gatekeeper.ini and then shape them to your desired speed.
The Linux equivalent of NM, GnomeMeeting has already the small RTP-range
builting by default, so you could also use that, if you have the option
to use Linux as workstation.

it'll be a bit of work to get your gatekeeper (for win there's a DUAL
gatekeeper iirc) up and running, but that's your best bet.

-- 
Best regards,
 Kilian


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil