From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: How to drop/reject packets amongst LAN clients?
Date: Mon, 10 May 2004 17:43:54 +0100 [thread overview]
Message-ID: <200405101743.54501.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1084206191.409fac6f1176a@webmail.floog.net>
On Monday 10 May 2004 5:23 pm, michael@floog.net wrote:
> The LAN currently has 5 computers connected to it with static IP
> addresses:
>
> 192.168.1.2
> 192.168.1.3
> 192.168.1.4
> 192.168.1.5
> 192.168.1.6
>
> I will be adding 3 more machines with with static IP addresses:
>
> 192.168.1.7
> 192.168.1.8
> 192.168.1.9
>
> Issue:
>
> *.9 needs to remain accessible from *.7 and *.8; however, I need to
> restrict any connection or accessibility to *.9 from *.2 - *.6.
Netfilter (on the gateway router) is no use to you here, because packets
between machines on the same subnet do not go through the router - they just
talk to each other directly across your hub / switch.
Install netfilter on 192.168.1.9 and put rules in the INPUT chain:
iptables -A INPUT -A INPUT -s 192.168.1.7 -j ACCEPT
iptables -A INPUT -A INPUT -s 192.168.1.0/29 -j DROP
Regards,
Antony.
--
The idea that Bill Gates appeared like a knight in shining armour to lead all
customers out of a mire of technological chaos neatly ignores the fact that
it was he who, by peddling second-rate technology, led them into it in the
first place.
- Douglas Adams in The Guardian, 25th August 1995
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-05-10 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 16:23 How to drop/reject packets amongst LAN clients? michael
2004-05-10 16:43 ` Antony Stone [this message]
2004-05-10 17:31 ` michael
2004-05-10 17:43 ` Antony Stone
2004-05-10 17:14 ` Cedric Blancher
2004-05-10 17:34 ` Antony Stone
2004-05-10 17:46 ` Cedric Blancher
2004-05-10 17:16 ` Aleksandar Milivojevic
2004-05-10 18:26 ` michael
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=200405101743.54501.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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.