Skip to content

Clarify what the VPN is and that Cyberlab wifi is part of the Platform - #50

Merged
jontyms merged 1 commit into
mainfrom
docs/clarify-vpn-terminology
Oct 26, 2026
Merged

jontyms merged 1 commit into
mainfrom
docs/clarify-vpn-terminology

Conversation

@jontyms

@jontyms jontyms commented Sep 7, 2026

Copy link
Copy Markdown
Member

Why

A member asked in Discord whether our VPN is "essentially something like NordVPN where it's a personal VPN to use for like banking and sensitive stuff," and read AUP section 10 as barring them from reaching UCF sites at all — on their own machine, on their own connection.

Both readings are reasonable given how the docs are worded. Every page called NetBird "the VPN," which members map onto consumer privacy VPNs, and section 10's "Users may not access any part of the UCF network" had no stated scope.

Terminology

  • Stop calling NetBird "the VPN" in prose across the index, OpenStack setup guide, and SSH key guide.
  • Add a short note at the bottom of the NetBird setup guide covering full-tunnel vs split-tunnel: ours only carries traffic bound for the Private Cloud, everything else keeps its normal route.

Scope

Rather than patching nine sections that each say "the Platform," this defines Platform in section 1 to include the Cyberlab Networks and the VPN — they are one system, run by the same admins, and the wifi exists to make connecting to the cloud easier from the lab. Sections 3, 6, 9, 14, and 17 now cover the wifi with no changes of their own.

Also:

  • Section 2 states what the wifi and VPN are for.
  • Section 10 gains a scoping lead-in, and its UCF-network bullet is scoped to the Platform instead of reading as a blanket ban on UCF sites.
  • Section 14 softened to "may be logged."
  • Section 16 names Cyberlab Networks access alongside VPN access. Worth knowing: Cyberlab Secure authenticates with SSO credentials, so sharing the wifi is sharing cloud access.
  • Closing paragraph mirrors the preamble.
  • Fixed an andregulations typo in the quoted UCF 4-002 text.

Not addressed here

Pre-existing, found while reviewing, left for separate PRs:

  • Sections 11 and 12 contradict each other on public IPs.
  • Section 7 refers to a permitted-machines list members have no way to find.
  • The Linux Cyberlab Secure guide instructs users to check "No CA certificate is required." With PEAP-MSCHAPv2 that disables server validation, so an evil-twin AP on the same SSID can harvest a member's SSO password. This is the one I'd prioritize.

🤖 Generated with Claude Code

Members were reading "VPN" as a NordVPN-style privacy service and
concluding the AUP barred them from reaching UCF sites on their own
machines. Two fixes:

Terminology: stop calling NetBird "the VPN" in prose, and add a note at
the bottom of the setup guide explaining full-tunnel vs split-tunnel and
that normal traffic keeps its usual route.

Scope: define "Platform" in AUP section 1 to include the Cyberlab
Networks and the VPN, since they are one system under the same admins
and exist to get members onto the cloud. Every section that says "the
Platform" now covers the wifi without needing its own edit. Section 10
gains a scoping lead-in and its UCF-network bullet is scoped to the
Platform rather than reading as a blanket ban.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01786ck4G5veASTE6hRp57PP
@jontyms
jontyms merged commit 948f469 into main Oct 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant