<?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: ASA dhcprelay per interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948911#M940996</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That makes sense, thank you very much.  If I understand correctly:  as long as the ASA 5505 is compliant with RFC 1542, it will substitute its own gateway address into the dhcp request packet before it forwards it to the dhcp servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then when the dhcp servers receive the request, it will know whether it needs to reply with an address based on if it has a dhcp scope configured that corresponds to the relay address provided in the request.  (assuming the dhcp servers are also rfc compliant and don't just blindly reply to all dhcp requests)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I have that correct?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Mar 2008 14:42:05 GMT</pubDate>
    <dc:creator>ippolito</dc:creator>
    <dc:date>2008-03-20T14:42:05Z</dc:date>
    <item>
      <title>ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948906#M940990</link>
      <description>&lt;P&gt;I have an ASA-5505 with 3 vlans:  outside, inside1, and inside 2.  I'd like DHCP requests from inside1 and inside2 to go to different DHCP servers, depending on which interface the requests are received on.  It would be the equivalent of issuing ip helper-address commands on two different router interfaces.  It doesn't appear to be possible on the ASA-5505.  Is that really correct???  If so, then do any of the other ASA models provide this capability?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:17:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948906#M940990</guid>
      <dc:creator>ippolito</dc:creator>
      <dc:date>2019-03-11T12:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948907#M940992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For your network you should better use a router or a switch for DHCP requests to be guided to DHCP servers depending on the interface. You can put the ASA after the router in your network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 21:05:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948907#M940992</guid>
      <dc:creator>amritpatek</dc:creator>
      <dc:date>2008-03-19T21:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948908#M940993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can configure your ASA  to be a Dynamic Host Configuration Protocol (DHCP) relay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a008075fcfb.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a008075fcfb.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Franco&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 21:13:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948908#M940993</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-03-19T21:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948909#M940994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I know about dhcp relay -- this is exactly what I'm trying to use.  But I want to relay to two different dhcp servers - one for dhcp requests on vlan1, one for dhcp requests on vlan2.  If I understand how the ASA works, it will forward all packets from all vlans on which dhcp relay is enabled to ALL of the dhcp relay servers that are configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2008 13:16:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948909#M940994</guid>
      <dc:creator>ippolito</dc:creator>
      <dc:date>2008-03-20T13:16:10Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948910#M940995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All the ASA is doing is just relay the dhcp request between client and server. When the DHCP relay agent on the ASA appliance receives a DHCP request from a host on one of it  interface, it will forward the request to one of the specified DHCP servers on an  interface the servers are behind. When the DHCP server replies to the client, the security appliance forwards that reply back. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to answer your question: Just make sure both that both DHCP servers are setup on the asa for example if the servers are behind the inside interface "dhcprelay server ****  inside" and make sure the servers are setup with the correct dhcp scope for the vlan1 and vlan 2. when the request is sent fromt her asa to the dhcp server, as long as the server have a dhcp scope for the correct vlan, it will respond back with an ip address to the asa and the asa will relay it to the client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm i making sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Franco&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2008 13:45:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948910#M940995</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-03-20T13:45:11Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948911#M940996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That makes sense, thank you very much.  If I understand correctly:  as long as the ASA 5505 is compliant with RFC 1542, it will substitute its own gateway address into the dhcp request packet before it forwards it to the dhcp servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then when the dhcp servers receive the request, it will know whether it needs to reply with an address based on if it has a dhcp scope configured that corresponds to the relay address provided in the request.  (assuming the dhcp servers are also rfc compliant and don't just blindly reply to all dhcp requests)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I have that correct?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2008 14:42:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948911#M940996</guid>
      <dc:creator>ippolito</dc:creator>
      <dc:date>2008-03-20T14:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948912#M940997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that's correct. give it a go and let me know the outcome. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Franco&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2008 14:50:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948912#M940997</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-03-20T14:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: ASA dhcprelay per interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948913#M940998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That worked, thank you very much for your help.  How to I tag this message as having been resolved?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2008 13:33:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dhcprelay-per-interface/m-p/948913#M940998</guid>
      <dc:creator>ippolito</dc:creator>
      <dc:date>2008-03-24T13:33:59Z</dc:date>
    </item>
  </channel>
</rss>

