Difference between revisions of "WLRH Internet Connection Project"
m (Hfuller moved page Mystery Internet Connection Project to WLRH Internet Connection Project without leaving a redirect: It's not a secret anymore.) |
(Add progress updates) |
||
Line 11: | Line 11: | ||
# <s>Gain approval from UAH to provide network services from their location for this purpose.</s> | # <s>Gain approval from UAH to provide network services from their location for this purpose.</s> | ||
#* Done as of 23 Mar 2018 | #* Done as of 23 Mar 2018 | ||
− | # Meet with the General Manager to make the offer of providing this service, on behalf of Makers Local. | + | # <s>Meet with the General Manager to make the offer of providing this service, on behalf of Makers Local.</s> |
#* Meeting has been scheduled as of 13 Apr 2018 | #* Meeting has been scheduled as of 13 Apr 2018 | ||
+ | #* Done as of 17 Apr 2018 | ||
# Decide on a location for the "receiver" equipment. | # Decide on a location for the "receiver" equipment. | ||
− | # Decide on a location for the "transmitter" equipment. | + | #* The temporary location will be on the tower, but closer to the base. |
− | #* | + | # <s>Decide on a location for the "transmitter" equipment.</s> |
− | # Decide on appropriate equipment based on those locations. | + | #* Approval gained from Optics Building staff to mount radio equipment on the building, approx 23 Apr 2018. |
+ | #* Support structure installation completed on the south side of the Optics Building telescope riser area approx 30 Apr 2018. | ||
+ | # <s>Decide on appropriate equipment based on those locations.</s> | ||
+ | #* 5GHz will work due to the readily available line of sight to this location. A backup link may need to be 2.4GHz, but I doubt it. | ||
+ | #* Proof of concept equipment was purchased: MikroTik RouterBoard SXTsq 5 ac | ||
+ | #* UAH-side equipment installation for proof of concept completed on 1 May 2018. | ||
# Buy and donate the equipment. | # Buy and donate the equipment. | ||
+ | #* Pending proof of concept completion. | ||
# Install the equipment. | # Install the equipment. | ||
# Set up the equipment. | # Set up the equipment. |
Revision as of 14:08, 3 May 2018
Creator: |
Contents
[hide]Overview
Due to funding and historical reasons, it has proven impossible or at least impractical for WLRH to gain access to a high-throughput Internet connection, despite UAH being incredibly nearby, and also being ready and willing to offer the connection itself. The only missing piece is the infrastructural build-out between the two. Since Makers Local has some expertise in point-to-point wireless (and is developing more as we speak), I figured we could help a fellow not-for-profit organization out, and come up with a solution to that problem.
Steps
-
Gain approval from UAH to provide network services from their location for this purpose.- Done as of 23 Mar 2018
-
Meet with the General Manager to make the offer of providing this service, on behalf of Makers Local.- Meeting has been scheduled as of 13 Apr 2018
- Done as of 17 Apr 2018
- Decide on a location for the "receiver" equipment.
- The temporary location will be on the tower, but closer to the base.
-
Decide on a location for the "transmitter" equipment.- Approval gained from Optics Building staff to mount radio equipment on the building, approx 23 Apr 2018.
- Support structure installation completed on the south side of the Optics Building telescope riser area approx 30 Apr 2018.
-
Decide on appropriate equipment based on those locations.- 5GHz will work due to the readily available line of sight to this location. A backup link may need to be 2.4GHz, but I doubt it.
- Proof of concept equipment was purchased: MikroTik RouterBoard SXTsq 5 ac
- UAH-side equipment installation for proof of concept completed on 1 May 2018.
- Buy and donate the equipment.
- Pending proof of concept completion.
- Install the equipment.
- Set up the equipment.
- ???
- Non-profit
Details
Make the offer
It should be clear that the support for the link will come from a Makers Local point of contact, and the rest will be best-effort. It may be worth covering what the needs are, and if non-critical services can use this link while critical services use the existing one. Maybe some sort of failover scheme.