| WRAP Access Server: User's and Developer's Guide | ||
|---|---|---|
| <<< Previous | Next >>> | |
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.
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.
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.
All the blue status LEDs are turned off when the boot procedure is finished and the Access Server is ready to be connected.
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.
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.
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).
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).
After logging in, you can configure several WRAP Access Server settings (see Figure 2-7). These are discussed in detail in Section 2.4.
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 and PAN profiles are disabled by default. Use the WWW interface to enable them, if needed. The PAN profile can also be enabled by sending enable-pan.wpk (available on-line at https://www.bluegiga.com/as/current/enable-pan.wpk) to the Access Server using Bluetooth Object Push profile or by inserting a USB memory dongle with the file in the root directory.
Note: The default username is root with password buffy.
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:
Have a PC with a free COM port.
Power off the Access Server.
Configure your terminal application, like HyperTerminal in Windows, to use the settings in with the free COM port
Connect the serial cable shipped with the Access Server to your PC's free COM port.
Connect the serial cable to the management (user) port in the Access Server (see Figure 2-1).
Power on the Access Server.
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.
The management console is now activated and you should see the boot log in your terminal window.
Note: The boot process may stop at the following U-Boot prompt:
Hit any key to stop autoboot: 0 U-Boot>If this happens, enter command boot to continue to boot Linux.
Wait for the device to boot up and end with the following prompt:
Please press Enter to activate this console.
|
Press enter to activate the console. You will be logged in as root in the directory /root:
[root@wrap root]
|
You are ready to control the Access Server from the management console.
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.
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.
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, the only Bluetooth profiles enabled are the Object Push and File Transfer Profiles, used to send files to/from the Access Server.
More Bluetooth profiles can be enabled and most of the settings of the WRAP Access Server can be configured 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 short help text.
Note: The default username is root with password buffy.
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 Setup → Security settings)
The different parts of a WWW Setup page are discussed in the following:
Changes have been saved. -line
This line comes visible when the user saves the changes by clicking the Save button (or by clicking a toggling Yes/No link). It confirms that the changes have been saved into permanent storage.
If invalid values were entered into one or more fields, an error message is shown at this line (see Figure 2-9).
Note: Rebooting of the Access Server is typically necessary to take changes into use. This can be done via 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 (like IP address or netmask), there are restrictions on the input format. Setup validates the input at save time and accepts only valid data. The fields with errors are shown to the user so that mistakes can be fixed (see Figure 2-9).
Help -link
Clicking the Help link will retrieve the setup page again with requested help information displayed, like in like in Figure 2-10.
Note: If you have made changes to settings on the page before clicking Help and not saved them yet, they are lost.
Yes and No radio buttons
These buttons are used to configure typically a setting that can be either enabled or disabled, but that is not connected to another setting that would be hidden or shown according to the value of this one.
Link to a configuration file
Some of the configurable settings are actually editable configuration files, like /etc/httpd.conf for WWW passwords. 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-11.
Note: Any file can be edited via the WWW Setup, in page Setup → Advanced setting → Edit other configuration files.
Reset -button
Reset -button resets the fields to the values currently in use by the Access Server, i.e. it discards the changes that have not been saved yet.
Note: This does not make a "factory reset".
Save -button
Save -button sends the WWW page for the setup application for validation. If the values in the fields are valid, they are saved to permanent storage and the page is refreshed with Changes have been saved. message at top and the accepted values in the fields.
If there were errors in the fields, these are shown as in Figure 2-9.
Note: Rebooting of the Access Server is typically necessary to take changes into use. This can be done via the WWW interface (Advanced settings menu).
Back -link
Returns to the previous level of the Setup menu hierarchy.
Note: This does not save changes in the fields at the current page.
Exit -link
Quits the setup application and returns to the WRAP Access Server's main WWW page.
Note: This does not save changes in the fields at the current page.
Toggling Yes/No and on/off links
Clicking Yes/No link (see Figure 2-12) immediately changes the setting and saves the change. Typically this is used with settings that require some other settings to come visible or to hide according to this setting.
The on/off links in Setup → Applications → Default bootup applications behave in a same way, making and saving the change immediately (see Figure 2-13).
Note: To configure the default bootup applications from the command line, use the chkconfig command.
Upload links
WWW Setup has settings that allow user to upload files to the Access Server, for example Setup → Advanced → Upload a software update (see Figure 2-14).
Use Browse... button to select a file to be uploaded, and send it to the Access Server by clicking Upload.
Browsing files
Some WWW Setup pages allow users to browse the WRAP Access Server filesystem or part of it, like Setup → Advanced → Browse files (see Figure 2-15).
Click the directory names to navigate in the filesystem.
Click del to delete a file or an empty directory.
| Warning |
Deletion is not confirmed. |
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.
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.
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.
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.
You can export configuration settings (expect passwords and the list of the default bootup applications) with the following command:
[root@wrap /root]$ setup -o > settings.bak
|
The saved settings can later be restored with the following commands:
[root@wrap /root]$ setup -m settings.bak
[root@wrap /root]$ reboot
|
| <<< Previous | Home | Next >>> |
| Introduction | Using the System |