Hey folks,
Small update on the OOM issue. With LEDE devices that only have
32megs, if you run iperf3 on the device itself, eventually iperf3 will
use tons of memory in trying to use different sized buffers, that the
device will OOM and kill init. However, if you use packet forwarding
and put iperf
Hi again,
I've done some pretty in depth debugging now to determine exactly what
the behavior of ipv6_stub->ipv6_dst_lookup is. First I'll start with
ip_route_output_flow, which I believe to be well behaved, and then
I'll show ipv6_stub->ipv6_dst_lookup, which seems ill-behaved:
Userspace:
ip
On 11/12/16 8:40 AM, Jason A. Donenfeld wrote:
> Hi again,
>
> I've done some pretty in depth debugging now to determine exactly what
> the behavior of ipv6_stub->ipv6_dst_lookup is. First I'll start with
> ip_route_output_flow, which I believe to be well behaved, and then
> I'll show ipv6_stub->i
Hi David,
On Sat, Nov 12, 2016 at 7:14 PM, David Ahern wrote:
> I believe that is coming from __ip_route_output_key_hash(), line 2232 with
> __ip_dev_find not finding a device with that address.
It's possible we simply are looking at different source trees, but I
have the -EINVAL return in 4.8
On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld wrote:
>> Gotcha. I don't see any checks that the saddr is valid similar to what IPv4
>> does.
>>
>> I think the right place to add a check is in ip6_dst_lookup_tail():
>> if (!ipv6_addr_any(&fl6->saddr)) {
>> // saddr is valid for L
On Sun, Nov 13, 2016, at 01:43, Jason A. Donenfeld wrote:
> On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld
> wrote:
> >> Gotcha. I don't see any checks that the saddr is valid similar to what
> >> IPv4 does.
> >>
> >> I think the right place to add a check is in ip6_dst_lookup_tail():
> >>
On Sun, Nov 13, 2016 at 1:43 AM, Jason A. Donenfeld wrote:
> In perusing through the v6 FIB code, I don't even see an analog of
> __ip_dev_find... Hm?
Of all places, the iscsi code actually has a nice side-by-side
comparison. So far as I can see, the other protocols just omit this
check in the v6
Hi Hannes,
On Sun, Nov 13, 2016 at 1:51 AM, Hannes Frederic Sowa
wrote:
> You probably need some combination of ipv6_chk_addr and/or
> ipv6_check_addr_and_flags (where dev can also be NULL). Be careful if a
> IFA_HOST or IFA_LINK address switches from one interface to another.
I can confirm this