All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
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.] Security & node authentication in BATMAN network
Date: Mon, 26 Apr 2010 07:14:34 +0200	[thread overview]
Message-ID: <20100426051434.GB3734@lunn.ch> (raw)
In-Reply-To: <201004260124.22098.adebex@gmail.com>

> However, I'm still concerned about issue of using fake nodes
> claiming they are someone else (e.g. sending fake OGMs) for sole
> reason of destroying the mesh.  Do you think this is important
> issue? Can it be somehow reduced?

There are much simpler ways of destroying the mesh, at last
locally. e.g, my wife has a cordless telephone which operates in the
2.4GHz band. Pick up the line and wireless in the area dies. That
phone quickly got replaced with a DECT phone operating in the USA DECT
band, 1.9GHz.

2.4GHz is in the so called ISM band, industrial, scientific and
medical. Bluetooth, WiFi, microwave ovens, ZigBee, sometimes radio car
keys all work in this band, and all potentially interfere with each
other. You are working in a medical environment, so you may find that
down by radiography, you can forget WiFi all together?

You really need to tell us your use cases. Do you need a network which
has 99.999% uptime? Then dig up the road and lay fibre. Can you live
with a best effort network, which will probably die every so often,
can easily to DOSed, and performance will probably very depending on
day/night, weekday/weekend and the phase of the moon?

	   Andrew


  reply	other threads:[~2010-04-26  5:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25 19:36 [B.A.T.M.A.N.] Security & node authentication in BATMAN network Adrian Byszuk
2010-04-25 19:53 ` Andrew Lunn
2010-04-25 20:08 ` Sven Eckelmann
2010-04-25 20:13 ` Daniel Golle
2010-04-25 21:14   ` Marek Lindner
2010-04-25 23:24   ` Adrian Byszuk
2010-04-26  5:14     ` Andrew Lunn [this message]
2010-04-25 21:07 ` Marek Lindner
2010-04-25 22:01 ` Simon Wunderlich

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=20100426051434.GB3734@lunn.ch \
    --to=andrew@lunn.ch \
    --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.