186
edits
Difference between revisions of "Mesh/Blog"
Jump to navigation
Jump to search
Clef AP Install
(Clef AP Install) |
|||
| Line 1: | Line 1: | ||
<startfeed /> | <startfeed /> | ||
=Downtown Oakland Access Point= | |||
We spent last Sunday installing a 2.4ghz AP pointing NW towards the street at 1212 Broadway in Downtown Oakland in the [https://getclef.com/ Clef] offices. They have a 1gbps connection in their 12th story office and they were willing to share, so we set up a Nanostation M2 pointing towards the street in an attempt to create an open AP. The tricky thing about setting up APs is that while our antenna is quite strong and has high gain, the majority of devices that would connect to it are weak and have low gain (mobile, laptops, etc). We're going to do some monitoring and testing of how usable the signal is on the street, and we may have to do some adjustments and add another antenna. It may be obvious, but one of our members is quite a cable management specialist :) | |||
<gallery> | |||
PeoplesOpen.net-Clef-Installation-1.jpeg|Showing off work | |||
PeoplesOpen.net-Clef-Installation-2.jpeg|That Cable Management | |||
PeoplesOpen.net-Clef-Installation-3.jpeg|Aiming towards the street | |||
</gallery> | |||
=Alpha Testing Network= | =Alpha Testing Network= | ||
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here: | We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here: | ||