From: "Miguel González Castaños" <mgc@tid.es>
To: fluca1978@virgilio.it, linux-admin@vger.kernel.org
Subject: Re: problem with iptables - wrong rules?
Date: Wed, 14 Jul 2004 09:36:24 +0200 [thread overview]
Message-ID: <40F4E278.7040108@tid.es> (raw)
In-Reply-To: <200407131850.55496.fluca1978@virgilio.it>
Hi,
I am not sure what is your network architecture but i assume this:
You have a LAN connected (lets call it LAN1) to the Internet through
the linux firewall (192.168.1.7). This firewall acts also as a router
being connected to the 192.168.1.8 router which is connected to
different LANs.
With the DROP rule you are blocking packets destined to 192.168.1.8 and
come from anywhere (in this case Internet and LAN1).
I assume when you say have NATTED the connection, you have NATTED
connections from LAN1 to the Internet and maybe connections from the
other LANs, am I wrong ? (maybe you should give us a picture or more
details of what you have in your NAT rules). If so, then LAN1 and the
other LANs are routed and not natted among them.
Then, you should block destination to network 192.168.2.0, 192.168.4.0,
etc...
HTH
BR,
Miguel
>Hi,
>this is the situation:
>192.168.1.7 linux firewall with eth0 on internet and eth1 on intranet
>192.168.1.8 router for internal networks (192.168.4.0,192.168.2.0,ecc.)
>The firewall is the main gateway of the whole network, so packets are sent to
>it and redirected to the internet or the other router (192.168.1.8).
>I'd like to block connections to everything that is going to the router
>192.168.1.8 excepts for certain machines, thus I've defined the following
>rules:
>
>$IPTABLES -A OUTPUT -o $INTIF -d 192.168.1.8 -s 192.168.1.30 -j ACCEPT
>$IPTABLES -A OUTPUT -o $INTIF -d 192.168.1.8 -s 192.168.1.37 -j ACCEPT
>$IPTABLES -A OUTPUT -o $INTIF -d 192.168.1.8 -s 192.168.1.64 -j ACCEPT
>$IPTABLES -A OUTPUT -o $INTIF -d 192.168.1.8 -s 192.168.1.3 -j ACCEPT
>$IPTABLES -A OUTPUT -o $INTIF -d 192.168.1.8 -s 0/0 -j DROP
>
>
>but it is not working, and I can connect from other machine trhu 192.168.1.8.
>In the OUTPUT chain packets should be already be natted, thus my doubt is
>that the destination address is the final one (e.g., 192.168.4.100) and not
>the router one. Is there a way to lock the traffic to the router using
>iptables?
>
>Thanks,
>Luca
>
>
next prev parent reply other threads:[~2004-07-14 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 16:50 problem with iptables - wrong rules? Luca Ferrari
2004-07-14 7:36 ` Miguel González Castaños [this message]
2004-07-14 8:13 ` Luca Ferrari
2004-07-14 9:33 ` Miguel González Castaños
2004-07-14 9:34 ` Miguel González Castaños
2004-07-14 9:54 ` urgrue
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=40F4E278.7040108@tid.es \
--to=mgc@tid.es \
--cc=fluca1978@virgilio.it \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).