1 / 10

Custom Network Protocol on Modified Ring Topology

Custom Network Protocol on Modified Ring Topology. Team: Radical Leader: Dallas Edwards Members: Sam Sieg Sani Musayev Changyong Jung. Introduction. Modified ring topology Linux based chat system Rewrite/Build Custom OSI-Model Network Monitoring tools

javan
Download Presentation

Custom Network Protocol on Modified Ring Topology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Custom Network Protocol on Modified Ring Topology Team: Radical Leader: Dallas Edwards Members:Sam Sieg Sani Musayev Changyong Jung

  2. Introduction • Modified ring topology • Linux based chat system • Rewrite/Build Custom OSI-Model • Network Monitoring tools • File transfer system

  3. Motivation • CUSTOM RING TOPOLOGY: -Five machines in a ring topology -Every node can act as a bridge/router or carry out its own functions as a single entity. • OSI Model: -Modulization -Standard implementation model

  4. Custom Ring Topology C1: 4 NICs, 4 connections, a gateway to other subnets B1, A1, A2, B2: 2 NICs, 2 connections

  5. Limitations • Not scalable beyond 25 hosts • Linux based system only • No encryption in Presentation layer

  6. Method • Connection to Physical Medium: - Discovery System (Remote-Hosts) • Network Stack: - Discovery of hardware on a local host • Routing algorithms - Vector distance routing algorithms - Packet forwarding • Flow Control - Throttling - Drop rate analysis • Dataflow multiplexing: - Pipelining dataflow into Programs - Management of multiple Program data flows

  7. Results • Ability to send/receive Ethernet packets • Communication among all layers • Working chat application • File transfer capability • Each layer is autonomous and independent

  8. Conclusion • Whole OSI network model is successfully re-built as our own • Each layer works independently and can communicate properly • The Chat application is working in our network stack environment • Above our own network model, the ring topology is successfully constructed. • For the future, advanced network stack might be needed to support multi-platform environment

  9. References [1] Douglas E. Comer, Internetworking with TCP/IP, pp 95 – 173, 2000. Prentice Hall [2] RFC2003: IP Encapsulation within IP, http://portal.acm.org/citation.cfm?id=RFC2003 [3] Richard Stevens, Unix Network Programming, pp 85 – 110, pp 655 – 70, pp 703 – 726, 1998. Prentice Hall [4] Kay A. Robbins & Steven Robbins, Practical UNIX Programming, pp333 – 400, 1996. Prentice Hall. [5] Andreas Schaufler, RAW Ethernet vs. UDP, http://www.landshut.org/bnla01/members/Faustus/fh/linux/udp_vs_raw/index.html [6] Chae Y. Lee & Seok J. Koh, A design of minimum cost ring-chain network with dual-homing survivability: A tabu search approach, Computers & Operations Research, Volume 24, Issue 9, September 1997, pp 883-897 [7] Brian "Beej" Hall, Beej's Guide to Unix Interprocess Communication, http://beej.us/guide/ipc/ [8] Pradeep Padala, NCURSES Programming HOWTO, http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/

  10. Experiments…

More Related