This issue should have been fixed quite a while ago. I need to go through my past commits and see if everything has been merged back into the 8.1 branch.
--Qing > -----Original Message----- > From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd- > n...@freebsd.org] On Behalf Of Chris Miller > Sent: Tuesday, August 16, 2011 3:05 PM > To: 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, 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 mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
