All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Chandran <vinod_chandran@multitech.co.in>
To: netfilter@lists.netfilter.org
Subject: Re: QoS with netfilter
Date: Mon, 12 Dec 2005 11:06:52 +0530	[thread overview]
Message-ID: <439D0C74.6050107@multitech.co.in> (raw)
In-Reply-To: <200512111419.34465.arny@ats.s.bawue.de>

Hi,

If  you want to know how DSMARK and DSCP is used for QOS, check out the 
following link
http://opalsoft.net/qos/DS-29.htm
However, this doesnt use netfilter.

If you want to use netfilter, I think the best way is to have 
iptablerules in FORWARD, to set mark values on the basis of specific 
conditions,

like --src 192.168.1.0/24 -j MARK --set-mark 1.

This mark value can be further used in tc filter commands..
If this will suffice you,  I can elaborate more on this process.

Regards,
Vinod C



Thilo Schulz wrote:

>On Sunday 11 December 2005 10:18, Erik wrote:
>  
>
>>I have a lot of answers to this but nobody have responded to what I
>>asked.  Please bear with me and help me find out what my problem might
>>*actually* be.
>>    
>>
>
>Sorry you are right.
>
>  
>
>>Have anyone actually used this feature in iptables?
>>    
>>
>
>Yes.
>
>  
>
>>No, I do not need this router to handle these packages with *any* QoS.
>>Other router handle QoS. In fact a lot of router are updated to handle QoS.
>>    
>>
>
>These bits should work nice in theory, but in my experience they offer little 
>to no improvement.
>
>  
>
>>a) confirmation that this feature actually is implemented and should
>>work with the 2.6.12 kernel (or that it is not!)
>>    
>>
>
>It should work, yes.
>
>  
>
>>b) things to verify like patches etc
>>    
>>
>
>No clue.
>
>  
>
>>c) actual commands to test this
>>    
>>
>
>tcpdump -i eth0 -v
> 
>prints out the tos field on all packets traversing the interface eth0.
>
>  
>



  reply	other threads:[~2005-12-12  5:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10 12:53 QoS with netfilter Erik
2005-12-10 12:57 ` Thilo Schulz
2005-12-10 13:28   ` Erik
2005-12-10 16:34     ` Cedric Blancher
2005-12-10 18:14       ` Erik
2005-12-10 18:40         ` Thilo Schulz
2005-12-10 19:45         ` Cedric Blancher
2005-12-11  0:56           ` Daniel Lopes
2005-12-11  8:07             ` Cedric Blancher
2005-12-11  9:18               ` Erik
2005-12-11 13:19                 ` Thilo Schulz
2005-12-12  5:36                   ` Vinod Chandran [this message]
2005-12-10 15:08 ` QoS with netfilter (nfcan: addressed to exclusive sender for this address) Jim Laurino
2005-12-11  9:40   ` Erik
2005-12-11 10:13     ` Cedric Blancher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=439D0C74.6050107@multitech.co.in \
    --to=vinod_chandran@multitech.co.in \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.