<?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: Cisco ASA 5505 Enable Live Traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903701#M458077</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By default, traffic is allowed from more secure (inside) networks to less secure (outside - often the Internet). That "implicit allow" plus a global NAT rule is sufficient for all Internet access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to lock things down to specific services, it's a bit more involved - many web-based services and even home pages call elements from more than one site / DNS entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We'd have to see your config to give a more accurate answer for your specific context.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Mar 2012 19:49:20 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2012-03-16T19:49:20Z</dc:date>
    <item>
      <title>Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903698#M458070</link>
      <description>&lt;P&gt;I am currently troubleshooting a firewall policy on a ASA 5505. What command can enter in the CLI to enable live view of traffic been block and which traffic is been allow?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my experiences with other firewall vendors, other firewalls allow me to narrow down the source and destination, too. is there such thing on the ASA 5505?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903698#M458070</guid>
      <dc:creator>par13</dc:creator>
      <dc:date>2019-03-11T22:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903699#M458071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A couple of tools can be used. If there is an access-list issue, you can "show access-list" and watch for hits. Better still is the packet tracer utility. Using it, one can test the firewall's handling of a hypothetical flow and tell if it pases or, if it fails, why it does. See the syntax and examples in the &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/p.html#wp2129824" rel="nofollow"&gt;command reference&lt;/A&gt;. You can also &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/c1.html#wp2147322" rel="nofollow"&gt;capture traffic&lt;/A&gt; but that won't necessarily show you how the firewall is handling the traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2012 16:08:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903699#M458071</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-03-15T16:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903700#M458074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, how do I configure the asa 5505 to allow my internal computers to go to windowsupdate.microsoft.com to get windows updates?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2012 19:44:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903700#M458074</guid>
      <dc:creator>par13</dc:creator>
      <dc:date>2012-03-16T19:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903701#M458077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By default, traffic is allowed from more secure (inside) networks to less secure (outside - often the Internet). That "implicit allow" plus a global NAT rule is sufficient for all Internet access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to lock things down to specific services, it's a bit more involved - many web-based services and even home pages call elements from more than one site / DNS entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We'd have to see your config to give a more accurate answer for your specific context.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2012 19:49:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903701#M458077</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-03-16T19:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903702#M458080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was reading online that version 8.2 supports fqdn which on that case it seems that I could use windowsupdate.microsoft.com on the network-object host or hostname area. Does this makes senses? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way, we are running ver 7.2. Is there something wrong to upgrade directly to 8.2 or do I need to follow the 8.0,8.1 and 8.2?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2012 20:08:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903702#M458080</guid>
      <dc:creator>par13</dc:creator>
      <dc:date>2012-03-16T20:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903703#M458083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well-established and unchanging FQDNs can indeed be used in access-lists (assuming your ASA can resolve them on a configured DNS server). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm just saying that, for instance, when I browse from my Windows 7 machine to windowsupdate.microsoft.com, it redirects to update.microsoft.com (at the same IP) which in turn instructs me to use the control panel applet. When I do that (and watch the connections from my machine) I see a connection open up to another address in the same network. A simple FQDN in the access-list might not follow all of that web redirection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrading from 7.2 to 8.2 is supported. Reference &lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa82/release/notes/asarn82.html#wp315678"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2012 20:24:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903703#M458083</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-03-16T20:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5505 Enable Live Traffic</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903704#M458087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you all! Beside the question above, can anyone tell me why my static ip address stop working. I created a static ip address which allow external traffic to access internal hosts. As you can see below, I added these lines:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip any host 152.18.75.133&lt;/P&gt;&lt;P&gt;static (inside,outside) 152.18.75.133 10.2.1.2 netmask 255.255.255.255&lt;BR /&gt;access-group outside_access_in in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Version 8.4&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;hostname cisco-asa&lt;/P&gt;&lt;P&gt;domain-name default.domain.invalid&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;names&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Vlan1&lt;/P&gt;&lt;P&gt;nameif inside&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;ip address 10.2.1.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Vlan2&lt;/P&gt;&lt;P&gt;nameif outside&lt;/P&gt;&lt;P&gt;security-level 0&lt;/P&gt;&lt;P&gt;ip address 152.18.75.132 255.255.255.240 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt;switchport access vlan 2&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/3&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/4&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/5&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/6&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/7&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;passwd 2KFQnbNIdI.2KYOU encrypted&lt;/P&gt;&lt;P&gt;ftp mode passive&lt;/P&gt;&lt;P&gt;dns server-group DefaultDNS&lt;/P&gt;&lt;P&gt;domain-name default.domain.invalid&lt;/P&gt;&lt;P&gt;object-group network dts-servers&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;network-object host 152.31.53.251&lt;/P&gt;&lt;P&gt;network-object host 152.31.53.195&lt;/P&gt;&lt;P&gt;object-group network frs_servers&lt;/P&gt;&lt;P&gt;network-object 152.111.5.22 255.255.255.255&lt;/P&gt;&lt;P&gt;access-list extended extended permit ip any any &lt;/P&gt;&lt;P&gt;access-list extended extended permit icmp any any &lt;/P&gt;&lt;P&gt;access-list extended extended permit ip any object-group dts-servers &lt;/P&gt;&lt;P&gt;access-list acl_out extended permit tcp any object-group frs_servers eq https &lt;BR /&gt;access-list outside_access_in extended permit ip any host 152.18.75.133&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging asdm informational&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;icmp unreachable rate-limit 1 burst-size 1&lt;/P&gt;&lt;P&gt;icmp permit any echo-reply inside&lt;/P&gt;&lt;P&gt;icmp permit 10.2.1.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;icmp permit any echo-reply outside&lt;/P&gt;&lt;P&gt;icmp permit 152.31.53.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;icmp permit 152.31.185.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;asdm image disk0:/asdm-523.bin&lt;/P&gt;&lt;P&gt;no asdm 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 (inside) 1 0.0.0.0 0.0.0.0&lt;BR /&gt;static (inside,outside) 152.18.75.133 10.2.1.2 netmask 255.255.255.255&lt;BR /&gt;access-group outside_access_in in interface outside&lt;BR /&gt;route outside 0.0.0.0 0.0.0.0 152.18.75.129 1&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;/P&gt;&lt;P&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00&lt;/P&gt;&lt;P&gt;timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;http 10.2.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 enable traps snmp authentication linkup linkdown coldstart&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh 10.2.1.2 255.255.255.255 inside&lt;/P&gt;&lt;P&gt;ssh 152.31.53.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;ssh 152.18.1.128 152.18.75.132 outside&lt;/P&gt;&lt;P&gt;ssh timeout 30&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;dhcpd auto_config outside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;dhcpd address 10.2.1.2-10.2.1.254 inside&lt;/P&gt;&lt;P&gt;dhcpd enable inside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt;match default-inspection-traffic&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map type inspect dns preset_dns_map&lt;/P&gt;&lt;P&gt;parameters&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt;class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225 &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rtsp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect esmtp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect skinny &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect xdmcp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect netbios &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp; inspect tftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;service-policy global_policy global&lt;/P&gt;&lt;P&gt;prompt hostname context &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 14:24:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5505-enable-live-traffic/m-p/1903704#M458087</guid>
      <dc:creator>par13</dc:creator>
      <dc:date>2012-03-21T14:24:31Z</dc:date>
    </item>
  </channel>
</rss>

