<?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 Managing ASA5510 using ASDM via internal interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900365#M436575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;it sounds like a better plan than opening up for each and every unit on the inside :).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if you have a old laptop or something like that I would state that setting that up with a syslog server and use that to manage the firewall would be a even better option.&lt;/P&gt;&lt;P&gt;that way you would get logs and a management station.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there are several syslog servers that are free and I like to use grep that is also free to filter information. &lt;/P&gt;&lt;P&gt;http 10.1.1.52 255.255.255.255 inside &lt;/P&gt;&lt;P&gt;will make the 10.1.1.52 the only server to work with asdm&lt;/P&gt;&lt;P&gt;but you will have to remove the old http 10.1.1.0 255.255.255.0 inside statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you find the answers helpful please rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2012 20:13:59 GMT</pubDate>
    <dc:creator>hobbe</dc:creator>
    <dc:date>2012-05-18T20:13:59Z</dc:date>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900362#M436566</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am currently managing an ASA5510 using ASDM through the management port but I would like to manage the ASA through the internal port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My concern is that I thought I remembered reading someplace that if you setup an internal port for management that it can't be used for anything else.&amp;nbsp; Is this correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I only configured one internal port and it is the path to my LAN.&amp;nbsp; I would hate to configure the port for management only to find that I disconnected my firewall from my internal network in the process.&amp;nbsp; Can I use my one and only configured internal port for both ASA management and route from my LAN thru the ASA firewall?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I currently have the management port set to 192.168.1.1 and my internal interface is 10.1.1.1.&amp;nbsp; If I open ASDM and connect thru the management port and select Configuration/Device Management/Management&amp;nbsp; Access/ASDM/HTTPS/Telnet/SSH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select "ADD"&lt;/P&gt;&lt;P&gt;select access type "ASDM/HTTPS"&lt;/P&gt;&lt;P&gt;select interface "internal"&lt;/P&gt;&lt;P&gt;IP Address&amp;nbsp;&amp;nbsp; "10.1.1.0"&lt;/P&gt;&lt;P&gt;Mask&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "255.255.255.0"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will that give me access to ASA management thru my internal network but cripple my network access to the ASA?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry if this is confusing... I don't know how else to phrase it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:08:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900362#M436566</guid>
      <dc:creator>Edward Luna</dc:creator>
      <dc:date>2019-03-11T23:08:52Z</dc:date>
    </item>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900363#M436569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;yes you can use the inside interface, no problem&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do you have a special address you know you will be coming from ?&lt;/P&gt;&lt;P&gt;if not you should have that &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;start the cli&lt;/P&gt;&lt;P&gt;http 10.1.1.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 19:57:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900363#M436569</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2012-05-18T19:57:57Z</dc:date>
    </item>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900364#M436572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks for the fast reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was thinking that I might use remote administration to my Small Business Server 2008 (RWW) to connect to my server (known internal IP address) and specify that only that IP can administer the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sound like a plan? &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 20:04:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900364#M436572</guid>
      <dc:creator>Edward Luna</dc:creator>
      <dc:date>2012-05-18T20:04:09Z</dc:date>
    </item>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900365#M436575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;it sounds like a better plan than opening up for each and every unit on the inside :).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if you have a old laptop or something like that I would state that setting that up with a syslog server and use that to manage the firewall would be a even better option.&lt;/P&gt;&lt;P&gt;that way you would get logs and a management station.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there are several syslog servers that are free and I like to use grep that is also free to filter information. &lt;/P&gt;&lt;P&gt;http 10.1.1.52 255.255.255.255 inside &lt;/P&gt;&lt;P&gt;will make the 10.1.1.52 the only server to work with asdm&lt;/P&gt;&lt;P&gt;but you will have to remove the old http 10.1.1.0 255.255.255.0 inside statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you find the answers helpful please rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 20:13:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900365#M436575</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2012-05-18T20:13:59Z</dc:date>
    </item>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900366#M436580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; oops... I just thought of something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RWW connects to the SBS 2008 via HTTPS (port 443)&lt;/P&gt;&lt;P&gt;The add device management in ASDM says it uses port 443 for HTTP admin access.&amp;nbsp; Sounds like a conflict.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will I need to change the port assignment for ASDM management from 443 to 444 or does the fact that the IP addresses are different for the two functions negate the need for different ports? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In other words... ASDM comes in port 443 but for ip addy 10.1.1.1 and RWW comes in port 443 but ip addy 10.1.1.2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="confused" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 20:22:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900366#M436580</guid>
      <dc:creator>Edward Luna</dc:creator>
      <dc:date>2012-05-18T20:22:40Z</dc:date>
    </item>
    <item>
      <title>Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900367#M436583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I will gladly rate... your answers are always very helpfull.&amp;nbsp; Now if I only knew how to rate we'd be fat.&amp;nbsp; How do I do it?&amp;nbsp; Rate I mean. &lt;SPAN __jive_emoticon_name="laugh" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 20:27:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900367#M436583</guid>
      <dc:creator>Edward Luna</dc:creator>
      <dc:date>2012-05-18T20:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: Managing ASA5510 using ASDM via internal interface</title>
      <link>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900368#M436584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Yes the different addres makes it a totally different thing.&lt;/P&gt;&lt;P&gt;443 is "standard" for https so basically most webservers that uses SSL use that port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is basic TCP/IP and if you are to work with firewalls you should study it until you know it front to back.&lt;/P&gt;&lt;P&gt;There are some realy nice books from o´reilly. if you have the time it would make sence to start reading up on ip v6 also. its not "here" when it comes to america and europe, but it is growing fast in Asia.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 21:47:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/managing-asa5510-using-asdm-via-internal-interface/m-p/1900368#M436584</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2012-05-18T21:47:11Z</dc:date>
    </item>
  </channel>
</rss>

