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@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] dynamic gateway / hna / services
Date: Sat, 4 Aug 2007 12:34:46 +0200 [thread overview]
Message-ID: <200708041234.46321.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20070803113132.f7ij8uf21xwsog8o@webmail.ddmesh.de>
Hi,
> > I also like the idea of dynamically changing some parameters but on
> > the other hand, what are the negative side-effects of restarting a
> > daemon ? - A client connected to the daemon might temporary loose
> > connection
> > - Do you know others?
>
> I think the first point is important enough. see the statement above.
at the moment we have more important issues to address than a broken debug
client connection I think. But we happily accept patches if ou want to
improve the current situation.
Note: This problem is more complicated than it might seem. You will have to
pay attention to various race conditions.
> I have looked through the code and have seen that the HNA is simply
> appended to
> the end of a message. if we want to send other information a TLV structure
> is needed (Tag-length-value). Batmand can ignore unknown Tags and is
> still working in the network. At moment the whole network needs an
> update at same time, because old batmand will interpret any data as HNA.
> I hope I'm not wrong :)
You are right. But why should we append random data to flood the network ? Why
can't we use _existing_ and _working_ solutions for service discovery ?
Did you read the discussion regarding this topic which was started by you ?
Regards,
Marek
next prev parent reply other threads:[~2007-08-04 10:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 9:31 [B.A.T.M.A.N.] dynamic gateway / hna / services Freifunk Dresden
2007-08-04 9:43 ` Axel Neumann
2007-08-04 21:38 ` Freifunk Dresden
2007-08-20 13:10 ` Alexander Morlang
2007-08-04 10:34 ` Marek Lindner [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-24 13:21 Freifunk Dresden
2007-07-24 18:35 ` Daniel Poelzleithner
2007-07-25 11:50 ` Alexander Morlang
2007-07-25 12:52 ` tetzlav
2007-07-25 15:06 ` Alexander Morlang
2007-07-25 15:19 ` Daniel Poelzleithner
2007-07-25 16:05 ` Alexander Morlang
2007-07-25 17:25 ` Daniel Poelzleithner
2007-07-26 12:33 ` Alexander Morlang
2007-07-25 16:21 ` clauz
2007-07-25 15:05 ` Daniel Poelzleithner
2007-07-25 14:56 ` Marek Lindner
2007-07-27 14:07 ` Marek Lindner
2007-07-27 14:43 ` Aaron Kaplan
2007-07-27 15:23 ` Marek Lindner
2007-07-27 16:03 ` Aaron Kaplan
2007-07-27 16:40 ` Marek Lindner
2007-07-27 20:41 ` Aaron Kaplan
2007-07-28 8:03 ` Axel Neumann
2007-07-27 14:59 ` Lui
2007-07-27 15:31 ` Marek Lindner
2007-08-02 14:26 ` Axel Neumann
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=200708041234.46321.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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.