From: Stephen Hemminger <shemminger@vyatta.com>
To: "Qin, Xiaohong" <Xiaohong.Qin@emc.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: vxlan in Linux kernel 3.7
Date: Thu, 27 Dec 2012 10:49:16 -0800 [thread overview]
Message-ID: <20121227104916.4fb2af04@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <A3CA455BB4F1DA4E92CB43AAF0E4BB1D0667E12B@MX01A.corp.emc.com>
On Thu, 27 Dec 2012 13:42:51 -0500
"Qin, Xiaohong" <Xiaohong.Qin@emc.com> wrote:
> Hi All,
>
> I have installed kernel 3.7 on my Linux box, see the following uname -a output,
>
> uname -a
> Linux c210-m2-sib-3 3.7.0-030700-generic #201212102335 SMP Tue Dec 11 04:36:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> Does that mean I've got VXLAN module loaded or I still need to go through some extra steps to enable or configure it? Do you have any VXLAN setup or configuration document by chance?
>
> Thanks.
>
> Dennis Qin
>
> P.S. If this is not the right place to ask this kind of questions, please let me know which mailing list I should use.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
VXLAN driver is part of the kernel config.
If using a vendor supplied kernel, most likely it is available as a module.
Try:
/sbin/modinfo vxlan
If you see 'ERROR: Module vxlan not found' then vxlan was not configured.
You will also need to have current iproute2 utilities.
$ ip -V
ip utility, iproute2-ss121211
next prev parent reply other threads:[~2012-12-27 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 18:42 vxlan in Linux kernel 3.7 Qin, Xiaohong
2012-12-27 18:49 ` Stephen Hemminger [this message]
2012-12-27 18:56 ` Qin, Xiaohong
2012-12-27 19:43 ` Stephen Hemminger
2012-12-28 0:46 ` Naoto MATSUMOTO
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=20121227104916.4fb2af04@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=Xiaohong.Qin@emc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.