Chapter 2. Getting Started with the Access Server

The WRAP Access Server can be controlled via the WWW interface, by entering commands and using applications at Access Server shell prompt or by sending and/or retrieving files to/from the Access Server.

Note: The default username is root with password buffy.

2.1. Powering Up

To get started with the WRAP Access Server, connect it to your local area network (LAN) using an Ethernet cable and connect the power adapter. The Access Server will power up and retrieve the network settings from your network's DHCP server.

The WRAP Access Server will also use Zeroconf (also known as Zero Configuration Networking or Automatic Private IP Addressing) to get an unique IP address in the 169.254.x.x network. Most operating systems also support this. So, you can connect your controlling laptop with a cross-over Ethernet cable to the WRAP Access Server, then power up the Access Server, and the devices will automatically have unique IP addresses in 169.254.x.x network.

Note: If you need to configure the network settings manually and cannot connect first using Zeroconf, you can do it using the management console, see subsection Section 2.3.1.

Locations of the physical interfaces of the Access Server are described in Figure 2-1 and Figure 2-2.

Figure 2-1. WRAP Access Server Connectors

Note: There is no power switch in the WRAP Access Server. Unplug and plug the power adapter to switch the power on and off. The power led in Figure 2-2 is on when the power adapter is connected.

Figure 2-2. WRAP Access Server LEDs

All the blue status LEDs are turned off when the boot procedure is finished and the Access Server is ready to be connected.

2.2. WWW Interface

Most WRAP Access Server functionality can be controlled via the WWW interface using any standard WWW browser.

The wrapfinder application (see Figure 2-3), available for Windows operating system from Bluegiga Techforum (https://www.bluegiga.com/techforum/) provides easy-to-use interface for finding the WRAP Access Servers (with SW version 2.1.0 or later) in the local area network.

Figure 2-3. WRAP Access Server Finder Application

The wrapfinder automatically identifies the broadcast address of the network it runs in and shows the IP addresses, serial numbers and WRAP Access Server device types it could find using UDP broadcast when it was launched.

Note: Normally, there are two entries for one Access Server. Use the one with the IP address in your local area network. Use the one with the 169.254.x.x, the Zeroconf network address, when it is the only one shown.

You can change the broadcast address used for finding the Access Servers. A new scan can be done by clicking Rescan.

Select an Access Server (by clicking its IP address) and click Details to see more information (like the Bluetooth addresses and friendly names) of the Access Server. See Figure 2-4 for details.

Figure 2-4. Details Dialog of WRAP Access Server Finder

Click Connect or double-click an IP address to connect to the selected Access Server using a WWW browser.

Click Exit to close the program.

Note: To find the IP address of the Access Server without wrapfinder, see Section 2.3.2.

The WWW interface is accessed at http://wrap-ip/, where wrap-ip is the IP address of the WRAP Access Server (see Figure 2-5).

Figure 2-5. WRAP Access Server WWW Interface

From the top-level page, click Setup to log in to the configuration interface. The default username is root and the default password is buffy (see Figure 2-6).

Figure 2-6. WWW Login Prompt for Access Server Setup

After logging in, you can configure several WRAP Access Server settings (see Figure 2-7). These are discussed in detail in Section 2.4.

Figure 2-7. The WWW Configuration Interface of the Access Server

2.3. Shell Prompt Access

Shell prompt access may be needed for advanced controlling operations that cannot be performed using the WWW interface.

You can get to the shell prompt using either SSH or the management console. The management console over a serial cable should only be needed to change the network configuration settings in the case were the network configuration using DHCP or Zeroconf is not possible. All further controlling activities can be performed remotely using SSH sessions over Ethernet or Bluetooth LAN/PAN connection.

If you can make SSH connection from a device that has Bluetooth LAN Access or PAN profile support, you don't need the management console. Just connect to the Access Server using LAN Access or PAN profile. The Access Server can be seen in Bluetooth inquiries as "Wserialno_n", where "serialno" is the serial number of the device and "n" is the number of the Bluetooth radio in question (model 2293 has three Bluetooth radios, any of which can be connected). After you have connected (no PIN code, username or password needed), connect using SSH to the device in the other end of the connection, typically 192.168.160.1. You can also use the wrapfinder application to find the IP address (see Section 2.2 for details).

Note: Bluetooth LAN Access is disabled by default. Use the WWW interface to enable it, if needed.

Note: The default username is root with password buffy.

2.3.1. Management Console

If you don't have Bluetooth LAN/PAN client and you don't have the Access Server connected to your LAN or you don't know the IP address given to the Access Server, you can get the first shell prompt access using the management console.

To setup management console do the following:

  1. Have a PC with a free COM port.

  2. Power off the Access Server.

  3. Configure your terminal application, like HyperTerminal in Windows, to use the settings in with the free COM port

    Table 2-1. The Management Console Port Settings

    SettingValue
    Speed115200bps
    Data Bits8
    ParityNone
    Stop Bits1
    Flow ControlNone
  4. Connect the serial cable shipped with the Access Server to your PC's free COM port.

  5. Connect the null-modem adapter shipped with the Access Server to the serial cable

  6. Connect the serial cable with the null-modem adapter to the management (user) port in the Access Server (see Figure 2-1).

  7. Power on the Access Server.

  8. Enter letter b in the terminal application during the first five seconds, while the blue LEDs in the Access Server turn on one by one.

  9. The management console is now activated and you should see the boot log in your terminal window. Wait for the device to boot up and end with the prompt [root@wrap /]$.

  10. You are ready to control the Access Server from the management console.

2.3.2. Accessing Remotely

When the WRAP Access Server is connected to a LAN it tries to get the IP address using DHCP and Zeroconf by default. You can then use the wrapfinder application to find the IP address (see Section 2.2).

If you cannot get the IP address using the wrapfinder, another way to see the IP address of the WRAP Access Server is to connect with a management console (see previous section), power on the board and, after the system is up and running, give the command ifconfig nap. The field inet addr for the interface nap contains the IP address of the WRAP Access Server board. For example, in the following capture from the management console, the IP address is 192.168.42.3.


        [root@wrap /]$ ifconfig nap
        nap      Link encap:Ethernet  HWaddr 00:07:80:00:BF:01
                 inet addr:192.168.42.3  Bcast:192.168.42.255  Mask:255.255.255.0
                 inet6 addr: fe80::207:80ff:fe00:bf01/64 Scope:Link
                 UP BROADCAST MULTICAST  MTU:1500  Metric:1
                 RX packets:12635 errors:0 dropped:0 overruns:0 frame:0
                 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
                 collisions:0 txqueuelen:100
                 RX bytes:1686246 (1.6 MiB)  TX bytes:1640 (1.6 KiB)
                 Interrupt:24 Base address:0xc000
      

You can use this address to connect the Access Server remotely via SSH, SCP or SFTP.

Note: The default username is root with password buffy.

2.3.3. Transferring Files to/from the Access Server

You can transfer file to and from the Access Server by default using for example:

  • SCP (secure copy over SSH)

  • SFTP (secure ftp connection over SSH)

  • FTP (plain ftp connection).

    Note: FTP is disabled by default for security reasons. Use SFTP instead.

    Tip: If enabled, use the integrated client of the Internet Explorer (type ftp://root:buffy@wrap-ip-address/ in the address bar)

  • Bluetooth OBEX (Object Push and File Transfer Profiles) to/from directory /tmp/obex in WRAP Access Server

  • NFS (mount a nfs-share from a remote device as a part of the file system of the Access Server)

  • SSHFS (mount a WRAP Access Server directory over SSH as a part of the filesystem of any other Linux host)

    To download and install SSHFS, visit http://fuse.sourceforge.net/sshfs.html.

  • USB memory dongle (see Section 3.4 for more information).

  • Xmodem/Ymodem/Zmodem (use rz/rx/rb/sz/sx/sb commands from the management console)

For examples of file transferring, see Section 5.3.4.

2.4. Introduction to Configuration

When the WRAP Access Server is installed and powered up for the first time, the default configuration settings are being used. With these settings, the Access Server automatically configures its network settings assuming that the board is connected to a LAN network with a DHCP server running. Additionally, the Access Server also uses Zero Configuration Networking (also known as Automatic Private IP Addressing) to connect to the 169.254.x.x network, which can be used if the network has no DHCP server.

After booting, you can use the Access Server as a Bluetooth PAN access point to the network without any changes in configuration. Also, the Serial Port Profile is enabled by default in listening mode. You can also use Object Push and File Transfer Profiles to send files to/from the Access Server.

Most of the settings of the WRAP Access Server are configurable using the setup application. It has a WWW interface at http://wrap-ip/setup but it can also be run at the command line.

All configurable settings in the setup application are listed in Appendix B with their help.

Note: The default username is root with password buffy.

2.5. Using the Setup WWW Interface

The easiest way to change the Access Server settings is to use the WWW interface. Accessing the WWW interface is instructed in Section 2.2.

Typical WWW configuration page example is shown in Figure 2-8 (This page can be found at SetupSecurity settings)

Figure 2-8. Example WWW Setup Page

The different parts of a WWW Setup page are discussed in the following:

The WWW Setup has also menu items that run commands in the Access Server and then show the output in the browser window. Some commands, like rebooting the Access Server, are confirmed before execution.

2.6. Using the setup Command Line Application

The basic configuration settings can also be changed using the setup application at command line interface.

The setup application displays the settings in a hierarchical menu (see Figure 2-16). Navigating the menu is accomplished by entering the number or letter corresponding to the setting to be viewed and/or changed and pressing Enter. Pressing only Enter either accepts the previous value of the setting or returns to the previous level in the menu hierarchy.

Figure 2-16. Using the setup Command Line Application

Note: Ensure that your terminal application does not send line ends with line feeds. If your terminal sends both CR and LF when Enter is pressed, you cannot navigate in the setup application.

2.7. Resetting Configuration

You can restore the default configuration with setup application and rebooting the board. When the system starts up, the default configuration settings are restored. If you have only changed the configuration by using the setup application, the following commands at the Access Server's command prompt will suffice:


      [root@wrap /]$ setup -r
      [root@wrap /]$ reboot
    

Note: This does not reset the edited files to factory defaults, only the other settings changed with WWW Setup or setup command line application.