Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

[Andre Oppermann]

Courtland,

the arpresolve observation is very important.  Do you have flowtable
enabled in your kernel?

-- 
Andre

On 06.03.2013 17:16, Adrian Chadd wrote:
> Another instance of it..
> Adrian
> On 6 March 2013 07:21, Courtland <ncrogers at gmail.com> wrote:
>> Has there been any progress on resolving this problem. Does anyone have a
>> better idea as to where it is breaking down?
>>
>> I am experiencing the same problem under FreeBSD 9.1-RELEASE. I use PF for
>> NAT, ALTQ, and RDR/filter rules. I'm not using PPPoE or dhclient. The
>> default gateway changes to an IP that is not on my network when under heavy
>> network load.
>>
>> The last time this happened I had a stream of arpresolve messages in the
>> kernel for the IP that the default route was changed to.
>> Mar  5 19:12:53  kernel: arpresolve: can't allocate llinfo for
>> 50.142.201.101
>> The default route was changed to 50.142.201.101 after these messages.
>>
>>
>>
>>
>> --
>> View this message in context: http://freebsd.1045724.n5.nabble.com/kernel-arpresolve-can-t-allocate-llinfo-for-65-59-233-102-tp5742320p5793139.html
>> Sent from the freebsd-net mailing list archive at Nabble.com.
>> _______________________________________________
>> 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"
> _______________________________________________
> 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"
>
>