From: Eric Leblond <eric@regit.org>
To: "Игорь Попов" <igor@garant.koenig.ru>
Cc: Netfilter-List <netfilter@lists.netfilter.org>
Subject: Re: Broadcast
Date: Mon, 01 Mar 2004 14:37:57 +0100 [thread overview]
Message-ID: <1078148276.20266.21.camel@tech004.alphalink.fr> (raw)
In-Reply-To: <200403011009.55740.igor@garant.koenig.ru>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Le lun 01/03/2004 à 09:09, Игорь Попов a écrit :
> I have a question, if my iface receive a broadcast packet in what chain it
> will go in INPUT or FORWARD?
As a broadcast packet is a packet internal to a network, it don't have
to go through a router, so it will go on INPUT chain.
BR,
--
Eric Leblond
NuFW, Now User Filtering Works (http://www.nufw.org)
[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-01 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 8:09 Broadcast Игорь Попов
2004-03-01 13:35 ` Broadcast Alexis
2004-03-01 13:37 ` Eric Leblond [this message]
2004-03-01 13:37 ` Broadcast Antony Stone
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=1078148276.20266.21.camel@tech004.alphalink.fr \
--to=eric@regit.org \
--cc=igor@garant.koenig.ru \
--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