With that ACL, nodisco, you imply a policy NAT. I prefer the static method and simple PAT.
remove the " nat (inside) 0 access-list inside_nat0_outbound" because it would prevent your sql server from ever going to the internet (which may be by design, but prevents you from getting MS updates directly for example )
Instead, add this:
static (inside,dmz) 10.1.1.13 10.1.1.13 netmask 255.255.255.255
And of course use the rules that nodisco supplied for the dmz acl (not the no-nat acl).
That takes care of the DMZ to SQL server. For the outbound Open DNS, because of the acls of the dmz and guest interfaces, you'll need this:
access-list dmz extended permit udp 192.168.10.0 255.255.255.0 any 255.255.255.0 eq domain
access-list dmz extended permit tcp 192.168.10.0 255.255.255.0 any 255.255.255.0 eq 53
access-list guest extended permit udp 172.16.1.0 255.255.255.0 64.42.233.0 255.255.255.0 eq domain
access-list guest extended permit tcp 172.16.1.0 255.255.255.0 64.42.233.0 255.255.255.0 eq 53
(I used ANY for the destination, but you can use specific IPs for your external DNS)
If you want to ping from DMZ, you need this:
access-list dmz extended permit icmp 192.168.10.0 255.255.255.0 any 255.255.255.0
Main Topics
Browse All Topics





by: nodiscoPosted on 2009-09-02 at 21:10:51ID: 25247818
hi there
To translate your internal network into the DMZ and allow access back:
1433, 1434, 4022 ,135, 2383, 2382
object-group service sql-inside-ports tcp
description - Ports that Web servers need to access
port-object eq 1433
port-object eq 1434
port-object eq 4022
port-object eq 135
port-object eq 2383
port-object eq 2382
access-list inside_nat0_outbound extended permit ip 10.1.1.0 255.255.255.0 192.168.10.0 255.255.255.0
access-list dmz extended permit tcp host 192.168.10.2 host 10.1.1.13 object-group sql-inside-ports
access-list dmz extended permit tcp host 192.168.10.3 host 10.1.1.13 object-group sql-inside-ports
access-list dmz extended permit tcp host 192.168.10.4 host 10.1.1.13 object-group sql-inside-ports
cheers