Hackerspace Network Planning: Bubbly Dynamics

Background

We're taking advantage of our building's shared internet access, which puts a limit on our network design. In particular, we will be double-nat-ed.

This isn't an ideal situation, but isn't necessarily something we can't work around.

Network Layout

For now, we'll refrain from setting up network segmentation internally.

┌────────────────────────────┐
│                            │
│                            │
│                            │
│       SSH:C Network        │
│       172.16.24.0/20       │
│                            │
│                            │
│                            │
└────────────────────────────┘
               │
               │
               │
               │
      ┌─────────────────┐
      │  SSH:C ROUTER   │
      │LAN: 172.16.24.1 │
      │ WAN: 10.1.10.x  │
      │                 │
      └─────────────────┘
               │
               │
               │
               │
               │
┌────────────────────────────┐
│                            │
│                            │
│                            │
│      Building Network      │
│        10.1.10.0/24        │
│                            │
│                            │
│                            │
└────────────────────────────┘
               │
               │
               │
    ┌────────────────────┐
    │  BUILDING ROUTER   │
    └────────────────────┘
               │
               │
               │
    ┌─────────────────────┐
    │      INTERNET       │
    └─────────────────────┘