PIX 501 routing issues

Discussion in 'Cisco' started by Justin, Jun 28, 2007.

  1. Justin

    Justin Guest

    Good day to everyone.

    I have been toying with a PIX 501 running v. 6.3(5) and have run into
    a routing issue. The configuration for this unit is very basic at
    this time. All it is intended to do is stand as the gateway to the
    internet and allow traffic out while blocking most outside traffic.
    Eventually it will be one end of a dedicated VPN tunnel but I need it
    to be able to pass information to the internet for right now.

    Internal devices (configured with the PIX as the gateway) can ping the
    inside interface of the PIX but not the outside. The PIX can ping
    devices on the inside and the outside, including successful ping
    replies from internet servers. Traceroute commands have the same
    results.

    If anyone can spot what I may be missing and offer a suggestion of a
    fix, I would be greatly appreciative.

    :
    PIX Version 6.3(5)
    interface ethernet0 auto
    interface ethernet1 100full
    nameif ethernet0 outside security0
    nameif ethernet1 inside security100
    enable password 8Ry2YjIyt7RRXU24 encrypted
    passwd 2KFQnbNIdI.2KYOU encrypted
    hostname drtest
    domain-name nonetospeakof.org
    clock timezone CST -6
    fixup protocol dns maximum-length 512
    fixup protocol ftp 21
    fixup protocol h323 h225 1720
    fixup protocol h323 ras 1718-1719
    fixup protocol http 80
    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
    fixup protocol tftp 69
    names
    pager lines 24
    icmp permit 172.16.0.0 255.255.0.0 inside
    icmp permit 10.10.10.0 255.255.255.0 inside
    mtu outside 1500
    mtu inside 1500
    ip address outside 63.225.175.115 255.255.255.224
    ip address inside 10.10.10.1 255.255.255.0
    ip audit info action alarm
    ip audit attack action alarm
    pdm location 172.16.0.0 255.255.0.0 inside
    pdm location 0.0.0.0 255.255.255.224 outside
    pdm logging informational 100
    pdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    route outside 0.0.0.0 0.0.0.0 63.225.175.113 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 sip-disconnect 0:02:00 sip-invite 0:03:00
    timeout uauth 0:05:00 absolute
    aaa-server TACACS+ protocol tacacs+
    aaa-server TACACS+ max-failed-attempts 3
    aaa-server TACACS+ deadtime 10
    aaa-server RADIUS protocol radius
    aaa-server RADIUS max-failed-attempts 3
    aaa-server RADIUS deadtime 10
    aaa-server LOCAL protocol local
    http server enable
    http 10.10.10.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server community public
    no snmp-server enable traps
    floodguard enable
    telnet 10.10.10.0 255.255.255.0 inside
    telnet timeout 5
    ssh timeout 5
    console timeout 10
    terminal width 80
    banner motd Unauthorized access is strictly prohibited.
    Cryptochecksum:f333d02c5a5d110ec76c7c460a896519
    Justin, Jun 28, 2007
    #1
    1. Advertising

  2. Justin

    Mike W. Guest

    You need to allow those pings that you send out back in. I am certain
    they are going out, they're just not being allowed back in by the firewall.

    Try adding the following commands:

    access-list outside_access_in permit icmp any any echo-reply
    access-group outside_access_in in interface outside

    HTH



    Justin wrote:
    > Good day to everyone.
    >
    > I have been toying with a PIX 501 running v. 6.3(5) and have run into
    > a routing issue. The configuration for this unit is very basic at
    > this time. All it is intended to do is stand as the gateway to the
    > internet and allow traffic out while blocking most outside traffic.
    > Eventually it will be one end of a dedicated VPN tunnel but I need it
    > to be able to pass information to the internet for right now.
    >
    > Internal devices (configured with the PIX as the gateway) can ping the
    > inside interface of the PIX but not the outside. The PIX can ping
    > devices on the inside and the outside, including successful ping
    > replies from internet servers. Traceroute commands have the same
    > results.
    >
    > If anyone can spot what I may be missing and offer a suggestion of a
    > fix, I would be greatly appreciative.
    >
    > :
    > PIX Version 6.3(5)
    > interface ethernet0 auto
    > interface ethernet1 100full
    > nameif ethernet0 outside security0
    > nameif ethernet1 inside security100
    > enable password 8Ry2YjIyt7RRXU24 encrypted
    > passwd 2KFQnbNIdI.2KYOU encrypted
    > hostname drtest
    > domain-name nonetospeakof.org
    > clock timezone CST -6
    > fixup protocol dns maximum-length 512
    > fixup protocol ftp 21
    > fixup protocol h323 h225 1720
    > fixup protocol h323 ras 1718-1719
    > fixup protocol http 80
    > 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
    > fixup protocol tftp 69
    > names
    > pager lines 24
    > icmp permit 172.16.0.0 255.255.0.0 inside
    > icmp permit 10.10.10.0 255.255.255.0 inside
    > mtu outside 1500
    > mtu inside 1500
    > ip address outside 63.225.175.115 255.255.255.224
    > ip address inside 10.10.10.1 255.255.255.0
    > ip audit info action alarm
    > ip audit attack action alarm
    > pdm location 172.16.0.0 255.255.0.0 inside
    > pdm location 0.0.0.0 255.255.255.224 outside
    > pdm logging informational 100
    > pdm history enable
    > arp timeout 14400
    > global (outside) 1 interface
    > nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    > route outside 0.0.0.0 0.0.0.0 63.225.175.113 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 sip-disconnect 0:02:00 sip-invite 0:03:00
    > timeout uauth 0:05:00 absolute
    > aaa-server TACACS+ protocol tacacs+
    > aaa-server TACACS+ max-failed-attempts 3
    > aaa-server TACACS+ deadtime 10
    > aaa-server RADIUS protocol radius
    > aaa-server RADIUS max-failed-attempts 3
    > aaa-server RADIUS deadtime 10
    > aaa-server LOCAL protocol local
    > http server enable
    > http 10.10.10.0 255.255.255.0 inside
    > no snmp-server location
    > no snmp-server contact
    > snmp-server community public
    > no snmp-server enable traps
    > floodguard enable
    > telnet 10.10.10.0 255.255.255.0 inside
    > telnet timeout 5
    > ssh timeout 5
    > console timeout 10
    > terminal width 80
    > banner motd Unauthorized access is strictly prohibited.
    > Cryptochecksum:f333d02c5a5d110ec76c7c460a896519
    >
    Mike W., Jun 28, 2007
    #2
    1. Advertising

  3. Justin

    Justin Guest

    Adding the icmp traffic back through the outside interface didn't make
    any difference.

    On Jun 28, 2:40 pm, "Mike W." <> wrote:
    > You need to allow those pings that you send out back in. I am certain
    > they are going out, they're just not being allowed back in by the firewall.
    >
    > Try adding the following commands:
    >
    > access-list outside_access_in permit icmp any any echo-reply
    > access-group outside_access_in in interface outside
    >
    > HTH
    >
    >
    >
    > Justin wrote:
    > > Good day to everyone.

    >
    > > I have been toying with a PIX 501 running v. 6.3(5) and have run into
    > > a routing issue. The configuration for this unit is very basic at
    > > this time. All it is intended to do is stand as the gateway to the
    > > internet and allow traffic out while blocking most outside traffic.
    > > Eventually it will be one end of a dedicated VPN tunnel but I need it
    > > to be able to pass information to the internet for right now.

    >
    > > Internal devices (configured with the PIX as the gateway) can ping the
    > > inside interface of the PIX but not the outside. The PIX can ping
    > > devices on the inside and the outside, including successful ping
    > > replies from internet servers. Traceroute commands have the same
    > > results.

    >
    > > If anyone can spot what I may be missing and offer a suggestion of a
    > > fix, I would be greatly appreciative.

    >
    > > :
    > > PIX Version 6.3(5)
    > > interface ethernet0 auto
    > > interface ethernet1 100full
    > > nameif ethernet0 outside security0
    > > nameif ethernet1 inside security100
    > > enable password 8Ry2YjIyt7RRXU24 encrypted
    > > passwd 2KFQnbNIdI.2KYOU encrypted
    > > hostname drtest
    > > domain-name nonetospeakof.org
    > > clock timezone CST -6
    > > fixup protocol dns maximum-length 512
    > > fixup protocol ftp 21
    > > fixup protocol h323 h225 1720
    > > fixup protocol h323 ras 1718-1719
    > > fixup protocol http 80
    > > 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
    > > fixup protocol tftp 69
    > > names
    > > pager lines 24
    > > icmp permit 172.16.0.0 255.255.0.0 inside
    > > icmp permit 10.10.10.0 255.255.255.0 inside
    > > mtu outside 1500
    > > mtu inside 1500
    > > ip address outside 63.225.175.115 255.255.255.224
    > > ip address inside 10.10.10.1 255.255.255.0
    > > ip audit info action alarm
    > > ip audit attack action alarm
    > > pdm location 172.16.0.0 255.255.0.0 inside
    > > pdm location 0.0.0.0 255.255.255.224 outside
    > > pdm logging informational 100
    > > pdm history enable
    > > arp timeout 14400
    > > global (outside) 1 interface
    > > nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    > > route outside 0.0.0.0 0.0.0.0 63.225.175.113 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 sip-disconnect 0:02:00 sip-invite 0:03:00
    > > timeout uauth 0:05:00 absolute
    > > aaa-server TACACS+ protocol tacacs+
    > > aaa-server TACACS+ max-failed-attempts 3
    > > aaa-server TACACS+ deadtime 10
    > > aaa-server RADIUS protocol radius
    > > aaa-server RADIUS max-failed-attempts 3
    > > aaa-server RADIUS deadtime 10
    > > aaa-server LOCAL protocol local
    > > http server enable
    > > http 10.10.10.0 255.255.255.0 inside
    > > no snmp-server location
    > > no snmp-server contact
    > > snmp-server community public
    > > no snmp-server enable traps
    > > floodguard enable
    > > telnet 10.10.10.0 255.255.255.0 inside
    > > telnet timeout 5
    > > ssh timeout 5
    > > console timeout 10
    > > terminal width 80
    > > banner motd Unauthorized access is strictly prohibited.
    > > Cryptochecksum:f333d02c5a5d110ec76c7c460a896519- Hide quoted text -

    >
    > - Show quoted text -
    Justin, Jun 28, 2007
    #3
  4. Justin

    Mike W. Guest

    Justin wrote:
    > Adding the icmp traffic back through the outside interface didn't make
    > any difference.
    >



    Try adding these too, then:

    icmp permit any outside
    icmp permit any echo-reply outside
    icmp permit any inside
    Mike W., Jun 28, 2007
    #4
  5. Justin

    Justin Guest

    No improvement.


    On Jun 28, 2:54 pm, "Mike W." <> wrote:
    > Justin wrote:
    > > Adding the icmp traffic back through the outside interface didn't make
    > > any difference.

    >
    > Try adding these too, then:
    >
    > icmp permit any outside
    > icmp permit any echo-reply outside
    > icmp permit any inside
    Justin, Jun 28, 2007
    #5
  6. Justin

    Justin Guest

    I have also just set this unit up so that there is a computer on each
    side of the interface and nothing else. The inside computer has the
    PIX as its default gateway; the outside computer has a non-existent
    gateway. I have also turned ICMP to be fully open both directions.

    The PIX can ping each computer. Each computer can ping the nearest
    PIX interface. Neither computer can ping the other.

    On Jun 28, 2:54 pm, "Mike W." <> wrote:
    > Justin wrote:
    > > Adding the icmp traffic back through the outside interface didn't make
    > > any difference.

    >
    > Try adding these too, then:
    >
    > icmp permit any outside
    > icmp permit any echo-reply outside
    > icmp permit any inside
    Justin, Jun 28, 2007
    #6
  7. Justin

    Mike W. Guest

    Justin wrote:
    > I have also just set this unit up so that there is a computer on each
    > side of the interface and nothing else. The inside computer has the
    > PIX as its default gateway; the outside computer has a non-existent
    > gateway. I have also turned ICMP to be fully open both directions.
    >
    > The PIX can ping each computer. Each computer can ping the nearest
    > PIX interface. Neither computer can ping the other.
    >



    Did you get rid of these statements:

    icmp permit 172.16.0.0 255.255.0.0 inside
    icmp permit 10.10.10.0 255.255.255.0 inside

    You should...you don't need them for testing.


    Add this line as well so that this one section looks like it does below:

    access-list outside_access_in permit icmp any any



    names
    access-list outside_access_in permit icmp any any echo-reply
    access-list outside_access_in permit icmp any any
    pager lines 24
    icmp permit any outside
    icmp permit any echo-reply outside
    icmp permit any inside
    mtu outside 1500
    mtu inside 1500
    ip address outside 63.225.175.115 255.255.255.224
    ip address inside 10.10.10.1 255.255.255.0
    Mike W., Jun 28, 2007
    #7
  8. Justin

    Chris Guest


    > Internal devices (configured with the PIX as the gateway) can ping the
    > inside interface of the PIX but not the outside.


    With a Pix you can only ping the closet IP address. You shouldn't be able
    to ping the outside address from the inside. This is quite normal.

    Chris.
    Chris, Jun 28, 2007
    #8
  9. Justin

    Justin Guest

    On Jun 28, 5:46 pm, Chris <> wrote:
    > > Internal devices (configured with the PIX as the gateway) can ping the
    > > inside interface of the PIX but not the outside.

    >
    > With a Pix you can only ping the closet IP address. You shouldn't be able
    > to ping the outside address from the inside. This is quite normal.
    >
    > Chris.


    Unfortunaltely, using ping and traceroute were just a tools to test
    routing in an attempt to see why internet traffic could not make it
    outside the PIX. I have tried resetting the box back to factory
    defaults and using the 192.168.1.x ip address scheme and connecting
    the outside interface directly to an internet router, setting up the
    default NAT and allowing all traffic on both sides and it still will
    not let a computer from the inside look outwards.

    Tis probably time for a call to Cisco.
    Justin, Jun 29, 2007
    #9
  10. Justin

    Scott Perry Guest

    You cannot PING the far interface of a PIX. It just won't ever happen.
    Find another way to test routing through the PIX.

    --

    ===========
    Scott Perry
    ===========
    Indianapolis, Indiana
    ________________________________________
    "Justin" <> wrote in message
    news:...
    > Good day to everyone.
    >
    > I have been toying with a PIX 501 running v. 6.3(5) and have run into
    > a routing issue. The configuration for this unit is very basic at
    > this time. All it is intended to do is stand as the gateway to the
    > internet and allow traffic out while blocking most outside traffic.
    > Eventually it will be one end of a dedicated VPN tunnel but I need it
    > to be able to pass information to the internet for right now.
    >
    > Internal devices (configured with the PIX as the gateway) can ping the
    > inside interface of the PIX but not the outside. The PIX can ping
    > devices on the inside and the outside, including successful ping
    > replies from internet servers. Traceroute commands have the same
    > results.
    >
    > If anyone can spot what I may be missing and offer a suggestion of a
    > fix, I would be greatly appreciative.
    >
    > :
    > PIX Version 6.3(5)
    > interface ethernet0 auto
    > interface ethernet1 100full
    > nameif ethernet0 outside security0
    > nameif ethernet1 inside security100
    > enable password 8Ry2YjIyt7RRXU24 encrypted
    > passwd 2KFQnbNIdI.2KYOU encrypted
    > hostname drtest
    > domain-name nonetospeakof.org
    > clock timezone CST -6
    > fixup protocol dns maximum-length 512
    > fixup protocol ftp 21
    > fixup protocol h323 h225 1720
    > fixup protocol h323 ras 1718-1719
    > fixup protocol http 80
    > 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
    > fixup protocol tftp 69
    > names
    > pager lines 24
    > icmp permit 172.16.0.0 255.255.0.0 inside
    > icmp permit 10.10.10.0 255.255.255.0 inside
    > mtu outside 1500
    > mtu inside 1500
    > ip address outside 63.225.175.115 255.255.255.224
    > ip address inside 10.10.10.1 255.255.255.0
    > ip audit info action alarm
    > ip audit attack action alarm
    > pdm location 172.16.0.0 255.255.0.0 inside
    > pdm location 0.0.0.0 255.255.255.224 outside
    > pdm logging informational 100
    > pdm history enable
    > arp timeout 14400
    > global (outside) 1 interface
    > nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    > route outside 0.0.0.0 0.0.0.0 63.225.175.113 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 sip-disconnect 0:02:00 sip-invite 0:03:00
    > timeout uauth 0:05:00 absolute
    > aaa-server TACACS+ protocol tacacs+
    > aaa-server TACACS+ max-failed-attempts 3
    > aaa-server TACACS+ deadtime 10
    > aaa-server RADIUS protocol radius
    > aaa-server RADIUS max-failed-attempts 3
    > aaa-server RADIUS deadtime 10
    > aaa-server LOCAL protocol local
    > http server enable
    > http 10.10.10.0 255.255.255.0 inside
    > no snmp-server location
    > no snmp-server contact
    > snmp-server community public
    > no snmp-server enable traps
    > floodguard enable
    > telnet 10.10.10.0 255.255.255.0 inside
    > telnet timeout 5
    > ssh timeout 5
    > console timeout 10
    > terminal width 80
    > banner motd Unauthorized access is strictly prohibited.
    > Cryptochecksum:f333d02c5a5d110ec76c7c460a896519
    >
    Scott Perry, Jun 29, 2007
    #10
  11. Justin

    Chris Guest

    On Fri, 29 Jun 2007 06:54:17 -0700, Justin wrote:

    > On Jun 28, 5:46 pm, Chris <> wrote:
    >>> Internal devices (configured with the PIX as the gateway) can ping the
    >>> inside interface of the PIX but not the outside.

    >>
    >> With a Pix you can only ping the closet IP address. You shouldn't be able
    >> to ping the outside address from the inside. This is quite normal.
    >>
    >> Chris.

    >
    > Unfortunaltely, using ping and traceroute were just a tools to test
    > routing in an attempt to see why internet traffic could not make it
    > outside the PIX. I have tried resetting the box back to factory
    > defaults and using the 192.168.1.x ip address scheme and connecting
    > the outside interface directly to an internet router, setting up the
    > default NAT and allowing all traffic on both sides and it still will
    > not let a computer from the inside look outwards.
    >
    > Tis probably time for a call to Cisco.


    Your config looked okay. I presume that you checked the routing on the
    client PC's? What did a "sh xlate" show on the pix? Could the clients
    resolve URL's to IP's?

    Chris.
    Chris, Jun 29, 2007
    #11
    1. Advertising

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Robert McIntosh

    PIX 501 and Routing

    Robert McIntosh, Sep 2, 2004, in forum: Cisco
    Replies:
    2
    Views:
    1,991
    Robert McIntosh
    Sep 2, 2004
  2. Replies:
    6
    Views:
    1,854
  3. Andre
    Replies:
    7
    Views:
    715
    Andre
    Feb 20, 2005
  4. Jogel

    PIX 501 Routing ?

    Jogel, May 17, 2006, in forum: Cisco
    Replies:
    0
    Views:
    547
    Jogel
    May 17, 2006
  5. ra170
    Replies:
    1
    Views:
    1,003
    ra170
    Nov 22, 2010
Loading...

Share This Page