From: Carsten Maass <cm@blinkenlichten.de>
To: netfilter@lists.netfilter.org
Subject: INET_IFACE: Secure to allow traffic from 192.168.x.0/24?
Date: Thu, 04 Mar 2004 13:29:25 +0100 [thread overview]
Message-ID: <40472125.4000608@blinkenlichten.de> (raw)
Dear List,
recently i connected together two internal networks over an IPSec-tunnel:
(Localnet A)---(Gateway A)==IPSec==(Gateway B)---(Localnet B)
Now i am unsure which iptables-rules i should apply to the external
interfaces of the gateways to match the traffic between the Localnets
without opening up a security hole. Is it sufficient to simply apply
some general rules like:
$IPTABLES -A FORWARD -i $INET_IFACE -s 192.168.a.0/24 -j ACCEPT
$IPTABLES -A FORWARD -i $INET_IFACE -s 192.168.b.0/24 -j ACCEPT
or would this approach be vulnerable to some kind of IP-spoofing attack?
What would be your solutions in this situation?
Thanks for your help,
Carsten.
next reply other threads:[~2004-03-04 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 12:29 Carsten Maass [this message]
2004-03-05 1:29 ` INET_IFACE: Secure to allow traffic from 192.168.x.0/24? Antony Stone
2004-03-05 11:28 ` Carsten Maass
2004-03-05 11:40 ` Antony Stone
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=40472125.4000608@blinkenlichten.de \
--to=cm@blinkenlichten.de \
--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