Today's node mount at Will's place in Rockridge was a success!
Will had everything ready to go so really I just ran the cable :)
The view from there is pretty great. You can see SF, and downtown Oakland
and the Storquest building next to Omni. Looks like Omni itself is hidden
behind other buildings though. The node is active and it is pointed
approximately at Omni. We may be able to link to it from the Rise Above
building one block from Omni, but that's probably only viable for another 6
months or so.
Sunday the 15th we will be mounting lots of indoor nodes at Omni and a node
on the roof if I manage to get ahold of the landlord's contractor.
Sunday the 22nd is currently open. If it doesn't look like it's going to
rain it may be a good day to do the mount on Hearth (where I live).
Sunday the 1st of March we are mounting on the roof of legind's place very
close to the grand lake theater. It is a two-story building with roof
height at least as tall as the immediately surrounding buildings.
Btw, there's no reason why we can't do multiple mounts on the same Sunday.
It all depends who is available, willing and able to work on this :)
--
marc/juul
# Background
We are currently using a luci-based web app as the admin interface on the
nodes.
luci is not pleasant to work with and luci2 is coming soon. We want to
switch away from luci and maybe switch to luci2.
EFF's Open Wireless router firmware is nice and simple. It uses a very
stripped down python as the back end. We want something like their front
end but probably not their back end.
# Lessons from tonight
ubus is a way for the different processes in openwrt to talk to each other.
ubus has an http interface with access limited by a set of ACLs:
http://wiki.openwrt.org/doc/techref/ubus#access_to_ubus_over_http
luci2 on the backend is simply a set of extensions to ubus that are then
accessed via the ubus http interface.
ubus, the ubus http interface and the luci2 ubus extensions all look good
to me.
The luci2 web app looks and feels great. Unfortunately the javascript is
not so great. In my opinion it's way too complicated for what it is.
I've decided to ditch the luci2 client side stuff and use only the server
side luci2 code. I'll write a very minimal javascript library for accessing
ubus functions.
# Progress
I started putting together a simple web app based on EFFs Open Wireless
router admin interface. It will have a testing mode where a node.js app
simulates a router on the backend to enable web developers to more easily
contribute.
Not much yet, but the beginnings are here:
https://github.com/sudomesh/sudowrt-luci2-webclient
# Trying luci2
I compiled luci2 for the atheros chipset. It is here:
http://juul.io/mesh/
To get it working, copy the ipk to the node and do:
opkg update
opkg install rpcd rpcd-mod-iwinfo uhttpd uhttpd-mod-ubus
opkg install luci2_2015-01-25_atheros.ipk
ln -s ../init.d/rpcd S80rpcd
(reboot the router)
It may complain about a missing function in the post-install script. Never
mind that.
Now access:
http://router_ip/luci2.html
--
marc/juul
hi friends,
sorry for the delay in getting this to you all. sometimes real jobs get
in the way, no? :-)
it was a productive weekend. the dev team made bable work, so big ups to
max, marc, alex, and jake for plowing through that.
the notes can be found after our last meeting's notes:
https://pad.riseup.net/p/sudomesh
we also got some implementation plans and definitions ironed out. please
thumb through the notes at your leisure. and hang in there.
i'll be in touch soon with new folks about plugging in and marking
things off a to-do list. thanks to all the new folks for coming!
all my very best, april
ps: the notes aren't that clean, but their not beyond the understanding.
pss: do you anyone who lives in the oakland hills that would love a new
antenna on their roof?
---
*definitions*
* What differentiates sudomesh from similar projects?
* It's not a mesh in a traditional sense, of like a single
omnidirectional antennas. We're talking about community
networks. Other installations around the US do not integrate the
notion of providing high levels of service. We want to provide a
high speed, symmetrical, and reliable connection.
* We are looking at aslightlydifferent kind of network topology.
We'll need some number of backbone links, likely with base
stations that individuals can connect to. Different than the
sort of "mesh" cloud of omni-directional links that "mesh" is
often referred.
* People's open also requires people who wants to peer on the
network to sign a lisence agreement that explicitly denotes
principles of network neutrality.
--
0x54FC570B
We're mounting a node this Sunday at Broadway and Ocean View (Rockridge).
This is Will's place. He bought a Nanobridge.
We're meeting at sudo room at noon and then we'll take it from there.
It's elevated, so if we're lucky it will be able to see Omni, but we'll
figure that out on Sunday.
--
marc/juul
Hi!
If anyone is interested in HAM! It is a great way to learn about
antennas and technology. Not sure if it is open for the community, but
you can ask. I suspect they will be OK with it.
Mitar
-------- Forwarded Message --------
From: Michael Lustig <mlustig(a)eecs.berkeley.edu>
Subject: [eecs-announce] 2015 ham radio in EECS
To: eecs-announce(a)lists.eecs.berkeley.edu
<eecs-announce(a)lists.eecs.berkeley.edu>
Dear Students, Faculty and Staff,
Topics:
1) Amateur Radio Exam on Campus
2) License Preparation Lectures on Campus
3) What is HAM and what is it good for
4) Ham-shack in Cory Hall + websdr server
1) Exam:
As part of a do-it-yourself, maker, I can build it trend the department
has been leading I am trying to revamp the amateur radio activity in the
department.
As such, I have organized a special exam session for an FCC Ham radio
operator license . The session will be on March 12th 7-10pm, Wozniac
Lounge, Soda Hall.
and is open for registration for students, staff, faculty. My students
in EE123: Digital Signal Processing and EE84 hands on ham radio will all
be taking the exam.
You will need to register to the exam by sending me an email.
Make sure the subject starts with [ham exam]. We will try to
accommodate all of those who are interested, but there's a chance it
will fill up. It will be first email first serve policy.
2) Preparation
Even though the exam is EASY for EECS/CS majors, in the next 4 weeks I
am going to give a series of lectures to prepare for it. The first one
is going to be this Tue, Feb 3rd 6:30-8pm Cory 521. The others will also
be on Tuesdays 6:30-8pm, same place.
3) Amateur Radio (Ham Radio) is a popular hobby and service in which
licensed Amateur Radio operators (hams) operate communications
equipment. Although Amateur Radio operators get involved for many
reasons, they all have in common a basic knowledge of radio technology
and operating principles, and pass an examination for the FCC license to
operate on radio frequencies known as the Amateur Bands.. These bands
are radio frequencies reserved by the Federal Communications Commission
(FCC) for use by ham radio operators.
The role of amateur radio has obviously changed with the presence of the
internet. Remarkably, amateur radio today offers unique opportunities
and capabilities due to its independence on commercial infrastructure.
For example, it is a legal ground for hands-on experimenting with
wireless communication technology and it allows communication in
emergencies and from remote areas.
What can you do as a HAM?
Talk to people (near and far)
Build stuff (amps, sdrs, antennas, receivers)
Emergency communications (emcom)
First person view (FPV) vehicles (drones) at much higher power of
communication for long distance
Hit satellites, moon, meteors, airplanes (with radio waves! not
something else)
Digital communication with Automatic Positioning and Reporting System,
packet radio
Use Repeaters covering bay-area, California and the United States, mesh
networks
4) Activities in amateur radio at the University of California Radio
Club go back to 1914! According to the January 1923 issue of CALIFORNIA
ENGINEER, the amateur radio station was originally established in the
Mechanics Building in February of 1914. For 30 years or more the radio
station was located in Cory Hall up until the renovation of this
building in the 1980s. We now have a small radio shack on Cory 5th
floor. There's an HF and VHF/UHF antenna's on the roof with cables
leading to the shack. We have a simple HF radio as well as a web-sdr
server. All hams are welcome to get access.
Finally, Checkout our websdr at: http://eids.eecs.berkeley.edu:8080/
which allows you to listen to the ham 2m VHF band online.
------------------------------
KK6MRI
Michael Lustig, Ph.D.
Assistant Professor
Department of Electrical Engineering and Computer Sciences,
506 Cory Hall, University of California, Berkeley CA, 94720
Office Tel: (510)643-9338
http://www.mlustig.com
--
http://mitar.tnode.com/https://twitter.com/mitar_m
Hello,
I posted recently to the main Sudo list, and it didn't seem to resonate
there. However I think it is of particular interest to Mesh folks.
I've seen some people here work on auto-discovery of services. Well, the
UBOS operating system, part of the Indiebox project, makes web apps easy to
deploy. Just like LiberOffice can be installed on a laptop with one
command, UBOS allows you to simply deploy Owncloud, Wordpress, Mediawiki,
etc. It takes care of all the database provision, apache configs, etc. It
even allows concurrent installations for different users. Combined with the
auto-discovery stuff you all are working on, I think it could be pretty
powerful addition to the mesh ecosystem.
The guy who runs it is named Johannes Ernst. I've seen him talk in Mountain
View, at the Hacker Dojo. I think the community here at Sudo, particularly
the Mesh group, may be an even better audience for it. He wants to bring
control back home, and I think the mesh group is trying to do the same. I
suggested it to him, and he asked me to reach out. Would anybody out there
be interested in having him come speak about his project? I also told him
about Peoples0pen.
The website is here: indieboxproject.org The project's vision is for a
series of consumer products branded as "Indie Boxes". The operating system
component, UBOS, is built on top of Arch Linux. See
https://github.com/indiebox?tab=repositories for some of the things that
have been packaged.
Let me know if you're interested, and I can arrange things with Johannes.
He is eager to come and talk if you guys are interested.
Thanks,
Dan
Hi All,
My name is Oren. I recently quit my job as a software engineer in startup
land to make big art and work on projects that actually help our community.
With respect to the latter, I'd love to get involved with the SudoMesh.
I'm proficient in C and Python, pick up new languages and protocols
quickly, and am fun and personable :D I tried showing up to the hack night
on the 29th, but all I saw at the Omni was a JavaScript user group and some
folks talking about an X-Ray gun (wowee!!).
Anyway, I'd like to sink up with everyone in person before I dive too deep
into code. Is the hack night, in fact, held at the Omni? Is there one this
coming Tuesday? What is the air-speed velocity of an unladen swallow?!?
In the meanwhile, I'd love to start at least *looking* at some code if
there's a particular place in the sudo-room GitHub org at which you usually
point new recruits. Any and all info is much appreciated.
Thanks!
Oren
Hi everybody,
Feel free to introduce edits. It's a draft. It's also attached.
Pls note that this is a tiny meeting for folks who have been focusing on
the project to make some core decisions and sprint.
Thanks to all!
-April
AGENDA FOR SUDOMESH RETREAT
/s//tarting at 11am, realistically at 12noon. (bfast at secret cafe at
April's?)
/
*Saturday*
12noon – Definitions
*
What differentiates sudomesh from similar projects?
*
What is peoplesopen.net vs. sudo mesh?
*
Peering agreements? Clarify.
*
Levels of participation, what?
1pm – Insights from Preston, formerly of Commotion and OTI, eat, walk
2:30 pm – Uplink decisions
3:30 pm – Stare at a map for an hour or so
4:30 – Mount antenna(s)
6:00 – List edits to website, cook dinner
Onward: /sprint to get Bable working, make list of website updates,
navigate bureaucracy, drink, go out on the water, take notes, burn them/
*Sunday*
12noon – Firmware project management and bug tracking, drink water and
coffee, make food
2pm – Funding options.
3pm – Sprint on firmware, navigate bureaucracy, update website, don't
lose faith
6pm – Calendar the future and cook food: where would we like to see the
project go over the next year? Something cool like (but more precise +
on a calendar):
*
Update website
*
Make a way to order pre-flashed nodes
*
Mount antennas
*
Run beta-test
*
Start deeper community outreach to find a local network need. Try to
mount nodes with the larger community of users...
*
Create materials for new node owners
*
Crowdfunding campaign?
7pm – Whatever we didn't cover? Refine a to-do list to ease on-boarding
new awesome participants? Cook together. Continue.
--
--
0x54FC570B
Hi friends,
Please excuse my excessive emailing today. Looking at our short list of
possible uplink options now; wanted to make sure I'm not missing any.
We have:
LMI
Internet Archive
Cogent
Level 3
365
UC Berkeley (how? Cloyne and Mitar?)
MonkeyBrains, if their in the East Bay
There are more, right? I may be dim.
-april
--
0x54FC570B
