From: michael@floog.net
To: netfilter@lists.netfilter.org
Subject: How to drop/reject packets amongst LAN clients?
Date: Mon, 10 May 2004 09:23:11 -0700 [thread overview]
Message-ID: <1084206191.409fac6f1176a@webmail.floog.net> (raw)
Hi Group:
Setup:
Linux box acting as gateway/router/firewall for a LAN connected to the
internet by way of DSL connection.
eth0 - goes to the internet
eth1 - is gateway for the LAN
Linux box is using iptables version 1.2.9
Environment:
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.
I know how to restrict all access to *.9 by doing the following rule:
$IPTABLES -t filter -A FORWARD -p all --destination 192.168.1.9 -j DROP
or
$IPTABLES -t filter -A FORWARD -p all --destination 192.168.1.9 -j
REJECT
But I don't know how to craft a rule that allows only some machines to
send/receive data packets to/from *.9 while blocking other machines'
access to *.9 on the LAN.
I don't think prerouting or postrouting is the answer for this situation
but I could be wrong. Thank you for your time and assistance. All
guidance and responses are greatly appreciated.
Mike
next reply other threads:[~2004-05-10 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 16:23 michael [this message]
2004-05-10 16:43 ` How to drop/reject packets amongst LAN clients? Antony Stone
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=1084206191.409fac6f1176a@webmail.floog.net \
--to=michael@floog.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 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.