At 01:57 PM 10/9/01 -0700, Luigi Rizzo wrote:
> >
> > When enabling this, I found that my kernel logs were full of all sorts of
> >
> > arplookup xxx.yyy.zzz.aaa failed: host is not on local network.
> > Any idea why this would be the case ? A bug ? An effect of a cache
> > lookup/miss?
>
>reques
>
> When enabling this, I found that my kernel logs were full of all sorts of
>
> arplookup xxx.yyy.zzz.aaa failed: host is not on local network.
>
> The strange this is that, that is correct, they are NOT on my local network
> and never have been. So, why would the box suddenly think, seemin
When enabling this, I found that my kernel logs were full of all sorts of
arplookup xxx.yyy.zzz.aaa failed: host is not on local network.
The strange this is that, that is correct, they are NOT on my local network
and never have been. So, why would the box suddenly think, seemingly
random ne
