[Mesh] node configurator

[Max B]

hmm ok try:
https://nodeconf.local/ (without the :8080 at the end)


On 04/27/2014 04:03 PM, brad gaffney wrote:
> Hey, Max. Thanks, we weren't using that cable. When we access the
> link we only see the images, and we already downloaded and flashed 
> the new one.
> 
> 
> On 04/27/2014 03:55 PM, Max B wrote:
>> On Sun 27 Apr 2014 03:43:22 PM PDT, brad gaffney wrote:
>>> Hi All,
>>> 
>>> Daniel and I are in the sudoroom right now and we are trying to
>>> access the configurator so that we can finish reflashing  my
>>> router.
>>> 
>>> Can someone help us find our way to it, please?
>>> 
>>> Thanks,
>>> 
>>> Brad
>>> 
>>> On 04/21/2014 05:38 PM, Marc Juul wrote:
>>>> 
>>>> 
>>>> On Mon, Apr 21, 2014 at 5:29 PM, Jenny Ryan
>>>> <tunabananas at gmail.com <mailto:tunabananas at gmail.com>>
>>>> wrote:
>>>> 
> On Mon 21 Apr 2014 12:28:46 AM PDT, David Keenan wrote:
> 
> 
>>>>> http://www.nytimes.com/2014/04/21/us/us-promotes-network-to-foil-digital-spying.html?hp&_r=0
>
>>>>> 
> 
> 
>> lets apply for some of that USAID to fight spying at home?
> 
> This article is seriously disturbing. I didn't realize OTI was 
> promoting mesh networks as a secure alternative to the Internet. In
> the Middle East. Maybe someone from the Commotion team is on this
>>>>> list and
> wants to speak to the actual goals of the project and ways in which
> the messaging around it could have been miscommunicated by the
> NYT?
> 
> 
>>>>> "The technology is built from the ground up to be resistant
>>>>> to outside snooping," Mr. Meinrath said...
> 
>>>>> I wonder what he was referring to. If he was referring to
>>>>> mesh networking as used by OTI as the article implies then
>>>>> he's either an idiot or an asshole.
> 
> I think it's really important we all understand and emphasize
>>>>> to new
> folks that mesh networks are not by default more secure than other 
> kinds of networks, though they are more resilient. This is why we
>>>>> have
> monthly cryptoparties at sudo, so we can teach good end-user
>>>>> security
> hygiene. We can further level up by promoting the use of more 
> trustworthy services, such as Riseup for email and OwnCloud for 
> storage, on the mesh splash page or some such.
> 
> One bonus point for SudoWRT is that it uses wlan-slovenija's 
> tunneldigger, routing all connections on the public network
>>>>> through a
> VPN. So actually, our mesh will be more anonymous (insofar as
>>>>> being
> unable to pin an IP to a specific identity) than most networks.
> 
> 
>>>>> Yes. Though it is so far less anonymous from inside the
>>>>> local mesh (we're working on this). Also, we should
>>>>> emphasize that this is not a good anonymity solution and
>>>>> that people should use Tor. For those who may be new to
>>>>> sudomesh: The only real purpose of the tunneldigger VPN is
>>>>> to make it much more likely that the mesh organization will
>>>>> be contacted about abuse complaints instead of the
>>>>> individual sharing their Internet connection.
> 
> 
> We are also not funded by the State Dept.
> 
>>>> 
>>>> _______________________________________________ mesh mailing
>>>> list mesh at lists.sudoroom.org
>>>> <mailto:mesh at lists.sudoroom.org> 
>>>> https://lists.sudoroom.org/listinfo/mesh
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________ mesh mailing
>>>> list mesh at lists.sudoroom.org 
>>>> https://lists.sudoroom.org/listinfo/mesh
>>> 
>>> 
>>> 
>>> _______________________________________________ mesh mailing
>>> list mesh at lists.sudoroom.org 
>>> https://lists.sudoroom.org/listinfo/mesh
>> Hey so it's two part: 1. After the node is finished flashing (the
>> green lights are no longer moving up adn ddown the node), take it
>> to the server closet and look for an ethernet cable that has a
>> piece of blue tape with the words node configurator (or something
>> like that). Connect the node to that ethernet cable. The node's
>> power light should turn on.
>> 
>> 2. Go to any machine on the sudoroom network (we tend to use the 
>> terminal that's directly opposite the server closet) and go to: 
>> https://nodeconf.local:8080/
> 
>