DOCSLIB.ORG

Access Point Reconfiguration Using Openwrt

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Access Point Reconfiguration Using Openwrt Access Point Reconfiguration Using OpenWrt Dalton M. Tavares1, Maicon J. Lima1, Rafael V. Aroca2, Glauco A. P. Caurin3, Antônio Carlos de Oliveira Jr1, Tércio A. Santos Filho1, Stella J. Bachega4, Marcos A. Batista1, and Sérgio F. da Silva1 1Computer Science Department, Federal University of Goiás, Catalão, Goiás, Brazil 2Mechanical Engineering Department / Federal University of São Carlos, São Carlos, São Paulo, Brazil 3Mechanical Engineering Department / University of São Paulo, São Carlos, São Paulo, Brazil 4Production Engineering Department / Federal University of Goiás, Catalão, Goiás, Brazil Abstract— The research project Mobile mEsh Network to The steps to build the M.E.N.A.C.E-TRACK infrastruc- Aid in CountEring drug TRAffiCKing (M.E.N.A.C.E-TRACK) ture involve the definition of the devices that can be used as proposes the creation of a dynamic mesh network, intended nodes, the choice of the operating system for such devices to interconnect field personnel to a base of operations and the selection of the best routing protocol(s) to provide whenever possible. This type of network accepts the dynamic routing adjustments considering mobile nodes with varying disconnection and reconnection of nodes. To configure a ranges. The chosen devices are off the shelf with the ability mesh node using, for instance, an access point, usually a to use wireless communication, i.e. IEEE 802.11 b/g/n, and modified firmware is needed. In this paper we present the the TCP/IP protocol suite. Specifically, we will cover the first steps to build the M.E.N.A.C.E-TRACK infrastructure adaptation of access points (APs) so they can be used as concerning the configuration of the access point, the chosen mesh nodes in the future. This procedure addresses the firmware and some configuration scenarios on an infra- selection of a firmware, preferably open source, which is structured network in order to demonstrate its flexibility. flexible enough to be modified according to the choice of the wireless environment to be implemented (e.g. infra- Keywords: Mesh Network, Ad hoc, OpenWrt structured or ad hoc network). 1. Introduction 2. Infra-structured versus Ad hoc net- The research project Mobile mEsh Network to Aid in works CountEring drug TRAffiCKing (M.E.N.A.C.E-TRACK) pro- An IEEE 802.11 W-LAN can be implemented either with poses the creation of a dynamic mesh network, intended to infrastructure or without infrastructure (i.e. ad hoc). In an interconnect field personnel (e.g. in vehicles or on foot) to a infrastructure based network, there is a centralized controller base of operations (e.g. a police station) whenever possible. for each cell. This cell represents the fundamental building This type of network accepts the dynamic disconnection and block of the 802.11 architecture, known as the basic service reconnection of a node or group of nodes leaving or returning set (BSS). A BSS typically contains one or more wireless to the main base network range. The use of day to day low stations and a central base station, known as access point cost and off the shelf devices, like access points, notebooks (AP). The wireless stations, which may be either fixed or or smartphones and open source software is one of the main mobile, and the central base station communicate among attractors to our approach. themselves using the IEEE 802.11 wireless MAC protocol. To configure a mesh node using, for instance, a wireless Multiple APs may be connected together (e.g. using a wired router, usually a modified firmware is needed. This firmware Ethernet or another wireless channel) to form a distribution allows the creation of a dynamic route between the base system (DS). The DS appears to upper-level protocols (e.g. station (the one that have the Internet connection and access IP) as a single 802.11 network, in much the same way that to the main systems) and the client nodes in a mesh a bridged wired 802.3 Ethernet network appears as a single environment. The dynamic route can be stablished directly network to the upper-layer protocols. We can use the same between the base station and mesh nodes, or using each analogy considering that an AP, which is normally connected mesh node as a “bridge” (in-between nodes) to amplify the to a wireline backbone (either wired or wireless) is also range of the original access point. Therefore, each mesh node considered a DS, thus providing Internet access to mobile receives a data connection from a given node and conveys devices. All traffic goes through the AP, even when this is data to the next node, extending the range of communication sent to a destination that belongs to the same cell [2], [3]. for each passing node [1]. In an ad hoc network there is no central control with connections to the Internet. Here, the network is a temporary arrangement as and when required. The benefit is that no infrastructure is needed and the users themselves may extend the area of coverage. Hence, mobile devices that have found themselves in proximity to each other, that have a need to communicate and find no pre-existing network infrastructure in the location (e.g. a pre-existing 802.11 BSS with an AP) may communicate using each other as the current medium [2], [4]. The focus of this paper will reside in extending the range of an infra-structured network using multiple APs. The main objective to be accomplish with this course of action is to gain the necessary expertise concerning the firmware operation and configuration, which will be invaluable in future experiments involving mesh networks. Fig. 1: Proposed testbed for the case study. 2.1 OpenWrt Features 3.1 Preparing the AP Devices OpenWrt is described as a GNU/Linux distribution for The first steps taken to install OpenWrt on the TP-LINK embedded devices, which provides a fully writable filesys- TL-WDR 4300 router are described at [7]. They involve tem with package management. In that sense, by definition, consulting the Buyers’ Guide [8], and verifying how much it is not strictly a firmware but a complete and modifiable a given router is compatible with OpenWrt using the table operating system. This frees the developer from the static of hardware [9]. application profile provided by a vendor and allows the The first installation of the OpenWrt firmware is done customization of the device through the use of packages that using the original web interface of the TP-LINK firmware. suit any particular need [5]. It is performed just like a flash update of some new version Compared to other distributions OpenWrt may also not of the original TP-LINK firmware. According to [6], it is rec- be regarded as a true end-user or user friendly firmware. ommended to turn off the Wi-Fi interfaces manually (there is Nevertheless, it can be used as such sometimes, depending a switch behind the device to disable them). Therefore, at the on the feature set provided in addition to the main package first boot, we will not have any wireless interface enabled by [5]. Therefore, OpenWrt was chosen as our base architecture default. The first login test is done using an Ethernet cable to implement M.E.N.A.C.E-TRACK. Section 3 presents a plugged into any Ethernet port (not the WAN port). The set of experiments devised to study OpenWrt flexibility computer interface must be set to any address in the range regarding a simple research question: how can I extend the 192.168.1.0/24, exception made to 192.168.1.1, which is the range of an infra-structured IEEE 802.11 wireless network? default address of the OpenWrt interface [10]. After the first connection it is recommended to setup the 3. Experimental Testbed root password (the only account). After the password is set, the telnet daemon is disabled and all future accesses are We chose as our experimental testbed a TP-LINK TL- done using the ssh service [10]. Considering our testbed WDR 4300 router. According to [6] this router provides a is essentially experimental and is intended to test multiple simultaneous dual band (concurrent 2.4 GHz and 5 GHz) mesh routing protocols, implying in a frequent change in its and is advertised as 750 Mbps in dual-stream mode on the configuration files, we still did not consider the procedures 2.4 GHz band, and triple-stream on the 5 GHz band. It’s described at [11] for network and system hardening. hardware can be summarized as an Atheros AR9344 CPU operating at 560MHz, 8MB internal flash, 128 MB RAM, 3.1.1 USB Storage 4 Gigabit Ethernet ports, 1 Gigabit Ethernet WAN port, 2 Considering the size of the internal flash memory (8 MB), USB 2.0 ports, Serial and JTag interfaces and support up to it is recommended to increase this size as soon as possible. 12 VLANs. After the base installation, we have up to 4 MB available, To simplify the presentation of the experimental results, which runs out relatively fast depending on the number of we organized this section to discuss the device preparation packages the administrator chooses to install. Fortunately, (section 3.1) and the case studies involving the two APs so OpenWrt allows the extension of this available size by means they can expand the indoor range of the Wi-Fi connection of an overlay file system. This means we can extend the shared by a desktop computer (section 3.2). The experimen- root file system (stored at the internal flash memory) to an tal testbed is presented in Figure 1.
Load more

Recommended publications
  • Computer Security Administration
    Information Security Group Information + Technology Services University of Toronto Endpoint Security Policy System A Network Access Control System with Vulnerability Detection and User Remediation Evgueni Martynov UNIX Systems Group Mike Wiseman Computer Security Administration Endpoint Security Policy System Table of Contents Acknowledgements............................................................................. 3 Change History .................................................................................... 4 Summary ............................................................................................. 5 Overview .............................................................................................. 5 Network Isolation ............................................................................... 6 Vulnerability Detection ....................................................................... 6 User Remediation ................................................................................ 8 Administering ESP ............................................................................... 8 ESP Operations Experience ................................................................ 9 Appendix I – Installation and Configuration of ESP server ........... 10 Using init.sh ..................................................................................... 10 Post-Installation ................................................................................ 11 Configuring an ESP Server to Work with an ESP Agent .......................
    [Show full text]
  • Hostscan 4.8.01064 Antimalware and Firewall Support Charts
    HostScan 4.8.01064 Antimalware and Firewall Support Charts 10/1/19 © 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco public. Page 1 of 76 Contents HostScan Version 4.8.01064 Antimalware and Firewall Support Charts ............................................................................... 3 Antimalware and Firewall Attributes Supported by HostScan .................................................................................................. 3 OPSWAT Version Information ................................................................................................................................................. 5 Cisco AnyConnect HostScan Antimalware Compliance Module v4.3.890.0 for Windows .................................................. 5 Cisco AnyConnect HostScan Firewall Compliance Module v4.3.890.0 for Windows ........................................................ 44 Cisco AnyConnect HostScan Antimalware Compliance Module v4.3.824.0 for macos .................................................... 65 Cisco AnyConnect HostScan Firewall Compliance Module v4.3.824.0 for macOS ........................................................... 71 Cisco AnyConnect HostScan Antimalware Compliance Module v4.3.730.0 for Linux ...................................................... 73 Cisco AnyConnect HostScan Firewall Compliance Module v4.3.730.0 for Linux .............................................................. 76 ©201 9 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
    [Show full text]
  • Lecture 11 Firewalls
    BSc in Telecommunications Engineering TEL3214 Computer Communication Networks Lecture 11 Firewalls Eng Diarmuid O'Briain, CEng, CISSP 11-2 TEL3214 - Computer Communication Networks Copyright © 2017 Diarmuid Ó Briain Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back- Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". TEL3214 Firewalls 09 May 2017 TEL3214 - Computer Communication Networks 11-3 Table of Contents 1. AN INTRODUCTION TO FIREWALLS........................................................................................................................5 2. THE DIGITAL SECURITY PROBLEM...........................................................................................................................5 2.1 HOME......................................................................................................................................................................5 2.2 ENTERPRISE...............................................................................................................................................................6 2.3 ROAMING INDIVIDUAL.................................................................................................................................................6 2.4 PERIMETER DEFENCE AND FIREWALLS.............................................................................................................................6
    [Show full text]
  • Comodo Korugan UTM Security Target Lite
    Comodo Yazılım A.Ş. Tasnif Dışı/Unclassified Comodo Korugan UTM Security Target Lite Comodo Yazılım A.Ş. Comodo Korugan UTM 1.10 Security Target Lite COMODO YAZILIM A.Ş. The copyright and design right in this document are vested in Comodo Yazılım A.Ş. and the document is supplied to you for a limited purpose and only in connection with this project. No information as to the contents or the subject matter of this document or any part thereof shall be communicated in any manner to any third party without the prior consent in writing of Comodo Yazılım A.Ş. Copyright © Comodo Yazılım A.Ş., 2014-2017 Comodo Yazılım A.Ş. 1 / 48 Author: Onur Özardıç Comodo Yazılım A.Ş. Tasnif Dışı/Unclassified Comodo Korugan UTM Security Target Lite List of Tables Table 1 ST and TOE References ........................................................................................ 6 Table 2 Functional features of TOE ..................................................................................... 8 Table 3 Major Security Features of TOE ............................................................................. 8 Table 4 Assets using TOE resources .................................................................................15 Table 5 Threats addressed by TOE only ............................................................................16 Table 6 Threats met by TOE and TOE Security Environment ............................................16 Table 7 Threats Addressed by TOE Security Environment .................................................16 Table
    [Show full text]
  • The Book of PF Covers the Most • Stay in Control of Your Traffic with Monitoring and Up-To-Date Developments in PF, Including New Content PETER N.M
    EDITION3RD BUILD A Covers OpenBSD 5.6, MORE SECURE FreeBSD 10.x, and NETWORK EDITION NETWORK 3RD NetBSD 6.x WITH PF THETHE BOOKBOOK THE BOOK OF PF OF THE BOOK THE BOOK OF PF OF THE BOOK OFOF PFPF OpenBSD’s stateful packet filter, PF, is the heart of • Build adaptive firewalls to proactively defend against A GUIDE TO THE the OpenBSD firewall. With more and more services attackers and spammers NO-NONSENSE placing high demands on bandwidth and an increas- OPENBSD FIREWALL • Harness OpenBSD’s latest traffic-shaping system ingly hostile Internet environment, no sysadmin can to keep your network responsive, and convert your afford to be without PF expertise. existing ALTQ configurations to the new system The third edition of The Book of PF covers the most • Stay in control of your traffic with monitoring and up-to-date developments in PF, including new content PETER N.M. HANSTEEN visualization tools (including NetFlow) on IPv6, dual stack configurations, the “queues and priorities” traffic-shaping system, NAT and redirection, The Book of PF is the essential guide to building a secure wireless networking, spam fighting, failover provision- network with PF. With a little effort and this book, you’ll ing, logging, and more. be well prepared to unlock PF’s full potential. You’ll also learn how to: ABOUT THE AUTHOR • Create rule sets for all kinds of network traffic, whether Peter N.M. Hansteen is a consultant, writer, and crossing a simple LAN, hiding behind NAT, traversing sysadmin based in Bergen, Norway. A longtime DMZs, or spanning bridges or wider networks Freenix advocate, Hansteen is a frequent lecturer on OpenBSD and FreeBSD topics, an occasional • Set up wireless networks with access points, and contributor to BSD Magazine, and the author of an lock them down using authpf and special access often-slashdotted blog (http://bsdly.blogspot.com/ ).
    [Show full text]
  • Nftables Och Iptables En Jämförelse Av Latens Nftables and Iptables a Comparison in Latency
    NFtables and IPtables Jonas Svensson Eidsheim NFtables och IPtables En jämförelse av latens NFtables and IPtables A Comparison in Latency Bachelors Degree Project in Computer Science Network and Systems Administration, G2E, 22.5 hp IT604G Jonas Svensson Eidsheim [email protected] Examiner Jonas Gamalielsson Supervisor Johan Zaxmy Abstract Firewalls are one of the essential tools to secure any network. IPtables has been the de facto firewall in all Linux systems, and the developers behind IPtables are also responsible for its intended replacement, NFtables. Both IPtables and NFtables are firewalls developed to filter packets. Some services are heavily dependent on low latency transport of packets, such as VoIP, cloud gaming, storage area networks and stock trading. This work is aiming to compare the latency between the selected firewalls while under generated network load. The network traffic is generated by iPerf and the latency is measured by using ping. The measurement of the latency is done on ping packets between two dedicated hosts, one on either side of the firewall. The measurement was done on two configurations one with regular forwarding and another with PAT (Port Address Translation). Both configurations are measured while under network load and while not under network load. Each test is repeated ten times to increase the statistical power behind the conclusion. The results gathered in the experiment resulted in NFtables being the firewall with overall lower latency both while under network load and not under network load. Abstrakt Brandväggen är ett av de viktigaste verktygen för att säkra upp nätverk. IPtables har varit den främst använda brandväggen i alla Linux-system och utvecklarna bakom IPtables är också ansvariga för den avsedda ersättaren, NFtables.
    [Show full text]
  • Netfilter:Making Large Iptables Rulesets Scale
    Netfilter:Netfilter: MakingMaking largelarge iptablesiptables rulesetsrulesets scalescale Netfilter Developers Workshop 2008 d.1/10-2008 by Jesper Dangaard Brouer <[email protected]> Master of Computer Science ComX Networks A/S Who am I Name: Jesper Dangaard Brouer Edu: Computer Science for Uni. Copenhagen Focus on Network, Dist. sys and OS Linux user since 1996, professional since 1998 Sysadm, Developer, Embedded OpenSource projects Author of ADSL-optimizer CPAN IPTables::libiptc Patches accepted into Kernel, iproute2 and iptables Netfilter: Making large iptables rulesets scale 2/29 Physical surroundings ComX delivers fiber based solutions Our primary customers are apartment buildings but with end-user relation Ring based network topology with POPs (Point Of Presence) POPs have fiber strings to apartment buildings CPE box in apartment performs service separation into VLANs Netfilter: Making large iptables rulesets scale 3/29 The Linux box The iptables box(es), this talk is all about placed at each POP (near the core routers) high-end server PC, with only two netcards Internet traffic: from several apartment buildings, layer2 terminated via VLANs on one netcard, routed out the other. Cost efficient but needs to scale to a large number of customers goal is to scale to 5000 customers per machine Netfilter: Making large iptables rulesets scale 4/29 Issues and limitations First generation solution was in production. business grew and customers where added; several scalability issues arose The two primary were: Routing performance reduced (20 kpps)
    [Show full text]
  • Firehol + Fireqos Reference
    FireHOL + FireQOS Reference FireHOL Team Release 2.0.0-pre7 Built 13 Apr 2014 FireHOL + FireQOS Reference Release 2.0.0-pre7 i Copyright © 2012-2014 Phil Whineray <[email protected]> Copyright © 2004, 2013-2014 Costa Tsaousis <[email protected]> FireHOL + FireQOS Reference Release 2.0.0-pre7 ii Contents 1 Introduction 1 1.1 Latest version........................................1 1.2 Who should read this manual................................1 1.3 Where to get help......................................1 1.4 Manual Organisation....................................1 1.5 Installation.........................................2 1.6 Licence...........................................2 I FireHOL3 2 Configuration 4 2.1 Getting started........................................4 2.2 Language..........................................4 2.2.1 Use of bash.....................................4 2.2.1.1 What to avoid..............................4 3 Security 6 3.1 Important Security Note..................................6 3.2 What happens when FireHOL Runs?............................6 3.3 Where to learn more....................................7 4 Troubleshooting 8 4.1 Reading log output.....................................8 FireHOL + FireQOS Reference Release 2.0.0-pre7 iii II FireQOS 11 5 Configuration 12 III FireHOL Reference 13 6 Running and Configuring 14 6.1 FireHOL program: firehol................................. 15 6.2 FireHOL configuration: firehol.conf............................ 18 6.3 control variables: firehol-variables............................. 23
    [Show full text]
  • Writing Netfilter Modules
    Writing Netfilter modules Jan Engelhardt, Nicolas Bouliane rev. July 3, 2012 The Netfilter/Xtables/iptables framework gives us the possibility to add features. To do so, we write kernel modules that register against this framework. Also, depending on the feature’s category, we write an iptables userspace module. By writing your new extension, you can match, mangle, track and give faith to a given packet or complete flows of interrelated connections. In fact, you can do almost everything you want in this world. Beware that a little error in a kernel module can crash the computer. We will explain the skeletal structures of Xtables and Netfilter modules with complete code examples and by this way, hope to make the interaction with the framework a little easier to understand. We assume you already know a bit about iptables and that you do have C programming skills. Copyright © 2005 Nicolas Bouliane <acidfu (at) people.netfilter.org>, Copyright © 2008–2012 Jan Engelhardt <jengelh (at) inai.de>. This work is made available under the Creative Commons Attribution-Noncom- mercial-Sharealike 3.0 (CC-BY-NC-SA) license. See http://creativecommons.org/ licenses/by-nc-sa/3.0/ for details. (Alternate arrangements can be made with the copyright holder(s).) Additionally, modifications to this work must clearly be indicated as such, and the title page needs to carry the words “Modified Version” if any such modifications have been made, unless the release was done by the designated maintainer(s). The Maintainers are members of the Netfilter Core Team, and any person(s) appointed as maintainer(s) by the coreteam.
    [Show full text]
  • List Software Pengganti Windows Ke Linux
    Tabel Padanan Aplikasi Windows di Linux Untuk Migrasi Selasa, 18-08-2009 Kesulitan besar dalam melakukan migrasi dari Windows ke Linux adalah mencari software pengganti yang berkesesuaian. Berikut ini adalah tabel padanan aplikasi Windows di Linux yang disusun dalam beberapa kategori. Nama Program Windows Linux 1) Networking. 1) Netscape / Mozilla. 2) Galeon. 3) Konqueror. 4) Opera. [Prop] Internet Explorer, 5) Firefox. Web browser Netscape / Mozilla, Opera 6) Nautilus. [Prop], Firefox, ... 7) Epiphany. 8) Links. (with "-g" key). 9) Dillo. 10) Encompass. 1) Links. 1) Links 2) ELinks. Console web browser 2) Lynx 3) Lynx. 3) Xemacs + w3. 4) w3m. 5) Xemacs + w3. 1) Evolution. 2) Netscape / Mozilla/Thunderbird messenger. 3) Sylpheed / Claws Mail. 4) Kmail. Outlook Express, 5) Gnus. Netscape / Mozilla, 6) Balsa. Thunderbird, The Bat, 7) Bynari Insight GroupWare Suite. Email client Eudora, Becky, Datula, [Prop] Sylpheed / Claws Mail, 8) Arrow. Opera 9) Gnumail. 10) Althea. 11) Liamail. 12) Aethera. 13) MailWarrior. 14) Opera. 1) Evolution. Email client / PIM in MS 2) Bynari Insight GroupWare Suite. Outlook Outlook style [Prop] 3) Aethera. 4) Sylpheed. 5) Claws Mail 1) Sylpheed. 2) Claws Mail Email client in The Bat The Bat 3) Kmail. style 4) Gnus. 5) Balsa. 1) Pine. [NF] 2) Mutt. Mutt [de], Pine, Pegasus, Console email client 3) Gnus. Emacs 4) Elm. 5) Emacs. 1) Knode. 2) Pan. 1) Agent [Prop] 3) NewsReader. 2) Free Agent 4) Netscape / Mozilla Thunderbird. 3) Xnews 5) Opera [Prop] 4) Outlook 6) Sylpheed / Claws Mail. 5) Netscape / Mozilla Console: News reader 6) Opera [Prop] 7) Pine. [NF] 7) Sylpheed / Claws Mail 8) Mutt.
    [Show full text]
  • The Nftables Tutorial
    The nftables tutorial Patrick McHardy Pablo Neira Ayuso <[email protected]> <[email protected]> Netdev 0.1 February 2015 Ottawa, Canada Proceedings of netdev 0.1, Feb 14-17, 2015, Ottawa, On, Canada What is nftables? ● New packet classification framework to replace {ip,ip6,arp,eb}tables based on lessons learnt. ● nftables was presented in Netfilter Workshop 2008 (Paris, France) and released in March 2009 by Patrick McHardy. ● Merged mainstream in October 2013, available since January 2014 in Linux kernel 3.13. ● It reuses the existing Netfilter building blocks: hooks, conntrack, NAT, logging and userspace queueing. ● We also reuse existing xtables extensions through nft compat. Proceedings of netdev 0.1, Feb 14-17, 2015, Ottawa, On, Canada Why nftables? ● Address iptables architectural design problems: – From kernelspace: ● Avoid code duplication – Four families (arp, ip, ip6, bridge) derivated from the original iptables codebase. – Very similar extensions to match protocol fields and metadata. ● Netlink API (including event notifications) ● Better dynamic/incremental updates support ● Linear ruleset evaluation: Generic set infrastructure allowing dictionaries. – From userspace: ● New command line tool (with improved new syntax): nft ● Proper userspace libraries for third party software Proceedings of netdev 0.1, Feb 14-17, 2015, Ottawa, On, Canada nftables source & documentation ● Grab the code ● Kernel: – http://www.kernel.org – http://git.kernel.org/cgit/linux/kernel/git/pablo/nf-next.git ● Library: git://git.netfilter.org/libnftnl
    [Show full text]
  • Migration from Windows to Linux for a Small Engineering Firm "A&G Associates"
    Rochester Institute of Technology RIT Scholar Works Theses 2004 Migration from Windows to Linux for a small engineering firm "A&G Associates" Trimbak Vohra Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Vohra, Trimbak, "Migration from Windows to Linux for a small engineering firm A&G" Associates"" (2004). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" (H ' _T ^^L. WBBmBmBBBBmb- Windows Linux by Trimbak Vohra Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Information Technology Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Date: December 2, 2004 12/B2/28B2 14:46 5854752181 RIT INFORMATION TECH PAGE 02 Rochester Institute of Teehnology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Trimbak Vohra Thesis Title: Migration from Windows to Unux for a Small Engineeriog Firm "A&G Associates" Thesis Committee Name Signature Date Luther Troell luther IrQell, Ph.D ttL ",j7/Uy Chair G. L. Barido Prof. ~~orge Barido ? - Dec:. -cl7' Committee Member Thomas Oxford Mr. Thomas OxfocQ \ 2. L~( Q~ Committee Member Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" I,Trimbak Vohra, hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part.
    [Show full text]