Download ebooks file Learn Wireshark: A definitive guide to expertly analyzing protocols and troubleshooting networks using Wireshark Lisa Bock all chapters
Download ebooks file Learn Wireshark: A definitive guide to expertly analyzing protocols and troubleshooting networks using Wireshark Lisa Bock all chapters
com
https://textbookfull.com/product/learn-wireshark-a-
definitive-guide-to-expertly-analyzing-protocols-and-
troubleshooting-networks-using-wireshark-lisa-bock/
OR CLICK BUTTON
DOWNLOAD NOW
https://textbookfull.com/product/practical-packet-analysis-using-
wireshark-to-solve-real-world-network-proble-3rd-edition-safari/
textboxfull.com
https://textbookfull.com/product/a-guide-to-software-managing-
maintaining-and-troubleshooting-jean-andrews/
textboxfull.com
https://textbookfull.com/product/learn-data-science-using-sas-studio-
a-quick-start-guide-engy-fouda/
textboxfull.com
Troubleshooting Electronic Circuits: A Guide to Learning
Analog Electronics 1st Edition Ronald Quan
https://textbookfull.com/product/troubleshooting-electronic-circuits-
a-guide-to-learning-analog-electronics-1st-edition-ronald-quan/
textboxfull.com
https://textbookfull.com/product/programming-mathematics-using-
matlab-1st-edition-lisa-a-oberbroeckling/
textboxfull.com
https://textbookfull.com/product/programming-mathematics-using-
matlab-1st-edition-oberbroeckling-lisa-a/
textboxfull.com
https://textbookfull.com/product/programming-mathematics-using-
matlab-1st-edition-oberbroeckling-lisa-a-2/
textboxfull.com
Learn Wireshark
Second Edition
Lisa Bock
BIRMINGHAM—MUMBAI
Learn Wireshark
Second Edition
Copyright © 2022 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means, without the prior written permission of the publisher,
except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the
information presented. However, the information contained in this book is sold without warranty,
either express or implied. Neither the author, nor Packt Publishing or its dealers and distributors,
will be held liable for any damages caused or alleged to have been caused directly or indirectly by
this book.
Packt Publishing has endeavored to provide trademark information about all of the companies
and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing
cannot guarantee the accuracy of this information.
ISBN 978-1-80323-167-9
www.packt.com
To all dreamers, know that there isn't always a clear path to achieving your dream.
In addition to celebrating and rejoicing each milestone, there will be times of
great sorrow and despair along the way. Nonetheless, keep moving toward your
dream while being authentic, harmonious, and true to yourself. One day you'll
see a sign, and you'll say to yourself with a smile, "I have arrived."
Contributors
About the author
Lisa Bock is an experienced author with a demonstrated history of working in the
e-learning industry. She is a security ambassador with a broad range of IT skills and
knowledge, including Cisco security, CyberOps, Wireshark, biometrics, ethical hacking,
and the IoT. Lisa is an author for LinkedIn Learning and an award-winning speaker who
has presented at several national conferences. She holds an MS in computer information
systems/information assurance from UMGC. Lisa was an associate professor in the IT
department at Pennsylvania College of Technology (Williamsport, PA) from 2003 until
her retirement in 2020. She is involved with various volunteer activities, and she and her
husband, Mike, enjoy bike riding, watching movies, and traveling.
I'd like to thank the author, Lisa Bock, and the team at Packt for giving me
the opportunity to do something that has been wholly enjoyable – reviewing
this great book. Most thanks, however, go to my long-suffering family and
colleagues for giving me the time and support to do so. Thank you, Chris,
Bryn, Jon, Caroline, Craig, and everybody else. You're brilliant.
Table of Contents
Preface
2
Using Wireshark
Examining the Finding information 34
Wireshark interface 28
Understanding the phases of
Streamlining the interface 28
packet analysis 34
Discovering keyboard shortcuts 31
Gathering network traffic 34
Recognizing the Wireshark authors 32
Decoding the raw bits 37
viii Table of Contents
3
Installing Wireshark
Discovering support for Beginning the installation 58
different OSes 50 Choosing components 58
Using Wireshark on Windows 50 Creating shortcuts and selecting
Running Wireshark on Unix 50 an install location 62
Installing Wireshark on macOS 51 Capturing packets and completing
the installation 63
Deploying Wireshark on Linux 51
Working with Wireshark Reviewing available resources 65
on other systems 52
Viewing news and help topics 65
Comparing different Evaluating download options 67
capture engines 54
Summary69
Understanding libpcap 54
Questions69
Examining WinPcap 54
Grasping Npcap 55 Further reading 71
Performing a standard
Windows installation 58
4
Exploring the Wireshark Interface
Opening the Wireshark Printing packets and closing Wireshark 82
welcome screen 74
Discovering the Edit menu 84
Selecting a file 74
Copying items and finding packets 84
Capturing traffic 75
Marking or ignoring packets 88
Exploring the File menu 76 Setting a time reference 89
Opening a file, closing, and saving 77 Personalizing your work area 90
Exporting packets, bytes, and objects 78
Exploring the View menu 91
Table of Contents ix
6
Personalizing the Interface
Personalizing the layout 130 Adding, editing, and deleting columns 141
Altering the appearance 130 Refining the font and colors 145
Changing the layout 132
Adding comments 148
Creating a tailored Attaching comments to files 148
configuration profile 136 Entering packet comments 148
Customizing a profile 136 Viewing and saving comments 149
Crafting buttons 139
Summary 150
Adjusting columns, Questions 151
font, and colors 141
x Table of Contents
7
Using Display and Capture Filters
Filtering network traffic 154 Understanding the
Analyzing traffic 154 expression builder 168
Comparing the filters' files 156 Building an expression 170
8
Outlining the OSI Model
An overview of the OSI model 182 Traveling over the Physical layer 197
Developing the framework 182
Exploring the
Using the framework 183
encapsulation process 198
Discovering the purpose Viewing the data 199
of each layer, the protocols, Identifying the segment 199
and the PDUs 183 Characterizing the packet 200
Evaluating the Application layer 185 Forming the frame 200
Dissecting the Presentation layer 186
Demonstrating frame
Learning about the Session layer 188
formation in Wireshark 201
Appreciating the Transport layer 190
Examining the network bindings 202
Explaining the Network layer 193
Examining the Data Link layer 196 Summary203
Questions203
Table of Contents xi
10
Managing TCP Connections
Dissecting the Permitting SACK 257
three-way handshake 242 Using timestamps 259
Isolating a single stream 243
Understanding TCP
Identifying the handshake packets 248
protocol preferences 260
Learning TCP options 252 Modifying TCP preferences 262
Grasping the EOL option 254
Tearing down a connection 264
Using NOP 254
Defining the MSS 255
Summary266
Scaling the WS 256 Questions266
Further reading 268
xii Table of Contents
11
Analyzing IPv4 and IPv6
Reviewing the network layer 270 Editing protocol preferences 287
Understanding the purpose of IP 271 Reviewing IPv4 preferences 287
Adjusting preferences for IPv6 290
Outlining IPv4 272
Dissecting the IPv4 header 273 Discovering tunneling protocols291
Modifying options for IPv4 282 Summary292
Exploring IPv6 282 Questions293
Navigating the IPv6 header fields 283 Further reading 295
12
Discovering ICMP
Understanding the purpose of Providing information using ICMPv6 312
ICMP298
Evaluating type and code values315
Understanding the ICMP header 299
Reviewing ICMP type and code values 315
Investigating the data payload 302
Defining ICMPv6 type and code values 317
Dissecting ICMP and ICMPv6 305
Configuring firewall rules 318
Reviewing ICMP 305
Acting maliciously 318
Outlining ICMPv6 306
Allowing only necessary types 323
Sending ICMP messages 307
Summary324
Reporting errors on the network 308
Issuing query messages 311
Questions324
Further reading 326
14
Examining DHCP
Recognizing the purpose of Understanding DHCP messages 375
DHCP 360 Comparing DHCP options 376
Configuring the client's IP address 361
Following a DHCP example 377
Using a DHCP relay agent 361
Releasing an IP address 377
Working with IPv6 addresses 363
Broadcasting a discover packet 379
Addressing security issues 365
Delivering an offer 380
Stepping through Requesting an IP address 382
the DORA process 366 Acknowledging the offer 383
Moving through DHCP states 366
Summary384
Obtaining an IP address 367
Leasing an IP address 370 Questions 385
Further reading 387
Dissecting a DHCP header 372
Examining DHCP field values 373
15
Decoding HTTP
Describing HTTP 390 Keeping track of the connection394
Dissecting a web page 390 Evaluating connection types 395
Understanding HTTP versions 393 Maintaining state with cookies 396
Recognizing HTTP methods 394
Comparing request and
response messages 398
xiv Table of Contents
16
Understanding ARP
Understanding the role and Reversing ARP 427
purpose of ARP 418 Evaluating InARP 428
Resolving MAC addresses 419 Issuing a gratuitous ARP 430
Investigating an ARP cache 421 Working on behalf of ARP 430
Replacing ARP with NDP in IPv6 423
Comparing ARP attacks and
Exploring ARP headers defense methods 432
and fields 423 Comparing ARP attacks and tools 432
Identifying a standard ARP Defending against ARP attacks 435
request/reply 423
Summary436
Breaking down the ARP header fields 425
Questions 437
Examining different types Further reading 438
of ARP 427
18
Subsetting, Saving, and Exporting Captures
Discovering ways Recognizing ways to
to subset traffic 466 export components 477
Dissecting by an IP address 467 Selecting specified packets 478
Narrowing down by conversations 470 Exporting various objects 480
Minimizing by port number 471
Breaking down by protocol 472
Identifying why and how
to add comments 482
Subsetting by stream 473
Providing file and packet comments 482
Understanding options Saving and viewing comments 484
to save a file 474
Using Save as 476
Summary 487
Questions 487
19
Discovering I/O and Stream Graphs
Discovering the Statistics menu 492 Comparing TCP stream graphs 506
Viewing general information 493 Using time sequence graphs 506
Assessing protocol effectiveness 494 Determining throughput 512
Graphing capture issues 497 Assessing Round Trip Time 514
Evaluating window scaling 515
Creating I/O graphs 499
Examining errors 500 Summary 517
Graphing duplicate ACKs 501 Questions 517
Modifying the settings 502
Exploring other options 504
20
Using CloudShark for Packet Analysis
Discovering CloudShark 522 Outlining the various
Modifying the preferences 523 filters and graphs 532
Uploading captures 525 Displaying data using filters 533
Working with capture files 526 Viewing data using graphs 534
xvi Table of Contents
Chapter 3, Installing Wireshark, illustrates how Wireshark provides support for different
operating systems. We'll compare the different capture engines, such as WinPCap,
LibPcap, and Npcap, walk through a standard Windows installation, and then review the
resources available at https://www.wireshark.org/.
Chapter 4, Exploring the Wireshark Interface, provides a deeper dive into some of the
common elements of Wireshark to improve your workflow. We'll investigate the welcome
screen and common menu choices, such as File, Edit, and View, so that you can easily
navigate the interface during an analysis.
Chapter 5, Tapping into the Data Stream, starts with a comparison of the different network
architectures and then moves on to the various capture options. You'll discover the
conversations and endpoints you'll see when tapping into the stream, and then learn about
the importance of baselining network traffic.
Chapter 6, Personalizing the Interface, helps you to realize all the ways you can customize
the many aspects of the interface. You'll learn how to personalize the layout and general
appearance, create a tailored configuration profile, adjust the columns, font, and color, and
create buttons.
Chapter 7, Using Display and Capture Filters, helps you to make examining a packet
capture less overwhelming. We'll take a look at how to narrow your scope by filtering
network traffic. We'll compare and contrast display and capture filters, discover the
shortcuts used to build filters, and conclude with a review of the expression builder.
Chapter 8, Outlining the OSI Model, provides an overview of the Open Systems
Interconnection (OSI) model, a seven-layer framework that outlines how the OS prepares
data for transport on the network. We'll review the purpose, protocols, and Protocol Data
Units (PDUs) of each layer, explore the encapsulation process, and demonstrate the frame
formation in Wireshark.
Chapter 9, Decoding TCP and UDP, is a deep dive into two of the key protocols in the
transport layer – the Transmission Control Protocol (TCP) and the User Datagram
Protocol (UDP). We'll review the purpose of the transport layer and then evaluate the
header and field values of both the TCP and the UDP.
Chapter 10, Managing TCP Connections, begins by examining the three-way handshake.
We'll discover the TCP options, get a better understanding of the TCP protocol
preferences, and then conclude with an overview of the TCP teardown process.
Chapter 11, Analyzing IPv4 and IPv6, provides a breakdown of the purpose of the Internet
Protocol (IP). We'll outline IPv4 and the header fields and then explore the streamlined
header of IPv6. We'll summarize with a discussion of the protocol preferences and see
how IPv4 and IPv6 can coexist by using tunneling protocols.
Preface xix
Chapter 12, Discovering ICMP, details the purpose of the Internet Control Message
Protocol (ICMP). We'll dissect ICMP and ICMPv6, compare query and error messages,
and discuss the ICMP type and code values. We'll cover how ICMP can be used in
malicious ways and outline the importance of configuring firewall rules.
Chapter 13, Diving into DNS, outlines the significance of the Domain Name System
(DNS). You'll learn how DNS works when resolving a hostname to an IP address. We'll
compare the different types of records, step through a query and response, review the
DNS header, and calculate the DNS response time using Wireshark.
Chapter 14, Examining DHCP, begins by explaining the need for the Dynamic Host
Configuration Protocol (DHCP). We'll then outline the DORA process – Discover Offer
Request Acknowledge. We'll dissect a DHCP header and review all the field values, flags,
and port numbers, and then finish by stepping through a DHCP example.
Chapter 15, Decoding HTTP, highlights the Hypertext Transfer Protocol (HTTP),
an application layer protocol used when browsing the web. We'll learn the details of
HTTP, explore common methods of transport, and dissect the header and fields. We'll
then compare request and response messages, and then summarize by following an
HTTP stream.
Chapter 16, Understanding ARP, takes a closer look at the Address Resolution Protocol
(ARP), which is a significant protocol in delivering data. We'll outline the role and
purpose of ARP, explore the header and fields, describe the different types of ARP, and
take a brief look at ARP attacks.
Chapter 17, Determining Network Latency Issues, outlines how even a beginner can
diagnose network problems. We'll explore coloring rules and the Intelligent Scrollbar, and
then conclude with an overview of the expert information, which divides the alerts into
categories and guides you through a more targeted evaluation.
Chapter 18, Subsetting, Saving, and Exporting Captures, helps you to explore the many
different ways in which to break down a packet capture into smaller files for analysis. We'll
cover the different options when saving a file, discover ways to export components such as
objects, session keys, and packet bytes, and then outline why and how to add comments.
Chapter 19, Discovering I/O and Stream Graphs, begins by covering the many ways the
statistics menu can help us when analyzing a capture file. We'll create basic I/O graphs to
help visualize network issues and summarize by comparing how the different TCP stream
graphs provide a visual representation of the streams.
xx Preface
Chapter 20, Using CloudShark for Packet Analysis, covers CloudShark, an online
application that is similar to Wireshark. You'll learn how to filter traffic and generate
graphs. We'll then review how you can share captures with colleagues and outline where
you can find sample captures so that you can continue improving your skills.
Conventions used
There are a number of text conventions used throughout this book.
Code in text: Indicates code words in text, database table names, folder names,
filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles.
Here is an example: "To write to a file, use -w, then the filename and path."
Any command-line input or output is written as follows:
Bold: Indicates a new term, an important word, or words that you see onscreen. For
instance, words in menus or dialog boxes appear in bold. Here is an example: "Once
you're in CloudShark, select the Export | Download File drop-down menu."
Get in touch
Feedback from our readers is always welcome.
General feedback: If you have questions about any aspect of this book, email us
at customercare@packtpub.com and mention the book title in the subject of
your message.
Errata: Although we have taken every care to ensure the accuracy of our content,
mistakes do happen. If you have found a mistake in this book, we would be grateful if
you would report this to us. Please visit www.packtpub.com/support/errata
and fill in the form.
Piracy: If you come across any illegal copies of our works in any form on the internet,
we would be grateful if you would provide us with the location address or website name.
Please contact us at copyright@packt.com with a link to the material.
If you are interested in becoming an author: If there is a topic that you have expertise
in and you are interested in either writing or contributing to a book, please visit
authors.packtpub.com.
In this section, we’ll outline the value of traffic analysis, learn about the evolution of
Wireshark, and step through the phases of packet analysis. We’ll then discuss some of
the command-line interface tools, outline how to download and install Wireshark, and
explore the interface along with commonly accessed menu choices.
The following chapters will be covered under this section:
In this chapter, we will address all of this by covering the following topics:
We use packet analysis in many places, including on a LAN, on a host, or in the real world.
Additionally, we use packet analysis when troubleshooting latency issues, testing Internet
of Things (IoT) devices, and as a tool when baselining the network.
Today, packet analysis using Wireshark is a valuable skill. However, analyzing packets has
been around in the networking world for many years. As early as the 1990s, various tools
enabled analysts to carry out packet analysis on the network to troubleshoot errors and to
monitor server behavior. In the next section, we'll examine some of the early tools used to
monitor network activity.
Reviewing packet analysis 5
In the next section, we'll take a look at the various devices that use packet analysis today.
6 Appreciating Traffic Analysis
• A router captures the traffic and examines the IP header to determine where to
send the traffic, as part of the routing process.
• An IDS examines the traffic and alerts the network administrator if there is any
unusual or suspicious behavior.
• A firewall monitors all traffic and will drop any packets that are not in line with
the Access Control List (ACL).
For example, when data passes through a firewall, the device examines the traffic and
determines whether to allow or deny the packets according to the ACL.
Using an ACL
When using a firewall, an ACL governs the type of traffic that is allowed on the network.
For example, an ACL has the following entries:
To decide whether to allow or deny a packet, the firewall must check each header as it
passes through the device. It will determine variables such as IP addresses, Transmission
Control Protocol (TCP) flags, and port numbers that are in use. If the packet does not
meet the ACL entry, the firewall will drop the packet. As shown in the following diagram,
an inbound SYN packet with a destination port of 80 is blocked because it does not match
the rule:
Random documents with unrelated
content Scribd suggests to you:
CHAPTER V
CROSS-COUNTRY FLYING
Cross-country flying differs from ordinary airdrome flying in that it
takes you a long way off from your landing field. On the airdrome
your chief anxiety is to learn how to fly, how to work the controls,
how to bank; but in cross-country work, you are supposed to have
all the technique of airplane operation well in hand, so that you do
not have to think much about it. In cross-country flying, then, your
chief anxiety will be to arrive at your destination and to be
constantly searching out available landing fields in case of engine
failure. The first cross-country flight you make may be a short, easy
one, in which there are plenty of available landing places, and on
which you will be able to make a regular reconnaissance report.
Further experience in cross-country work will involve more and more
difficult trips, until you will think nothing of flying, for example, on
long raiding tours over unfamiliar enemy country.
Equipment.—Knowing that you may have to land far away from
any headquarters, you must take a complete set of tools and covers
for the airplane. Your clothing need not be different from usual, and
will comprise helmet, goggles, leather suit, and gloves. Do not forget
your handkerchief, which you frequently need to clean off your
goggles.
The instruments needed on a cross-country trip are: a compass,
which should be properly adjusted before starting and the variation
angle noted. A wrist watch is necessary; ordinary dashboard clocks
go wrong on account of the vibration. Take an aneroid barometer
with adjustable height reading. Of course you will depend upon a
revolution indicator, for no matter how experienced a pilot may be in
“listening out” faulty engine operation, after a long flight his ear
loses its acuteness, and he will fall back on the revolution indicator
for assistance. The air-speed meter, whether of the Pitot type or
pressure-plate type, will prove invaluable in flying through clouds or
mist when the ground is obscured. Also the inclinometer is able to
give the angle of flight when the earth is not visible, although the
speed indicator usually is sufficient to give the angle of flight, for an
increase of speed means downward motion and decrease of speed
means upward motion. Additional instruments may be used.
Map.—The map is essential for cross-country work. It should be
tacked on to the map board if the flight is short, but made to run on
rollers if the flight is long. In the latter case the map is in the form of
a single long strip, while your flight may be full of angles; therefore
you will have to practice using this sort of map, in which the corners
of your flight are all drawn as straight lines. The scale of maps may
be 2 or 4 miles to the inch for long flights. This scale is sometimes
spoken of as a fractional figure; that is, 2 miles to the inch is the
same as 1/127,000 scale. The map should be studied most carefully
before the start of the trip. The course which you propose to fly
should be marked out on it; all available landmarks which could be
of service as guides should be distinctly noticed and marked on the
map where necessary. These landmarks will in case there is no wind
enable you to make your trip without using the compass at all, and
in case of wind, are essential as a check on the compass. Mark off
the distance in miles between consecutive points of your course.
Mark the compass bearing of each leg of this course.
As landmarks towns are the best guides, and they should be
underscored on the map, or enclosed in circles. It is customary not
to fly actually over towns. Railways are very good assistance to
finding your way, and these should be marked on the map in black
wherever they approach within 10 miles of the course. Mark water
courses with blue color, and roads with red.
Landmarks.—Only practice can make a pilot good at observing
the various features of the ground beneath him. The various
features which can be used as guides are those which are most
visible. After towns, railways come next in importance. Their bridges,
tunnels, etc., make good landmarks. On windy days when relying on
the compass, it will be well to keep in sight of a railway even if this
be the longer way around, because the railway gives a constant
check upon the compass bearing. In this case you will have noted on
your map a general magnetic bearing of the railway, which bearing
you can readily compare with your compass reading. Moreover, the
railway is good in case you become involved in a fog or mist for a
time. It should be remembered, however, that on most of the maps
no distinction is made between one and two-track roads; also that it
is easy to make mistakes where branch lines are not shown on the
map because they are dead ends leading to private quarries, etc.,
and may be taken for junctions. Railways sometimes seem to end
abruptly, which means that you are looking at a tunnel.
Water is visible from a great distance. Cautions to be observed are
that after a heavy rain small flooded streams may take on the
appearance of larger bodies of water or lakes, which you will have
difficulty in reconciling with the map. Small rivers are often overhung
with foliage, and to follow them in all their curves will waste a lot of
time.
The use of roads as guides may be governed by the fact that
paved roads are usually main roads, and telegraph wires may be
expected along them. In the newer parts of the United States the
system of laying out roads provides a very useful means of gaging
distances; I refer to the section system which is in use, for instance,
in Illinois, where there is a road every mile running north and south,
so that the entire country is cut up into squares 1 mile on each side,
with occasional roads of course at ½-mile and ¼-mile points.
Navigation by Landmarks.—In all cases of cross-country flying
the pilot will have two independent systems of maintaining his
proper directions: first, the computed compass bearing; second, the
use of landmarks whose position is known. In comparing his
computed course with the course actually indicated by passing over
these landmarks the rule should be made that, in case of doubt
when a landmark is not distinctly recognized, take the compass
course; there are many chances that a landmark may be altered or
even removed without being so recorded on the pilot’s map,
whereas the errors of the compass of course are presumably
understood by the pilot who has secured every opportunity to check
it when passing previous landmarks.
It is important to note the time of completing successive stages of
the flight, that is when passing over predetermined landmarks. Time
is a very uncertain condition to ascertain in airplane flying for it
seems to pass quickly on calm days but slowly when the journey is
rough. If the pilot does not check the time interval between
successive objects he is quite likely to expect the next before it is
really due.
Landing Fields.—Next to the ever-present worry which the pilot
has regarding the perfect operation of his engine, the most
important thing about cross-country flying is that wherever he may
be he must have available a landing field within gliding distance in
case his engine defaults. The question is of course immediately
raised, “What if there is no landing field within gliding range?” The
answer to this is that the pilot will instinctively learn to keep his eyes
open for landing possibilities every minute of his progress whether
he expects to use them or not; in cross-country flying the lookout for
fields is first and foremost in his mind; if there are no fields, it is up
to him to pick out a spot of ground which is the least objectionable
for a landing. In the State of Illinois the question of landing fields is
almost non-existent, because there are large, flat fields and pastures
in almost every square mile of the farming district, and a cross-
country flight from Rantoul to Chicago could have no terrors for the
beginner as regards the choice of a landing ground.
When it comes to a cross-country flight like Ruth Law’s, from
Chicago to New York, these favorable conditions begin to disappear
after the middle of the journey, that is, east of Buffalo. The most
ideal condition for cross-country flying would be one like that on the
London-Edinburgh route, where landing grounds are so frequent
that by flying at a height of a couple of miles the pilot can free his
mind completely of the worry of suitable landing places; but in the
United States we have very few established airdromes, and the only
approach to the London-Edinburgh route is the St. Louis-New York
route, where the jumps are approximately 150 miles; namely, St.
Louis, Champaign, Indianapolis, Dayton, Sandusky, Erie,
Hammondsport, Philadelphia, and New York. That is why long cross-
country trips are such an adventure in this country and such an
ordinary affair in England.
The beginner will have special difficulty in training his mind to pick
out available landing places; first of all because the earth looks so
different from the sky that it is only with practice a beginner learns
the shades and hues of color which mean certain kinds of ground, or
learns to spot the different features of flat and hilly country. Even for
an accomplished pilot it is hard to tell whether a field is good or bad
from a height of over 1000 ft.; and as it is dangerous to fly this low
over unknown territory, you can at once see what is meant by the
worry of scanning the countryside for available fields.
Choose the best field that you can get, having a smooth surface
and being easy to get out of in all directions. The following
considerations are intended as a guide to what constitute the best
field, in case you have a choice between several possibilities.
1. Choose a field near a town if possible, or failing that, near a
main road or at least a good road. Remember that a field which
appears to be near a town from the air may actually turn out to be a
long walk after you have landed there and find that there are various
trips to be made to and fro between your chosen landing spot and
the town for the purpose of securing ropes, gasoline, supplies, etc.
If you land near a main road there will probably be telegraph wires
along it, which are undesirable in the case of a small field and wind
direction such that you have to rise off the field over the telegraph
wires. It is often hard to distinguish between main roads and minor
roads, and it will be wise to look for the number of vehicles on any
road in determining whether or not it is the main road.
2. The best field is a stubble field, and is most numerous of course
in the fall when the crops are in. It will have a lightish brown color
when seen from a height, and is pretty sure to be smooth, without
ditches or mounds. Grass land is next best, but is often full of
mounds. Plowed, furrow fields are to be avoided. It might be said
that stubble fields will be hard to get out of after a wet night.
Vegetable and corn fields have a dark green appearance which the
pilot must learn to distinguish from grass pastures, etc. If you
choose pasture land, remember that in summer evenings the farm
animals will generally be lying down near the hedges.
3. Avoid river valleys for landing over night, as there is liable to be
a fog in the morning.
4. Any field which has been previously used for landing with
success by an army officer can be wisely chosen.
The final determination of landing field characteristics can be
made when your airplane has descended to a height of 1000 ft. off
the ground, and in case you are not making a forced landing and
your engine is still going, you can check up your estimate by
descending to this level.
Proper Dimensions of Fields and Airdromes.—There are
three kinds of flying fields. One is the airdrome which is used
exclusively for flying, and may be as large as a mile square; very few
of these will be found in cross-country flights in the United States.
Second, there is what is called the “one-way” field, a long, narrow,
open space which is usable when the wind blows parallel to its
length. Third, there is the “two-way” field, which has two sufficiently
long runways at right angles to each other. A two-way field is very
much better than a one-way field, inasmuch as you can always head
within 45° of the wind, whereas in a one-way field an extreme case
would be 90°. Moreover, two-way fields, such as the crescent-
shaped field at Dayton, Ohio, sometimes permit of almost universal
direction of flight. The two-way field may be crescent-shaped, T-
shaped, or L-shaped. An L-shaped field should have each arm 200 by
300 yd. Under certain conditions there may be buildings located
inside or outside the angle which do no harm aside from creating
eddies in case of strong wind. A T-shaped field should also have its
arms 300 by 200 yd. in size.
Regarding the size of fields it can be said that, while the JN-4
machine will rise off the ground after a run of 100 yd. or so, a field
of this length is of course not big enough for frequent use, especially
if bordered by trees, telegraph lines, fences, and so forth. A field for
temporary use should be at least 200 by 200 yd., about 9 acres. If
obstructions at the edges are more than 5 ft. high add to this 200
yd. a distance equal to twelve times the height of the obstruction.
For a permanent field 300 yd. is the minimum dimension necessary
for clearing obstacles and must be increased if the trees exceed 50
ft. in height. This minimum dimension assumes hard ground and the
possibility of starting in any direction. Training fields are ½ mile
square or more.
Whatever field is used either temporarily or permanently by the
pilot should be absolutely familiar to him over every inch of its
surface. The adjacent country should also be absolutely familiar to
him from the standpoint of possible forced landings which he may
have to make during his flight; he should make a habit of informing
himself as to all the woods and hills, etc., which can affect air
currents in the neighborhood of the field from which he is going to
start.
Guide Posts on Airdromes.—Some fields have pot holes in
them, and these holes should be marked in each case with a large
high red or yellow flag. Do not use short, small flags, as they will
frequently be invisible to pilots taxying on the ground. All telephone
wires, etc., should have large blankets or other suitable signals hung
over them to warn the pilot away.
Commonly accepted marks for designating a landing spot on
airdromes are as follows:
For day use a large letter “T” lying on the ground, made out of
white cloth strips 15 by 3 ft. This letter T is shifted with the wind so
that its long leg always points in the direction of the wind and the
pilot will therefore have nothing to do in landing but approach the
letter “T” from the bottom, so to speak.
For night flying a system of four flares is used, so arranged that
the pilot in making a proper landing will pass flare A on his left;
within 50 yd. further on, flare B; then 100 yd. further on, flare C,
also on his left. In passing flare C he will have a fourth flare, D, 50
yd. to his right. That is to say, the four flares make the outline of a
letter “L” and the pilot approaches the letter having the long leg on
his left. The flares may be made by putting half a gallon of gasoline
into a pail. This will burn for 30 min. and will be visible 8 miles away.
Sometimes at night instead of flares white sheets can be spread on
the ground and a shaded lamp used to illuminate the sheets.
All searchlights on the landing field should point in the direction of
landing. All other lights within a distance of a mile should be
extinguished, and red lamps should be used at danger points.
On moonlight nights the same signals and guides may be used as
in the daytime.
Pegging Down an Airplane.—In landing for the night do not
stay up until it gets dark but choose a landing place which will allow
you to come down 1 hr. before dark; this amount of time will be
needed for laying up the machine over night. As you come to the
landing ground note the time so that you can compute the actual
duration of your flight in your report, then make a good landing.
Taxy the machine to the spot where you intend to leave it over
night, such as the lee of a hedge, etc.; or if there is no choice of
position taxy the machine to the approximate location from which
you will make your start next morning; this will save trouble when
you get ready to start.
Dismount from your machine, lift up the tail enough to leave the
wings edgewise to the wind, the machine, of course, facing the
wind, and jack up the tail in this position by the use of any
convenient prop. Lash the control wheel or joy stick fast in a fixed
position so that the wind can not flap the control surfaces around
and damage them.
Choose a sunken trench if possible in which the wheels may be
sunk; if the wind is going to blow and there is no sunken trench it
will be wise to dig one so that the effect of the wind on the airplane
will be lessened. If the trench is not necessary, at least put chocks
under the wheels. Peg down the wings and the tail to stakes driven
into the ground using rope if you can get some or lacking this in an
emergency fence wires which you can secure by means of your wire
cutters. Do not lash tightly enough to induce strains in the
framework of the machine.
Next, fill up the tanks if a supply of gasoline or oil is available. Put
the covers on the propellers, engine, cowls, etc., in order that rain
and dew shall do no damage to these parts. The wings and body are
varnished waterproof and will not be seriously damaged by a little
moisture; to avoid the collection of moisture in the wings small
eyelet holes are sometimes set in the wings at the trailing edge to
let out the water.
Of course, you will engage a guard to watch the machine all night;
see that a rope is strung around the airplane to keep off the crowd
which may collect.
AERIAL NAVIGATION
Modulus of rupture,
Weight per cubic foot, Compression strength,
Wood pounds per square
pounds (15% moisture) pounds per square inch
inch
Hickory 50 16,300 7,300
White
46 12,000 5,900
Oak
Ash 40 12,700 6,000
Walnut 38 11,900 6,100
Spruce 27 7,900 4,300
White
29 7,600 4,800
Pine
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
textbookfull.com