netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Stevens <dlstevens@us.ibm.com>
Cc: 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: Wed, 15 May 2013 10:43:08 -0700	[thread overview]
Message-ID: <20130515104308.5de3e852@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <OFF100C7ED.6500FAB3-ON85257B6C.005DCF7C-85257B6C.005F309B@us.ibm.com>

On Wed, 15 May 2013 13:19:43 -0400
David Stevens <dlstevens@us.ibm.com> wrote:

> netdev-owner@vger.kernel.org wrote on 05/15/2013 12:53:22 PM:
> 
> > From: Stephen Hemminger <stephen@networkplumber.org>
>  
> > No. I want all users to get the IANA assigned port unless they 
> specifically
> > override it. For compatibility kernel can't change to the IANA value
> > but user space needs to nudge users in the correct direction.
> 
> It's more than a nudge -- it doesn't interoperate with itself.
> 
> 1) The kernel binds to 8472 on module load.
> 2) After it's bound, iproute2 "changes" the port to 4789, but
>         the kernel binding is still 8742 for listening. All destinations 
> use
>         the new port, but all bindings use the old port.
> 
> So, boot two systems without specifying a port and they can't
> talk to each other. They both listen on 8742 and they both send to
> 4789.
> 
> This clearly is worse than changing the kernel default port to 4789, but
> what's the point of having a kernel default if a user-level program 
> overrides
> it even when the user did not specify a port, and only for half of it (the
> sender side)?
> 
> You could make a port change close and rebind, but that's little different
> than changing the default in the kernel, if "ip" does it without a port
> specification. 
>                                                                 +-DLS
> 

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.

  reply	other threads:[~2013-05-15 17:43 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 [this message]
2013-05-15 18:11         ` David Stevens
2013-05-16  8:24           ` David Laight
2013-05-16 16:02             ` Stephen Hemminger
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=20130515104308.5de3e852@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --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).