DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Tetsuro Nakamura <xyz1.8tn@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [pktgen] A sequence command doen't work
Date: Tue, 1 Aug 2017 13:59:43 +0000	[thread overview]
Message-ID: <7DF0CC99-1CF8-405A-BE5B-7F8CC5EE03EA@intel.com> (raw)
In-Reply-To: <CADr1gdRepTnxwWAbu57Gzd8TEdCXD=vB=i+m9GCLqomCV0wQQg@mail.gmail.com>


> On Aug 1, 2017, at 2:04 AM, Tetsuro Nakamura <xyz1.8tn@gmail.com> wrote:
> 
> Hi Keith,
> 
> I had to comment out the lines below to compile pktgen3.3.5,
> but now the sequence commands work on pktgen3.3.5.
> 
> /*
> #ifndef RTE_DEVTYPE_BLACKLISTED_PCI
> #define RTE_DEVTYPE_BLACKLISTED_PCI RTE_DEVTYPE_BLACKLISTED
> #endif
> 
> #ifndef RTE_DEVTYPE_WHITELISTED_PCI
> #define RTE_DEVTYPE_WHITELISTED_PCI RTE_DEVTYPE_WHITELISTED
> #endif
> /  
> 

Please upgrade to the latest version 3.3.8 to have this fix.

> Thank you very much for your help.
> 
> 2017-07-23 2:12 GMT+09:00 Wiles, Keith <keith.wiles@intel.com>:
> 
> > On Jul 20, 2017, at 8:28 PM, Tetsuro Nakamura <xyz1.8tn@gmail.com> wrote:
> >
> > Hi all,
> >
> >
> > I moved from using pktgen3.0.13 to pktgen3.3.4
> >
> > But sequence commands dont work as well on pktgen3.3.4.
> 
> 
> I found the problem and push a new version pktgen-3.3.5 please give that one a try.
> 
> >
> >
> > ```````
> >
> > Pktgen:/>  set 0 seq_cnt 2
> >
> > # It works
> >
> >
> > Pktgen:/> sequence 0 0 0c:c4:7a:cf:66:11 0c:c4:7a:cf:66:01 192.168.1.1
> > 192.168.0.1/24 1234 5678 ipv4 udp 1 64
> > Sequence invalid command:
> >  Invalid line: <sequence 0 0 0c:c4:7a:cf:66:11 0c:c4:7a:cf:66:01
> > 192.168.1.1 192.168.0.1/24 1234 5678 ipv4 udp 1 64 >
> >
> > # doen't work though the command works on pktgen3.0.13
> >
> >
> > Pktgen:/> sequence 0 0 0c:c4:7a:cf:66:11 0c:c4:7a:cf:66:01 192.168.1.1
> > 192.168.0.1 1234 5678 ipv4 udp 1 64
> > Sequence invalid command:
> >  Invalid line: <sequence 0 0 0c:c4:7a:cf:66:11 0c:c4:7a:cf:66:01
> > 192.168.1.1 192.168.0.1 1234 5678 ipv4 udp 1 64 >
> >
> > # without networkmask specification doen't work as well
> >
> > ```````
> >
> > page seq works but shows the same sequences.
> > ```
> >
> > Port:  0, Sequence Count:  2 of 16
> >                                        GTPu
> >  Seq:            Dst MAC           Src MAC          Dst IP
> > Src IP    Port S/D Protocol:VLAN  Size  TEID
> > *   0:  00:00:00:00:00:00 0c:c4:7a:cf:66:c4     192.168.1.1
> > 192.168.0.1/24   1234/5678 IPv4/TCP:0001   64     0
> > *   1:  00:00:00:00:00:00 0c:c4:7a:cf:66:c4     192.168.1.1
> > 192.168.0.1/24   1234/5678 IPv4/TCP:0001   64     0
> >
> > ```
> >
> > Is this a known problem?
> > Are there any way to work around?
> >
> > Thanks in advance.
> > Tetsuro Nakamura
> 
> Regards,
> Keith
> 
> 

Regards,
Keith

      reply	other threads:[~2017-08-01 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  1:28 Tetsuro Nakamura
2017-07-22 17:12 ` Wiles, Keith
2017-08-01  7:04   ` Tetsuro Nakamura
2017-08-01 13:59     ` Wiles, Keith [this message]

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=7DF0CC99-1CF8-405A-BE5B-7F8CC5EE03EA@intel.com \
    --to=keith.wiles@intel.com \
    --cc=users@dpdk.org \
    --cc=xyz1.8tn@gmail.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).