All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Andrés Pozo Muñoz" <andres.pozom@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Problem with syslog in bridge(?) with ethernet broadcast packets with QinQ
Date: Thu, 12 Oct 2017 07:58:34 -0700	[thread overview]
Message-ID: <20171012075834.78103e4d@xeon-e3> (raw)
In-Reply-To: <CAPfKRs4GmA4568nt4a2kaHkmm3WmMETL1sXcT8xyByCvVGgFkQ@mail.gmail.com>

On Mon, 18 Sep 2017 17:21:11 +0200
Andrés Pozo Muñoz <andres.pozom@gmail.com> wrote:

> Hi all,
> 
> I'm facing some problem with ethernet multicast traffic and QinQ
> (802.3q in both tags) in -apparently- a bridge in Ubuntu 16.04
> (4.12.0-041200-generic).
> 
> My set up is the following:
> +-----------+
> |     VM    |
> +-----+-----+
>       |
>       | tag 55
> +---------+------------+
> |        OVS           |
> +-----------+----------+
>                 | veth3.9
> veth3   +  |
>      +--+
>      | veth2
> +-------+----------+
> |       BRIDGE     |
> +-------+----------+
>      |
>      |
> +-------+----------+
> |      ens11f1     |
> +------------------+
> 
> 
> I am setting the inner tag with OVS and the outer tag with a vlan type veth.
> The problem I have is that every packet sent from the VM to Ethernet
> broadcast addresses (33:33:xx:xx:xx:xx) generates a "IPv6 header not
> found" entry in syslog.
> 
> If I generate a 'ens11f1.9' interface and remove the BRIDGE, the log
> entry dissapears.
> 
> Some questions:
> * Is there any problem with these packets (ethernet multicast with
> QinQ) in bridges?
> * Is there any configuration I should change for the problem to dissapear?
> 
> Thanks in advance for your help! Any hint about what could be
> generating those logs is appreciated.
> 
> Regards,
> Andrés Pozo

Where is the log message coming from? Could you change the printk into
a WARN_ON_ONCE and get backtrace? My guess is the firewall code doesn't
understand the additional tag.

  reply	other threads:[~2017-10-12 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 15:21 [Bridge] Problem with syslog in bridge(?) with ethernet broadcast packets with QinQ Andrés Pozo Muñoz
2017-10-12 14:58 ` Stephen Hemminger [this message]
2017-10-16 10:39   ` Andrés Pozo Muñoz

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=20171012075834.78103e4d@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=andres.pozom@gmail.com \
    --cc=bridge@lists.linux-foundation.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.