All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Craig <philipc@snapgear.com>
To: George Gao <ggao@nortelnetworks.com>
Cc: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: How to differentiate packets generated locally or received from t	he network using the NF_IP_PRE_ROUTING filter
Date: Tue, 06 Apr 2004 10:11:43 +1000	[thread overview]
Message-ID: <4071F5BF.50806@snapgear.com> (raw)
In-Reply-To: <2F1FC1DEA077D5119FAD00508BCFD6D20BBB0110@zsc3c030.us.nortel.com>

George Gao wrote:
> Is there any way to differentiate a local IP Multicast or IP brocast from an
> inbound mal-formed packet with the exact same content? Thanks much in
> advance!

Use '-m pkttype --pkt-type multicast' and '-m pkttype --pkt-type broadcast'.

-- 
Philip Craig - SnapGear, A CyberGuard Company - http://www.SnapGear.com



      parent reply	other threads:[~2004-04-06  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 22:02 How to differentiate packets generated locally or received from t he network using the NF_IP_PRE_ROUTING filter George Gao
2004-04-05 23:31 ` How to differentiate packets generated locally or received from the " Antony Stone
2004-04-06  0:11 ` Philip Craig [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=4071F5BF.50806@snapgear.com \
    --to=philipc@snapgear.com \
    --cc=ggao@nortelnetworks.com \
    --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.