From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: iptables on DLink DSL-502T Modem/Router
Date: Tue, 8 Nov 2005 15:16:20 -0600 [thread overview]
Message-ID: <200511081516.21132.rob0@gmx.co.uk> (raw)
In-Reply-To: <cc8f3f150511081239x4bd4d8favd7e2807f0748711c@mail.gmail.com>
Please do not top-post. Thank you.
On Tuesday 2005-November-08 14:39, Paul Goodyear wrote:
> Thanks for the reply, that would explain a few things. I did try the
> rule in both INPUT and FORWARD chains, but neither worked, I took a
> guess that it would be INPUT to use so I posted with that chain.
There is no need to guess when we have "man iptables" at our
fingertips. :)
> Order, when I do a iptables -L -n I can see my rule, but it is always
> at the bottom of the pile, so this might be the whole issue. How do I
> know what <ruleid> the other rules are so I can add above them?
"iptables -h" gives a brief syntax overview. The "--line-numbers"
option, available in recent versions of iptables, can help. With older
versions, I just list the rules and count them manually!
> I have read the -A param is "to add a rule at the end of the chain"
> how do I add at the begining of the chain?
In Jim's reply and also in "iptables -h" and "man iptables".
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-11-08 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 1:47 iptables on DLink DSL-502T Modem/Router Paul Goodyear
2005-11-08 2:31 ` /dev/rob0
2005-11-08 20:39 ` Paul Goodyear
2005-11-08 20:58 ` iptables on DLink DSL-502T Modem/Router (nfcan: addressed to exclusive sender for this address) Jim Laurino
2005-11-08 21:16 ` /dev/rob0 [this message]
2005-11-08 21:57 ` iptables on DLink DSL-502T Modem/Router Paul Goodyear
2005-11-08 22:28 ` /dev/rob0
2005-11-09 0:57 ` Paul Goodyear
2005-11-09 1:04 ` Anthony Sadler
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=200511081516.21132.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox