From: Bill Chappell <chappewr@critical.com>
To: bahamin takhtaei <b_takhtaei@yahoo.com>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: specified protocl number problem
Date: Tue, 18 Nov 2008 02:47:48 -0500 [thread overview]
Message-ID: <49227324.4080508@critical.com> (raw)
In-Reply-To: <59826.13109.qm@web55306.mail.re4.yahoo.com>
The packets you are seeing (TCP, UDP, and ICMP)
are what you would get if you were to specify
"-p all".
"all" is not as inclusive as one might expect.
To get packets with other protocols, you must
specific them explicitly.
Bill
bahamin takhtaei wrote:
> Hi everybody,
>
> Why I can't QUEUE some ip-protocol packets such as IGMP, AH, ESP
> and so on?
> I add these rules to Iptables:
>
> iptables -A INPUT -j QUEUE
> iptables -A OUTPUT -j QUEUE
>
> and I see that TCP, UDP and ICMP packets are queued only and
> other protocol packets are not! But I see them by tcpdump. :(
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
William Chappell, Software Engineer, Critical Technologies Inc.
* Creativity * Diversity * Expertise * Flexibility * Integrity *
Suite 400 Technology Center, 4th Floor 1001 Broad St, Utica NY 13501
315-793-0248 x148 FAX -9710 <bill.chappell@critical.com> www.critical.com
next prev parent reply other threads:[~2008-11-18 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 7:31 specified protocl number problem bahamin takhtaei
2008-11-18 7:47 ` Bill Chappell [this message]
2008-11-18 9:35 ` bahamin takhtaei
2008-11-19 10:25 ` Pascal Hambourg
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=49227324.4080508@critical.com \
--to=chappewr@critical.com \
--cc=b_takhtaei@yahoo.com \
--cc=netfilter@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.