From: "Nicolás Echániz" <nicoechaniz@codigosur.org>
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.] [OT] ruci / Was: link alternation when radios are not on batman-adv router?
Date: Sat, 31 Mar 2012 22:53:15 -0300 [thread overview]
Message-ID: <4F77B50B.6030402@codigosur.org> (raw)
In-Reply-To: <4F77AFDD.7050909@codigosur.org>
On 03/31/2012 10:31 PM, Nicolás Echániz wrote:
> This effectively "invisibilizes" some links for batman.
>
> You should use this with care, mainly if you are playing with it
> remotely because you may be left out of a portion of your network.
One more thing, not specific to batman, but useful for the kind of
experimentation you might be doing in the near future.
We (QuintanaLibre and DeltaLibre) have designed a tool for "fail-proof"
remote administration of OpenWRT nodes, which Guido (also participating
in this thread) has developed and maintains.
It's called ruci (for remote uci) and it has many useful features:
1) uses a centralized mercurial repository to store all your nodes
configuration.
2) can "pull" configurations from nodes at any time into the repo.
3) can push configuration changes to a node or set of nodes.
4) can compare configuration status between repo and nodes.
5) can always revert nodes or the whole network to any previous state
(provided by mercurial), as long as you keep a useful commit policy.
When new configuration is pushed, the remote router updates and reboots
(we found this to be safer than just restarting services). It then boots
with the new configuration and a 10min. revert timer, which triggers
unless you confirm the changes.
This simple method provides enormous experimentation possibilities. You
can, for example modify your entire network's IP addressing policy in
your local configs repo and then push the change simultaneously. If
something goes wrong, the routers will revert configuration and reboot
in 10 min.; if everythig went well, you can just confirm your changes
during the "revert window" to make them permanent.
You don't need to use uci locally, you may just edit config files by
hand and push them, but uci really comes in handy to avoid human error
when making changes or to implement some modifications programatically.
Guido might like to add some more detail, but that's a short description
of ruci[0].
Anyone who would like to test it, and might need some initial guidance
(mainly to set up things, the rest is self-explanatory), just drop guido
or me an e-mail and we will gladly help you out. There's no list or
forum yet...
Cheers,
NicoEchániz
[0] http://bitbucket.org/guidoi/ruci
next prev parent reply other threads:[~2012-04-01 1:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:35 [B.A.T.M.A.N.] link alternation when radios are not on batman-adv router? dan
2012-03-30 16:33 ` Guido Iribarren
2012-03-30 17:18 ` dan
2012-03-31 3:48 ` Guido Iribarren
2012-03-31 15:45 ` Dan Denson
2012-03-31 18:11 ` Guido Iribarren
2012-03-31 21:03 ` dan
2012-04-01 1:31 ` Nicolás Echániz
2012-04-01 1:53 ` Nicolás Echániz [this message]
2012-04-01 2:10 ` [B.A.T.M.A.N.] [OT] ruci / Was: " dan
2012-06-14 19:51 ` [B.A.T.M.A.N.] " gtolon
2012-06-15 9:55 ` Simon Wunderlich
2012-06-18 18:46 ` gtolon
2012-07-13 20:56 ` gtolon
2012-07-14 21:30 ` Guido Iribarren
2012-07-14 21:35 ` Guido Iribarren
2012-07-17 13:36 ` gtolon
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=4F77B50B.6030402@codigosur.org \
--to=nicoechaniz@codigosur.org \
--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