From: Andriy Berestovskyy <aber@semihalf.com>
To: sml <sml.caerus@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Configuring MAC Address of KNI - Don't want random
Date: Mon, 11 Apr 2016 11:01:47 +0200 [thread overview]
Message-ID: <CAOysbxr4EgteH_kvHLYn9uhnLVWdYw2zq-fj2_J4OA_tW8p=JQ@mail.gmail.com> (raw)
In-Reply-To: <CAHXxcudp7E+r_FWYZK3rhn6uCQXP6S3=LkWPvwV1oazOquC_xg@mail.gmail.com>
Hi sml,
The KNI uses old ixgbe and igb Linux drivers in order to support
ethtool. Here is the list of supported e1000 devices:
http://dpdk.org/browse/dpdk/tree/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_hw.h#n37
The list is somewhat shorter than the list of supported devices in
DPDK itself. So there are some devices which work well in DPDK, but
KNI generates random MACs for them.
The DPDK community decided to get rid of the KNI, so your only option
is to set the MAC on vEth using ip(8) or ifconfig(8). You can also add
an option into the /etc/network/interfaces (or similar), so the MAC
will be configured once your vEth device is up.
Andriy
On Sat, Apr 9, 2016 at 7:41 AM, sml <sml.caerus@gmail.com> wrote:
> Hello,
>
> I am having an issue where when creating the KNI interface I would like to
> KEEP the hardware MAC address. I can properly create the interface. It
> starts in a down state, I then need to manually ifconfig the IP Address and
> MAC address with UP to get what I need. If I just do the plain ifconfig -v
> vEth0_0 up - it assigns a random mac address. (Using a e1000 as well I350
> and emulated e1000)
>
> This also happens if you DOWN the interface and bring it UP using ifconfig
> again. Using Version 2.2.0
>
> What is the proper procedure/flow for doing this within the codebase so I
> can have the end result of the original hardware MAC and the interface in
> an UP state?
>
> Sorry if this seems basic I just can't seem to find any examples of how
> this is done.
--
Andriy Berestovskyy
next prev parent reply other threads:[~2016-04-11 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 5:41 sml
2016-04-11 9:01 ` Andriy Berestovskyy [this message]
2016-04-11 16:50 ` Jason Kwon
2016-04-12 11:46 ` Andriy Berestovskyy
2016-04-12 15:40 ` Jay Rolette
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='CAOysbxr4EgteH_kvHLYn9uhnLVWdYw2zq-fj2_J4OA_tW8p=JQ@mail.gmail.com' \
--to=aber@semihalf.com \
--cc=sml.caerus@gmail.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).