All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Error in "15.10 Example of full nat solution with QoS"?
Date: Sun, 09 Oct 2005 01:02:28 +0000	[thread overview]
Message-ID: <43486C24.5050507@dsl.pipex.com> (raw)
In-Reply-To: <91740-22005104613054248@earnware.com>

Sean Dwyer wrote:
> On Wednesday 05 October 2005 18:30, Sean Dwyer wrote:
> 
>>Near the end of section 15.10, the following commands are shown for prioritizing SYN packets:
>>
>>  iptables -t mangle -I PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j MARK --set-mark 0x1
>>  iptables -t mangle -I PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j RETURN
>>
>>Shouldn't the "-I" option really be "-A"? Like so:
>>
>>  iptables -t mangle -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j MARK --set-mark 0x1
>>  iptables -t mangle -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j RETURN
>>
>>Won't using "-I" cause these entries to be inserted at the top of the chain, putting the RETURN
>>before the MARK is set? Maybe I'm missing something.
> 
> 
> Does anybody who maintains lartc.org read this mailing list?

I doubt if Bert reads every or maybe any post - I agree about the -I 
being wrong. The LARTC hasn't been changed for a while but will be 
someday I guess. There is going to be a wiki soon - there is already a 
new one for Linux-net http://linux-net.osdl.org/ .

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

      parent reply	other threads:[~2005-10-09  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06  1:30 [LARTC] Error in "15.10 Example of full nat solution with QoS"? Sean Dwyer
2005-10-07 17:42 ` Sean Dwyer
2005-10-09  1:02 ` Andy Furniss [this message]

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=43486C24.5050507@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@vger.kernel.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.