From: David Miller <davem@davemloft.net>
To: zealot0630@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] reset nf before xmit vxlan encapsulated packet
Date: Tue, 05 Mar 2013 23:56:33 -0500 (EST) [thread overview]
Message-ID: <20130305.235633.2031561829817668254.davem@davemloft.net> (raw)
In-Reply-To: <1362413254-10520-1-git-send-email-zealot0630@gmail.com>
From: Zang MingJie <zealot0630@gmail.com>
Date: Tue, 5 Mar 2013 00:07:34 +0800
>
> We should reset nf settings bond to the skb as ipip/ipgre do.
>
> If not, the conntrack/nat info bond to the origin packet may continually
> redirect the packet to vxlan interface causing a routing loop.
>
> this is the scenario:
>
> VETP VXLAN Gateway
> /----\ /---------------\
> | | | |
> | vx+--+vx --NAT-> eth0+--> Internet
> | | | |
> \----/ \---------------/
>
> when there are any packet coming from internet to the vetp, there will be lots
> of garbage packets coming out the gateway's vxlan interface, but none actually
> sent to the physical interface, because they are redirected back to the vxlan
> interface in the postrouting chain of NAT rule, and dmesg complains:
>
> Mar 1 21:52:53 debian kernel: [ 8802.997699] Dead loop on virtual device vxlan0, fix it urgently!
> Mar 1 21:52:54 debian kernel: [ 8804.004907] Dead loop on virtual device vxlan0, fix it urgently!
> Mar 1 21:52:55 debian kernel: [ 8805.012189] Dead loop on virtual device vxlan0, fix it urgently!
> Mar 1 21:52:56 debian kernel: [ 8806.020593] Dead loop on virtual device vxlan0, fix it urgently!
>
> the patch should fix the problem
>
> Signed-off-by: Zang MingJie <zealot0630@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2013-03-06 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 16:07 [PATCH 1/1] reset nf before xmit vxlan encapsulated packet Zang MingJie
2013-03-06 4:56 ` David Miller [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=20130305.235633.2031561829817668254.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=zealot0630@gmail.com \
/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).