[Prev][Next][Index][Thread]

Re: my ARP message




On Fri, 1 Nov 1996, Ira Abramov wrote:

> Date: Fri, 1 Nov 1996 08:04:07 +0200 (IST)
> From: Ira Abramov <ira@scso.com>
> To: Randy Wright <randy@dune.ramat-negev.org.il>
> Cc: ILUG <linux-il@linux.org.il>, mark@netmedia.net.il
> Subject: Re: my ARP message
> 
> On Tue, 29 Oct 1996, Randy Wright wrote:
> 
> "ARP: dev->type mangled! 15 dlci00" is now what I get on the console
> (printk)
> 
> #define ARPHRD_DLCI     15              /* Frame Relay DLCI             */
> 
> and indeed it is coming through interfacedlci00, which is the link to
> Netmedia...

not to patch your kernel, but the idea is simply:
ARP is used on local networks only. if you get it through a frame-relay
link, it means the remote side is missconfigured - it's probably not a
linux bug (i.e. if it's an iincoming packet, just dump it to bit bucket,
and ask netmedia to check their definitions).

(just to clarify: ARP is for LANS only cause it's used to translate an IP
address to a MAC address (addresses such as ethernet addresses) in order
to allow sending packets to a machine that is directly accesibly through
one of your connected interfaces.one machine sends an ARP request, which
is a broadcast asking "who has this and this IP address". only one
machine on the net answers 'IT is I', and through this message revealses
its ethernet address (or whatever local net is used), and then all
machines cache this info (cause it's a broadcast too).)

in short : this is probably not a linux bug, rather a netmedia feature.

guy


Follow-Ups: References: