Hardware Reference
In-Depth Information
RX —his section provides feedback on the received network traic, including the
number of errors and dropped packets recorded. If you start to see errors appearing in
this section, there's something wrong with the network.
TX— his provides the same information as the RX section, but for transmitted pack-
ets. Again, any errors recorded here indicate a problem with the network.
collisions— If two systems on the network try to talk at the same time, you get a colli-
sion which requires them to retransmit their packets. Small numbers of collisions
aren't a problem, but a large number here indicates a network issue.
txqueuelen— he length of the transmission queue , which will usually be set to 1000
and rarely needs changing.
RX bytes, TX bytes— A summary of the amount of traic the network interface has
passed.
If you're having problems with the network on the Pi, you should irst try to disable and then
re-enable the network interface. he easiest way to do this is with two tools called ifup and
ifdown .
If the network is up, but not working correctly—for example, if ifconfig doesn't list any-
thing in the inet addr section—start by disabling the network port. From the terminal,
type the following command:
sudo ifdown eth0
Once the network is disabled, make sure that the cable is inserted tightly at both ends, and
that whatever network device the Pi is connected to (hub, switch or router) is powered on
and working. hen bring the interface back up again with the following command:
sudo ifup eth0
You can test the networking by using the ping command, which sends data to a remote
computer and waits for a response. If everything's working, you should see the same response
as shown in Figure 3-3. If not, you may need to manually conigure your network settings,
which you'll learn how to do in Chapter 4, “Network Coniguration”.
Search WWH ::




Custom Search