b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] DAT broken in 2014.4.0?
Date: Fri, 13 Mar 2015 12:52:13 +0100	[thread overview]
Message-ID: <5502CF6D.3030408@meshcoding.com> (raw)
In-Reply-To: <OFC7CC1C02.68EA7DC9-ONC1257E07.00275710-C1257E07.002916EB@phoenixcontact.com>

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

Hi Andreas,

so far we don't have any known DAT regression in 2014.4.0.

Could you please provide a more detailed description about your setup
including how the nodes have their bridges configured and what
interfaces have been added to batman-adv?

Thanks!

On 13/03/15 08:28, Andreas Pape wrote:
> Is there a known issue conerning the DAT functionality in batman-adv 
> 2014.4.0?
> 
> I have got a problem with looping ARP packets / multiplication of ARP 
> packets causing ARP storms in a setup with enabled DAT and BLA. My setup 
> consists of 6 mesh nodes of which 3 are connected to the same backbone 
> network. I connected a PC to the backbone which has an open ssh connection 
> to one ot the mesh nodes not connected to the backbone network directly. 
> Using arp -d to delete the ARP cache of the Windows PC forces the PC to 
> send an ARP request to the mesh node used for the ssh session. I can then 
> see multiple copies of that ARP request in the backbone in a wireshark 
> recording and also multiple ARP replies from the mesh node. 
> Sometimes also BLA gratuitous ARP telegrams seem to be looping, but it's 
> easier to force this behaviour with regular ARPs (via arp -d on a PC). 
> Non-ARP telegrams don't seem to be affected and except the waste of 
> bandwith in the mesh and backbone I don't have problems with normal 
> network communication in the mesh.
> 
> I could provide the mentioned wireshark recordings made in the backbone 
> network with a switch using port mirroring if someone explains how to 
> provide such a file to the mailing list (I guess simple attachments are 
> not allowed?).
> 
> If I disable DAT, everything looks fine again, i.e. no duplicated ARP 
> telegrams anymore (except for a few ARP replies from the mesh node which 
> are received twice, which could be a race for claiming the device?)..
> 
> Regards,
> Andreas
> 
> 
> ..................................................................
> PHOENIX CONTACT ELECTRONICS GmbH
> 
> Sitz der Gesellschaft / registered office of the company: 31812 Bad Pyrmont
> USt-Id-Nr.: DE811742156
> Amtsgericht Hannover HRB 100528 / district court Hannover HRB 100528
> Geschäftsführer / Executive Board: Roland Bent, Dr. Martin Heubeck
> ___________________________________________________________________
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren, jegliche anderweitige Verwendung sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> ----------------------------------------------------------------------------------------------------
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure, distribution or other use of the material or parts thereof is strictly forbidden.
> ___________________________________________________________________
> 

-- 
Antonio Quartulli


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

  reply	other threads:[~2015-03-13 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  7:28 [B.A.T.M.A.N.] DAT broken in 2014.4.0? Andreas Pape
2015-03-13 11:52 ` Antonio Quartulli [this message]
2015-03-13 14:35   ` Andreas Pape
2015-03-18 10:45     ` Andreas Pape
2015-03-19  6:10       ` Antonio Quartulli

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=5502CF6D.3030408@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 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).