Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Aug 2011 03:32:38 +0000
From:      "Li, Qing" <qing.li@bluecoat.com>
To:        Chris Miller <chrismiller.bsd@gmail.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   RE: arpresolve: can't allocate llinfo
Message-ID:  <B143A8975061C446AD5E29742C53172310143E@PWSVL-EXCMBX-01.internal.cacheflow.com>
In-Reply-To: <CA%2B3_3nMPiSo80vX=4AuB%2BaYXWnRV4NFiFMo-gwFN3b8V8DO=1w@mail.gmail.com>
References:  <CA%2B3_3nPfJFwCHDE4s95iUBzDmfJaQhS2XBnZsm0geyics4XVRg@mail.gmail.com> <B143A8975061C446AD5E29742C5317230FD4B1@PWSVL-EXCMBX-01.internal.cacheflow.com> <CA%2B3_3nMPiSo80vX=4AuB%2BaYXWnRV4NFiFMo-gwFN3b8V8DO=1w@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thank you Chris for the verification. I will wait a few days before committ=
ing the patch.

--Qing


From: Chris Miller [mailto:chrismiller.bsd@gmail.com]
Sent: Monday, August 29, 2011 7:31 PM
To: Li, Qing
Cc: freebsd-net@freebsd.org
Subject: Re: arpresolve: can't allocate llinfo

Qing-

This patch seems to be working. I was not seeing the issue every time so I =
can't say with 100% certainty, but I'd say I'm 95% certain at this point. I=
f you don't hear otherwise in the next few days, assume that it is fixed.

Thanks for your help.

-Chris

On Sat, Aug 27, 2011 at 2:13 PM, Li, Qing <qing.li@bluecoat.com<mailto:qing=
.li@bluecoat.com>> wrote:
Hi,

Could you please try the patch sitting at

       http://people.freebsd.org/~qingli/in.c.diff<http://people.freebsd.or=
g/%7Eqingli/in.c.diff>

and let me know if it works for you?

Thanks,

-- Qing


> -----Original Message-----
> From: owner-freebsd-net@freebsd.org<mailto:owner-freebsd-net@freebsd.org>=
 [mailto:owner-freebsd-<mailto:owner-freebsd->
> net@freebsd.org<mailto:net@freebsd.org>] On Behalf Of Chris Miller
> Sent: Tuesday, August 16, 2011 3:05 PM
> To: freebsd-net@freebsd.org<mailto:freebsd-net@freebsd.org>
> Subject: arpresolve: can't allocate llinfo
>
> I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> frequently.
>
> IPv4 address: "169.254.231.172" is not on the network
> arpresolve: can't allocate llinfo for 169.254.231.172
>
> Background:
> I have two interfaces attached to the same LAN, both configured using
> 169.254/16 link local automatic addressing.
> ARP entries exist for each interface.
> There are two routing entries for 169.254.0.0/16<http://169.254.0.0/16>, =
one going out each
> interface.
>
> I've done some debugging and it appears that this happens when a packet
> is
> received on one of the interfaces and while sending the reply the
> routing
> lookup code says that we should send it out the other interface. This
> causes
> the "not on the network" message.
>
> I'm looking for suggestions or patches to allow this configuration to
> work
> as I need to have both interfaces on this network for redundancy.
>
> Thanks for any help.
>
> -Chris Miller
> _______________________________________________
> freebsd-net@freebsd.org<mailto:freebsd-net@freebsd.org> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org<mai=
lto:freebsd-net-unsubscribe@freebsd.org>"




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