Re: server in DMZ

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 02, 2004 at 09:13:25AM -0400, Jason Opperisano wrote:
> i think there's some confusion here...there are three rules involved in
> this scenario:

Yes, I already have the 3 rules. The only thing I am worrying about 
is how do I let my internal LAN users access the DMZ machine using
its public IP if I use the 3 rules given by you below. The below rules
will effectively block all traffic except from 1.2.3.4 and my LAN users
are on 192.168.x.x series and using squid as their proxy.
(squid machine is the gateway/firewall machine itself)
-Payal

> 
> (1) NAT rule that maps port 80 on the outside to port 80 on your DMZ
> server:
> 
>   -A PREROUTING -d 5.6.7.8 -p tcp -m tcp --dport 80 \
>     -j DNAT --to-destination 10.10.10.3
> 
> (2) FILTER rule that allows external access to server in DMZ from client
> IP:
> 
>   -A FORWARD -p tcp -s 1.2.3.4 -d 10.10.10.3 --dport 80 -j ACCEPT
> 
> (3) FILTER rule that allows squid proxy running directly on your
> firewall to fetch content from server in DMZ:
> 
>   -A OUTPUT -p tcp -d 10.10.10.3 --dport 80 -j ACCEPT
> 
> remember:  packets passing through the firewall are filtered by FORWARD,
> packets coming from the firewall are filtered by OUTPUT.
> 
> -j
> 
> -- 
> Jason Opperisano <opie@xxxxxxxxxxx>
> 
> 


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux