arpresolve: can't allocate llinfo
Li, Qing
qing.li at bluecoat.com
Tue Aug 30 03:32:41 UTC 2011
Thank you Chris for the verification. I will wait a few days before committing the patch.
--Qing
From: Chris Miller [mailto:chrismiller.bsd at gmail.com]
Sent: Monday, August 29, 2011 7:31 PM
To: Li, Qing
Cc: freebsd-net at 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. If 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 at bluecoat.com<mailto:qing.li at bluecoat.com>> wrote:
Hi,
Could you please try the patch sitting at
http://people.freebsd.org/~qingli/in.c.diff<http://people.freebsd.org/%7Eqingli/in.c.diff>
and let me know if it works for you?
Thanks,
-- Qing
> -----Original Message-----
> From: owner-freebsd-net at freebsd.org<mailto:owner-freebsd-net at freebsd.org> [mailto:owner-freebsd-<mailto:owner-freebsd->
> net at freebsd.org<mailto:net at freebsd.org>] On Behalf Of Chris Miller
> Sent: Tuesday, August 16, 2011 3:05 PM
> To: freebsd-net at freebsd.org<mailto:freebsd-net at 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 at freebsd.org<mailto:freebsd-net at freebsd.org> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org<mailto:freebsd-net-unsubscribe at freebsd.org>"
More information about the freebsd-net
mailing list