netdev - Re: DPAA Ethernet problems with mainstream Linux kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 18 Jan 2018 08:52:14 +0100
From:   Christian Zigotzky <chzigotzky@...osoft.de>
To:     Jamie Krueger <jamie@...bybitsoftwaregroup.com>
Cc:     Madalin-cristian Bucur <madalin.bucur@....com>,
        Darren Stevens <darren@...vens-zone.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: DPAA Ethernet problems with mainstream Linux kernels

Hi Jamie,

Many thanks for your effort. If you need a new kernel for testing please let me know.

Cheers,
Christian

Sent from my iPhone

> On 18. Jan 2018, at 02:59, Jamie Krueger <jamie@...bybitsoftwaregroup.com> wrote:
> 
> Hi Madalin,
> 
> On 01/16/2018 11:33 AM, Madalin-cristian Bucur wrote:
> 
> Here are some results from testing on the X5000/20 with 4.15.0-rc8
> (w/CONFIG_FSL_PAMU disabled):
> 
> In my tests I can now get the interface to obtain an IP Address via DHCP,
> at least *part* of the time that is.
> 
> Here is a link to a screenshot of a Wireshark capture which shows
> a successful DHCP request/response for the X5000/20, followed by some
> failed ping attempts.
> 
> (This traffic was captured on an external machine on the same subnet, and not from the X5000/20 itself)
> http://bitbybitsoftwaregroup.com/share/X5000-DHCP-Answered-Wireshark.png
> 
> Additionally, here is a link to the export of the packet data shown in the above image:
> http://bitbybitsoftwaregroup.com/share/Wireshark-X5000-DHCP-Success.html
> 
> As you can see by this example, even when the interface does obtain an IP address via
> DHCP (about half the time), subsequent traffic still fails to receive responses.
> 
> In this example, I attempt to ping the gateway (192.168.1.1), and one or two other
> local addresses, and nothing pings back (even when trying Skateman's suggestion
> of expanding the buffers for the interface -
> 
> "A workaround to keep the nic alive a bit longer.... is the following command
> ip link set eth0 qlen 10000"
> 
> For reference:
> 
> I have attached the Kernel config that the version I tested was built with.
> Also, I have attached the dmesg output I am currently seeing.
> 
> -- 
> Best Regards,
> 
> Jamie Krueger
> BITbyBIT Software Group LLC
> 
> <proc_config-4.15.0-rc8-NO_PAMU.txt>
> <fsl_dmesg_output.txt>