netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "David Laight" <David.Laight@ACULAB.COM>
Cc: "David Stevens" <dlstevens@us.ibm.com>,
	"Cong Wang" <amwang@redhat.com>, <netdev@vger.kernel.org>,
	<netdev-owner@vger.kernel.org>
Subject: Re: [Patch iproute2] vxlan: use 8472 as default dst port
Date: Thu, 16 May 2013 09:02:39 -0700	[thread overview]
Message-ID: <20130516090239.06067273@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B723D@saturn3.aculab.com>

On Thu, 16 May 2013 09:24:47 +0100
"David Laight" <David.Laight@ACULAB.COM> wrote:

> > > From: Stephen Hemminger <stephen@networkplumber.org>
> > >
> > > I want all new users to get the IANA port without asking.
> > > Old users with existing nets have to force the port to the one they
> > > were using.
> > 
> > That'd be great -- what we're getting is all new users are getting
> > a listen port of 8472 and a send port of 4789. So new users who aren't
> > aware of why will simply see that two *new* installations don't talk
> > to each other (and never will, using default ports, because the kernel
> > and ip will need to be compatible with their incompatible selves).
> 
> Could the kernel listen on both port numbers?
> Then the default 'send' port could be changed while maintaining
> functionality for existing systems.
> 
> At some later time the listener on 8372 could be removed.
> 
> 	David
> 
> 
> 

Actually with the destination port per vxlan it is possible to do.

1. Create vxlan0 with old port number
2. Create vxlan1 with new port number
3. Create a bridge vxlanbr0
4. Put both vxlan's into the bridge

Then the bridge will silently handle finding the correct port
and allow migrating other hosts to the new port number.

  reply	other threads:[~2013-05-16 16:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 11:11 [Patch iproute2] vxlan: use 8472 as default dst port Cong Wang
2013-05-15 11:32 ` David Stevens
2013-05-15 16:53   ` Stephen Hemminger
2013-05-15 17:19     ` David Stevens
2013-05-15 17:43       ` Stephen Hemminger
2013-05-15 18:11         ` David Stevens
2013-05-16  8:24           ` David Laight
2013-05-16 16:02             ` Stephen Hemminger [this message]
2013-05-15 20:23         ` David Miller
2013-05-15 17:48       ` Stephen Hemminger
2013-05-15 18:42         ` David Stevens
2013-05-15 21:37           ` [RFT] vxlan: listen on multiple ports Stephen Hemminger
2013-05-16  2:51             ` Cong Wang
2013-05-16  6:20               ` Stephen Hemminger
2013-05-15 20:22     ` [Patch iproute2] vxlan: use 8472 as default dst port David Miller
2013-05-15 20:25       ` Stephen Hemminger
2013-05-15 20:48       ` [PATCH] vxlan: force user to set port value Stephen Hemminger
2013-05-15 21:47         ` David Miller
2013-05-15 22:04           ` Stephen Hemminger
2013-05-15 22:40             ` David Miller
2013-05-15 22:19           ` Stephen Hemminger
2013-05-15 21:57         ` Sridhar Samudrala
2013-05-15 22:01           ` Stephen Hemminger

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=20130516090239.06067273@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=amwang@redhat.com \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev-owner@vger.kernel.org \
    --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 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).