Trilliant SkyPilot Gateway Pro, Установка и настройка

Страница: 45 / 62

Confirming SkyPilot Extender DualBand Access Point Connectivity | 37
without arguments returns a path that the device identifies as its exit from the
network.
For example:
> traceroute
traceroute to 00:0a:db:00:00:a6
>> 1 (48) --> 00:00:43 --> (36)
2 (36) --> 00:00:a6 --> (36)
 Use the
ping
command to verify that you can reach the device’s default
gateway.
For example:
> ping 192.168.5.1
PING 192.168.5.1: 56 data bytes
64 bytes from 192.168.5.1: icmp_seq=0. time=11. ms
64 bytes from 192.168.5.1: icmp_seq=1. time=12. ms
64 bytes from 192.168.5.1: icmp_seq=2. time=12. ms ----
192.168.5.1 PING
Statistics---- 3 packets transmitted, 3 packets received, 0%
packet loss round-trip (ms) min/avg/max = 0/16/32
Confirming SkyPilot Extender DualBand
Access Point Connectivity
There are four ways to confirm SkyPilot Extender DualBand access point
connectivity:
 Use the
ping
command to verify that the access point is up and running—for
example,
ping 192.168.0.3
.
 For SkyPilot firmware versions 1.2p3 and later, use the show version ap
command to verify the firmware version and, indirectly, that proper heartbeats
are being sent from the PePLink Linux access point.
 From the command line, enable debugging (using the debug on
command) and use the
set log apwatchdog 3
command to display
successful or failed heartbeat updates, reboot notices, factory resets, and so
on.
 Using an 802.11b/g wireless card, connect to the default SSID, a string
representation of the SkyPilot Extender’s MAC address with the WPA
passphrase
publicpublic
.