DOCSLIB.ORG

Using Silk for Network Traffic Analysis: Analysts' Handbook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using Silk for Network Traffic Analysis: Analysts' Handbook Analysis with SiLK Analyst’s Handbook for SiLK Version 3.15.0 and Later AUGUST 2020 Paul Krystosek Nancy Ott Timothy Shimeall CERT® Situational Awareness Group Network Traffic Analysis with SiLK Analyst’s Handbook for SiLK Versions 3.15.0 and Later Paul Krystosek Nancy M. Ott Geoffrey Sanders Timothy Shimeall August 2020 CERT® Situational Awareness Group [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. https://www.sei.cmu.edu Copyright 2020 Carnegie Mellon University. All Rights Reserved. This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trade mark, manu- facturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100 NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING IN- STITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MAT- TER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MER- CHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited dis- tribution. Please see Copyright notice for non-US Government use and distribution. Internal use:* Permission to reproduce this material and to prepare derivative works from this material for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. External use:* This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at [email protected]. * These restrictions do not apply to U.S. government entities. Carnegie Mellon®, CERT®, CERT Coordination Center® and FloCon® are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University. DM20-0675 SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY ii [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Adobe is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries. Akamai is a registered trademark of Akamai Technologies, Inc. Apple and OS X are trademarks of Apple Inc., registered in the U.S. and other countries. Cisco Systems is a registered trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. DOCSIS is a registered trademark of CableLabs. FreeBSD is a registered trademark of the FreeBSD Foundation. IEEE is a registered trademark of The Institute of Electrical and Electronics Engineers, Inc. JABBER is a registered trademark and its use is licensed through the XMPP Standards Foundation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. MaxMind, GeoIP, GeoLite, and related trademarks are the trademarks of MaxMind, Inc. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. OpenVPN is a registered trademark of OpenVPN Technologies, Inc. Perl is a registered trademark of The Perl Foundation. Python is a registered trademark of the Python Software Foundation. SNORT is a registered trademark of Cisco and/or its affiliates. Solaris is a registered trademark of Oracle and/or its affiliates in the United States and other countries. UNIX is a registered trademark of The Open Group. VPNz is a registered trademark of Advanced Network Solutions, Inc. Wireshark is a registered trademark of the Wireshark Foundation. All other trademarks are the property of their respective owners. SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY iii [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. This page intentionally left blank. SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY iv [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Contents Contents v List of Figures xi List of Tables xiii List of Examples xv List of Hints xix Acknowledgements xxi Handbook Goals xxiii 1 Introduction to SiLK 1 1.1 What is SiLK? ............................................ 1 1.2 The SiLK Flow Repository ..................................... 2 1.2.1 What is Network Flow Data?................................ 2 1.2.2 Structure of a Flow Record................................. 3 1.2.3 Flow Generation and Collection............................... 3 1.2.4 Introduction to Flow Collection............................... 6 1.2.5 Where Network Flow Data Are Collected ......................... 6 1.2.6 Types of Network Traffic .................................. 7 1.2.7 The Collection System and Data Management ...................... 7 1.2.8 How Network Flow Data Are Organized.......................... 8 1.3 The SiLK Tool Suite......................................... 8 1.4 How to Use SiLK for Analysis.................................... 9 1.4.1 Single-path Analysis..................................... 9 1.4.2 Multi-path Analysis ..................................... 9 1.4.3 Exploratory Analysis..................................... 10 1.5 Workflow for SiLK Analysis..................................... 10 1.5.1 Formulate........................................... 10 1.5.2 Model............................................. 11 1.5.3 Test.............................................. 12 1.5.4 Analyze............................................ 12 1.5.5 Refine............................................. 12 1.6 Applying the SiLK Workflow .................................... 12 1.7 Avoiding Cognitive Biases...................................... 13 1.8 Dataset for Single-path, Multi-path, and Exploratory Analysis Examples............ 14 SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY v [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. CONTENTS 2 Basic Single-path Analysis with SiLK: Profiling and Reacting 17 2.1 Single-path Analysis: Concepts................................... 17 2.1.1 Scoping Queries of Network Flow Data........................... 18 2.1.2 Excluding Unwanted Network Traffic............................ 19 2.1.3 Example Single-Path Analysis................................ 19 2.2 Single-path Analysis: Analytics................................... 19 2.2.1 Get a List of Sensors With rwsiteinfo .......................... 19 2.2.2 Choose Flow Records With rwfilter ........................... 23 2.2.3 View Flow Records With rwcut .............................. 27 2.2.4 Viewing File Information with rwfileinfo ........................ 29 2.2.5 Profile Flows With rwuniq and rwstats .......................... 31 2.2.6 Characterize Traffic by Time Period With rwcount .................... 39 2.2.7 Sort Flow Records With rwsort .............................. 41 2.2.8 Use IPsets to Gather IP Addresses............................. 43 2.2.9 Resolve IP Addresses to Domain Names With rwresolve . 47 2.3 Situational Awareness and Single-Path Analysis.......................... 51 2.3.1 Components of Situational Awareness ........................... 51 2.3.2 Single-Path Analysis for Desired Awareness: Validate Web and DNS Servers . 52 2.3.3 Single-Path Analysis for Actual Awareness: Examine Network Traffic.......... 54 2.3.4 Translate IDS Signatures into rwfilter Calls with rwidsquery . 57 2.4 Summary of SiLK Commands in Chapter 2 ............................ 58 3 Case Studies: Basic Single-path Analysis 59 3.1 Profile Traffic Around an Event................................... 59 3.1.1 Examining Shifts in Traffic ................................. 60 3.1.2 How to Profile Traffic .................................... 61 3.2 Generate Top N Lists ........................................ 63 3.2.1 Using rwstats to Create Top N Lists ........................... 63 3.2.2 Interpreting the Top-N Lists ................................ 66 4 Intermediate Multi-path Analysis with SiLK: Explaining and Investigating 69 4.1 Multi-path Analysis: Concepts ................................... 69 4.1.1 What Is Multi-path Analysis?................................ 69 4.1.2 Example of a Multi-path Analysis: Examining Web Service Traffic........... 71 4.1.3 Exploring Relationships and Behaviors With Multi-path Analysis............ 73 4.1.4 Integrating and Interpreting the Results of Multi-path Analysis............. 73 4.1.5 “Gotchas” for Multi-path Analysis............................. 74 4.2 Multi-path Analysis: Analytics
Load more

Recommended publications
  • At—At, Batch—Execute Commands at a Later Time
    at—at, batch—execute commands at a later time at [–csm] [–f script] [–qqueue] time [date] [+ increment] at –l [ job...] at –r job... batch at and batch read commands from standard input to be executed at a later time. at allows you to specify when the commands should be executed, while jobs queued with batch will execute when system load level permits. Executes commands read from stdin or a file at some later time. Unless redirected, the output is mailed to the user. Example A.1 1 at 6:30am Dec 12 < program 2 at noon tomorrow < program 3 at 1945 pm August 9 < program 4 at now + 3 hours < program 5 at 8:30am Jan 4 < program 6 at -r 83883555320.a EXPLANATION 1. At 6:30 in the morning on December 12th, start the job. 2. At noon tomorrow start the job. 3. At 7:45 in the evening on August 9th, start the job. 4. In three hours start the job. 5. At 8:30 in the morning of January 4th, start the job. 6. Removes previously scheduled job 83883555320.a. awk—pattern scanning and processing language awk [ –fprogram–file ] [ –Fc ] [ prog ] [ parameters ] [ filename...] awk scans each input filename for lines that match any of a set of patterns specified in prog. Example A.2 1 awk '{print $1, $2}' file 2 awk '/John/{print $3, $4}' file 3 awk -F: '{print $3}' /etc/passwd 4 date | awk '{print $6}' EXPLANATION 1. Prints the first two fields of file where fields are separated by whitespace. 2. Prints fields 3 and 4 if the pattern John is found.
    [Show full text]
  • Unix Introduction
    Unix introduction Mikhail Dozmorov Summer 2018 Mikhail Dozmorov Unix introduction Summer 2018 1 / 37 What is Unix Unix is a family of operating systems and environments that exploits the power of linguistic abstractions to perform tasks Unix is not an acronym; it is a pun on “Multics”. Multics was a large multi-user operating system that was being developed at Bell Labs shortly before Unix was created in the early ’70s. Brian Kernighan is credited with the name. All computational genomics is done in Unix http://www.read.seas.harvard.edu/~kohler/class/aosref/ritchie84evolution.pdfMikhail Dozmorov Unix introduction Summer 2018 2 / 37 History of Unix Initial file system, command interpreter (shell), and process management started by Ken Thompson File system and further development from Dennis Ritchie, as well as Doug McIlroy and Joe Ossanna Vast array of simple, dependable tools that each do one simple task Ken Thompson (sitting) and Dennis Ritchie working together at a PDP-11 Mikhail Dozmorov Unix introduction Summer 2018 3 / 37 Philosophy of Unix Vast array of simple, dependable tools Each do one simple task, and do it really well By combining these tools, one can conduct rather sophisticated analyses The Linux help philosophy: “RTFM” (Read the Fine Manual) Mikhail Dozmorov Unix introduction Summer 2018 4 / 37 Know your Unix Unix users spend a lot of time at the command line In Unix, a word is worth a thousand mouse clicks Mikhail Dozmorov Unix introduction Summer 2018 5 / 37 Unix systems Three common types of laptop/desktop operating systems: Windows, Mac, Linux. Mac and Linux are both Unix-like! What that means for us: Unix-like operating systems are equipped with “shells”" that provide a command line user interface.
    [Show full text]
  • Linux Commands Cheat Sheet
    LINUX COMMANDS CHEAT SHEET System File Permission uname => Displays Linux system information chmod octal filename => Change file permissions of the file to octal uname -r => Displays kernel release information Example uptime => Displays how long the system has been running including chmod 777 /data/test.c => Set rwx permissions to owner, group and everyone (every- load average one else who has access to the server) hostname => Shows the system hostname chmod 755 /data/test.c => Set rwx to the owner and r_x to group and everyone hostname -i => Displays the IP address of the system chmod 766 /data/test.c => Sets rwx for owner, rw for group and everyone last reboot => Shows system reboot history chown owner user-file => Change ownership of the file date => Displays current system date and time chown owner-user: owner-group => Change owner and group owner of the file timedatectl => Query and change the System clock file_name chown owner-user:owner-group- => Change owner and group owner of the directory cal => Displays the current calendar month and day directory w => Displays currently logged in users in the system whoami => Displays who you are logged in as Network finger username => Displays information about the user ip addr show => Displays IP addresses and all the network interfaces Hardware ip address add => Assigns IP address 192.168.0.1 to interface eth0 192.168.0.1/24 dev eth0 dmesg => Displays bootup messages ifconfig => Displays IP addresses of all network interfaces cat /proc/cpuinfo => Displays more information about CPU e.g model, model name, cores, vendor id ping host => ping command sends an ICMP echo request to establish a connection to server / PC cat /proc/meminfo => Displays more information about hardware memory e.g.
    [Show full text]
  • Chapter 19 RECOVERING DIGITAL EVIDENCE from LINUX SYSTEMS
    Chapter 19 RECOVERING DIGITAL EVIDENCE FROM LINUX SYSTEMS Philip Craiger Abstract As Linux-kernel-based operating systems proliferate there will be an in­ evitable increase in Linux systems that law enforcement agents must process in criminal investigations. The skills and expertise required to recover evidence from Microsoft-Windows-based systems do not neces­ sarily translate to Linux systems. This paper discusses digital forensic procedures for recovering evidence from Linux systems. In particular, it presents methods for identifying and recovering deleted files from disk and volatile memory, identifying notable and Trojan files, finding hidden files, and finding files with renamed extensions. All the procedures are accomplished using Linux command line utilities and require no special or commercial tools. Keywords: Digital evidence, Linux system forensics !• Introduction Linux systems will be increasingly encountered at crime scenes as Linux increases in popularity, particularly as the OS of choice for servers. The skills and expertise required to recover evidence from a Microsoft- Windows-based system, however, do not necessarily translate to the same tasks on a Linux system. For instance, the Microsoft NTFS, FAT, and Linux EXT2/3 file systems work differently enough that under­ standing one tells httle about how the other functions. In this paper we demonstrate digital forensics procedures for Linux systems using Linux command line utilities. The ability to gather evidence from a running system is particularly important as evidence in RAM may be lost if a forensics first responder does not prioritize the collection of live evidence. The forensic procedures discussed include methods for identifying and recovering deleted files from RAM and magnetic media, identifying no- 234 ADVANCES IN DIGITAL FORENSICS tables files and Trojans, and finding hidden files and renamed files (files with renamed extensions.
    [Show full text]
  • “Linux at the Command Line” Don Johnson of BU IS&T  We’Ll Start with a Sign in Sheet
    “Linux at the Command Line” Don Johnson of BU IS&T We’ll start with a sign in sheet. We’ll end with a class evaluation. We’ll cover as much as we can in the time allowed; if we don’t cover everything, you’ll pick it up as you continue working with Linux. This is a hands-on, lab class; ask questions at any time. Commands for you to type are in BOLD The Most Common O/S Used By BU Researchers When Working on a Server or Computer Cluster Linux is a Unix clone begun in 1991 and written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. 64% of the world’s servers run some variant of Unix or Linux. The Android phone and the Kindle run Linux. a set of small Linux is an O/S core programs written by written by Linus Richard Stallman and Torvalds and others others. They are the AND GNU utilities. http://www.gnu.org/ Network: ssh, scp Shells: BASH, TCSH, clear, history, chsh, echo, set, setenv, xargs System Information: w, whoami, man, info, which, free, echo, date, cal, df, free Command Information: man, info Symbols: |, >, >>, <, ;, ~, ., .. Filters: grep, egrep, more, less, head, tail Hotkeys: <ctrl><c>, <ctrl><d> File System: ls, mkdir, cd, pwd, mv, touch, file, find, diff, cmp, du, chmod, find File Editors: gedit, nedit You need a “xterm” emulation – software that emulates an “X” terminal and that connects using the “SSH” Secure Shell protocol. ◦ Windows Use StarNet “X-Win32:” http://www.bu.edu/tech/support/desktop/ distribution/xwindows/xwin32/ ◦ Mac OS X “Terminal” is already installed Why? Darwin, the system on which Apple's Mac OS X is built, is a derivative of 4.4BSD-Lite2 and FreeBSD.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
    [Show full text]
  • Praat Scripting Tutorial
    Praat Scripting Tutorial Eleanor Chodroff Newcastle University July 2019 Praat Acoustic analysis program Best known for its ability to: Visualize, label, and segment audio files Perform spectral and temporal analyses Synthesize and manipulate speech Praat Scripting Praat: not only a program, but also a language Why do I want to know Praat the language? AUTOMATE ALL THE THINGS Praat Scripting Why can’t I just modify others’ scripts? Honestly: power, flexibility, control Insert: all the gifs of ‘you can do it’ and ‘you got this’ and thumbs up Praat Scripting Goals ~*~Script first for yourself, then for others~*~ • Write Praat scripts quickly, effectively, and “from scratch” • Learn syntax and structure of the language • Handle various input/output combinations Tutorial Overview 1) Praat: Big Picture 2) Getting started 3) Basic syntax 4) Script types + Practice • Wav files • Measurements • TextGrids • Other? Praat: Big Picture 1) Similar to other languages you may (or may not) have used before • String and numeric variables • For-loops, if else statements, while loops • Regular expression matching • Interpreted language (not compiled) Praat: Big Picture 2) Almost everything is a mouse click! i.e., Praat is a GUI scripting language GUI = Graphical User Interface, i.e., the Objects window If you ever get lost while writing a Praat script, click through the steps using the GUI Getting Started Open a Praat script From the toolbar, select Praat à New Praat script Save immediately! Save frequently! Script Goals and Input/Output • Consider what
    [Show full text]
  • Deviceinstaller User Guide
    Device Installer User Guide Part Number 900-325 Revision C 03/18 Table of Contents 1. Overview ...................................................................................................................................... 1 2. Devices ........................................................................................................................................ 2 Choose the Network Adapter for Communication ....................................................................... 2 Search for All Devices on the Network ........................................................................................ 2 Change Views .............................................................................................................................. 2 Add a Device to the List ............................................................................................................... 3 View Device Details ..................................................................................................................... 3 Device Lists ................................................................................................................................. 3 Save the Device List ................................................................................................................ 3 Open the Device List ............................................................................................................... 4 Print the Device List ................................................................................................................
    [Show full text]
  • Sys, Shutil, and OS Modules
    This video will introduce the sys, shutil, glob, and os modules. 1 The sys module contains a few tools that are often useful and will be used in this course. The first tool is the argv function which allows the script to request a parameter when the script is run. We will use this function in a few weeks when importing scripts into ArcGIS. If a zero is specified for the argv function, then it will return the location of the script on the computer. This can be helpful if the script needs to look for a supplemental file, such as a template, that is located in the same folder as the script. The exit function stops the script when it reach the exit statement. The function can be used to stop a script when a certain condition occurs – such as when a user specifies an invalid parameter. This allows the script to stop gracefully rather than crashing. The exit function is also useful when troubleshooting a script. 2 The shutil module contains tools for moving and deleting files. The copy tool makes a copy of a file in a new location. The copytree tool makes a copy of an entire folder in a new location. The rmtree tool deletes an entire folder. Note that this tool will not send items to the recycling bin and it will not ask for confirmation. The tool will fail if it encounters any file locks in the folder. 3 The os module contains operating system functions – many of which are often useful in a script.
    [Show full text]
  • ANSWERS ΤΟ EVEN-Numbered
    8 Answers to Even-numbered Exercises 2.1. WhatExplain the following unexpected are result: two ways you can execute a shell script when you do not have execute permission for the file containing the script? Can you execute a shell script if you do not have read permission for the file containing the script? You can give the name of the file containing the script as an argument to the shell (for example, bash scriptfile or tcsh scriptfile, where scriptfile is the name of the file containing the script). Under bash you can give the following command: $ . scriptfile Under both bash and tcsh you can use this command: $ source scriptfile Because the shell must read the commands from the file containing a shell script before it can execute the commands, you must have read permission for the file to execute a shell script. 4.3. AssumeWhat is the purpose ble? you have made the following assignment: $ person=zach Give the output of each of the following commands. a. echo $person zach b. echo '$person' $person c. echo "$person" zach 1 2 6.5. Assumengs. the /home/zach/grants/biblios and /home/zach/biblios directories exist. Specify Zach’s working directory after he executes each sequence of commands. Explain what happens in each case. a. $ pwd /home/zach/grants $ CDPATH=$(pwd) $ cd $ cd biblios After executing the preceding commands, Zach’s working directory is /home/zach/grants/biblios. When CDPATH is set and the working directory is not specified in CDPATH, cd searches the working directory only after it searches the directories specified by CDPATH.
    [Show full text]
  • Linux Networking Cookbook.Pdf
    Linux Networking Cookbook ™ Carla Schroder Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Linux Networking Cookbook™ by Carla Schroder Copyright © 2008 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Indexer: John Bickelhaupt Production Editor: Sumita Mukherji Cover Designer: Karen Montgomery Copyeditor: Derek Di Matteo Interior Designer: David Futato Proofreader: Sumita Mukherji Illustrator: Jessamyn Read Printing History: November 2007: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. The Cookbook series designations, Linux Networking Cookbook, the image of a female blacksmith, and related trade dress are trademarks of O’Reilly Media, Inc. Java™ is a trademark of Sun Microsystems, Inc. .NET is a registered trademark of Microsoft Corporation. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    [Show full text]
  • Configuration and Administration of Networking for Fedora 23
    Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Stephen Wadeley Networking Guide Draft Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Edition 1.0 Author Stephen Wadeley [email protected] Copyright © 2015 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]