DOCSLIB.ORG

Openflow, in Proceedings of the Interna- Tional Conference on Pervasive Computing and Communication Workshops (Percom Workshops)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Traffic Control for Multi-homed End-hosts via Software Defined Networking Anees Mohsin Hadi Al-Najjar B.Sc. (Computer Science), M.Sc. (Computer Science) A thesis submitted for the degree of Doctor of Philosophy at The University of Queensland in 2019 School of Information Technology & Electrical Engineering Abstract Software Defined Networking (SDN) is an emerging technology that allows computer networks to be more efficiently managed and controlled by providing a high level of abstraction and network programmability. Having powerful abstractions and pro- grammability via a centralised network controller provides new potential improve- ments to computer networks, such as easier network management, faster innovation and reduced cost. SDN has been successfully applied in wide area and data centre networks, and has achieved a significant improvement in network performance and efficiency. However, using SDN to control network traffic in end-host devices has not been investigated thoroughly. The research presented in this thesis aims to address this gap and inves- tigates the potential benefits of SDN for end-hosts. This thesis explores the feasibility of applying the SDN methodology to control network traffic on multi-homed end de- vices. The objective was to create a control mechanism by changing the network stack on the client in a way that is transparent to the application layer, the network infras- tructure, and other hosts on the network. In contrast to other solutions such as MPTCP, which require a protocol stack upgrade on all the participating nodes, the approach presented in this thesis allows quick and easy client-side-only deployment. This thesis presents an architecture for embedding SDN components, i.e. the SDN controller and switch, on multi-homed devices, and its use for traffic control. The simultaneous use of multiple network interfaces was explored and utilised for the im- plementation and evaluation of various load balancing algorithms. In order to do effective load balancing, it is important to know the state of the various host interfaces and related links, in particular the link capacity. To enable this, the thesis also presents an approach to monitor and measure link capacity, which is tightly integrated with the SDN traffic control architecture. For this purpose, the method of Variable Packet size (VPS) probing was adapted to work in the SDN context on end- hosts. The approach of SDN-based traffic control and load balancing was extensively evalu- ated for two specific use cases, web traffic and Voice over IP (VoIP), considering differ- i ent transport layer protocols. Our experimental evaluation has shown the feasibility of the proposed method, and has demonstrated its potential for improving the Quality of Experience (QoE) for end-users. The experiments have shown that our SDN-based approach can even outperform MPTCP, even though MPTCP has the advantage of controlling both end points of the communication. ii Declaration by author This thesis is composed of my original work, and contains no material previously pub- lished or written by another person except where due reference has been made in the text. I have clearly stated the contribution by others to jointly-authored works that I have included in my thesis. I have clearly stated the contribution of others to my thesis as a whole, including sta- tistical assistance, survey design, data analysis, significant technical procedures, pro- fessional editorial advice, financial support and any other original research work used or reported in my thesis. The content of my thesis is the result of work I have car- ried out since the commencement of my higher degree by research candidature and does not include a substantial part of work that has been submitted to qualify for the award of any other degree or diploma in any university or other tertiary institution. I have clearly stated which parts of my thesis, if any, have been submitted to qualify for another award. I acknowledge that an electronic copy of my thesis must be lodged with the University Library and, subject to the policy and procedures of The University of Queensland, the thesis be made available for research and study in accordance with the Copyright Act 1968 unless a period of embargo has been approved by the Dean of the Graduate School. I acknowledge that copyright of all material contained in my thesis resides with the copyright holder(s) of that material. Where appropriate I have obtained copyright per- mission from the copyright holder to reproduce material in this thesis and have sought permission from co-authors for any jointly authored works included in the thesis. iii Publications during candidature [1] Anees Al-Najjar, Siamak Layeghy, and Marius Portmann, Pushing SDN to the End-host, Network Load Balancing using OpenFlow, in Proceedings of the Interna- tional Conference on Pervasive Computing and Communication Workshops (PerCom Workshops). IEEE, 2016, pp. 1−6. [2] Anees Al-Najjar, Farzaneh Pakzad, Siamak Layeghy, and Marius Portmann, Link Capacity Estimation in SDN-based End-hosts, in Proceedings of the 10th Interna- tional Conference on Signal Processing and Communication Systems (ICSPCS). IEEE, 2016, pp. 1−8. [3] Anees Al-Najjar, Samuel Teed, Jadwiga Indulska, and Marius Portmann, Flow- based Load Balancing of Web Traffic using OpenFlow, in Proceedings of the 27th International Telecommunication Networks and Applications Conference (ITNAC). IEEE, 2017, pp. 1−6. [4] Anees Al-Najjar, Siamak Layeghy, Marius Portmann, and Jadwiga Indulska, Enhancing Quality of Experience of VoIP Traffic in SDN based End-hosts, in Proceedings of the 28th International Telecommunication Networks and Applications Conference (ITNAC). IEEE, 2018, pp. 1−8. [5] Anees Al-Najjar, Marius Portmann, Siamak Layeghy, and Jadwiga Indulska, Flow-level Load Balancing of HTTP Traffic using OpenFlow, Australian Journal of Telecommunications and the Digital Economy, vol. 6, pp. 75-95, 2018. iv Publications included in this thesis [1] Anees Al-Najjar, Siamak Layeghy, and Marius Portmann, Pushing SDN to the End- host, Network Load Balancing using OpenFlow, in Proceedings of the International Conference on Pervasive Computing and Communication Workshops (PerCom Work- shops). IEEE, 2016, pp. 1−6. Contributor Statement of contribution Author Anees Al-Najjar (Candidate) Conception and design (90%) Analysis and interpretation (90%) Drafting and production (85%) Author Siamak Layeghy Drafting and production (5%) Author Marius Portmann Conception and design (10%) Analysis and interpretation (10%) Drafting and production (10%) [2] Anees Al-Najjar, Farzaneh Pakzad, Siamak Layeghy, and Marius Portmann, Link Capacity Estimation in SDN-based End-hosts, in Proceedings of the 10th Interna- tional Conference on Signal Processing and Communication Systems (ICSPCS). IEEE, 2016, pp. 1−8. Contributor Statement of contribution Author Anees Al-Najjar (Candidate) Conception and design (90%) Analysis and interpretation (90%) Drafting and production (85%) Author Farzaneh Pakzad Drafting and production (5%) Author Siamak Layeghy Drafting and production (5%) Author Marius Portmann Conception and design (10%) Analysis and interpretation (10%) Drafting and production (5%) v [3] Anees Al-Najjar, Samuel Teed, Jadwiga Indulska, and Marius Portmann, Flow- based Load Balancing of Web Traffic using OpenFlow, in Proceedings of the 27th International Telecommunication Networks and Applications Conference (ITNAC). IEEE, 2017, pp. 1−6. Contributor Statement of contribution Author Anees Al-Najjar (Candidate) Conception and design (90%) Analysis and interpretation (85%) Drafting and production (85%) Author Samuel Teed Conception and design (5%) Author Jadwiga Indulska Analysis and interpretation (5%) Drafting and production (5%) Author Marius Portmann Conception and design(5%) Analysis and interpretation (10%) Drafting and production (10%) [4] Anees Al-Najjar, Siamak Layeghy, Marius Portmann, and Jadwiga Indulska, En- hancing Quality of Experience of VoIP Traffic in SDN based End-hosts, in Proceed- ings of the 28th International Telecommunication Networks and Applications Confer- ence (ITNAC). IEEE, 2018, pp. 1−8. Contributor Statement of contribution Author Anees Al-Najjar (Candidate) Conception and design (95%) Analysis and interpretation (90%) Drafting and production (80%) Author Siamak Layeghy Drafting and production (10%) Author Marius Portmann Conception and design (5%) Analysis and interpretation (5%) Drafting and production (5%) Author Jadwiga Indulska Analysis and interpretation (5%) Drafting and production (5%) vi [5] Anees Al-Najjar, Marius Portmann, Siamak Layeghy, and Jadwiga Indulska, Flow-level Load Balancing of HTTP Traffic using OpenFlow, Australian Journal of Telecommunications and the Digital Economy, vol. 6, pp. 75-95, 2018. Contributor Statement of contribution Author Anees Al-Najjar (Candidate) Conception and design (95%) Analysis and interpretation (90%) Drafting and production (80%) Author Siamak Layeghy Drafting and production (5%) Analysis and interpretation(5%) Author Marius Portmann Conception and design (5%) Analysis and interpretation (5%) Drafting and production (10%) Author Jadwiga Indulska Drafting and production (5%) vii Contributions by others to the thesis A/Prof Marius Portmann and Prof Jadwiga Indulska provided valuable guidance and feedback during conducting this research and contributed in the conception, design, interpretation and drafting parts of the work. Statement of parts of the thesis submitted to qualify for the award of another degree
Recommended publications
  • Microsoft Network Load Balancing

    Microsoft Network Load Balancing

    Ethernet Routing Switch Engineering > Technical Configuration Guide for Microsoft Network Load Balancing Avaya Data Solutions Document Date: June 2010 Document Number: NN48500-593 Document Version: 3.0 avaya.com Abstract The document provides an overview on how to configure Nortel Ethernet & Ethernet Routing Switches to support Microsoft’s Network Load Balancing (NLB) server clustering technology. Avaya Inc. – Proprietary & Confidential. 1 Use pursuant to the terms of your signed agreement or Avaya policy. avaya.com Table of Contents DOCUMENT UPDATES ............................................................................................................................. 4 CONVENTIONS .......................................................................................................................................... 4 1. OVERVIEW: NETWORK LOAD BALANCING ........................................................................... 5 1.1 ARCHITECTURE .............................................................................................................................. 6 1.2 OPERATION .................................................................................................................................... 7 1.3 LOAD BALANCING ALGORITHM ................................................................................................... 11 1.4 CONVERGENCE ............................................................................................................................ 11 1.5 MAC ADDRESS FORMATS ..........................................................................................................
  • Catalyst Switches for Microsoft Network Load Balancing Configuration Example

    Catalyst Switches for Microsoft Network Load Balancing Configuration Example

    Catalyst Switches for Microsoft Network Load Balancing Configuration Example Document ID: 107995 Contributed by Shashank Singh, Cisco TAC Engineer. Dec 19, 2013 Contents Introduction Prerequisites Requirements Components Used Background Information Unicast Mode Multicast Mode Configure Network Diagram Configurations Verify Troubleshoot Related Information Introduction This document describes how to configure Cisco Catalyst switches to interact with Microsoft Network Load Balancing (NLB). Prerequisites Requirements There are no specific requirements for this document. Components Used The information in this document is based on these software and hardware versions: • Catalyst 6500 switch which runs Cisco IOS® Software • Catalyst 4500 switch which runs Cisco IOS Software • Catalyst 3550 switch which runs Cisco IOS Software • Catalyst 3560 switch which runs Cisco IOS Software • Catalyst 3750 switch which runs Cisco IOS Software • Microsoft Windows 2000/2003 Servers The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Background Information NLB technology can be used to distribute client requests across a set of servers. In order to make sure clients always experience acceptable performance levels, Windows NLB is often used to ensure that you can add additional servers to scale out stateless applications, such as IIS−based web servers, as client load increases. In addition, it reduces downtime caused by servers that malfunction. End users will never know that a particular member server in the Windows NLB is or has been down. Network Load Balancing is a clustering technology offered by Microsoft as part of all Windows 2000 Server and Windows Server 2003 family operating systems.
  • Technical Configuration Guide for Microsoft Network Load Balancing

    Technical Configuration Guide for Microsoft Network Load Balancing

    Ethernet Routing Switch Virtual Services Platform Engineering > Technical Configuration Guide for Microsoft Network Load Balancing Avaya Data Solutions Document Date: February 2014 Document Number: NN48500-593 Document Version: 4.4 avaya.com © 2014 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product.
  • (IP) Addressing and Protocols Feature Overview and Configuration Guide

    (IP) Addressing and Protocols Feature Overview and Configuration Guide

    Technical Guide Internet Protocol (IP) Addressing and Protocols Feature Overview and Configuration Guide Introduction This guide describes how to configure IPv4 addressing and the protocols used to help IP function on your network. As well as the familiar Internet (with uppercase “I”), the term internet (with lowercase “i”) can refer to any network (usually a wide area network) that uses the Internet Protocol. This guide concentrates on this definition—a generalized network that uses IP as its network protocol. Products and software version that apply to this guide This guide applies to all AlliedWare Plus™ products, running version 5.4.4 or later. However, feature support and implementation varies between products. To see whether a product supports a particular feature or command, see the following documents: The product’s Datasheet The AlliedWare Plus Datasheet The product’s Command Reference These documents are available from the above links on our website at alliedtelesis.com. Feature support may change in later software versions. For the latest information, see the above documents. C613-22007-00 REV I alliedtelesis.com Internet Protocol (IP) Addressing and Protocols Content Introduction .........................................................................................................................................1 Products and software version that apply to this guide ...............................................................1 Assigning an IP Address .....................................................................................................................3
  • Ipv6 for Helenos

    Ipv6 for Helenos

    Charles University in Prague Faculty of Mathematics and Physics MASTER THESIS Mgr. Bc. Anton´ınSteinhauser IPv6 for HelenOS Department of Distributed and Dependable Systems Supervisor of the master thesis: Mgr. Martin Dˇeck´y Study programme: Informatics Specialization: Software Systems Prague 2013 I am much obliged to my thesis supervisor, Mgr. Martin Dˇeck´y,for his advices and hints in this research. I declare that I carried out this master thesis independently, and only with the cited sources, literature and other professional sources. I understand that my work relates to the rights and obligations under the Act No. 121/2000 Coll., the Copyright Act, as amended, in particular the fact that the Charles University in Prague has the right to conclude a license agreement on the use of this work as a school work pursuant to Section 60 paragraph 1 of the Copyright Act. In Prague date 18. 7. 2013 Anton´ınSteinhauser N´azevpr´ace:IPv6 for HelenOS Autor: Anton´ınSteinhauser Katedra: Katedra distribuovan´ych a spolehliv´ych syst´em˚u Vedouc´ıdiplomov´epr´ace: Mgr. Martin Dˇeck´y,Katedra distribuovan´ych a spolehliv´ych syst´em˚u Abstrakt: Tato pr´acerozˇsiˇrujeoperaˇcn´ısyst´emHelenOS o podporu nov´ehoIPv6 protokolu. Implementace protokolu IPv6 je na stejn´e´urovni jako dˇr´ıvˇejˇs´ıimple- mentace IPv4 protokolu. S´ıˇtov´ystack HelenOS nyn´ınab´ız´ıtˇrim´odypr´acese s´ıt´ı: uˇz´ıv´an´ıpouze IPv4 protokolu, uˇz´ıv´an´ıpouze IPv6 protokolu a du´aln´ım´od, kter´y umoˇzˇnujepouˇz´ıvat oba protokoly najednou. Pr´acepopisuje pˇredchoz´ıstav s´ıˇtov´ehostacku HelenOS, analyzuje rozd´ılymezi IPv4 protokolem a IPv6 protokolem a zd˚uvodˇnujejednotliv´astrategick´arozhod- nut´ı.
  • Shelf Manager User Guide (May 15, 2018) Page 1 / 321

    Shelf Manager User Guide (May 15, 2018) Page 1 / 321

    User Guide Pigeon Point Shelf Manager Release 3.7.1 May 15, 2018 nVent Schroff GmbH [email protected] www.pigeonpoint.com schroff.nVent.com This document is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by nVent. nVent assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, manual, recording, or otherwise, without the prior written permission of nVent. The Pigeon Point Shelf Manager uses an implementation of the MD5 Message-Digest algorithm that is derived from the RSA Data Security, Inc. MD5 Message-Digest algorithm. All nVent marks and logos are owned or licensed by nVent Services GmbH or its affiliates. All other trademarks are the property of their respective owners. nVent reserves the right to change specifications without notice. Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 1 / 321 Table of contents 1 About this document 9 1.1 Shelf Manager documentation 9 1.1.1 Conventions used in this document 9 1.2 Additional resources 10 2 Introduction 11 2.1 In this section 11 2.2 Intelligent Platform Management: an ATCA overview 11 2.3 Pigeon Point Board Management Reference: hardware and firmware 14 2.4
  • Linux Audio Conference 2019

    Linux Audio Conference 2019

    Proceedings of the Linux Audio Conference 2019 March 23rd – 26th, 2019 Center for Computer Research in Music and Acoustics (CCRMA) Stanford University, USA “In Ping(uins) e trust! Published by CCRMA, Stanford University, California, US March 2019 All copyrights remain with the authors http://lac.linuxaudio.org/2019 ISBN 978-0-359-46387-9 Credits Layout: Frank Neumann and Romain Michon Typesetting: LATEX and pdfLaTeX Logo Design: The Linuxaudio.org logo and its variations copyright Thorsten Wilms c 2006, imported into "LAC 2014" logo by Robin Gareus Thanks to: Martin Monperrus for his webpage "Creating proceedings from PDF files" ii Partners and Sponsors Linuxaudio.org iii iv Foreword Welcome everyone to LAC 2019 at CCRMA! For the second time in its seventeen year history, the Linux Audio Conference (LAC) is hosted in the United Stated of America by the Center for Computer Research in Mu- sic and Acoustics (CCRMA) at Stanford University. With its informal workshop-like at- mosphere, LAC is a blend of scientific and technical papers, tutorials, sound installations, and concerts centered on the free GNU/Linux operating system and open-source free soft- ware for audio, multimedia, and musical applications. LAC is a unique platform during which members of this community gather to exchange ideas, draft new projects, and see old friends. In these times of increasing political tensions and of rising extremism throughout the world, we believe that emphasizing and promoting the universality of this type of event is of the utmost importance. The Linux audio community exists worldwide; we believe it should remain a priority to diversify LAC’s geographical location from year to year for the benefit of those who can’t afford to travel to the other side of the world.
  • Configuring Network Load Balancing

    Configuring Network Load Balancing

    cc01ConfiguringNetworkLoadBalancing.indd01ConfiguringNetworkLoadBalancing.indd PagePage 1 30/10/1430/10/14 4:494:49 PMPM useruser //208/WB01466/9781118882993/ch01/text_s208/WB01466/9781118882993/ch01/text_s Configuring Network LESSON 1 Load Balancing 70-412 EXAM OBJECTIVE Objective 1.1 – Configure Network Load Balancing (NLB). This objective may include but is not limited to: Install NLB nodes; configure NLB prerequisites; configure affinity; configure port rules; configure cluster operation mode; upgrade an NLB cluster. LESSON HEADING EXAM OBJECTIVE Understanding Fault Tolerance Configuring Network Load Balancing Configuring NLB Prerequisites Configure NLB prerequisites Installing NLB Nodes Install NLB nodes Configuring Port Rules Configure port rules Configuring Filtering Mode and Affinity Configure affinity Configuring Cluster Operation Mode Configure cluster operation mode Controlling Hosts in NLB Upgrading an NLB Cluster Upgrade an NLB cluster KEY TERMS affinity Internet Group Management Protocol port rules cluster Multicast mode stop action convergence multicastCOPYRIGHTED MATERIAL unicast drainstop multicast mode unicast mode filter mode Network Load Balancing (NLB) heartbeats node ■ Understanding Fault Tolerance When a server goes down, it most likely causes your company to lose money. If your network contains an external website or database that controls your sales, ordering, THE BOTTOM LINE inventory, or production, server downtime can be detrimental to these business needs. If it is an internal server, it might not allow your users to perform their jobs. In either case, your company loses money either through revenue or through productivity. 1 cc01ConfiguringNetworkLoadBalancing.indd01ConfiguringNetworkLoadBalancing.indd PagePage 2 30/10/1430/10/14 4:494:49 PMPM useruser //208/WB01466/9781118882993/ch01/text_s208/WB01466/9781118882993/ch01/text_s 2 | Lesson 1 As a server administrator, you need to minimize downtime by identifying potential fail- ures and taking steps to avoid those failures and to reduce their effects.
  • Protocols Support Equal Path Load Balancing

    Protocols Support Equal Path Load Balancing

    Protocols Support Equal Path Load Balancing Appassionato and easeful Hailey corrode some personalist so unmercifully! Shannon often strops fancifully when antitank Waine harasses vastly and underestimates her scorn. Walled Anatol placards her katydids so flaccidly that Adrick deliver very drastically. Description on their own ip address families by leveraging bgp path load balancing One is Cisco proprietary PAgP Port Aggregation Protocol. ECMP load balancing is done bring the session level quality at the packet levelthe start consult a. Load-balancing up you should likely know NETMANIAS. Command shows which path load balancing possible due to equal cost load balancing, protocols except for training course was using ip. Universal algorithm The universal load-balancing algorithm allows each router. Dual Internet Design Part 2 Load Balancing Network David. In this diagram R3 has two paths to the 1921612024 a fast ethernet link. Protocol MLPPP link groups use manual-robin to transmit packets so much load. How are load balancing work with World. Cisco devices support two versions of Routing Information Protocol RIP RIP. Using the flat Cost the Path ECMP. One inspire the ways Avi Vantage can save load balancing capacity among a virtual universe is to. Core switches via 2 separate L3 links which should we load-balanced. Equal-Cost Multi-Path ECMP Routing Chapter Static. Virtual can Network Load Balancing Using OSPF Routing. If two routes from them same protocol are unequal only have best query is. The mine with chip-packet load balancing is bright when packets 1 3 and 4. Description In the ribd routing protocol model the maximum-paths ecmp.
  • Technical Configuration Guide for Microsoft Network Load Balancing

    Technical Configuration Guide for Microsoft Network Load Balancing

    Ethernet Routing Switch Virtual Services Platform Engineering > Technical Configuration Guide for Microsoft Network Load Balancing Avaya Data Solutions Document Date: August 2012 Document Number: NN48500-593 Document Version: 4.2 avaya.com © 2012 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product.
  • Module 8: Concepts of a Network Load Balancing Cluster

    Module 8: Concepts of a Network Load Balancing Cluster

    Module 8: Concepts of A Network Load Balancing Cluster Contents Overview 1 Network Load Balancing Concepts 2 Application and Service Environment 8 Network Load Balancing Functionality 12 Network Load Balancing Architecture 19 Lab A: Planning an Installation 31 Review 36 Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2000 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BackOffice, Jscript, PowerPoint, Visual Basic, Visual Studio, Win32, Windows, Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
  • WM PAN9420 Software Guide.Pdf

    WM PAN9420 Software Guide.Pdf

    PAN9420 Software Guide Rev. 1.0 Wireless Modules PAN9420 Wi-Fi Module By purchase of any of the products described in this document the customer accepts the document's validity and declares their agreement and understanding of its contents and recommendations. Panasonic Industrial Devices Europe GmbH (Panasonic) reserves the right to make changes as required at any time without notification. © Panasonic Industrial Devices Europe GmbH 2019. This document is copyrighted. Reproduction of this document is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Do not disclose it to a third party. All rights reserved. This Software Guide does not lodge the claim to be complete and free of mistakes. The information contained herein is presented only as guidance for Product use. No responsibility is assumed by Panasonic for any infringement of patents or any other intellectual property rights of third parties that may result from the use of Product. No license to any intellectual property right is granted by this document, whether express or implied, by estoppel or otherwise. Description of hardware, software, and other information in this document is only intended to illustrate the functionality of the referred Panasonic product. It should not be construed as guaranteeing specific functionality of the product as described or suitable for a particular application. Any provided (source) code shall not be used or incorporated into any products or systems whose manufacture, use or sale is prohibited under any applicable laws or regulations. Any outlined or referenced (source) code within this document is provided on an “as is” basis without any right to technical support or updates and without warranty of any kind on a free of charge basis according to § 516 German Civil Law (BGB) including without limitation, any warranties or conditions of title, non-infringement, merchantability, or fitness for a particular purpose.