2.1. Powering Up

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

Access Point and 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. In other words, you can connect your controlling laptop with a cross-over ethernet cable to Access Server, then power up Access Server, and the devices will automatically have unique IP addresses in the 169.254.x.x network. With Access Point, also a direct ethernet cable works.

The physical interface locations of Access Point are described in Figure 2-1.

The physical interface locations of Access Server are described in Figure 2-2 and Figure 2-3.

All the blue status leds are turned off and the rightmost blue led (closest to the power led, led number 1 in Acccess Point) will start blinking slowly when the boot procedure is finished and the unit is ready to be connected.

2.2. WWW Interface

Most Access Point and Access Server functionality can be controlled through the WWW interface by using any standard WWW browser.

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

When wrapfinder is launched, it automatically identifies the broadcast address of the network it runs in and sends a special query packet (UDP broadcast) to units. Most important information in their answers is then shown in table format.

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

Select a unit by clicking its serial number, and click Details to see more information (such as all Bluetooth addresses and friendly names). See Figure 2-5 for details.

Click Connect or double-click a serial number to connect to the selected Access Point or Access Server by using a WWW browser.

Click Exit to close the program.

To access the WWW interface, enter the IP address of Access Point or Access Server to the browser's address field and press Enter (see Figure 2-6).

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-7).

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

2.3. Shell Prompt Access

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

You can get to the shell prompt by using either SSH or the management console. The management console is only needed to change the network configuration settings if you cannot configure the network by using DHCP or Zeroconf. The management console is connected to Access Server with a serial cable. All further controlling activities can be performed remotely using SSH sessions over ethernet or Bluetooth LAN/PAN connection.

If you can establish an SSH connection from a device that has Bluetooth LAN Access or PAN profile support, you do not need the management console. Just connect to Access Server by using LAN Access or PAN profile. 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 baseband in question (model 2293 has three Bluetooth basebands, any of which can be connected). After you have connected to the server (no PIN code, username or password needed), establish an SSH connection to the device at 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).

        [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
      

2.4. Introduction to Configuration

When Access Server is installed and powered up for the first time, the default configuration settings are being used. With these settings, Access Server automatically configures its network settings assuming that it is connected to a LAN network with a DHCP server running. Additionally, 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 up, the only Bluetooth profiles enabled are the Object Push and File Transfer Profiles, used to send files to/from Access Server.

More Bluetooth profiles can be enabled, and most of Access Server settings can be configured by 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 short help texts.

2.5. Using the Setup WWW Interface

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

A typical WWW configuration page is shown in Figure 2-9 (This page can be found at Setup → Security settings)

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

• Status area

  The status area serves two purposes:

  • It indicates that the changes are permanently saved when the user clicks the Save button (or when the user clicks a toggling Yes/No link).

  • If invalid values were entered in one or more fields, an error message is shown in this area (see Figure 2-10).

  Figure 2-10. Trying to Save an Invalid Input

  Note: It is typically necessary to reboot Access Server for the changes to take effect. This can be done through the WWW interface (Advanced settings menu).

• Number or text entry fields

  Most of the configurable settings are text (or number) entry fields. For some fields, such as the IP address or netmask, there are restrictions on the input format. Setup validates the input at save time and accepts valid data only. The fields with errors are shown to the user so that mistakes can be fixed (see Figure 2-10).

• Help -link

  Click the Help link to retrieve the setup page again with requested help information displayed. For an example, see Figure 2-11.

  Figure 2-11. Help Links in WWW Setup

  Warning

  If you have made changes to the settings on the page before clicking Help and not saved them yet, they are lost.

• Yes and No radio buttons

  These buttons are typically used to configure a setting that can be either enabled or disabled, and this setting has no effect on the visibility of other settings.

• Reset button

  Reset button resets the fields to the values currently in use at Access Server. In other words, the Reset button discards unsaved changes.

  Note: The Reset button does not make a "factory reset".

• Save button

  Save button sends the WWW page to the setup application for validation. If the values in the fields are valid, they are permanently saved and the page is refreshed with the Changes have been saved. message at the top. The accepted values are shown in the page fields.

  If there were errors in the fields, these are shown as in Figure 2-10.

  Note: It is typically necessary to reboot Access Server for the changes to take effect. This can be done through the WWW interface (Advanced settings menu).

• Back link

  Press the Back link to return to the previous level of the Setup menu hierarchy.

  Note: Pressing the Back link does not save changes in the fields on the current page.

• Exit link

  Exit link quits the setup application and returns to the Access Server's main WWW page.

  Note: Pressing the Exit link does not save changes in the fields on the current page.

• Link to a configuration file

  Some of the configurable settings are actually editable configuration files, such as /etc/rc.d/rc.local for Setup → Advanced setting → System startup script. Clicking the link will retrieve the file for editing in the browser window, or create a new file, if it does not exist. See Figure 2-12.

  Figure 2-12. Editing Files in WWW Setup

  Note: You can edit any file through the WWW Setup. to edit files, navigate to Setup → Advanced setting → Edit other configuration files.

• Toggling Yes/No and on/off links

  Clicking the Yes/No link (see Figure 2-13) immediately changes the setting and saves the change. Typically these links are used display or hide further settings.

  Figure 2-13. Yes / No links in WWW Setup

  The on/off links in Setup → Applications → Default startup applications behave in a same way, making and saving the change immediately (see Figure 2-14).

  Figure 2-14. Selecting Default startup applications in WWW Setup

  Note: To configure the default startup applications from the command line, use the chkconfig command.

• Upload links

  The WWW Setup has settings that allow user to upload files to Access Server, for example Setup → Advanced → Upload a software update (see Figure 2-15).

  Figure 2-15. Uploading files via WWW Setup

  Use the Browse... button to select the file to be uploaded, and send it to Access Server by clicking Upload.

• Browsing files

  Some WWW Setup pages allow users to browse the Access Server file system or part of it, such as Setup → Advanced settings → Browse all files (see Figure 2-16).

  Figure 2-16. Browsing files via WWW Setup

  Click the directory names to navigate in the file system.

  Click a file name to view its contents.

  Click del to delete a file or an empty directory.

  Warning

  Deletion is not confirmed.

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

2.6. Using the setup Command Line Application

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

The setup application displays the settings in a hierarchical menu (see Figure 2-17). 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.

2.7. Resetting a Configuration

You can reset the default configuration with the setup -r command. The command requires rebooting of Access Server. 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
    

2.8. Exporting and Importing Configurations

You can export configuration settings (expect for passwords and the list of default startup applications) with the following command:

      [root@wrap /root]$ setup -o > settings.txt
    

The saved settings can later be restored with the following commands:

      [root@wrap /root]$ setup -m settings.txt
      [root@wrap /root]$ reboot