All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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.] [PATCHv2] batman-adv: fix visualization output without neighbors on the primary interface
Date: Fri, 11 May 2012 04:19:56 +0800	[thread overview]
Message-ID: <201205110419.56441.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4FAC1B52.7050804@universe-factory.net>

On Friday, May 11, 2012 03:47:30 Matthias Schiffer wrote:
> 1st, implementations [1-3] aren't very configurable, and [4], an
> implementation by Intel, is hard to configure and *huge* (stripped
> binary ~400KB). Most of the implementations don't support announcing
> IPv6 addresses (I'm not sure which anymore), although that isn't really
> an important feature for me, as I'd use it mostly to announce hostnames
> for the MAC addresses, but I consider software that only supports IPv4
> as deprecated. Also, most of these projects seem to be dead for years.
> 
> 2nd, I think without batman-adv specific extensions LLDP isn't very
> useful, as the LLDP daemon only cares about the bat0/bridge MAC
> addresses, and not the hardif MAC addresses which are visible in the
> vis. The softif MAC addresses are shown in the vis as TT records, of
> course, but as one can't really discern between the adresses of the node
> itself and those of other clients on the bridge, it's rather useless in
> my opinion.

I understand all reason except for the last one. What are you trying to 
achieve that you need to auto-discover all batman-adv interfaces ? Are you 
trying to replace vis ? 
As far as I understood Martin was trying to point you to a protocol which 
broadcasts arbitrary data on layer2 (similar to mDNS on layer3).

Regards,
Marek

  reply	other threads:[~2012-05-10 20:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 15:05 [B.A.T.M.A.N.] [PATCH] batman-adv: fix visualization output without neighbors on the primary interface Matthias Schiffer
2012-05-05 15:29 ` Sven Eckelmann
2012-05-05 15:49   ` Matthias Schiffer
2012-05-05 15:51     ` [B.A.T.M.A.N.] [PATCHv2] " Matthias Schiffer
2012-05-06 20:14       ` Simon Wunderlich
2012-05-07  4:35         ` Matthias Schiffer
2012-05-07  6:40           ` Marek Lindner
2012-05-07 11:10             ` Matthias Schiffer
2012-05-07 11:28               ` Sven Eckelmann
2012-05-08  6:04               ` Marek Lindner
2012-05-08 12:51                 ` Matthias Schiffer
2012-05-08 20:52                   ` Guido Iribarren
2012-05-09 11:33                     ` Marek Lindner
2012-05-09 16:10                     ` Martin Hundebøll
2012-05-10 19:47                       ` Matthias Schiffer
2012-05-10 20:19                         ` Marek Lindner [this message]
2012-05-10 20:46                           ` Matthias Schiffer
2012-05-07  6:43           ` Sven Eckelmann
2012-05-07  6:43       ` Marek Lindner

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=201205110419.56441.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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.