From: Phil Yang <Phil.Yang@arm.com>
To: "Liu, Yong" <yong.liu@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>, nd <nd@arm.com>
Subject: [dts] How to disable the BOOTP and LLDP packets on tester ?
Date: Wed, 13 Jun 2018 10:12:37 +0000 [thread overview]
Message-ID: <AM4PR08MB091367A12845421488AEF39FE97E0@AM4PR08MB0913.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 464 bytes --]
Hi Marvin,
I captured groups of bootp and LLDP packets while running DTS on DUT PMD.
My environment:
Application: l2fwd
DUT NIC: 82599ES
Tester NIC: X710
Link:
Tester <------> DUT
X710 port A <-------> 82599ES port A
X710 port B <-------> 82599ES port B
Please check the attachment. Thanks.
How to disable the BOOTP and LLDP packets on tester ?
Ps: I didn't find lldpd service running on my tester.
Best Regards,
Phil Yang
[-- Attachment #1.2: Type: text/html, Size: 3229 bytes --]
[-- Attachment #2: capture_broadcast.log --]
[-- Type: application/octet-stream, Size: 5176 bytes --]
16:37:55.193237 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:01.362649 LLDP, length 59
16:38:06.146145 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:13.428062 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:38:13.460402 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:14.341085 IP6 :: > ff02::1:ff8d:37c7: ICMP6, neighbor solicitation, who has fe80::e34c:fa1b:6b8d:37c7, length 24
16:38:14.383063 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:38:15.343094 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:38:15.372317 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:38:16.093064 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:38:19.373296 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:38:19.720536 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:23.374555 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:38:26.304610 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:31.266639 LLDP, length 59
16:38:36.815344 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:48.459372 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:58.429950 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:38:58.462200 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:38:59.028977 IP6 :: > ff02::1:ff8d:37c7: ICMP6, neighbor solicitation, who has fe80::e34c:fa1b:6b8d:37c7, length 24
16:38:59.346956 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:00.032028 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:00.372540 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:39:00.425943 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:01.170632 LLDP, length 59
16:39:03.629032 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:04.373074 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:39:08.374367 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:39:17.535490 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:31.074631 LLDP, length 59
16:39:34.051616 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:43.427832 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:43.429825 IP6 :: > ff02::1:ff8d:37c7: ICMP6, neighbor solicitation, who has fe80::e34c:fa1b:6b8d:37c7, length 24
16:39:43.461165 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:43.469842 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:44.431033 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:44.432148 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:39:44.904870 IP6 fe80::e34c:fa1b:6b8d:37c7 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
16:39:46.447711 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:48.373841 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:39:51.136886 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:39:52.373337 IP6 fe80::e34c:fa1b:6b8d:37c7 > ip6-allrouters: ICMP6, router solicitation, length 8
16:40:00.978623 LLDP, length 59
16:40:04.799450 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:40:15.959479 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 3c:fd:fe:02:c2:80 (oui Unknown), length 300
16:40:30.882618 LLDP, length 59
16:41:00.786614 LLDP, length 59
16:41:30.690609 LLDP, length 59
16:42:00.594604 LLDP, length 59
16:42:30.498599 LLDP, length 59
16:43:00.402593 LLDP, length 59
16:43:30.306588 LLDP, length 59
16:44:00.210580 LLDP, length 59
16:44:30.114575 LLDP, length 59
next reply other threads:[~2018-06-13 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 10:12 Phil Yang [this message]
2018-06-14 2:37 ` Phil Yang
2018-06-15 9:03 ` Liu, Yong
2018-06-15 9:37 ` Phil Yang
2018-06-20 7:51 ` Liu, Yong
2018-06-20 10:04 ` Phil Yang
2018-06-20 14:19 ` Xu, Qian Q
2018-06-21 6:01 ` Phil Yang
2018-06-21 8:55 ` Xu, Qian Q
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=AM4PR08MB091367A12845421488AEF39FE97E0@AM4PR08MB0913.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=dts@dpdk.org \
--cc=nd@arm.com \
--cc=yong.liu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).