From: Andreas Hartmann <andihartmann@01019freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange problem with vxlan!
Date: Sun, 5 Jan 2014 18:06:12 +0100 [thread overview]
Message-ID: <20140105180612.1234613e@dualc.maya.org> (raw)
In-Reply-To: <20140103152719.4a8db2ce@dualc.maya.org>
On Fri, 3 Jan 2014 15:27:19 +0100
Andreas Hartmann <andihartmann@01019freenet.de> wrote:
[...]
> Now the problem:
>
> If the VM (=AP) runs e.g. Linux 3.4.x, all is working fine as expected.
> If the VM runs 3.12.x or even 3.10.x, the tunnel works fine a few minutes after creation. Afterwards it is broken.
>
> Broken means:
> A "dhcpcd eth0" e.g. on the notebook times out, doesn't work any more. Traces show:
> The udp-tunnel-packages sent by the STA through vxlan0 can be seen on the host / tap0, but they can't be seen on vxlan0 (if it works, they can be seen on the vxlan0 device, too).
>
> On the host runs Linux 3.10.x, on the STA 3.11.6.
Some more findings:
- Problem can be seen with Linux 3.7 in the AP (VM), too.
- *Problem disappears* if the bridge device br0 on the host is set to
promiscuous mode.
- Sometimes, there can be seen the warning
"notebook dhcpcd[2784]: eth0: bad UDP checksum, ignoring"
when starting dhcpcd on the notebook with br0 / host set to promiscuous
mode (nevertheless dhcpcd worked fine). I never saw this warning
before.
Any idea how to fix the problem w/o running the bridge br0 on the host
in promiscuous mode?
Thanks for any hint,
Andreas
next prev parent reply other threads:[~2014-01-05 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 14:27 Andreas Hartmann
2014-01-05 17:06 ` Andreas Hartmann [this message]
2014-01-09 6:48 ` Andreas Hartmann
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=20140105180612.1234613e@dualc.maya.org \
--to=andihartmann@01019freenet.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®