iptables firewall do-over



I am revisiting my firewall and before I begin, I need to make sure my
understandings are right.

Here's the geography:

WAN (Internet) public routable IPs

Interface (ppp0)

fw machine

interface (eth1)

LAN private non-routable IPs

Assuming NAT is setup correctly, Here's what I'm thinking.

Since the LAN uses only non-routable IP's, and there is no one on the
LAN that I'm worried about, I only need to focus on NEW packets from
ppp0 destined for the fw machine (INPUT chain where -i ppp0 and --state NEW). Any NEW packets from the WAN are blocked from the LAN by virtue of non-routable IP addresses.

Default policies should be; INPUT DROP, OUTPUT ACCEPT, and FORWARD DROP. Then by looking at specific ports, protocols, and interface sources, selectively jump to ACCEPT. Everything else should fall through to the default policy (DROP). It almost sounds like I could get away with one rule -i ppp0 -m state --state ESTABLISHED, RELATED -j ACCEPT.

If these assumptions are correct, is there anything onppp0 --state NEW that should get accepted?


Bill






.



Relevant Pages

  • Re: Help on Cisco ASA 5510 VPN IPsec
    ... Inbound TCP connection denied from 10.100.7.245/22 to 10.100.5.10/1953 flags SYN ACK on interface lan ... mtu wan 1500 ...
    (comp.dcom.sys.cisco)
  • Re: SBS Routing & Remote access changes
    ... interfacing the WAN and the other the LAN of course). ... cannot route traffic to the port ranges on the LAN side from a WAN IP ... We have opened up the port ranges on the router to the servers WAN NIC ... interface, but we need to be able to also forward these port ranges ...
    (microsoft.public.windows.server.sbs)
  • SBS Routing & Remote access changes
    ... interfacing the WAN and the other the LAN of course). ... cannot route traffic to the port ranges on the LAN side from a WAN IP ... We have opened up the port ranges on the router to the servers WAN NIC ... interface, but we need to be able to also forward these port ranges ...
    (microsoft.public.windows.server.sbs)
  • Re: WORM? ... server generating NBT-NS (port 137) traffic on WAN interface
    ... issue on the SBS2003 server itself (problem turned out to be IP Packet ... the LAN does have Trend Micro ... mentioned a WAN NIC, so I have to assume you are running 2 nics and SBS is ... packets that are leaving the SBS2003 WAN interface ... ...
    (microsoft.public.windows.server.sbs)
  • Re: 3750 load balancing over dual links with seperated VLANs
    ... I'm trying to setup a system which uses 2 transparent networks as WAN. ... VLAN 1 and 5 are not to be routed over the WAN ... interface FastEthernet1/0/2 ...
    (comp.dcom.sys.cisco)