Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Mar 2013 18:09:28 +0100
From:      Andre Oppermann <andre@freebsd.org>
To:        Nick Rogers <ncrogers@gmail.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)
Message-ID:  <5138C9C8.6030809@freebsd.org>
In-Reply-To: <CAKOb=YYPzSfUmcmmvE0fy-2QhzUK5hZUVUEdJs3uho2a6iGz%2Bg@mail.gmail.com>
References:  <CAJ-VmokO85PaW6DksfqsBuSdMPUEGv9f_2qEMAD7WTv4QK0vcw@mail.gmail.com> <51378A9D.6080306@freebsd.org> <CAKOb=YYPzSfUmcmmvE0fy-2QhzUK5hZUVUEdJs3uho2a6iGz%2Bg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 07.03.2013 17:54, Nick Rogers wrote:
> I'm not sure. I have not explicitly enabled/disabled it. I am using
> the GENERIC kernel from 9.1 plus PF+ALTQ.
>
> # sysctl net.inet.flowtable.enable
> sysctl: unknown oid 'net.inet.flowtable.enable'
> # sysctl -a | grep flow
> kern.sigqueue.overflow: 0
> net.inet.tcp.reass.overflows: 0
> net.inet6.ip6.auto_flowlabel: 1
>
> uname -v
> FreeBSD 9.1-RELEASE #0 r245436M: Mon Jan 14 16:34:21 EST 2013
> root@fbsd_91:/usr/obj/usr/src/sys/CUSTOM
>
> 8.0 release notes say flowtable is enabled by default on amd64/i386.
> So I presume it is enabled? I can't seem to find much information
> about this for FreeBSD 9.x

It's not compiled in GENERIC on 9.x because it had/has some stability
issues.  I just wanted to make sure that the problem really come out
of the arpresolve area before digging into it.

-- 
Andre

> On Wed, Mar 6, 2013 at 10:27 AM, Andre Oppermann <andre@freebsd.org> wrote:
>> 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@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@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>>>
>>> _______________________________________________
>>> 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"
>>>
>>>
>>
>
>




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