DPDK usage discussions
 help / color / mirror / Atom feed
From: Marko Niinimaki <manzikki@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Pktgen question: range of source IP addresses
Date: Wed, 20 Apr 2016 14:58:01 +0700	[thread overview]
Message-ID: <CAMfE_jf8wcBbiBT42gwR+iSLt1M=6zv5JZxXgyJfdsJngUn+vQ@mail.gmail.com> (raw)
In-Reply-To: <ED0FD7C3-0BA9-4CFF-B930-583A80DC5961@intel.com>

many thanks! Now I can impress my boss without just by entering the
commands below

src.ip min 0 192.168.2.1
src.ip start 0 192.168.2.1
src.ip max 0 192.168.2.254
src.ip inc 0.0.0.1
range 0 on
start 0


On Wed, Apr 20, 2016 at 11:42 AM, Wiles, Keith <keith.wiles@intel.com>
wrote:

> >Hi,
> >
> >I'm using pktgen to create DNS query packets for internal testing (I
> >tweaked the source code a bit). It's certainly fast enough, but I'd need
> >some more functionality to build a more comprehensible DNS testing suite.
> >First I'd need a range of IP addresses, for instance the first DNS query
> >would come from 1.1.1.1, the next from 1.1.1.2 etc. As far as I know, port
> >X's IP is assigned only once (for instance set ip src 0 1.1.1.1/24). Is
> >there a clever way to change this? If you consider this a useful feature,
> >I'll submit the code of course.
>
> Pktgen does have the range command ‘page range’ which allows setting up
> the addresses to be changed on the fly have you looked at that option?
>
> I accept just about any improvement to Pktgen, just send a patch :-)
>
> >
> >Best regards,
> >Mark
> >
>
>
> Regards,
> Keith
>
>
>
>
>

      reply	other threads:[~2016-04-20  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  2:36 Marko Niinimaki
2016-04-20  4:42 ` Wiles, Keith
2016-04-20  7:58   ` Marko Niinimaki [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='CAMfE_jf8wcBbiBT42gwR+iSLt1M=6zv5JZxXgyJfdsJngUn+vQ@mail.gmail.com' \
    --to=manzikki@gmail.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).