lkml.org 
[lkml]   [1997]   [Jul]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Strange Network behavior
Date
> address is 204.178.40.0, netmask is 255.255.248.0. Why would it be
> ARPing a broadcast address? In principle, with a netmask of 255.255.248.0,
> the broadcast address should be 204.178.47.255, but many machines use
> the broadcast address of each 'C' subnet, i.e., 40.255, 41.255, 42.255, etc.

So you have your machine misconfigured. Or they have theirs wrong. One of
the two. Either they have their netmask wrong OR you should have yours as
.255 and route to the other networks via a router or by having alias
addresses to each network

> ARPing these addresses? It seems real strange. The ARP cache contains
> these addresses, put there I think, when the machine was configured for
> routing and transparent proxy:

Heard, learned and refreshed occasionally.

> I think that these addresses are being `expired` and the network
> code attempts to `refresh` them by sending the ARP who-is message
> on the LAN. If so, this might be a tiny bug.

No thats regarded as "the right technique" nowdays - you'll see cisco
routers do the same thing.

Alan


\
 
 \ /
  Last update: 2005-03-22 13:40    [from the cache]
©2003-2011 Jasper Spaans