01-04-2009 08:33 AM - edited 03-04-2019 03:19 AM
I have a question about using static routes with DHCP.
I understand that a static default route pointing to an interface, as the next hop, will generate superfluous ARP entries for every destination. So, with that in mind, will the static route (A) below, produce the same kind of superfluous ARP messages as the static route (B) below?
A. ip route 0.0.0.0 0.0.0.0 dhcp
B. ip route 0.0.0.0 0.0.0.0 fa 0/4
Solved! Go to Solution.
01-04-2009 02:45 PM
Using DHCP in your static route will not produce the superfluous ARP entries on your router. I would recommend using ip route 0.0.0.0 0.0.0.0 dhcp over ip route 0.0.0.0 0.0.0.0 fa 0/4.
Having a static route to point to specific IP address is better practice than pointing to interface. Specifically for default route learned from DHCP server (in your case is probably the ISP DHCP server).
HTH,
Mark
01-04-2009 02:45 PM
Using DHCP in your static route will not produce the superfluous ARP entries on your router. I would recommend using ip route 0.0.0.0 0.0.0.0 dhcp over ip route 0.0.0.0 0.0.0.0 fa 0/4.
Having a static route to point to specific IP address is better practice than pointing to interface. Specifically for default route learned from DHCP server (in your case is probably the ISP DHCP server).
HTH,
Mark
01-06-2009 05:02 PM
Thanks! That makes sense!
01-04-2009 02:47 PM
Michael
I believe that your A static route will not generate the number of ARP entries that the B static route would. It is my understanding that Cisco added the ability to specify dhcp in a static route to address this very issue. The DHCP information typically includes the address of the gateway router and this configuration allows your router to use this learned address so that it does not need to ARP for the next hop address.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide