Networking!

• Three things needed to make a network

• Applications
• Programs that communicate with each other
• Protocols
• Languages used on a network to allow communication
• Hardware
• Physical pieces
 Applications

• Web browsers

• Media servers

• File transfers
 Protocols

• Set of rules and standards for communication

• A group of protocols is a Protocol Stack

• TCP/IP
• Transmission Control Protocol / Internet Protocol
• Most common on the internet and for our use
Hardware
 Hardware
• Computers
• Network components
• NIC – Network interface cards
• Hubs
• Dumb, aren’t used anymore, repeat everything
• Switches
• Managed: Smart and powerful
• Unmanaged: Not smart, only talks to hardware
• Allow for multiple point-to-point connections to happen at the same time
• Routers
• Smart, assigns IPs
• Connect LANs together (including WANs)
• Media
• Cable
• Cat 5, 6, 6a, fiber
 Ethernet

• Broad range of standards and technologies used to describe how

separate hosts on a network can share the same link

• AKA the reason why everything can talk on one cable

 Moving through the OSI

• Open Systems Interconnect

• Information that moves through is referred to as a payload, or

Protocol Data Unit (PDU)

• Moves from the top layer down, then back up

• Each layer adds data to the PDU
 Packets
• Since we have multiple signals sharing the same line, data is broken into
Packets

• Protocols figure out how to do that, and where to move what using
Header information

• Different protocols handle packets differently

• Some order and time matters most, some correctness is most

important

• TCP vs UDP
 Routing Schemes
• Broadcast

• Sent to everything on the network directly

• Multicast

• Sent to only receivers that care

• Unicast

• Sent to only one receiver

 Protocols
• Live at Layer 4 on OSI

• TCP

• Communicating to other network devices including projectors, video switches, etc

• Guarantees delivery by making a “virtual circuit”, opening the connection, sending data, closing the
connection

• Slow, but reliable

• UDP

• No guarantee, so faster

• IP

• Naming scheme that we use

 IP Addressing
• IPv4

• 4 octets = 32 bits of data

• 192.168.123.100
• 11000000.10101000.01111011.01100100

• IPv6
• Future is now
• Don’t have to worry about it for us yet
• 255.255.127.0

• 11111111.11111111.01111111.00000000

• 255.255.240.0

• 11111111.11111111.11110000.00000000

• 192.168.123.100

• 11000000.10101000.01111011.01100100
• DHCP (Dynamic Host Configuration Protocol)
• Systems want to be helpful and smart

• Static IP
• We want total control
• Everything in the system should have a consistent IP
address
• Coded into our programming
 Important IP ideas
• Subnet mask
• Defines which part is the network vs host
• 255.255.255.0 (Class B)
• 192.168.123 is the network, .100 is the host
• 255.255.0.0
• 192.168 is the network, .123.100 is the host(ish)
• How much of the network can each host see before going
out to another network
• Gateway
• IP Ranges
• LAN only, so don’t have to follow official rules
• Class B vs Class C
• Separate physical networks for systems
• Control: Servers, projectors, switches
• ”Quiet” network
• Content: Moving content, file transfers
• Automation
• KVM
• VLANs
• Make logical systems
• Media servers 10.0.0.10, 11, 12
• Projectors 10.0.0.100,101,102
• Content network (separate) 10.0.10.100, 101
• Broadcast .255
• Router .1 (typically)
• .0 do not use
• Local host 127.0.0.1
• Internet access lives on separate network
 Ports and Sockets
• More specific of where the information is heading

• Some applications have standardized ports

• HTTP: 80, FTP: 20

• Applications that communicate with each other define ports

• We can customize them in QLab, control software, etc

• Network Design

• STP - Spanning Tree Protocol

• Electricity is lazy, travel is expensive

• Picks the one best path between all points

• Allows for the system to survive after failure of a switch

• VPNs

• Virtual Private Networks

• Your safe way to access something remotely

• Can be used to connect two remote networks and make them

believe they are both local

• Good to use on the outbound Internet connected system

 Other Protocols

• DMX, Art-NET, ETC Net

• MSC

• OSC
 MSC - MIDI Show Control

• Built on top of the MIDI protocol

• Commands based on the needs of the entertainment industry

• Typically requires USB-MIDI adapters; MSC over IP implemented in

all applications
 OSC - Open Sound Control

• More powerful, and Open

• Implimented in many (but not all) applications we use

• Slash / arguments allow for a lot of detail to be written in one

command
 Demos

• QLab to QLab

• TouchOSC to TouchDesigner