Excuse me for resending this email treat, but the Sudo-mesh list was not
linked from the first email that I sent out.
Thx!
-------- Original Message --------
Subject: Re: [sudo-discuss] Server Room Status
Date: Sun, 06 Jul 2014 17:12:03 -0700
From: hol(a)gaskill.com
To: David Keenan <dkeenan44(a)gmail.com>
CC: sudo-discuss(a)lists.sudoroom.org
>the compressor for that could also provide cooling for the servers.
i think doing experiments on heat recovery and regenerative hx are good
for longterm - using a compressor and refrigerant to cool hot things may
be less green than using fans and just circulating fresh cool air and
letting convection do the work. if there's no objection, we could set
up temp racks where daniel and others propose until we can run coax to a
more optimal area. i finally have some time this week so i'll be around
to assist with low-level tasks in support of setting up basic infrastructure
cheers
On 2014-07-06 10:00, David Keenan wrote:
> hey guys,
>
>
> I applaud the effort to find a good, secure server space! I definitely
> wanna help.
>
> The main issue with using this particular room is, as you can see by
> looking at the floorplan, the Backspace wellness collective is
> already paying rent on that particular area (NW groundfloor
> corner) and will be making their own changes to that space. Backspace
> is myself, Andrew of course, Margaretha, Athena, and Sarah.
>
> The wellness collective needs quiet - thats partly an attraction for
> that corner of the building - and, a cabinet full of fans plus almost
> certainly AC for the cabinet, is loud. Also, it takes up Backspace,
> and to be honest, i have hard time inamagining Sudo wont need to get
> into it alla the time, so it seems nonideal to me.
>
> In general I would think, before using other essentially non-shared
> areas of the building for Sudo's servers, we would have to
> actually rule out why building the room in other locations, like Sudo
> room, wouldnt work, and why we think actually that particular location
> in someone else's area is really the only place it could work.
>
> Regardless of Bsckspace, having racked & stacked for going on 20 years
> that would not be my first location in the entire building for a lot
> of reasons.
>
> Also, a server cabinet / closet does not need to be near the main
> electrical panel. Nor does it does not need to be near the street.
>
> We could find a room in the basement. There is excellent ventilation
> to the basement, that just needs a small fix. Also the furnaces are in
> the basement, and heat from the servers could tap into that venting to
> actually help heat the building, which could save on energy. Also,
> there is a plan to build a walk-in in the basement - the compressor
> for that could also provide cooling for the servers.
>
> In other words, in my view, we should attempt a green solution that
> ties the serbers into the infrastructure for the building.
>
> :)
> d
>
> On Saturday, July 5, 2014, Somebody <somebody(a)riseup.net> wrote:
>
> === SERVER ROOM UPDATES ===
> 2014/07/05:
> Today Luis, Matt, and I did the walk in the building, and so far the
> only place that seems the
> most appropriate to have the server room is the room by the bar.
>
> This area is the most ideal in the whole building because the air
> flow,
> temperature, electricity proximity, and also because it is where the
> Internet access enters the building.
>
> Since this area is not is not part of the SudoRoom space, we will have
> to talk about it with the rest of the Sudo-Mesh group and the group
> approves it, then we would have to present the idea at our
> Omni Collective meeting for approval.
>
> If approved by the Omni Collective, we would need to build:
>
> * A 2" or so high floor (two by fours and plywood would do, I believe.
> * A 55" x 65" cage with chicken wire walls and a door.
>
> If this place is NOT approved by the OOC then perhaps we should
> consider
> building the Server Room in the SudoRoom Space. High temperature and
> noise levels are the main issues.
>
> If others have ideas/comments/or want to be part of this process
> please
> jump in. You may contact Matt, Luis, or myself (Daniel).
>
> This update and all other Network/Reboot project is found at:
> https://sudoroom.org/mediawiki/index.php?title=Network/Reboot
>
>
> This update and all other Network/Reboot project is found at:
> https://sudoroom.org/wiki/Network/Reboot
>
> Thx!
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/sudo-discuss
>
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss(a)lists.sudoroom.org <mailto:sudo-discuss@lists.sudoroom.org>
> https://lists.sudoroom.org/listinfo/sudo-discuss
exit1.sudomesh.org is not working!
It crashed and after rebooting it is listing all of the connected
tunneldigger clients, but batctl o says "No batman nodes in range ..."
Anyone change any config on this server?
I haven't been able to find anything wrong. Someone else want to take a
stab at it? Or maybe we should blast it and re-install.
Thanks to Pete Forsyth for alerting us!
--
marc/juul
:)
Max B <maxb.personal(a)gmail.com> wrote:
>_______________________________________________
>mesh mailing list
>mesh(a)lists.sudoroom.org
>https://lists.sudoroom.org/listinfo/mesh
We will be having our hacknight at the NEW sudo room location 4799 Shattuck
Ave, Oakland, tonight at 7:30 pm!
We brought back a bunch of gear from Portland that Russel from Personal
Telco donated to sudo mesh! (weird and awesome stuff) We should play around
with it!
hack hack hack
I will bring beers, caffeinated herbal tea and high spirits!
--
marc/juul
Hey all,
Brief discussion of a potential spot to mount a node near 17th and
Franklin, mapped a bit of it sound, seems like there is line-of-sight to
Laney college tower:
Laney: 37*47'48.53" N 122*15'46.52" W
17th and Franklin: 37 48 20.86 N 122 16 06.12 W
I'm not against it. It could be appropriate to use a key or additional labels. However, I wasn't sure how to represent participants by skill, and their distribution, so this diagram is effectively agnostic to it at the moment. Maybe there's s simple way to add it in?
I used the purple circle shape in respect of the symbol for gender neutrality. I changed the colors of some faces to represent folks of various communities / geographies, and how they build up and intersect with the core group and may overlap with one another. I left the core purple because as far as I can tell it remains true that to get a network to critical mass, there needs to be at least one group building and promoting tools for the network, as well as engaging others to grow.
I'm not satisfied with the captions, so any improvements / changes welcome.
// Matt
----- Reply message -----
From: "Mitar" <mitar(a)tnode.com>
To: "Matthew Senate" <mattsenate(a)gmail.com>
Cc: <drwho(a)virtadpt.net>, "mesh" <mesh(a)lists.sudoroom.org>
Subject: [Mesh] Network Development Diagram
Date: Thu, Jun 26, 2014 08:10
Hi!
Do you think it would be interesting for community diagram to maybe
identify various types of community members needed ideally? Also to
suggest in a way that participants do not have to be necessary
technically skilled, but also everyone else can have a role and can help
as well?
I know that I spent a lot of time explaining to people from
non-technical backgrounds that we need them as well.
Mitar
> Hey all,
>
> Haven't caught up entirely on this thread, but looking forward to
> re-reading shortly.
>
> I felt compelled to finish the updates to see what ya'll think of my
> depiction of a simplified and abstract representation of the overall
> pattern of network development / growth, this time paralleled with the
> community development that propels the growth. (I may switch Right with
> Left also btw)
>
> See attached.
>
>
> // Matt
>
>
> On Wed, Jun 25, 2014 at 11:44 AM, Mitar <mitar(a)tnode.com> wrote:
>
>> Hi!
>>
>>> In the US, sharing one's bandwidth is considered risky at best,
>>> dangerous at worst. Getting DMCA'd because somebody ran a torrent
>>> over your connection, getting raided because a neighbor downloaded
>>> something illegal using your connection, getting your service cut off
>>> because they found out you were sharing it... Additionally, there is
>>> always some risk incurred in using a network that you don't know the
>>> provenance of.
>>
>> All these issues we addressed by using VPN tunnels from nodes to connect
>> all nodes first together into a common network, and then Internet access
>> is a network-wide service. Public IP of host's Internet connection is
>> not visible.
>>
>> As I said, we made things easy. People do not have to know how to
>> protect their sharing of Internet, we designed that once and then can
>> just use it (they can of course also hack further on it, but this is not
>> a requirement for you to participate), so that they can then easily
>> share Internet.
>>
>> I agree with you, if you leave things complicated, then people will want
>> to learn first technology to be able to protect themselves and
>> understand better the risks. But if you develop technology in a way that
>> the risks are low, then they do not feel anymore that is necessary and
>> they are still willing to participate.
>>
>>> Looking at it from a user's perspective, hopping onto someone's AP can
>>> be hazardous because you don't know if it's a boobytrap or not.
>>
>> That's clients issue. Not hosts issue (the person who would host an open
>> AP). We should educate clients as well, they should not trust any
>> network anyway.
>>
>> The question is how to make many hosts to participate. You are saying by
>> teaching them how technology works. I am saying by making technology so
>> easy and safe, that they do not have to learn that. (But are of course
>> very much encouraged to do it, if they want, but it should not be a
>> requirement.)
>>
>>> In our experience, people started using the black box when they
>>> understood that it was set up for them, and intended for them to use.
>>> When it's less unknown it's often seen as safer, and more likely to
>>> be used.
>>
>> That's why you put a sticker on the black box which says "use me" and
>> you put SSID into the air which says "use me".
>>
>>> Most of the contact we've gotten was from activists who were actively
>>> setting up meshes for that purpose. Emergencies, unrest, disaster
>>> preparation, things like that. Very few people for the second. About
>>> as many people for the third as the second.
>>
>> OK, emergencies, unrest, disaster preparation are definitely a very
>> different use cases than what we are trying to address primarily in
>> Slovenia. Probably you really want and need to understand technology
>> when you want to deploy it in such situations.
>>
>> But for home use, for casual browsing, I would argue that this might not
>> be necessary (but of course welcoming and empowering).
>>
>>
>> Mitar
>>
>> --
>> http://mitar.tnode.com/
>> https://twitter.com/mitar_m
>> _______________________________________________
>> mesh mailing list
>> mesh(a)lists.sudoroom.org
>> https://lists.sudoroom.org/listinfo/mesh
>>
>
--
http://mitar.tnode.com/https://twitter.com/mitar_m
