Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 May 1998 13:10:50 -0300 (GMT)
From:      Fernando Schapachnik <fpscha@ns1.sminter.com.ar>
To:        mike@seidata.com (Mike)
Cc:        brian@Awfulhak.org, fpscha@ns1.sminter.com.ar, hackers@FreeBSD.ORG
Subject:   Re: arplook
Message-ID:  <199805291610.NAA22492@ns1.sminter.com.ar>
In-Reply-To: <Pine.BSF.3.96.980529115501.16830B-100000@ns1.seidata.com> from "Mike" at May 29, 98 12:01:53 pm

next in thread | previous in thread | raw e-mail | index | archive | help
En un mensaje anterior, Mike escribió:
> 
> On Fri, 29 May 1998, Brian Somers wrote:
> 
> [snip]
> > > > arplookup 102.255.209.107 failed: host is not on local network
> > > > arplookup 102.255.207.132 failed: host is not on local network
> [snip]
> 
> I've encountered this as well...  I asked a guru contact of mine and this
> is what he had to say:
> 
> <transcript>
> 
> > Also, looking over 'messages' on ns1 today and I have some questions
> > about the following errors:
> >
> > 'arplookup 1.2.3.45 failed: host is not on local network'
> >
> > I think we established that this one was related to improper usage of
> > subnet masks before...  I'm getting sick of seeing dmesg flooded with
> > these.  Is this definately a subnet/subnet mask issue?
> 
> This is actually caused because the server has some IP addresses from
> 1.2.3.X on it and so it believes it should be able to create an
> arp entry for 1.2.3.45 but then notices that it can't because
> it isn't on the same network :)
> 
> The solution is to move 1.2.3.45 to the 4.5.6 subnet along
> with every other device on the LAN there... 1 LAN, 1 subnet... thats
> the goal. This raises the issues of virtual addresses and async 
> addresses also... but I'd definately start with the actual LAN
> devices. Move every ethernet device to the 4.5.6 subnet.  Routing will
> work better, accesses will be quicker, etc...
> 
> </transcript>
> 
> 'ns1' is on the '4.5.6' class C with 30-40 '1.2.3' aliases.  Hope it

This is not my case: I don't have any alias on the 102 network.
Here is my ifconfig, it may clarify my situation:
1001]ns3:/usr/home/fpscha>ifconfig -a
vx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 200.10.104.25 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.26 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.27 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.28 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.29 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.30 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.31 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.32 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.33 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.34 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.35 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.36 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.37 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.39 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.40 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.41 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.42 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.43 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.44 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.46 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.47 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.49 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.50 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.52 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.53 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.54 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.61 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.63 netmask 0xffffffc0 broadcast 200.10.104.63
        inet 200.10.104.65 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.69 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.70 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.71 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.72 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.73 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.74 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.76 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.80 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.81 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.83 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.84 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.86 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.87 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.88 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.89 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.90 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.91 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.94 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.97 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.98 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.99 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.100 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.101 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.102 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.103 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.104 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.105 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.106 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.108 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.109 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.110 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.111 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.112 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.113 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.114 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.115 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.116 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.117 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.118 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.119 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.120 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.123 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.124 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.125 netmask 0xffffffc0 broadcast 200.10.104.127
        inet 200.10.104.129 netmask 0xffffffc0 broadcast 200.10.104.191
        inet 200.10.104.130 netmask 0xffffffc0 broadcast 200.10.104.191
        inet 200.10.104.131 netmask 0xffffffc0 broadcast 200.10.104.191
        inet 200.10.104.132 netmask 0xffffffc0 broadcast 200.10.104.191
        inet 200.10.102.251 netmask 0xffffff00 broadcast 200.10.102.255
        inet 200.10.100.16 netmask 0xffffff00 broadcast 200.10.100.255
        ether 00:60:97:61:91:71 
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 

Thank you!

> helps...
> 
> ---
>  Mike Hoskins				Email: mike@seidata.com
>  SEI Data Network Services, Inc.	  WWW: http://www.seidata.com
>  P.O. Box 7, 14005 U.S. 50 (BLD2)	Voice: 800.925.6746 ex. 251
>  Dillsboro, IN 47018			  Fax: 812.744.8000
> 
> 


Fernando P. Schapachnik
Administracion de la red
S&M Internet

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805291610.NAA22492>