->For point to point interfaces, you can use static routes that point to the interface or to the next hop address. There is only one possible next hop and its L2 address will be used to build L2 frame.
->For multipoint/Broadcast interfaces, it is more suitable to use static routes that point to a next hop address to avoid the need for resolving every destination address to its L2 address. As you have seen above it is still possible to use static routes pointing to the interface but not a scalable solution.
bornwith wrote: »
How does this work? With 2 separate commands or one with both the interface and next hop. If it's the later how does that work. I can't find an example and IOS doesn't seem to like it when I try it.
txn41655 wrote: »
ip route 172.31.0.0 255.255.255.0 s0/0/1 172.31.1.197
ccie14023 wrote: »
Well, this resulted in a separate ARP entry for every address on the Internet they were reaching, which meant a separate dCEF entry on the line card. It would run for a few weeks before memory would be consumed and then, crash. Whoops.
dontstop wrote: »
To what MAC Address was it resolving to for each of the IP Addresses? Was something upstream proxying for it?