PIX 501 using 6.3

Discussion in 'Cisco' started by John Court, Jul 23, 2003.

  1. John Court

    John Court Guest

    Hi,

    I got a 501 yesterday and have just managed to get it working using
    the CLI. I have no experience of this, so just patched together this
    config by rtFm and copying bits of other people's configs. I am
    beginning to understand the various commands, but there are a few
    things that I still haven't worked out how to do:

    1. Get the machines to use static (internal) ip addresses. At the
    moment, if I specify the IP rather than use DHCP, outside access is
    blocked.

    2. Access the GUI for configuration. Admittedly things are going OK at
    the moment, but I think it could help me understand the configuration
    settings.

    The other problem is that I am unaware of how effectively the
    configuration below will be protecting the network!

    Any help, criticism or links would be much appreciated.

    John.

    Info about my particular set-up
    -------------------------------

    the network looks like this:

    DSL Router / Switch
    <?>.78
    |
    <?>.76
    PIX 501
    192.168.0.1
    |
    SWITCHES ETC...
    |
    192.168.0.50-100

    -of which-
    192.168.0.50 should appear externally as.. <?>.65
    192.168.0.51 should appear externally as.. <?>.66
    192.168.0.52 should appear externally as.. <?>.67
    192.168.0.53 should appear externally as.. <?>.68
    192.168.0.54 should appear externally as.. <?>.69

    Maybe I need to use static addresses outside the DHCP pool or
    something?

    BTW I have 16 static ip addresses.

    Here is my config file:

    PIX Version 6.3(1)
    interface ethernet0 auto
    interface ethernet1 100full
    nameif ethernet0 outside security0
    nameif ethernet1 inside security100
    enable password * encrypted
    passwd * encrypted
    hostname pixfirewall
    domain-name klross.com
    fixup protocol ftp 21
    fixup protocol h323 h225 1720
    fixup protocol h323 ras 1718-1719
    fixup protocol http 80
    fixup protocol ils 389
    fixup protocol rsh 514
    fixup protocol rtsp 554
    fixup protocol sip 5060
    fixup protocol sip udp 5060
    fixup protocol skinny 2000
    fixup protocol smtp 25
    fixup protocol sqlnet 1521
    names
    name <?>.64 public-lan
    access-list acl_out permit icmp any any
    access-list outside_access_in permit tcp any host <?>.65 eq www
    access-list outside_access_in permit tcp any host <?>.65 eq domain
    access-list outside_access_in permit udp any host <?>.65 eq domain
    access-list outside_access_in permit icmp any any echo-reply
    access-list outside_access_in permit icmp any any unreachable
    access-list outside_access_in permit icmp any any time-exceeded
    pager lines 24
    mtu outside 1500
    mtu inside 1500
    ip address outside <?>.76 255.255.255.240
    ip address inside 192.168.0.1 255.255.255.0
    ip audit info action alarm
    ip audit attack action alarm
    pdm location 192.168.0.5 255.255.255.255 inside
    pdm location 192.168.0.50 255.255.255.255 inside
    pdm logging informational 100
    pdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 1 192.168.0.0 255.255.255.0 0 0
    nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    static (inside,outside) <?>.65 192.168.0.50 netmask 255.255.255.255 0
    0
    static (inside,outside) <?>.66 192.168.0.51 netmask 255.255.255.255 0
    0
    static (inside,outside) <?>.67 192.168.0.52 netmask 255.255.255.255 0
    0
    static (inside,outside) <?>.68 192.168.0.53 netmask 255.255.255.255 0
    0
    static (inside,outside) <?>.69 192.168.0.54 netmask 255.255.255.255 0
    0
    access-group outside_access_in in interface outside
    route outside 0.0.0.0 0.0.0.0 <?>.78 1
    timeout xlate 0:05:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225
    1:00:00
    timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
    timeout uauth 0:05:00 absolute
    aaa-server TACACS+ protocol tacacs+
    aaa-server RADIUS protocol radius
    aaa-server LOCAL protocol local
    http server enable
    http public-lan 255.255.255.240 inside
    no snmp-server location
    no snmp-server contact
    snmp-server community public
    no snmp-server enable traps
    floodguard enable
    telnet timeout 5
    ssh timeout 5
    console timeout 0
    dhcpd address 192.168.0.50-192.168.0.100 inside
    dhcpd dns 212.23.8.1
    dhcpd lease 3600
    dhcpd ping_timeout 750
    dhcpd domain klross.com
    dhcpd auto_config outside
    dhcpd enable inside
    terminal width 80
    Cryptochecksum:24869104f9a7165c01ecf449a0d7ff03
     
    John Court, Jul 23, 2003
    #1
    1. Advertisements

  2. Is that because you specify only IP address, but not gateway or
    DNS servers?
    These two lines control the access to the GUI:

    http server enable
    http public-lan 255.255.255.240 inside

    If you want to access the PDM from inside you should have
    the last line like:

    http 192.168.0.0 255.255.255.0 inside
    Well, usually a Pix has a access-group defined to each interface.
    You seem to have one only at the outside interface. That means
    that you can't control outbound connections.
    Then about the access-list statements. It's not a big deal, but I
    like to have them as thigh as possible. No "any any"s. Always
    any to "something" or "something" to any.
    This line doesn't seem to do anything:

    access-list acl_out permit icmp any any

    Why there are two nat statements? Only the first is needed.

    global (outside) 1 interface
    nat (inside) 1 192.168.0.0 255.255.255.0 0 0
    nat (inside) 1 0.0.0.0 0.0.0.0 0 0
     
    Jyri Korhonen, Jul 23, 2003
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.