one interface, basic setup
Hi,
I'm just getting started with iptables and after reading the HOWTO's (basic and packet filtering) I still feel unsure. I want to build a FW for outgoing packets only. My setup looks like this:
internet <---->Netgear FVS318 <----> LAN
Where LAN is a Linux FC3 and several Windows machines. The router closes all outbound traffic except from the FC3 box. Currently, Windows machines DHCP from the router, so that is the gateway, and proxy out through squid et. al. on FC3. I'll move the DHCP service to FC3 and make that the gateway. I want the FC3 gateway to allow all outbound traffic from squid; destination ports might be more than HTTP. I also want to allow outbound SMTP and POP to a specific destination only. FC3 is also providing services http, telnet, ftp, ssh, smtp, imap/imaps and pop/pop-ssl. Eventually, I'll want to do a transparent proxy as well.
So it looks like I want both the INPUT and OUTPUT chains to ACCEPT all and I should build rules in the FORWARD chain. With only one interface, is that correct?
Thanks,
Bill
Signature · 3 lines
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/52 - Release Date: 7/19/2005
Quoted 3 lines · Bill McCormick
(basic and packet filtering) I still feel unsure. I want to build a FW for outgoing packets only. My setup looks like this:
internet <---->Netgear FVS318 <----> LAN
A dual-homed Linux machine could do a better job in place of that router. A lot of folks believe in "hardware routers", but in fact those are only software routers which provide less control and may have unknown vulnerabilities. (Exception: Linksys embedded Linux devices. Using a Linux distro for that platform makes them very powerful.)
Quoted 1 line
Where LAN is a Linux FC3 and several Windows machines. The router closes all outbound traffic except from the FC3 box. Currently, Windows machines DHCP from the router, so that is the gateway, and proxy out
Right now I'm like this at home:
Internet <---> Linksys WRT54G [switch + WAP] <---> LAN
The DHCP server is one of the LAN hosts, but the Linksys is still the gateway. There's no inherent connection between who is DHCP and who is the default gateway.
Quoted 1 line
through squid et. al. on FC3. I'll move the DHCP service to FC3 and make that the gateway.
That's awkward in that each packet destined to go out will pass twice over the LAN: once from originator to FC3, then again from FC3 to the router. Will it cause problems for you? I don't know.
Quoted 1 line
I want the FC3 gateway to allow all outbound traffic from squid; destination ports might be more than HTTP. I also want to allow outbound SMTP and POP to a specific destination only. FC3 is also
It's very important to restrict outbound SMTP of Windows machines, especially if it happens that they get infected. Most spam these days originates (in SMTP terms) from unsecured home Windows machines.
Quoted 1 line
providing services http, telnet, ftp, ssh, smtp, imap/imaps and pop/pop-ssl. Eventually, I'll want to do a transparent proxy as well.
Note that with shell access, your users could get out directly. I believe that even a Windows machine can tunnel ports over ssh.
Quoted 1 line
So it looks like I want both the INPUT and OUTPUT chains to ACCEPT all and I should build rules in the FORWARD chain. With only one interface, is that correct?
I think you're right, yes. With only one interface you have the problem of not being able to filter on the incoming interface. You have to use IP-based rules, and a determined and capable "attacker" could get around your limits.
I think I'd set up a different logical segment for the clients, such that they could not reach the router at all. Just one more hurdle for any would-be "extruder" trying to get out.
Signature · 2 lines
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: headerQuoted 6 lines · /dev/rob0 wrote:
Quoted 3 lines · Bill McCormick
(basic and packet filtering) I still feel unsure. I want to build a FW for outgoing packets only. My setup looks like this:
internet <---->Netgear FVS318 <----> LAN
[snip]
Quoted 1 line
I think I'd set up a different logical segment for the clients, such that they could not reach the router at all. Just one more hurdle for any would-be "extruder" trying to get out.
This a home setup. First and formost, I want to restrict, limit and control what clients can send out and to where. Basically, I just want ALL out-bound traffic to pass through FC3 iptables then get routed to the FVS318.
So, the best (easiest) way to accomplish this is to make the FC3 the gateway router by adding another interface? Do the NAT rules get crazy for that? Are the routing tables complicated?
Thanks
Signature · 3 lines
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/53 - Release Date: 7/20/2005
Quoted 7 lines · Bill McCormick
Quoted 5 lines · /dev/rob0 wrote:
Quoted 3 lines · Bill McCormick
(basic and packet filtering) I still feel unsure. I want to build a FW for outgoing packets only. My setup looks like this:
internet <---->Netgear FVS318 <----> LAN
The case he wants
internet <------ Netgear FVS 318 <---- FC3 ----> LAN
internet -------> something else or nothing ----> (FC3) ? ---> LAN
Quoted 3 lines
...Basically, I just want ALL out-bound traffic to pass through FC3 iptables then get routed to the FVS318.
So, the best (easiest) way to accomplish this is to make the FC3 the gateway router by adding another interface?
I'm right that routing to outside should be via dmz in this case?
Figured like this:
internet ------> FC3 <------> LAN
|
| DMZ
|internet <---- Netgear FVS 318
Quoted 1 line
Do the NAT rules get crazy for that?
In this case NAT must translate the incoming traffic for the lan and the outgoing for routing in the dmz. To transfer the traffic out in the internet is be done by the netgearrouter.
Are the routing tables complicated?
Regards,
Ruprecht
------------------------------------------------------------------------------------------
Ruprecht Helms IT-Service & Softwareentwicklung
Tel./Fax +49[0]7621 16 99 16
Web: htp://www.rheyn.de