<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Pix as router? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521113#M527202</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of allowing all/permitting all ssh connections from outside and inside do mention the particular subnet blocks which requires the access or which can access the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Mar 2006 11:20:11 GMT</pubDate>
    <dc:creator>spremkumar</dc:creator>
    <dc:date>2006-03-07T11:20:11Z</dc:date>
    <item>
      <title>Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521109#M527181</link>
      <description>&lt;P&gt;I've got an old 1605R that just crapped out on me. The only thing that I have available with two eth interfaces is a pix 506.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know I can set it up to route between two networks and then allow ip any any between the two. What are the cons to using a pix as a router? Should I push to get a new router in?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:44:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521109#M527181</guid>
      <dc:creator>jcw009</dc:creator>
      <dc:date>2020-02-21T08:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521110#M527185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From my experience, a PIX cannot make routing decisions as it has no routing protocol. It needs to have explicit routes defined for each interface/network, and its default gateway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would recommend replacing your router, I don't think a PIX can do routing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2006 15:38:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521110#M527185</guid>
      <dc:creator>Glenn Hanratty</dc:creator>
      <dc:date>2006-02-23T15:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521111#M527188</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As already pointed out by Glen PIX doesnt do all kinda of activities which your router delievers to you also the features differs irrespective of the platform.&lt;/P&gt;&lt;P&gt;PIX Firewalls are introduced keeping Security as the main core focus when there was lack of device/equipment to take care of that part.&lt;/P&gt;&lt;P&gt;Though the lates PIX software versions supports most of the features which routers support still itz not a general/common/best practice to overload the PIX to handle both.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This link gives you the features which your new pix firewall software versions brings in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://cisco.com/en/US/products/hw/vpndevc/ps2030/products_data_sheet0900aecd8040c5b5.html" target="_blank"&gt;http://cisco.com/en/US/products/hw/vpndevc/ps2030/products_data_sheet0900aecd8040c5b5.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But its not supported for PIX 506 platform which you hold off here.As a general recommendation try to get your device upgraded based on the connectivity and the main focus you give over ther in network..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2006 15:55:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521111#M527188</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-02-23T15:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521112#M527194</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've put the 506e (pixA) in place. It sort of works. I can rdc to a laptop on the "dmz" network, and I get the correct, external ip address when I hit &lt;A class="jive-link-custom" href="http://www.nwtools.com" target="_blank"&gt;www.nwtools.com&lt;/A&gt; from the laptop. But I'm trying to setup another 506e (pixB) to do a site-site vpn to a remote pix 506e (pixC). I can't ssh into pixB from off-site, and can't figure out why. (I'm also concerned that I might not be able to setup a vpn session, also, but haven't tried, yet.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can ssh into pixB from the external network and have ssh 0.0.0.0 0.0.0.0 outside in the config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's my pixA (as router) config...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pixfirewall# sh ru&lt;/P&gt;&lt;P&gt;: Saved&lt;/P&gt;&lt;P&gt;:&lt;/P&gt;&lt;P&gt;PIX Version 6.3(3)&lt;/P&gt;&lt;P&gt;interface ethernet0 auto&lt;/P&gt;&lt;P&gt;interface ethernet1 auto&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;enable password HsJlBQXq9eIeQtEC encrypted&lt;/P&gt;&lt;P&gt;passwd HsJlBQXq9eIeQtEC encrypted&lt;/P&gt;&lt;P&gt;hostname pixfirewall&lt;/P&gt;&lt;P&gt;domain-name tccms.net&lt;/P&gt;&lt;P&gt;fixup protocol dns maximum-length 512&lt;/P&gt;&lt;P&gt;fixup protocol ftp 21&lt;/P&gt;&lt;P&gt;fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;fixup protocol http 80&lt;/P&gt;&lt;P&gt;fixup protocol rsh 514&lt;/P&gt;&lt;P&gt;fixup protocol rtsp 554&lt;/P&gt;&lt;P&gt;fixup protocol sip 5060&lt;/P&gt;&lt;P&gt;fixup protocol sip udp 5060&lt;/P&gt;&lt;P&gt;fixup protocol skinny 2000&lt;/P&gt;&lt;P&gt;fixup protocol smtp 25&lt;/P&gt;&lt;P&gt;fixup protocol sqlnet 1521&lt;/P&gt;&lt;P&gt;fixup protocol tftp 69&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;access-list 101 permit ip any any&lt;/P&gt;&lt;P&gt;access-list 101 permit icmp any any&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;ip address outside 172.43.91.38 255.255.255.252&lt;/P&gt;&lt;P&gt;ip address inside 172.43.91.65 255.255.255.192&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;pdm logging informational 100&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (outside) 0 access-list 101&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 101&lt;/P&gt;&lt;P&gt;access-group 101 in interface outside&lt;/P&gt;&lt;P&gt;access-group 101 in interface inside&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 172.43.91.37 1&lt;/P&gt;&lt;P&gt;timeout xlate 0:05:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00&lt;/P&gt;&lt;P&gt;timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;http server enable&lt;/P&gt;&lt;P&gt;http 192.168.1.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community public&lt;/P&gt;&lt;P&gt;no snmp-server enable traps&lt;/P&gt;&lt;P&gt;floodguard enable&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh 0.0.0.0 0.0.0.0 outside&lt;/P&gt;&lt;P&gt;ssh 0.0.0.0 0.0.0.0 inside&lt;/P&gt;&lt;P&gt;ssh timeout 30&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;terminal width 80&lt;/P&gt;&lt;P&gt;Cryptochecksum:c5b0f8b73aea7740355f6251c56bcdf9&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;&lt;P&gt;pixfirewall#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Mar 2006 20:47:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521112#M527194</guid>
      <dc:creator>jcw009</dc:creator>
      <dc:date>2006-03-03T20:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521113#M527202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of allowing all/permitting all ssh connections from outside and inside do mention the particular subnet blocks which requires the access or which can access the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 11:20:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521113#M527202</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-03-07T11:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521114#M527208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Whoops, my bad. Forgot the default route on the inside pix (pixB).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 13:47:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521114#M527208</guid>
      <dc:creator>jcw009</dc:creator>
      <dc:date>2006-03-07T13:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: Pix as router?</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521115#M527214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only thing is that I'm not sure where I'll be managing the pix from. Is there a way to disable the use of pix@ in the ssh connetions, or to define a different username to connect?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2006 13:49:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-router/m-p/521115#M527214</guid>
      <dc:creator>jcw009</dc:creator>
      <dc:date>2006-03-07T13:49:33Z</dc:date>
    </item>
  </channel>
</rss>

