netdev - RE: [Intel-wired-lan] i40e error handling LLDP messages from Arista switches

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Apr 2016 18:31:41 +0000
From:	"Parikh, Neerav" <neerav.parikh@...el.com>
To:	Jeremy Ashton <jeremy.ashton@...pify.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: RE: [Intel-wired-lan] i40e error handling LLDP messages from Arista
 switches



> -----Original Message-----
> From: Jeremy Ashton [mailto:jeremy.ashton@...pify.com]
> Sent: Tuesday, April 19, 2016 11:10 AM
> To: Parikh, Neerav <neerav.parikh@...el.com>
> Cc: netdev@...r.kernel.org; intel-wired-lan@...ts.osuosl.org
> Subject: Re: [Intel-wired-lan] i40e error handling LLDP messages from Arista
> switches
> 
> So, what commands exactly are you looking to have run?  Would packet
> capture of the lldp traffic help?
> 
LLDP is running in the i40e device firmware so unless you've a packet capture on
the wire (Xgig) you may not see that in the wireshark/tshark on the host system.

The debugfs commands I was referring to below can help capture some 
information; and for that you may need to mount the debugfs file system on 
your setup. If debugfs is supported then once you've that mounted and have the
i40e driver loaded then you may see an entry named "i40e" under the mount point.
Assuming debugfs is mounted on /sys/kernel/debug the i40e directory will be under
/sys/kernel/debug/i40e. This directory will have entry for each PCIe device being
managed by the i40e driver. You can select the PCIe device that maps to the device
in question and can run the commands like:
echo "dump port" > /sys/kernel/debug/i40e/<pci-path>/command
echo "lldp get local" > /sys/kernel/debug/i40e/<pci-path>/command
echo "lldp get remote" > /sys/kernel/debug/i40e/<pci-path>/command

The output of these commands will show up in the dmesg log.

One another I noticed in your thread on the PF_RING bz is that you're using inbox
Ubuntu driver. Have you tried with current upstream and seen this issue?

Thanks,
Neerav

> On Tue, Apr 19, 2016 at 1:53 PM, Parikh, Neerav <neerav.parikh@...el.com>
> wrote:
> > Resending as the original email was sent in HTLM format and hence my reply
> went in that format
> > as well; which got rejected by netdev mailer.
> >
> >> -----Original Message-----
> >> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@...ts.osuosl.org] On
> Behalf Of Parikh, Neerav
> >> Sent: Tuesday, April 19, 2016 10:45 AM
> >> To: Jeremy Ashton <jeremy.ashton@...pify.com>
> >> Cc: netdev@...r.kernel.org; intel-wired-lan@...ts.osuosl.org
> >> Subject: Re: [Intel-wired-lan] i40e error handling LLDP messages from Arista
> switches
> >>
> >> > From: Intel-wired-lan [mailto:intel-wired-lan-bounces@...ts.osuosl.org] On
> Behalf Of Jeremy Ashton
> >> > Sent: Tuesday, April 19, 2016 10:26 AM
> >> > Cc: netdev@...r.kernel.org; intel-wired-lan@...ts.osuosl.org
> >> > Subject: [Intel-wired-lan] i40e error handling LLDP messages from Arista
> switches
> >> >
> >> > I have been trying to get pf_ring with zc running on ubuntu 14.04.  The
> thread can be found here:
> >> >
> >> > https://github.com/ntop/PF_RING/issues/81
> >> >
> >> > Unfortunately it seems there is a bug in i40e which is carried into the code
> base for i40e_zc.
> >> >
> >> > $ modinfo i40e
> >> > filename:       /lib/modules/3.19.0-58-
> generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
> >> > version:        1.2.2-k
> >> > license:        GPL
> >> > description:    Intel(R) Ethernet Connection XL710 Network Driver
> >> > author:         Intel Corporation, <e1000-devel@...ts.sourceforge.net>
> >> > srcversion:     E3DEEE00F49BBFBB8FF33A7
> >> > alias:          pci:v00008086d00001586sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001585sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001584sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001583sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001581sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001580sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d0000157Fsv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001574sv*sd*bc*sc*i*
> >> > alias:          pci:v00008086d00001572sv*sd*bc*sc*i*
> >> > depends:        ptp,vxlan
> >> > intree:         Y
> >> > vermagic:       3.19.0-58-generic SMP mod_unload modversions
> >> > signer:         Magrathea: Glacier signing key
> >> > sig_key:
> DE:B3:43:0A:26:E6:7D:3D:3B:54:B9:DD:13:25:B3:3A:46:B2:F2:DD
> >> > sig_hashalgo:   sha512
> >> > part:           debug:Debug level (0=none,...,16=all) (int)
> >> >
> >> >
> >> > I wonder if someone might offer some insight as to the next steps to
> debug/resolve this.
> >> >
> >> > Cheers.
> >> >
> >> > Can you send us the dmesg output after running i40e debugfs commands
> >> > viz. “dump port”, “llpd get local” , “lldp get remote”, for the port that is
> showing
> >> > this behavior? Also, do you happen to know what is the Arista side
> configuration?
> >> > This will help us debug better.
> >> >
> >> > Thanks,
> >> > Neerav