Hi all, I'm not sure what's the best way to contact folks in Sudo Mesh
For legal reasons, every omni collective needs to have 1 member
formally represented on the Omni Commons executive board. Right now
Sudo Mesh appears to not be represented by anybody, because we haven't
updated our bylaws since you joined as a member collective. Could you
all figure out who you want on Omni's board? We are hoping to have a
formal meeting to update Omni's bylaws this Thursday. It would be
great if Sudo Mesh could send a delegate to this meeting!
Thursday March 4th 7-9pm https://meet.google.com/diw-hszw-msr or
515-428-1108 (PIN: 465 814 905)
Last night I switched the mesh over to a new exit node. The exit node is
the server that acts as a VPN for all of the traffic coming from people
connected to a peoplesopen.net access point.
This switchover means two things:
1. You won't see any more nasty capthas form google. Craigslist works
again, and so does editing wikipedia \o/
2. You may get a warning from google or other sites that you're logging in
from a new IP (since our new exit node has a new IP)
This new exit node actually has multiple IP addresses which means we're no
longer sharing a single IP for the entire mesh (so feel free to set your
torrent clients to use as many simultaneous connections as you please :p).
It's also hosted at a Tor-exit-node-friendly hosting company (psychz.net)
so we shouldn't get any trouble for running a VPN.
A few people have removed the ability for sudo mesh to remote-update their
mesh nodes and opted to manage their own nodes. If this is you and you
still want to switch to the new exit node then you can log into your node
as root and run the attached script (note that this will reboot your node).
I should note that the old and new exit nodes are interconnected so even if
you aren't using the new exit node yet, you're still on the mesh. I'm not
sure how long the old exit node will stay up though.
If you have any questions, just reply to this email :)
and as always: MESH THE PLANET!
I've been putting this off for a while now, but I think it's important
that I finally come out and say this.
I'm no longer interested in a being a member or in any way involved with
sudomesh. This might surprise some folks, largely because so much of the
dysfunction in this group has been swept under the rug, but I don't want
to continue to participate in the facade of "everything is fine here and
we're building a community mesh network". I don't think it's fair to new
folks or to the community at large.
The ownership and power structures of the organization are choking a
really good idea to death. At first I tried to cope with it, thinking
that it was better than nothing. Later I attempted to take action to
help correct it, but was met with a complete unwillingness. The work is
difficult enough. I no longer feel any need to compound it with the
interpersonal, power dynamics, and bureaucratic difficulties that
sudomesh is burdened with.
As I'm currently the owner and maintainer of the sudomesh exit node, if
people are using a "peoplesopen.net" router and want to continue to do
so, they should speak with someone involved with sudomesh (probably
Juul) to coordinate ongoing functionality. I will continue to maintain
some infrastructure, mostly those nodes that I personally installed. I'm
happy to support folks who I personally met with and helped setup.
I do continue to care deeply about building community owned and operated
internet infrastructure. I'm happy to talk about my future plans with
folks as well as what I think went off the rails here. Obviously there
is a lot of work to be done in this domain and though I'm discouraged by
the situation here, I do think that we can move forwards in positive
directions. Feel free to reach out directly to me if you'd like to be a
part of that.
I think we probably want to be a little patient with this before we switch
over, but yeah it's definitely nice that he came around to building this.
We can start testing it on the dev exit server.
Oh and we might be able to just abandon our changes to the code in our git
repo because fixing the history is a nightmare right now.
On Wed, Feb 10, 2016 at 3:10 PM, Marc Juul <juul(a)labitat.dk> wrote:
> On Wed, Feb 10, 2016 at 3:03 PM, Juliusz Chroboczek <
> jch(a)pps.univ-paris-diderot.fr> wrote:
>> I've finally done some work on redesigning the local control interface of
> Nice! Looks like we can finally abandon our own patched version and switch
> to mainline. Thanks for adding this!
> Babel-users mailing list
Ok exit server is back up. Thanks for the patience. We're probably gonna
have to migrate to another vps tomorrow. I'm gonna go with linode unless
anyone else has suggestions. We need 3-4TB transfer per month and debian 8,
all the other requirements are pretty soft.
On Sun, Jan 3, 2016 at 8:28 PM, Max B <maxb.personal(a)gmail.com> wrote:
> Hey folks,
> There's gonna be an hour or so of network downtime tonight. I just got an
> email from digital ocean saying that we've received too many dmca
> complaints and that they're gonna bring down our server until I respond to
> the latest one. I'm out of the house for the next hour and I don't know
> that I can deal with it until I get back.
> Sorry about this - I'm gonna try to get this fixed asap and avoid this
> moving into the future.
There's gonna be an hour or so of network downtime tonight. I just got an email from digital ocean saying that we've received too many dmca complaints and that they're gonna bring down our server until I respond to the latest one. I'm out of the house for the next hour and I don't know that I can deal with it until I get back.
Sorry about this - I'm gonna try to get this fixed asap and avoid this moving into the future.
Hey so this is a kind of long back and forth that's taking place on the
babel-users list, but for our devs I think it's something we're going to
want to keep an eye on:
The gist of it is that the wlanslovenija project switched to babeld some
time ago and is starting to encounter a few issues. One in particular might
be w/ regards to their topology (which is similar to ours) in that a
central node with an enormous routing table might not be a use case that
babeld in its current implementation supports well.
It's not clear that there is any single determined cause of the issues with
the slovenia network, but this back and forth is somewhat illustrative:
The amount of state that a Babel node maintains is proportional to v*r,
> where v is the number of neighbours and r the number of routes. Your
> network is somewhat unusual in that it has some very central nodes -- 75
> neighbours max, I believe --, which is something that Babel doesn't like
> very much. The protocol should be able to deal with that (75 * 500 is
> less than 40000), but the implementation will likely need some tuning.
> I'm hoping that you can help me do the tuning.
> > Or are we now the largest network using it and this is why we are
> > getting in all this trouble?
> You are the largest Babel network right now. I'm very excited about your
> deployment, and I'm looking forward to tuning the babeld implementation to
> work well enough for your needs.
> > So this is just another academic project which looks good on the paper
> > but in practice it is not really production grade?
> Most academic projects produce no useful software, just simulation. We
> are doing our best to provide production-quality software, and as a matter
> of fact babeld is running right now in a production network of 200 nodes.
> However, Nexedi's network has been designed with Babel in mind, and it
> doesn't have any central nodes -- all nodes have roughly the same number
> of neighbours.
> > We had to turn of Babel in the network and go back to OLSRv1.
> Which is a reasonable thing to do in order to solve your short-term
> issues. I hope that you'll remain open to working with me to get babeld
> to scale to your needs -- I assure you that it can be done, but I need
> profiling data in order to do that.
We haven't run into any issues yet, but we have a much smaller network than
the slovenian one. We should keep our eyes out for any resolutions of this
issue over on the babel-users list and watch for any error messages we
might receive from any of our nodes, in particular our exit server.
I wanted to let everyone know about this event that will be happening in
Richmond this Saturday, Nov 21st. Sudomesh/peoplesopen.net is a co-sponser
and will have a table there. I don't have a particularly good idea of what
it will look like, but I do have a ton of respect for the work that BBK and
OTX do and it'll be a really good opportunity to see what grassroots
digital literacy work looks like.
The fair will be at:
Building Blocks for Kids
312 9th St, Richmond, CA 94801 (a pretty short walk from the BART station)
11/21/2015 10am - 1pm.
We were asked to show up at 9am to prepare for tabling, etc. I'll be there
to bottom line it, but if other folks want to show up and talk about
sudomesh/peoplesopen.net I'd love the company.
Our last Tuesday of the month general meeting is tomorrow, Tuesday October
27th at the Omni!
We've been busy alpha testing the network and have been getting some
promising results! More info on that process can be found here:
We're especially interested in finding a handful of new folks who would
want to host nodes. If you're willing to share some of your home bandwidth,
generally reliable, and interested in our project, it's a great way to
learn about the network while helping us out a lot with very little initial
investment! If you're able to email me in advance of the meeting letting me
know that you're interested in hosting a home node, that would be
especially helpful, but if not that's ok too.
We take notes of our meetings (which everyone is encouraged to check out
even if you're not in attendance) here:
Feel free to add agenda items if there are things you want to bring
We're also generally on IRC on freenode servers in channel #peoplesopen.net
For information on how to join, check out
Hope to see you there!