From: "Pawel Staszewski" <pstaszewski@artcom.pl>
To: "Håkan Engblom" <cynic_0@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: source-mac filtering
Date: Sun, 11 Jan 2004 01:13:23 +0100 [thread overview]
Message-ID: <003801c3d7d7$ba8ed850$0d04460a@orion> (raw)
In-Reply-To: Sea1-F7gMiX6AZCFgXe000520e9@hotmail.com
Hello
Maybe try to block broadcast to the "blocked" client....
"-m pkttype --pkttype broadcast ........."
I use it and this work fine...
----- Original Message -----
From: "Håkan Engblom" <cynic_0@hotmail.com>
To: <netfilter@lists.netfilter.org>
Sent: Sunday, January 11, 2004 12:20 AM
Subject: source-mac filtering
> Hi,
>
> I've run in to a strange problem. I have a dhcp-server on a 2.4.22 kernel
> with a 1.2.8 iptables. The dhcp-server is configured only to offer
> IP-addresses to one single mac-address (it is a single host on a private
> network)
>
> However I'd like to block all other mac-addresses on this interface since
I
> plan to have a W-LAN here as well. (to prevent attackers from using
> potential exploits in the dhcp-server)
>
> The mac-filter works fine for http, telnet, ssh aso, I can see the
> drop-counter increasing and no traffic is let through (when I change the
> mac-address in the iptables-config to something else than what I have on
my
> "dhcp-client-host"). BUT the dhcp-server keeps sending offers and ack's
> evethough the incoming discover/request is blocked by iptables.
>
> What makes this even more strange is that the "DROP-counters" when using
> "iptables -L -v" increases, and at the same time the dhcp server responds
to
> the requests.
>
> I'm using Internet Software Consortium DHCP Server V3.0.1rc11
>
> The machine has only one physical interface whith two IP's one private and
> one for public. The IP-address offered by the dhcp-server is private (as
> seen below)
>
> Does anyone have a clue ?
>
> br Håkan Engblom
>
> Some "logs" :
>
> 00:30:88:00:63:10 is my DSL-connection (having to accepted packets during
> this test)
>
> X.X.X.X is my public IP.
>
> (This is not the complete iptables, but it is teh interesting part for
this
> matter)
>
> 00:08:29.540872 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover -
> Transaction ID 0xae749e48
> 00:08:29.541303 X.X.X.X -> 10.0.0.217 DHCP DHCP Offer - Transaction
ID
> 0xae749e48
> 00:08:29.542117 0.0.0.0 -> 255.255.255.255 DHCP DHCP Request -
> Transaction ID 0xae749e48
> 00:08:29.542299 X.X.X.X -> 10.0.0.217 DHCP DHCP ACK - Transaction
ID
> 0xae749e48
>
>
>
> # date
> Sun Jan 11 00:08:08 CET 2004
> # iptables -L -v
> Chain INPUT (policy DROP 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 0 0 mactable all -- eth0 any anywhere
anywhere
> 0 0 ACCEPT all -- lo any anywhere
anywhere
> 0 0 DROP !icmp -- any any anywhere
anywhere
> state INVALID
> 0 0 eth0_in all -- eth0 any !10.0.0.0/24
anywhere
> 0 0 eth0_1_in all -- eth0 any anywhere
anywhere
> 0 0 common all -- any any anywhere
anywhere
>
> Chain mactable (2 references)
> pkts bytes target prot opt in out source
> destination
> 0 0 ACCEPT all -- any any anywhere
anywhere
> MAC 01:01:01:01:01:01
> 0 0 RETURN all -- any any anywhere
anywhere
> MAC 00:30:88:00:63:10
> 0 0 RETURN all -- any any anywhere
anywhere
> MAC 00:90:D0:AF:A3:F1
> 0 0 LOG all -- any any anywhere
anywhere
> LOG level info prefix `Shorewall:mac:DROP:'
> 0 0 DROP all -- any any anywhere
anywhere
>
> # date
> Sun Jan 11 00:08:36 CET 2004
> # iptables -L -v
> Chain INPUT (policy DROP 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 4 948 mactable all -- eth0 any anywhere
anywhere
> 0 0 ACCEPT all -- lo any anywhere
anywhere
> 0 0 DROP !icmp -- any any anywhere
anywhere
> state INVALID
> 2 288 eth0_in all -- eth0 any !10.0.0.0/24
anywhere
> 0 0 eth0_1_in all -- eth0 any anywhere
anywhere
> 0 0 common all -- any any anywhere
anywhere
>
> Chain mactable (2 references)
> pkts bytes target prot opt in out source
> destination
> 0 0 ACCEPT all -- any any anywhere
anywhere
> MAC 01:01:01:01:01:01
> 2 288 RETURN all -- any any anywhere
anywhere
> MAC 00:30:88:00:63:10
> 0 0 RETURN all -- any any anywhere
anywhere
> MAC 00:90:D0:AF:A3:F1
> 2 660 LOG all -- any any anywhere
anywhere
> LOG level info prefix `Shorewall:mac:DROP:'
> 2 660 DROP all -- any any anywhere
anywhere
> #
>
> _________________________________________________________________
> Lättare att hitta drömresan med MSN Resor http://www.msn.se/resor/
>
>
>
>
next prev parent reply other threads:[~2004-01-11 0:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 23:20 source-mac filtering Håkan Engblom
2004-01-10 23:37 ` Antony Stone
2004-01-11 0:13 ` Pawel Staszewski [this message]
2004-01-11 0:25 ` Antony Stone
2004-01-11 0:34 ` Pawel Staszewski
2004-01-11 5:55 ` Unknown, Alistair Tonner
2004-01-11 16:37 ` Ramin Dousti
2004-01-11 19:05 ` Tarek W.
2004-01-12 6:10 ` Unknown, Alistair Tonner
[not found] ` <200401120110.08378.Alistair Tonner <>
2004-01-12 15:52 ` Ramin Dousti
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 0:43 Håkan Engblom
2004-01-11 0:59 Håkan Engblom
2004-01-11 17:36 Håkan Engblom
2004-01-11 17:39 Håkan Engblom
2004-01-11 17:50 ` Antony Stone
2004-01-12 17:56 ` Ramin Dousti
2004-01-12 16:06 ` Ramin Dousti
2004-01-11 18:16 Håkan Engblom
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='003801c3d7d7$ba8ed850$0d04460a@orion' \
--to=pstaszewski@artcom.pl \
--cc=cynic_0@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox