Hey so is anyone planning on being at sudo this Sunday? There are probably
some things we can do, though it will depend a bit on whether Will will be
thre or not.
I went to the ham store, but they definitely didn't have any affordable
mounts that fit our purposes. That being said, I actually think it'd be
pretty trivial to make a mount ourselves with a bit of angle iron and a few
bolts. I don't imagine we'll have the time this Sunday to do that, but if
anyone were to be excited about it, some group could go in that direction.
There is plenty of cabling and setting up routers to do, though. Who's
coming with me....?
any ideas what this is about?
On Thursday, May 7, 2015, Gratipay Support <support(a)gratipay.com> wrote:
> [image: Gratipay]
> We have an unfortunate announcement to make: after 152 weeks of
> continuous operation, we are for the first time today skipping Gratipay's
> weekly payment cycle
> <https://medium.com/gratipay-blog/gratipocalypse-42fd0ec0d9e8>. We are
> deeply sorry. :-(
> Something not right? Reply to this email for help.
> Sent by Gratipay, LLC <https://gratipay.com/> | 716 Park Road, Ambridge,
> PA, 15003, USA
>
Hi all,
i have a 90-foot antenna tower in my driveway for sudomesh. It's a telescoping
tower like this:
http://alumatower.com/towers-telescoping-mast-systems/telescopic-antenna-to…
but it's NOT aluminum, it's old-fashioned steel. It has one place it needs
welding, but my neighbor offered to fix that. it extends to 90 feet total
(which means you need the guy wires in a 108' diameter circle if you extend it
to the full 90' height, according to the 60% rule)
anyway, i paid $100 for it and Marc paid $45 in gasoline to get it, and i'm
willing to sell it to sudomesh at ZZZERO PROFIT, but it has to move somewhere
else. I may be able to help move it (although i would have to borrow
neighbors' truck)
collapsed down, it's about 23' long and weighs like 250 lbs i think.
if sudomesh is not interested i'm going to put it on craigslist.
thank you!
-jake
Thanks Yar!
So I have some ideas about Sunday, but I haven't really decided on anything
yet. Here they are in more or less random order:
- Meet at Sudoroom, I show whoever is there how to flash our newest
firmware, run makenode and create a mesh node. Depending on time and how
many folks show up, we could also set up extender access points or extender
node->node radios and perhaps set up a 5ghz extender node link in the omni.
I would probably trust these folks to take those mesh nodes home with them
as I think the new rule is starting to shape up as: "if you can flash and
configure a node yourself, you can take it home and be part of the alpha
release".
- We try to get on the roof of the omni and build a connection to Will's
house. I don't really know much about the roof status, so I'd be hesitant
to go this direction unless someone else was there who was comfortable with
the roof situation. This would also require us to have the proper mounting
materials and figure out the correct mounting technique and locations for
the roof. We DO have a nanostation m5 which would be a good match for
Will's nanobridge and we could also set up a nanostation m2 which would be
an access point broadcasting internet signal to the neighborhood.
- Folks come to my house and help me set up an extender node. I have a
mynet setup in my house and nanostation m2 which I'd like to broadcast to
the neighborhood, but the mounting situation is a tiny bit tricky. Ideally
we'd have a ladder as well as some sort of materials/techniques for
following my comcast cable line back through the wall out of the house and
to the roof (so probably just those wall brackets as well as whatever it
takes to get through the wall). If we were feeling particularly ambitious,
we could set up an extender node which would face south and *perhaps* be
able to see Alex.
Just some thoughts. If no one else shows I'll probably just be hacking on
some firmware tweaks and/or setting up a mesh service at my house. Also -
send an email to the list if you want to show up. I likely won't be at
sudoroom unless I know that someone else will be there as well.
On Thu, May 14, 2015 at 8:01 PM, yar <yardenack(a)gmail.com> wrote:
> This message got sent during server migration and lost in limbo. Here it
> is.
>
> ---------- Forwarded message ----------
> From: Will Martin <will(a)willmartin.com>
> Date: Thu, May 14, 2015 at 4:17 PM
> Subject: Sunday Node Mounting
> To: "mesh(a)lists.sudoroom.org" <mesh(a)lists.sudoroom.org>
>
>
> I'm free this sunday and would love to help mount some nodes.
>
> My Nanobridge NB-5G25 dish is up-and-running and facing the Omni - I'd
> like to get it set up as a backbone so I can begin adding 2.4ghz nodes
> in my neighborhood.
> Do we have any 5G dishes on top of the Omni yet?
>
> Will Martin
> _______________________________________________
> mesh mailing list
> mesh(a)lists.sudoroom.org
> https://sudoroom.org/lists/listinfo/mesh
>
On Thu, May 14, 2015 at 4:02 PM, yar <yardenack(a)gmail.com> wrote:
> Please don't do anything important until the DNS finishes propagating.
> Avoid any important mailing list messages, wiki edits, blog posts,
> etc. I will send an update when we're done. Thanks!
Ok, all should be well now. If you have any trouble please email
sudo-sys(a)lists.sudoroom.org. Thanks!
Just wanted to ask if people are up for a quick round of testing Serval
after this Tuesday's meeting.
If you're up for it, make sure to bring your rooted android device for the
meeting and pre-install Serval if you have time!
Then we can spread out and see how far Serval reaches and decide whether
it's really worth it.
Oh, and if you didn't already see it, there's a $9 open hardware wifi linux
board coming out that's made by a small company a few blocks from where I
live(!):
https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-com…
I tweeted at them to ask what the wifi chip is but no reply so far. I can
make out a RealTek logo though. We should invite them over for BBQ or
something. They have the Shenzhen hookups.
If the power requirements are low enough and the wifi chip isn't too sucky
(also allwinner chips don't have a great rep) then this could be
interesting since it'd be capable of doing what a garden sensor node does,
but also run babel and web apps. The USB stack is sure to suck though and
no Ethernet + shitty on-board wifi antenna so this will never be a viable
home or extender node.
--- begin: Some thoughts on Serval
I don't feel like the wifi meshing part of Serval is likely to be useful
(but maybe I'm wrong). Mostly because it doesn't actually work unless you
have a rooted and compatible device, which probably excludes the vast
majority of folk. Then there's the limited range of smartphone wifi and the
extra battery usage for relaying.
I'm not sure I fully understand Serval's Mesh Datagram Protocol nor their
mesh routing protocol, but if my mental model is correct then MDP provides
security and some of the functionality of IP (addressing) and they don't
have a mesh routing protocol but resort to ad-hoc wifi broadcast (
http://developer.servalproject.org/dokuwiki/doku.php?id=content:tech:mesh_r…
) though they plan to implement their own protocol that relies on MDP.
They're basically re-implementing not just mesh routing but also IP and
UDP/TCP. Sounds ludicrously ambitious for such a small team if you ask me.
The voice calling sounds nice. They basically implemented a minimal voice
protocol from scratch that is optimized for mobile meshing (though without
mesh routing I'm not sure how useful it is and it relies on MDP for
security). The mapping sounds cool, but not yet included in a stable
release. The Rhizome/MeshMS system seems useful, (it looks like the same
kind of protocol as scuttlebutt, not sure what the protocol is nor how
encryption works). Bluetooth as an alternate transport is really great, but
is not included in any stable version yet.
The GUI is almost non-existant, and parts of it seem likely to become
unusable if any number of people are actively using the mesh. That's ok.
It's early experimental software.
It looks like the actual useful parts of serval will be the
Rhizome/MeshMS/Mapping over the upcoming bluetooth transport. This is of
course a non-real-time type of communication where data is stored and
forwarded as people walk around and phones sync as they come within range.
For real-time communications I think it's probably better to rely on
something like sudo mesh and then only allow calls when a you're near an
access point.
btw, I ran into an Android app that does Rhizome/MeshMS style store and
forward, but which has an unfortunate (but probably easily removable)
integration with twitter:
https://code.google.com/p/twimight/
Honestly I think Serval has fallen into the trap of inventing everything
themselves and becoming their own island of "stuff that we make only work
with our stuff".
The useful parts of Serval should probably just be separate apps that work
equally well on mesh and non-mesh infrastructures.
Since RedPhone already exists it might be better to add multicast-based
signalling (right now a server is required) and then be able to use it on a
Mesh. We'd need a way for phones to call someone directly based on their
pubkey hash instead of their phone number. A simple and reliable version of
that could be simply entering the pubkey, but a better version could be
registering RedPhone to handle specific URLs and then adding the ability to
show a QR code of your own pubkey which encodes such a URL. This exchange
would require that everyone also has a QR-code scanning app, but there is a
nice open source one available already. The fallback would be manually
entering the pubkey hash. The major problem would be that Android push
notifications don't work without the Google Cloud. MEH! Battery usage might
be a problem since a background service would have to actively parse all
incoming RedPhone multicast messages.
If I were to write something like Rhizome/MeshMS/Mapping then I'd grab the
bluetooth auto-disovery and auto-connect code from twimight, then I'd use
secure-scuttlebutt via jxcore for non-realtime communication (might require
a bit of hacking to get leveldb talking to the js code). For maps the
mapsforge library already does Open Streetmap offline vector-based mapping.
--
marc/juul
I am so late.
I've been sick since last Thursday and have made little progress since
Thursday.
I will show up before 2100 hours, order a pizza and commence swlib hacking.
btw does anyone know much about serval mesh? I'm wondering if it makes
sense to make every node a serval mesh gateway or if it will just be a
useless resource hog.
also, i had a weird idea: I believe cell phone speakers are capable of
making noises above the level of human hearing (though unfortunately not
above the level of dog or cat hearing) and i was thinking about the GPS
method of repeating a signal below the noise floor and then using
auto-correlation at the receiver to bring it back above the noise floor.
I'm wondering: Would it be possible to transmit using this method over
fairly long distances using just the audio input/output of a smartphone as
long as the bitrate is low enough? Could we multiplex multiple signals
without centrally assigned gold codes? Could this be used to make a
jamming-resistant low-bandwidth mesh for e.g. decentralized messaging in a
disaster scenario? How much would this affect animals?
--
marc/juul
