All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: lartc@vger.kernel.org
Subject: bridging vlan tagged packet problems
Date: Sat, 23 Aug 2014 01:20:01 +0000	[thread overview]
Message-ID: <53F7EC41.6020308@conversis.de> (raw)

Hi,
I'm currently trying to set up a virtual machine that uses vlan
interfaces. The guests "physical" interface (eth0) is plugged into a
bridge on the host together with the physical interface (eth2) of the host.

The problem is that while I can send pings in the guest trough e.g.
eth0.10 all I see is ARP requests but no response.
Checking the pings target system I can see the ARP request arriving and
the response leaving with the correct Layer 2 address as the destination
(the MAC of the virtual machine).

However doing a tcpdump on the host on the physical interface eth2 only
shows the requests leaving but no responses arriving. I looks like the
host is filtering the incoming traffic.

Iptables is deactivated and the bridge knobs look like this:

[root@node1 ~]# for i in `ls -1 /proc/sys/net/bridge/*`; do echo -n "$i
= "; cat $i; done
/proc/sys/net/bridge/bridge-nf-call-arptables = 0
/proc/sys/net/bridge/bridge-nf-call-ip6tables = 0
/proc/sys/net/bridge/bridge-nf-call-iptables = 0
/proc/sys/net/bridge/bridge-nf-filter-pppoe-tagged = 0
/proc/sys/net/bridge/bridge-nf-filter-vlan-tagged = 0

Does anyone have an idea why the incoming traffic is blocked/not routed?

Regards,
  Dennis

                 reply	other threads:[~2014-08-23  1:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53F7EC41.6020308@conversis.de \
    --to=dennisml@conversis.de \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.