Subject: Re: arp problem
To: Ignatios Souvatzis <is@beverly.kleinbus.org>
From: Andrei Petrov <and@genesyslab.com>
List: tech-net
Date: 09/27/2000 12:36:05
On Wed, 27 Sep 2000, Ignatios Souvatzis wrote:

> On Tue, Sep 26, 2000 at 03:39:30PM -0700, Andrei Petrov wrote:
> > 
> > I tried to move net-boot server from i386/1.5B to alpha/1.5F
> > and discovered that I can't make published entry by arp.
> > 
> > I'm doing 
> > arp -s <hostname or ip doesn't mater> ether_addr pub
> > 
> > arp returns silently or with error
> > arp: writing to routing socket: File exists
> > 
> > Check by 'arp -a' doesn't show requested entry.
> 
> what does netstat -r show?
> 	-is
> 

I did it before, have no idea how to interpret it. New entry doesn't
appear.

before:

Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu
Interface
default            zeus-net7.genesysl UGS         0        0   1500  tlp0
loopback           localhost          UGRS        0        0  33192  lo0
localhost          localhost          UH          1        0  33192  lo0
192.168.7          link#1             UC          0        0   1500  tlp0
zeus-net7.genesysl 00:02:17:f1:48:00  UHL         1        0   1500  tlp0
flipper.genesyslab 08:00:2b:bb:46:67  UHL         1        4   1500  tlp0

After arp -s muppet 08:00:20:88:ed:05 published

Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu
Interface
default            link#1             UCS2        0        0   1500  tlp0
=>
default            zeus-net7.genesysl UGS         0        0   1500  tlp0
loopback           localhost          UGRS        0        0  33192  lo0
localhost          localhost          UH          1        0  33192  lo0
192.168.7          link#1             UC          0        0   1500  tlp0
zeus-net7.genesysl 00:02:17:f1:48:00  UHL         1        0   1500  tlp0
flipper.genesyslab 08:00:2b:bb:46:67  UHL         1       11   1500  tlp0

What bother me that if that's misalighnment or different padding
in application and kernel(?) why it doesn't screwed up when arp
reads entries? Another thing is: I tried to use gdb to check what's 
inside : 
gdb /netbsd
(gdb) target kcore /dev/kmem
/dev/kmem: Invalid argument.
I thought that I saw somewhere how to do it, any pointers will be
appreciated.

Thanks for your interest,
	Andrey