[lkml]   [2003]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [2.4 PATCH] bugfix: ARP respond on all devices
I have received reply from Cisco:

*********** BEGIN FORWARDED MESSAGE ***********

On 06/08/2003 at 11:40 Oscar Madrid <> wrote:

>My name is Oscar Madrid and I'm Luis Isselin's escalation engineer.
>decided to answer to this case straight as this is a question of
>or not Cisco is following a standard.
>I can only think of one scenario where an arp request would come in
>192.168.140.x to a router interface that has That one
>scenario is a misconfiguration.
>ARP is designed to find the next hop on a LAN. If the host has an IP
>address of and wants to get to, it will
>to have a default gateway configured.
>This default gateway would have to be on the same logical local
>Now, lets say that the host has an IP address of
>will include both 192.168.128.x and 192.168.140.x. This would still
be a
>misconfig as the router is not on the same subnet. (meaning the router
>does not have the same /17 mask. The host can see the router, but the
>router cannot see the host).
>You could, in theory, say that we're not following "similar algorithm"
>the RFC as we check the source, but this is more for a sanity check as
>it was a perfect world and everything is configured properly and there
>were no such things as bad implementations of TCP/IP stacks, then we
>wouldn't need to check.
>If the router for some reason was responding to the ARP broadcast, how
>would anyone know where the packet came from since the network is not
>being advertised as connected to this router? Meaning, how would a
>packet make it back to the host? The router doesn't "see" the host in
>logical network therefore it cannot communicate with it.
>I believe that reason we do the sanity check is because of basic IP
>routing. If the source is not from an IP address on the interface we
>received it on, we cannot reply to that IP address. It is simple as
>As I stated, ARP is designed to be used on a LAN. This means that all
>stations that send/receive ARP packets are on the same subnet. This
>the reason we do the check.
>Please also note another portion of the RFC 0826 in question:
>[The purpose of this RFC is to present a method of Converting
>Protocol Addresses (e.g., IP addresses) to Local Network
>Addresses (e.g., Ethernet addresses). This is a issue of general
>concern in the ARPA Internet community at this time. The
>method proposed here is presented for your consideration and
>comment. This is not the specification of a Internet Standard.]
>When it is talking about Local Network Addresses, that means IP
>on the same network. This is why we can perform the checks we
perform in
>our IOS.
>The point of the check would be to verify that the hosts are
>correctly. There is no case where a properly configured host should
>send a ARP request for an IP address on a different subnet.
>The best example I can point out is this:
>Ethernet is a Broadcast network which uses ARP to find HW addresses
>other IP addresses on the same broadcast network. If the IP address
>not on the same network, then the host/router/client needs to find the
>gateway which is on the local network.
>Basic and proper implementations of the TCP/IP stack should never ARP
>for a device that it is not located on the same logical network the
>is, the reason for this being they cannot communicate directly unless
>gateway is involved. The only ARP request a host should send in this
>is for its gateway that should also be a "local" device to the host
>I hope this clears up the reson why Cisco's ARP implementation has
>safeguard you have found along with several others, HOWEVER, please
>to RFC 1027, ( and under section
>it contains the following paragraph:
>[If the IP networks of the source and target hosts of an ARP request
>are different, an ARP subnet gateway implementation should not
>reply. This is to prevent the ARP subnet gateway from being used to
>reach foreign IP networks and thus possibly bypass security checks
>provided by IP gateways. ]
>I would also ask you if you would be so kind to send me the link to
>netdev list of linux kernel you are making mention to so I can
escalate it
>and respond to the linux community if higher up is deemed up necesary.
>Best Regards,
>Oscar Madrid
>Customer Support Engineer
>Routing Protocols Team
>Cisco Systems
>Open a TAC case on the web for faster response!
>Visit the TAC Web Site for quick access to technical support!
>Use the new TAC Advanced Search to find information fast!

*********** END FORWARDED MESSAGE ***********

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.288 / U:1.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site