[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OFDD155B0F.E457F85C-ON85257B3B.0065B415-85257B3B.00662700@us.ibm.com>
Date: Wed, 27 Mar 2013 14:35:51 -0400
From: David Stevens <dlstevens@...ibm.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Alexander Duyck <alexander.h.duyck@...el.com>,
David Miller <davem@...emloft.net>,
"Gasparakis, Joseph" <joseph.gasparakis@...el.com>,
netdev <netdev@...r.kernel.org>, netdev-owner@...r.kernel.org,
pshelar@...ira.com, Stephen Hemminger <shemminger@...tta.com>
Subject: Re: Is there a preferred way to get the VXLAN port number?
netdev-owner@...r.kernel.org wrote on 03/27/2013 01:52:54 PM:
> On Tue, 26 Mar 2013 15:02:45 -0700
> Alexander Duyck <alexander.h.duyck@...el.com> wrote:
>
> > I was wondering if someone would happen to know if there is already a
> > preferred way to get the VXLAN port number for things such as
> > configuring a device to recognize a VXLAN frame on receive for parsing
> > purposes?
> >
> > I just wanted to check to make sure I hadn't missed something before
> > submitting a patch that would export a simple function for supplying
the
> > vxlan_port value.
To answer your question, though, the current vxlan can only listen
on one port per host, supplied with by a module parameter. You can find
what port it's listening on by:
cat /sys/modules/vxlan/parameters/udp_port
[which you can also read with a program, of course].
If multi-port server support is added, that should probably include the
port as part of the current "ip -d link show dev XXX" output, where other
per-device parameters are found.
+-DLS
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists