From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: how to stop broadcasts using iptables
Date: Tue, 27 Apr 2004 13:50:11 +0100 [thread overview]
Message-ID: <200404271350.11890.lists@edeca.net> (raw)
In-Reply-To: <20040427123529.HVYI23570.viefep19-int.chello.at@localhost>
On Tuesday 27 April 2004 13:35, sschlesi@chello.at wrote:
> I'm trying to stop broadcasts getting forwarded, but I'm not sure how
> to do this. i read that *.255 - which are afaik broadcast addresses -
My first question is why are broadcasts getting forwarded anyway? Neither
ethernet or IP broadcasts should leave your subnet. How and where
exactly are broadcasts being forwarded?
IP addresses ending in .255 are not always broadcast addresses. Any
subnet larger than class C (/24) can span more than one "block" of 256 IP
addresses.
> doesnt guarantie that its a broadcast. then i read that its possible by
> matching the mac address, because broadcast will have ff:ff:ff:ff:ff:ff
> . but I'm not sure if that's all nonsense.
There is the difference here between an IP broadcast and an ethernet
broadcast. IP broadcasts are sent to the ethernet broadcast address [1],
so you may be able to do a MAC match.
According to the manual page I have here, the module "mac" only offers a
--mac-source option but there are more options in PoM I believe, you may
want to check the mailing list archives.
David
1- A ping to the broadcast address on a LAN:
13:44:59.765871 0:10:XX:XX:XX:XX Broadcast ip 98: 192.168.0.100 >
192.168.0.255: icmp: echo request (DF)
next prev parent reply other threads:[~2004-04-27 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 12:35 how to stop broadcasts using iptables sschlesi
2004-04-27 12:50 ` David Cannings [this message]
2004-04-28 0:11 ` Alexander Samad
2004-04-27 14:46 ` Aleksandar Milivojevic
2004-04-27 15:40 ` Angel j Alvarez
-- strict thread matches above, loose matches on Subject: below --
2004-04-27 13:19 sschlesi
2004-04-27 14:56 ` Aleksandar Milivojevic
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=200404271350.11890.lists@edeca.net \
--to=lists@edeca.net \
--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