All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shaun T. Erickson" <ste@smxy.org>
To: netfilter@lists.netfilter.org
Subject: Need to replace a SonicWall firewall with an iptables firewall.
Date: Mon, 30 Aug 2004 12:01:54 -0400	[thread overview]
Message-ID: <41334F72.4010402@smxy.org> (raw)

I have a SonicWall Pro 330 that's giving me no end of grief, and so I 
want to replace it. It's my primary firewall. Becase we have two LANs 
and the SonicWall only has one LAN port, I have an iptables 
router/firewall that's connected to the LAN port of the SonicWall. The 
two LANs hang off of the iptables machine. The SonicWall provides our 
DMZ, as well.

I want to collapse the two systems into one, but I'm not quite sure how 
to do it.

I want one iptables-based firewall, with four NICs, that connect to our 
external router, our DMZ switch, and each of our two internal LAN switches.

I believe I know how to set it up so that traffic from either internal 
LAN gets NAT'd to the firewall's external IP address, for traffic headed 
to the Internet, and de-NAT'd on the way back. I also believe I know how 
to allow traffic to flow back and forth between the two LANs, where 
NAT'ing isn't needed.

However, I'm not sure how to handle the external network and the DMZ. We 
have a /28 subnet from our ISP. Our router uses one address on the 
subnet. From the router, you proceed to a switch, where three devices 
are plugged in: a wireless access point, a VPN device, and the external 
interface of the SonicWall firewall. All three devices have addresses on 
the same /28 subnet as the router. Additionally, the SonicWall's DMZ 
interface does not have and address assigned to it - it is somehow 
logically bridged to the external interface. The systems in the DMZ are 
also on the same /28 subnet. You tell the SonicWall which IP addresses 
are in use in the DMZ, so that it knows which interface to send traffic 
for that subnet out of. Internal traffice, heading out either the 
external or DMZ interfaces of the SonicWall, appear to come from the 
external address of the SonicWall. I have no idea how to replicate this 
setup under iptables.

Lastly, some systems in the DMZ need to access database servers on one 
of the internal LANs. The LANs use private, non-routable address space 
(192.168.32.0 & 192.168.40.0). So, I need certain systems in the DMZ, to 
be able to initiate connections through the firewall, to systems on my 
40-net. No NAT'ing is needed for these connections, but I'm not sure how 
to set them up, either. On the SonicWall, we just put a rule in that 
allows it, and two static routes, so it knows to forward traffic for 
those nets to the linux box. Somehow I think it isn't as simple under 
iptables, but hopefully I'm wrong.

Sorry for the length of this, but I wanted to try and describe it all 
accurately. I've never set up an iptables firewall that is so 
(seemingly) complicated before.

Thanks, in advance, for any guidance you can give me.

	-ste


             reply	other threads:[~2004-08-30 16:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 16:01 Shaun T. Erickson [this message]
2004-08-30 18:41 ` Need to replace a SonicWall firewall with an iptables firewall Shaun T. Erickson
  -- strict thread matches above, loose matches on Subject: below --
2004-08-30 19:30 Jason Opperisano
2004-08-30 20:23 ` Shaun T. Erickson
2004-08-30 20:41 Jason Opperisano
2004-08-30 21:11 ` Shaun T. Erickson
2004-08-30 20:45 Jason Opperisano
2004-08-30 22:23 Daniel Chemko
2004-08-31  0:02 ` Nick Drage
2004-08-30 22:25 Jason Opperisano
2004-08-31 13:47 ` Shaun T. Erickson
2004-08-31 14:11 Jason Opperisano

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=41334F72.4010402@smxy.org \
    --to=ste@smxy.org \
    --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.