1. Team Daniel Scarlett Miles O’Keefe Cody Clark Samuel Pesek Network/authentication model for Flex Radio’s SDR over WAN

2. Project Goals ●Develop a network/authentication model for accessing Flex Radio’s SDR over WAN via a linux based computer ●Identify various possible solutions for networking and security ●Analyze the resources, time, costs, and risks needed to obtain a working model of the solutions ●Prototype a working model of one of the solutions

3. System block diagram Existing Our Project

4. Network Solution Options Resources Time Cost RiskComment VPN / DDNS Service Provider of DDNS (3rd party or, VPN Client software & VPN compatible router) Minimal client-side setup Quick development & deployment Low/no cost to consumer Maintenance cost for operation via Flex Radio (0$ < DDNS < $500/yr) Low/medium depending on authentication method used Authentication based on username/password Most recommended method depending on authentication used as well Port Forwarding/ Static IP Dedicated router setup for use for client Minimal client-side setupOne time large fee for client to own IP address Low/medium depending on authentication scheme Not recommended because of non mobile use & fee for customer Web GUI Dedicated server for FlexRadio Medium to large setup to deploy Medium/high running the server Low/Medium - depending on server running & maintenance Not recommended because of the server and development cost Dedicated VPN Server Linux Platform Radio Side/Third Party Server (Cloud) Low/medium developmentMedium/high running the server Medium - using a 3rd party server Not recommended because of the 3rd party server

5. Security Solution Options ResourcesTimeCostRiskComments User/PW + One-Time-Pw Google Authenticator or Authy like software OTP Electronic Hardware Low/medium developer hours Low client-side setup Low implementation cost Low if no one gets a hold of the seed Recommended because everything needed is simple to implement Public Key Infrastructure (PKI) Use an existing PKI encryption scheme independent of a Certificate Authority (CA) Low developer hours Low client-side setup Low implementation cost Low if no one gets a hold of the private key Most recommended because of the use of advanced cryptography methods Web GUI SSL/TPL Protocols X.509 Certificates Low/medium developer hours Low client-side setup Medium/high maintenance cost of running server Medium if trusted 3rd party web server Not recommended because of difficult authentication approval Codec Codecs like.aac,.H.264/.mpeg Large - developing a complex compression - decompression algorithm Dependent on extensive development time High - may have unknown flaws Not recommended because time and risk high

6. Timeline 17/Sep/1408/Oct/1412/Nov/1405/Dec/1415/Jan/1511/Feb/1411/Mar/1415/Apr/14 Project Structuring & Conceptual Design Design Phase 1 Resource problem & potential methods to solve Design Phase 2 Develop several solutions for problem Present Potential Solutions Prototype a Solution Implement a Solution Test a Solution Deliver Finished Product Fall 2014 SemesterSpring 2015 Semester

7. Thank You!