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@xxxxxxxxxxxx> wrote:

Hi,

Could you please try the patch sitting at

http://people.freebsd.org/~qingli/in.c.diff

and let me know if it works for you?

Thanks,

-- Qing


-----Original Message-----
From: owner-freebsd-net@xxxxxxxxxxx [mailto:owner-freebsd-
net@xxxxxxxxxxx] On Behalf Of Chris Miller
Sent: Tuesday, August 16, 2011 3:05 PM
To: freebsd-net@xxxxxxxxxxx
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, 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@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: [2.4 PATCH] bugfix: ARP respond on all devices
    ... What RFC is breaking? ... The actual behaviour of linux makes loopback interfaces no sense. ... Also, as long as I know, 127.0.0.1 is not answered in ARP, although ... I think the hidden patch is also RFC compliant. ...
    (Linux-Kernel)
  • Re: [take22 0/4] kevent: Generic event handling mechanism.
    ... February I changed interfaces 4 times - and it is just interfaces, ... When all requested features are implemented I definitely with patch some ... that my guesses were told by The Big Jury to you already: ... why do you care about indent of the userspace ...
    (Linux-Kernel)
  • [PATCH] PCIERR : interfaces for synchronous I/O error detection on driver
    ... This patch proposes new interfaces, that known by few as iochk_*, ... for synchronous I/O error detection on PCI drivers. ... I suppose that proposed interfaces will solve most of remaining issues. ... - i.e. this feature improves Serviceability. ...
    (Linux-Kernel)
  • Re: if_clone.c allows creating multiple interfaces with the same name
    ... allows T> D> multiple interfaces to be created with exactly the same name ... T> I decided to simply if_clone code utilizing generic unit allocator. ... Please review my patch and test it, and then we can commit it. ... Your patch with IFNET_NAMING_LOCKjust plumbs one race case: ...
    (freebsd-current)
  • arpresolve: cant allocate llinfo
    ... I'm using FreeBSD 8.1 and I'm seeing the following messages spit out ... "169.254.231.172" is not on the network ... I have two interfaces attached to the same LAN, ... There are two routing entries for 169.254.0.0/16, ...
    (freebsd-net)