I've been reading this:
http://gen.lib.rus.ec/book/index.php?md5=B96257CF84CE1CBD7D1E544B431F74E5
and while that book is a lot less to the point than I'd like, it got me
thinking about how the internet is structured in the bay area with regards
to stakeholders, their relationships and their physical connections.
I would like to begin an effort to map this out on our wiki. Who's
interested in helping out?
Here are some of my questions:
Exactly who owns the fiber?
How much do those companies pay the cities/counties to lay the fiber?
Is it mostly run on phone poles or in the ground?
Is it a recurring monthly fee or all up front?
Can anyone lay down fiber?
When someone is laying down fiber, do those companies have to provide an
opportunity for other companies to lay down fiber at the same time
(apparently some cities require this in order to prevent the same street
from being repeatedly dug up)?
Why exactly did Google Fiber give up on the bay area?
Was it too expensive for them to lay down fiber? If so, why is Comcast
special? (they are currently laying down massive fiber in Oakland and
starting to offer 2 GB to the home)
Which internet exchanges exist here and where are they located?
Are the exchanges for-profit companies?
What are the requirements to have a presence at an exchange?
Do the exchanges charge per rack-mounted unit?
Do they charge per peered connection?
How do small ISPs get peering agreements with Level 1 ISPs?
What do those agreements look like?
How do the agreements between AT&T and Comcast resellers work?
Where do wireless ISPs like Unwired get their bandwidth?
How do they physically bring it to their towers?
Where are the major data centers?
Where do data centers get their bandwidth?
How physically separate is Internet2?
Would it make sense for us to get on Internet2?
How would we go about that?
--
marc/juul
We may have an opportunity to get affordable gigabits from LMI.
They may allows us to put an AirFiber node on their roof. I haven't gotten
the quote yet but I'm expecting it to be around $1000 per month +/- 50%.
We'd need somewhere with line of sight to the LMI rooftop where we can
mount a few rooftop node.
Does anyone on this list live near this address or know someone who does?
One obvious peer would be one of the Berkeley Student Coops, e.g. Cloyne.
Can someone use e.g. Google Earth to check line of sight from the LMI roof
to the surrounding student coops?
The LMI address is:
1700 Martin Luther King Jr Way
Berkeley, CA 94709
--
marc/juul
a business i'm associated with which owns its own building at 64th and San
Pablo is presently hating Comcast and needs a new internet provider.
this business is community-oriented and is open to proposals from sudomesh to
do something like subscribe to high-power internet and allow PON to put a tower
on the roof and beam signals to other places.
the address is 6323 San Pablo avenue and it's a warehouse-style building with a
peak about 25 feet off the ground.
first step would be to suggest a vendor of high-powered internet and then
sudomesh would volunteer people to help get it plugged in inside the building,
and setup a simple private network for the business (the equivalent of a plain
wireless router)
i work there so i can help setup stuff.
-jake
The treasurer of my ISOC chapter said it took a loooong time to get
(Federal) 501c3 status for the chapter.
Overall it seems better to use the one that's already in place.
Of course I don't know what/how bad these headaches are:
"inherited bureaucratic headaches from ooc (old-omni entity)"
> I second jorrit on using the old entity, as long as it our lawyer gives us
> the OK. It seems like the easier option. And our bylaws need a rewrite
> anyway, maybe this would be a good reason to give them a once over?
> -grant
>
> On Fri, Apr 21, 2017 at 10:28 AM, Jorrit Poelen <jhpoelen(a)xs4all.nl>
wrote:
> > I'd be for recycling the old entity if the paperwork is not too crazy
and
> > that the mission is tailored to what sudomesh does.
> > On Wed, 2017-04-19 at 13:34 -0700, Jenny Ryan wrote:
> > Should we:
> > 1) take over omni's old 501c3? -or-
> > 2) submit our own application for 501c3 status?
> >
> > *1) - take over omni's old 501c3?*
> > (a) It doesn't have a purpose at the moment, and we worked hella hard on
> > procuring it. was a long-form application, so has already been
rigorously
> > reviewed by the irs.
<snip>
Hi all,
At the board meeting on Tuesday, we consented on acquiring 501c3 status by
the end of 2017.
Should we:
1) take over omni's old 501c3? -or-
2) submit our own application for 501c3 status?
*1) - take over omni's old 501c3?*
(a) It doesn't have a purpose at the moment, and we worked hella hard on
procuring it. was a long-form application, so has already been rigorously
reviewed by the irs.
(b) can submit amendments to our Articles of Incorporation changing the
name, primary activities + board of directors (this is what we did for the
ooc -> oc switch)
c) maybe best to wait & hear back from the IRS first (jenny submitted 2014
& 2015 taxes about a week ago) as well as omni's lawyer (jesse palmer)
d) has no assets, but does have 3 years of accounting & credit history. is
up to date on all required gov filings.
*2) - submit our own application for 501c3 status?*
(a) probably best to do a short-form (1023-EZ) application (less overhead &
faster turnaround) - tho that assumes we are not budgeting for more then
$50K annual gross income. contact jenny to get shared on current iteration
of app.
(b) no inherited bureaucratic headaches from ooc (old-omni entity)
(c) more iffy - the IRS only really scrutinizes you when you initially
apply; but they hardly blink on eye wrt amendments to articles, bylaws,
board, etc;
Thoughts appreciated, hopefully we can make a decision on this by Mayday :)
--
<3
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
i think it's perfect with the numbers, and I DON'T think it should be
obfuscated with dictionary words or emojis or something.
in fact i think the entire router IP address should be in there!
people need to learn more about networking, it's not that hard, and this is a
perfect opportunity for that. it's really important that people start to see
IP addresses, especially if we want people to put up web services on the mesh
itself! it's really exciting.
peoplesopen.net 10.64.2.1
peoplesopen.net 5GHz 10.64.2.1
-jake
PS i was an early whiner about the same-SSID roaming problems :)
> We finally have unique SSIDs for the nodes.
>
> Instead of them all being named "peoplesopen.net" they will now have the
> last three parts of the IPv4 address added to the name. E.g. for a home
> node with the IP 100.64.2.1 the SSIDs will be:
>
> 2.4 Ghz: "peoplesopen.net 64.2.1"
> 5 GHZ: "peoplesopen.net fast 64.2.1"
>
> An extender node with the IP 100.64.2.2 will have the SSID "peoplesopen.net
> 64.2.2" even if it is a 5 GHz node. Extender nodes always only have one
> radio, so this is fine.
>
> This only applies to home nodes configured after this change and extender
> nodes flashed with the latest (not yet downloadable) build.
>
> I moved builds.sudomesh.org to be hosted on the VPS running the
> peoplesopen.net website and will grant Grant access as soon as I have his
> SSH key so he can upload the latest builds.
>
> We should later upgrade this to map the scary numbers to either nice simple
> english language words (or why limit to english? give an option of spanish)
> or emojis.
>
> For those of you who are not read up on this issue, the nodes need to have
> unique SSIDs because they we do not have layer 3 roaming working, so when a
> client device is connected to a node's "peoplesopen.net" wifi network and
> auto-roams to a different node's wifi network also called "peoplesopen.net"
> then it will suddenly be on a new subnet but it will not ask for a new DHCP
> lease, since clients assume that multiple access points with the same name
> are on the same layer 2 networs / subnet. The result is that people who are
> sitting approximately between two mesh nodes will have their internet
> intermittently stop working for minutes at a time.
>
> --
> marc/juul
I was working on some changes to the babeld-lab repo. I ended up not using
any of the existing code, but learning from the concepts, so I put the new
code in its own repo: https://github.com/sudomesh/network-lab
It reads a JSON network graph format defining nodes and edges and uses it
to create nodes in network namespaces linked by virtual ethernet edges of
differing quality (babeld-lab connects all nodes to one switch).
Each edge has configurable latency and packet loss in both directions
provided by tc netem.
Each node can run arbitrary scripts in its namespace on startup. These
scripts could be used to start a routing protocol.
-Jehan
Hey everybody!
Exciting news, the new firmware has been pushed to the builds server!
You can now go ahead, flash your router, and let us know what you think of
the new dashboard. After flashing, you will have redo makenode, unless
someone has a method for upgrading the firmware without resetting the
router, (this could be a cool feature to add to the dashboard).
I recommend following the walkthrough if its been awhile since you last
flashed. I am working on making more updates to that guide, but everything
in it is still applicable (except the one screenshot of the old web-ui).
Walkthrough: https://sudoroom.org/wiki/Mesh/WalkThrough
Direct download:
https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-gener…
One other thing, does anyone know why the builds server is throwing 403
error when trying to list the builds at
https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ but is still
letting me download the new firmware and go to https://builds.sudomesh.org/?
Were the permissions changed on the builds directory?
Thanks!
-grant
We finally have unique SSIDs for the nodes.
Instead of them all being named "peoplesopen.net" they will now have the
last three parts of the IPv4 address added to the name. E.g. for a home
node with the IP 100.64.2.1 the SSIDs will be:
2.4 Ghz: "peoplesopen.net 64.2.1"
5 GHZ: "peoplesopen.net fast 64.2.1"
An extender node with the IP 100.64.2.2 will have the SSID "peoplesopen.net
64.2.2" even if it is a 5 GHz node. Extender nodes always only have one
radio, so this is fine.
This only applies to home nodes configured after this change and extender
nodes flashed with the latest (not yet downloadable) build.
I moved builds.sudomesh.org to be hosted on the VPS running the
peoplesopen.net website and will grant Grant access as soon as I have his
SSH key so he can upload the latest builds.
We should later upgrade this to map the scary numbers to either nice simple
english language words (or why limit to english? give an option of spanish)
or emojis.
For those of you who are not read up on this issue, the nodes need to have
unique SSIDs because they we do not have layer 3 roaming working, so when a
client device is connected to a node's "peoplesopen.net" wifi network and
auto-roams to a different node's wifi network also called "peoplesopen.net"
then it will suddenly be on a new subnet but it will not ask for a new DHCP
lease, since clients assume that multiple access points with the same name
are on the same layer 2 networs / subnet. The result is that people who are
sitting approximately between two mesh nodes will have their internet
intermittently stop working for minutes at a time.
--
marc/juul
