From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next] documentation: bring vxlan documentation more up-to-date
Date: Tue, 11 Aug 2015 15:18:54 -0700 [thread overview]
Message-ID: <55CA74CE.3000704@hp.com> (raw)
In-Reply-To: <20150811150957.78de9c33@urahara>
On 08/11/2015 03:09 PM, Stephen Hemminger wrote:
> On Tue, 11 Aug 2015 13:47:16 -0700 (PDT)
> raj@tardy.usa.hp.com (Rick Jones) wrote:
>
>> + # ip link add vxlan0 type vxlan id 42 group 239.1.1.1 dev eth1
>> +
>> +This creates a new device named vxlan0. The device uses the
>> +multicast group 239.1.1.1 over eth1 to handle traffic for which there
>> +is no entry is in the forwarding table. The Linux implementation of
>> +VXLAN pre-dates the IANA's selection of a standard destination port
>> +number and uses the Linux-selected value by default to maintain
>> +backwards compatibility. If you wish to use the IANA-assigned
>> +destination port number of 4789 you can add "dstport 4789" to the
>> +command line above.
>
> This example should be changed to use "dstport 4789".
> Almost anyone reading the documentation will want to use the IANA value.
I'll spin a v2.
> Note: ip command will give a noisy warning if dstport is not set.
Indeed. It was that noisy warning which sent me down this path in the
first place :)
rick jones
prev parent reply other threads:[~2015-08-11 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 20:47 [PATCH net-next] documentation: bring vxlan documentation more up-to-date Rick Jones
2015-08-11 22:09 ` Stephen Hemminger
2015-08-11 22:18 ` Rick Jones [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=55CA74CE.3000704@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).