project byzantium

25
Project Byzantium Networking for the Zombie Apocalypse

Upload: eris

Post on 13-Jan-2016

50 views

Category:

Documents


0 download

DESCRIPTION

Project Byzantium. Networking for the Zombie Apocalypse. The Internet is BROKEN. It fails on many levels, but let's just focus on the lowest ones for now. Assumptions. You know what the Internet is You're familiar with the OSI model You know what routing does (layer 3) - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Project Byzantium

Project Byzantium

Networking for the Zombie Apocalypse

Page 2: Project Byzantium

The Internet is BROKEN.

It fails on many levels, but let's just focus on the lowest ones for now.

Page 3: Project Byzantium

Assumptions

• You know what theInternet is

• You're familiar with theOSI model

• You know what routingdoes (layer 3)

• You know how to use 802.11 (layers1 & 2)

• You like being connected

Page 4: Project Byzantium

Use Case: Egypt Problem• Deliberate compromise of infrastructure• ISPs offline• Trunk lines go dark• Services are filtered• Need to collaborate

Page 5: Project Byzantium

Use Case: Katrina Problem

• Massive infrastructure failure• Natural disaster• Connectivity is all or nothing • Need to communicate

Page 6: Project Byzantium

Our Approach

• Mobile, ad-hoc mesh network• Not all nodes need to run mesh routing software• Provides services to associated clients

Page 7: Project Byzantium

Ad-Hoc Networking

• Takes place at OSI layers 1 and 2• Built into 802.11• Requires minimal configuration to bootstrap a network• Nodes can move around while maintaining

connectivity • Nodes can relay traffic to extend range • Any wi-fi enabled device can do it

Page 8: Project Byzantium

Mesh Routing

• Takes place at OSI layer 3• Nodes perform IP routing• A number of protocols exist• Not all protocols have the same features, solve the

same problems, or are efficient

Page 9: Project Byzantium

How Routing Works

Page 10: Project Byzantium

But wait! Isn't the Internet a mesh network?

Not really.

Page 11: Project Byzantium

The Internet is a partial mesh. It's mostly hierarchical.  Lots of networks have routers which are

also single points of failure.

Page 12: Project Byzantium

What we need is a fully connected mesh (or something close to it).

Page 13: Project Byzantium

Ad-hoc wireless + mesh routing ==Mobile ad-hoc mesh network

We can already do this, but we need to make it easier.

Page 14: Project Byzantium

Design Goals

• Cheap, readily available equipment• Improvisable• Rapidly deployable • Robust and reliable• Secure• Low maintenance

Page 15: Project Byzantium

Design Constraints

• Solving Katrina first, Egypt second• A small group of geeks can deploy the solution to enable the

larger community to connect.• Not all nodes have (or need) the mesh software• Minimal collusion required

Page 16: Project Byzantium

Wireless network

• Ad-hoc wireless clients• Mesh nodes

o Hacked routerso Laptops or netbooks o Desktop PCso Plug computers

• Inter-mesh linkso Cantennao Dial-upo Something more exotic?

Page 17: Project Byzantium

Mesh routing

• Route traffic through the network• Route traffic between networks• Support both mesh and non-mesh nodes• Protocols

o OLSRo Babelo BATMAN-adv 

Page 18: Project Byzantium

OLSR (Optimized Link State Routing)

• Not optimized for wirelesso No link-quality awareness

• Routing loops are possible• Tries to propagate the full routing table to every node

Page 19: Project Byzantium

Babel

• Enhancement of OLSR• Link-quality aware• Loop avoidance• No kernel code required• Works by managing the OS routing table• Only supports IPv4 & IPv6 at layer 3• Easy to start• Minimal configuration• Easy to troubleshoot

Page 20: Project Byzantium

BATMAN-adv

• Better Approach To Mobile Ad-hoc Networking • Also has link-quality awareness• Also has loop avoidance• Requires a kernel module

o Included in kernel tree since v2.6.38• Provides a virtual layer 2 interface

o Works with any layer 3 protocol• Very active community• Challenging to troubleshoot

Page 21: Project Byzantium

Resources provided• Wiki• Microblogs• Etherpad• Instant messenger• Forums • Telephony• Chat• File dump• Audio streaming

All of these use existing software.XMPP supports many of these features.

Page 22: Project Byzantium

The Byzantium Live Distribution

• LiveCD/LiveUSB Linux distribution• Mesh routing software

o Including source code• Software development/debugging tools• Network troubleshooting/monitoring tools• Resource hosting software

Page 23: Project Byzantium

The Byzantium Live Distribution

• Utilities for easy setup and configurationo Shell scripts? o Local web app?

• Multi-lingual documentation• Library (CD3WD)• Utilities for replicating copies of the distro in the field

Page 24: Project Byzantium

Technical difficulties

• Client configurationo DHCPo AHCP

• Resource discoveryo DNSo Bonjour/ZeroConf/mDNSo Handwriting on the wall o QR Codeso A P2P searchable resource directory service

Page 25: Project Byzantium

Technical difficulties

• Inter-mesh linkso Exotic != {easy,reliable}o May be specific to use caseo Execution over style

• Easy, intuitive user interfaceo Configuring mesh routing daemon o Configuring networking

• Distributing the solution before the crisis