public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Ajith Adapa <adapa.ajith@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Regarding vxlan unicast configuration
Date: Tue, 17 May 2016 08:41:47 -0300	[thread overview]
Message-ID: <20160517114147.GB13977@localhost.localdomain> (raw)
In-Reply-To: <CADAe=++oAXEuxOrJ0xw5VAvkre98SQa71vur6SjkyuWB4jg8xQ@mail.gmail.com>

Hi,

On Mon, May 16, 2016 at 06:52:33PM -0700, Ajith Adapa wrote:
> Hi,
> 
> I am trying vxlan unicast configuration on a back to back connected
> interfaces of VM1 and VM2 running fedora 23 with 4.2 version of
> kernel. Below is my configuration
> 
> VM1
> 
> ip address add 100.1.1.1/24 dev enp0s8
> ifconfig enp0s8 up
> ip link add name vxlan42 type vxlan id 42 dev enp0s8 remote 50.1.1.2
> local 50.1.1.1 dstport 4789

Local and remote refers to the underlying interface actually, enp0s8 in
your case.

  Marcelo

> ip address add 50.1.1.1/24 dev vxlan42
> ip link set up vxlan42
> 
> VM2
> 
> ip address add 100.1.1.2/24 dev enp0s8
> ifconfig enp0s8 up
> ip link add name vxlan42 type vxlan id 42 dev enp0s8 remote 50.1.1.1
> local 50.1.1.2 dstport 4789
> ip address add 50.1.1.2/24 dev vxlan42
> ip link set up vxlan42
> 
> 
> Now when I try to ping 50.1.1.1 from VM2, I am receiving ARP packets
> on VM1 which are not vxlan tagged. As a result ping is not working.
> 
> I am able to successfully configure multicast based vxlan but having
> issues with vxlan unicast.
> 
> Is there something wrong with my configuration ?
> 
> Regards,
> Ajith
> 

      reply	other threads:[~2016-05-17 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  1:52 Regarding vxlan unicast configuration Ajith Adapa
2016-05-17 11:41 ` Marcelo Ricardo Leitner [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=20160517114147.GB13977@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=adapa.ajith@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox