Suggest not using conduits. 6.0 and above should use access-lists instead. Conduit support will die out in newer revisions of code.
Suggest upgrading to latest code - 6.3(3) with PDM 3.01. You'll like the PDM GUI
Suggest VPN'ing in to access the servers. Much more secure. Just make sure your home local LAN is not 192.168.1.x - same as the LAN there. Use the Cisco IPSEC VPN client 4.x
Since you have an assigned IP address, you'll first want to change this:
>ip address outside dhcp setroute
to this:
ip address outside xx.xx.xx.175 255.255.255.224 < assuming this is correct mask
You'll also need a default gateway:
route outside 0.0.0.0 0.0.0.0 xx.xx.xx.143 < whatever is upstream router
Setup static addresses for servers:
static (inside,outside) xx.xx.xx.144 192.168.1.10 netmask 255.255.255.255
static (inside,outside) xx.xx.xx.145 192.168.1.11 netmask 255.255.255.255
static (inside,outside) xx.xx.xx.146 192.168.1.12 netmask
255.255.255.255
<etc>
now create access-lists for all your services
access-list inbound permit tcp any host xx.xx.xx.145 eq http
access-list inbound permit tcp any host xx.xx.xx.148 eq http
access-list inbound permit tcp any host xx.xx.xx.153 eq http
access-list inbound permit tcp any host xx.xx.xx.145 eq https
access-list inbound permit tcp any host xx.xx.xx.148 eq https
access-list inbound permit tcp any host xx.xx.xx.153 eq https
access-list inbound permit tcp any host xx.xx.xx.145 eq ftp
access-list inbound permit tcp any host xx.xx.xx.148 eq ftp
access-list inbound permit tcp any host xx.xx.xx.153 eq ftp
<etc>
>smtp, pop3, and ports 143, 366, 389, 465, 995, 1000, 3000 and 3002:
access-list inbound permit tcp any host xx.xx.xx.144 eq smtp
access-list inbound permit tcp any host xx.xx.xx.144 eq pop3
access-list inbound permit tcp any host xx.xx.xx.144 eq 143
access-list inbound permit tcp any host xx.xx.xx.144 eq 366
access-list inbound permit tcp any host xx.xx.xx.144 eq 389
access-list inbound permit tcp any host xx.xx.xx.144 eq 465
access-list inbound permit tcp any host xx.xx.xx.144 eq 995
access-list inbound permit tcp any host xx.xx.xx.144 eq 1000
access-list inbound permit tcp any host xx.xx.xx.144 eq 3000
access-list inbound permit tcp any host xx.xx.xx.144 eq 3002
<etc>
You could create protocol groups that includes all the above ports, and assign the servers into groups. Then assign the protocol group to the server group in a simpler access-list, but then we're getting away from the basics..
>The other thing I'm looking for is some idea of what statements are not really necessary but that might pop up in the default config, as well as clarity on which statements MUST exist.
Everything you see in the default config should stay except for the outside address, and the snmp community string.
Change this:
>snmp-server community public
to
snmp-server community <anything except "public">
Use good password rules for the community string, i.e.
snmp-server community MyGoodPa$$worD
Here are directions for setting up for the VPN client:
http://www.cisco.com/warp/
Main Topics
Browse All Topics





by: dmgadminPosted on 2003-10-14 at 01:05:27ID: 9545277
see if this helps you out. I used this for the first PIX i ever configured.
public/707 /28.html#c onduit
http://www.cisco.com/warp/