From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
Weilong Chen <chenweilong@huawei.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
Netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] ixgbevf: fix 'Etherleak' in ixgbevf
Date: Thu, 22 Dec 2016 10:00:50 +0800 [thread overview]
Message-ID: <74e1e76d-40f6-db8e-74ac-90b0474d4e11@huawei.com> (raw)
In-Reply-To: <CAKgT0Uf+hV=TDvNTqFz0aiKQ+iio7VhBc5pusc4aDtFAVbREpA@mail.gmail.com>
On 2016/12/21 10:20, Alexander Duyck wrote:
> I find it curious that only the last 4 bytes have data in them. I'm
> wondering if the NIC/driver in the Windows/Nessus system is
> interpreting the 4 byte CRC on the end of the frame as padding instead
> of stripping it.
>
> Is there any chance you could capture the entire frame instead of just
> the padding? Maybe you could run something like wireshark without
> enabling promiscuous mode on the VF and capture the frames it is
> trying to send and receive. What I want to verify is what the actual
> amount of padding is that is needed to get to 60 bytes and where the
> CRC should start.
>
> - Alex
Here is the verbose output, is this useful?
Or we will try according to your advice, thanks,
D:\Program Files\Tenable\Nessus>nasl.exe -aX -t 192.169.0.151 etherleak.nasl
--------------------------
---[ ICMP ]---
0x00: 45 00 00 1D 20 81 00 00 40 01 D7 F3 C0 A9 00 97 E... ...@.......
0x10: C0 A9 00 82 00 00 87 FD 00 01 00 01 78 00 00 00 ............x...
0x20: 00 00 00 00 00 00 00 00 00 00 98 E4 75 DF ............u.
--------------------------
---[ ICMP ]---
0x00: 45 00 00 1D 20 85 00 00 40 01 D7 EF C0 A9 00 97 E... ...@.......
0x10: C0 A9 00 82 00 00 87 FD 00 01 00 01 78 00 00 00 ............x...
0x20: 00 00 00 00 00 00 00 00 00 00 FB DA F8 13 ..............
---[ ether1 ]---
0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 98 E4 75 ...............u
0x10: DF .
---[ ether2 ]---
0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 FB DA F8 ................
0x10: 13 .
Padding observed in one frame :
0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 98 E4 75 ...............u
0x10: DF .
Padding observed in another frame :
0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 FB DA F8 ................
0x10: 13
next prev parent reply other threads:[~2016-12-22 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 11:40 [PATCH net-next] ixgbevf: fix 'Etherleak' in ixgbevf Weilong Chen
2016-12-15 16:13 ` Alexander Duyck
2016-12-20 11:50 ` Weilong Chen
2016-12-20 16:36 ` Alexander Duyck
2016-12-21 1:40 ` Weilong Chen
2016-12-21 2:20 ` Alexander Duyck
2016-12-22 2:00 ` Kefeng Wang [this message]
2016-12-22 17:55 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74e1e76d-40f6-db8e-74ac-90b0474d4e11@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=alexander.duyck@gmail.com \
--cc=chenweilong@huawei.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox