Commit fc62b5bd authored by Alyx's avatar Alyx
Browse files

updated for post launch

parent 657d2a06
Loading
Loading
Loading
Loading
+8 −8
Original line number Diff line number Diff line
@@ -5,26 +5,26 @@ type: docs

# en0.io's Fremont 2 WiFi Project

Historically, WiFi access in Fremont 2's suites has been scarce and unreliable. This is an attempt to make something
more consistent and reliable.

We're expecting to begin our first deployments in Q4 2025 and Q1 2026.
This project is an attempt to deploy a reliable wireless option available at the FMT2 datacenter.

# Details

This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have
participating. The network is open, using Opportunistic Wireless Encryption (OWE).
participating. The network is open, using Opportunistic Wireless Encryption (OWE). Client Isolation is enabled. 2.4GHz is currently enabled, but is slated to be disabled next time
we have someone on site to validate configuration changes.

You can connect to the SSID "wifi.fmt2.en0.io" as of December 6th, 2026.

We currently have three cabinets in 1200, 1400 and 1500 committed to participation.

# Contribute

We have a few possible ways of back-hauling traffic back to the controller, where it is terminated and will hit the
internet.

- Layer 2 (requires you to provide cross-connect and be within 100 meters of us)
- Layer 3 (tunneled, requires a way to terminate WireGuard and a PoE injector) (coming soon!)
- Layer 3 (v6 over FCIX or FREMIX) (coming soon!)

# Contribute
- Layer 3 (v6 RAP tunnel via mutual IXs such as FCIX or FREMIX) (coming soon!)

## Hardware

+13 −16
Original line number Diff line number Diff line
@@ -9,27 +9,24 @@ https://github.com/alex-shpak/hugo-book

<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="en0.io’s Fremont 2 WiFi Project# Historically, WiFi access in Fremont 2’s suites has been scarce and unreliable. This is an attempt to make something more consistent and reliable.
We’re expecting to begin our first deployments in Q4 2025 and Q1 2026.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE).
<meta name="description" content="en0.io’s Fremont 2 WiFi Project# This project is an attempt to deploy a reliable wireless option available at the FMT2 datacenter.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE). Client Isolation is enabled. 2.4GHz is currently enabled, but is slated to be disabled next time we have someone on site to validate configuration changes.
">
<meta name="theme-color" media="(prefers-color-scheme: light)" content="#ffffff">
<meta name="theme-color" media="(prefers-color-scheme: dark)" content="#343a40">
<meta name="color-scheme" content="light dark"><meta property="og:url" content="https://wifi.fmt2.en0.io/">
  <meta property="og:site_name" content="wifi.fmt2.en0.io">
  <meta property="og:title" content="Home">
  <meta property="og:description" content="en0.io’s Fremont 2 WiFi Project# Historically, WiFi access in Fremont 2’s suites has been scarce and unreliable. This is an attempt to make something more consistent and reliable.
We’re expecting to begin our first deployments in Q4 2025 and Q1 2026.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE).">
  <meta property="og:description" content="en0.io’s Fremont 2 WiFi Project# This project is an attempt to deploy a reliable wireless option available at the FMT2 datacenter.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE). Client Isolation is enabled. 2.4GHz is currently enabled, but is slated to be disabled next time we have someone on site to validate configuration changes.">
  <meta property="og:locale" content="en_us">
  <meta property="og:type" content="website">


  <meta itemprop="name" content="Home">
  <meta itemprop="description" content="en0.io’s Fremont 2 WiFi Project# Historically, WiFi access in Fremont 2’s suites has been scarce and unreliable. This is an attempt to make something more consistent and reliable.
We’re expecting to begin our first deployments in Q4 2025 and Q1 2026.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE).">
  <meta itemprop="wordCount" content="275">
  <meta itemprop="description" content="en0.io’s Fremont 2 WiFi Project# This project is an attempt to deploy a reliable wireless option available at the FMT2 datacenter.
Details# This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have participating. The network is open, using Opportunistic Wireless Encryption (OWE). Client Isolation is enabled. 2.4GHz is currently enabled, but is slated to be disabled next time we have someone on site to validate configuration changes.">
  <meta itemprop="wordCount" content="298">

<title>Home | wifi.fmt2.en0.io</title>
<link rel="icon" href="/favicon.png" >
@@ -150,21 +147,21 @@ Details# This is an Aruba-based installation, currently being deployed on Aruba
      
      
  <article class="markdown book-article"><h1 id="en0ios-fremont-2-wifi-project">en0.io&rsquo;s Fremont 2 WiFi Project<a class="anchor" href="#en0ios-fremont-2-wifi-project">#</a></h1>
<p>Historically, WiFi access in Fremont 2&rsquo;s suites has been scarce and unreliable. This is an attempt to make something
more consistent and reliable.</p>
<p>We&rsquo;re expecting to begin our first deployments in Q4 2025 and Q1 2026.</p>
<p>This project is an attempt to deploy a reliable wireless option available at the FMT2 datacenter.</p>
<h1 id="details">Details<a class="anchor" href="#details">#</a></h1>
<p>This is an Aruba-based installation, currently being deployed on Aruba AP-635s. Our range is only as good as cabinets we have
participating. The network is open, using Opportunistic Wireless Encryption (OWE).</p>
participating. The network is open, using Opportunistic Wireless Encryption (OWE). Client Isolation is enabled. 2.4GHz is currently enabled, but is slated to be disabled next time
we have someone on site to validate configuration changes.</p>
<p>You can connect to the SSID &ldquo;wifi.fmt2.en0.io&rdquo; as of December 6th, 2026.</p>
<p>We currently have three cabinets in 1200, 1400 and 1500 committed to participation.</p>
<h1 id="contribute">Contribute<a class="anchor" href="#contribute">#</a></h1>
<p>We have a few possible ways of back-hauling traffic back to the controller, where it is terminated and will hit the
internet.</p>
<ul>
<li>Layer 2 (requires you to provide cross-connect and be within 100 meters of us)</li>
<li>Layer 3 (tunneled, requires a way to terminate WireGuard and a PoE injector) (coming soon!)</li>
<li>Layer 3 (v6 over FCIX or FREMIX) (coming soon!)</li>
<li>Layer 3 (v6 RAP tunnel via mutual IXs such as FCIX or FREMIX) (coming soon!)</li>
</ul>
<h1 id="contribute">Contribute<a class="anchor" href="#contribute">#</a></h1>
<h2 id="hardware">Hardware<a class="anchor" href="#hardware">#</a></h2>
<p>Have a bunch of Aruba AP-5xx or Aruba AP-6xx APs? We can use them, though AP-6xxs are preferred due to 6GHz support!
We mostly need the following indoor AP models:</p>