All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] br-lan: received packet on bat0 with own address as source address
Date: Tue, 01 Apr 2014 14:09:16 +0200	[thread overview]
Message-ID: <533AAC6C.80302@meshcoding.com> (raw)
In-Reply-To: <1732522.mMifORosKp@vaio-gio>

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

On 01/04/14 12:35, Gioacchino Mazzurco wrote:
> On Tuesday 01 April 2014 11:33:01 Ilario GELMETTI wrote:
>> I tried changing the mac address
>> config interface 'lm_eth0_batadv'
>>         option ifname 'eth0.11'
>>         option proto 'batadv'
>>         option mesh 'bat0'
>>         option mtu '1496'
>>         option macaddr 'dc:9f:db:31:c1:38'
>> and that error in dmesg went away.
> 
> Why a packet form eth0.11 should arrive periodically to the bridge ?
> Someone can make some sense out of this ?
> 

I guess that the packet hits the bridge before being de-multiplexed by
the vlan code (or both the paths are followed till a certain point?).
We should dig into the bridge/vlan code to better understand what is
going on..

Cheers,

-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

      reply	other threads:[~2014-04-01 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 20:10 [B.A.T.M.A.N.] br-lan: received packet on bat0 with own address as source address Ilario Gelmetti
2014-04-01  9:33 ` Ilario GELMETTI
2014-04-01 10:35   ` Gioacchino Mazzurco
2014-04-01 12:09     ` Antonio Quartulli [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=533AAC6C.80302@meshcoding.com \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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.