Silicon Laboratories Finland AP3241 User Manual

BLUEGIGA ACCESS DEVICES

USER GUIDE

Tuesday, 20 September 2011
Version 4.3

Copyright © 2001 - 2011 Bluegiga Technologies

Bluegiga Technologies reserves the right to alter the hardware, software, and/or specifications detailed herein at
any time without notice, and does not make any commitment to update the information contained herein.
Bluegiga Technologies assumes no responsibility for any errors which may appear in this manual. Bluegiga
Technologies' products are not authorized for use as critical components in life support devices or systems.

Bluegiga Access Server, Access Point, AX4, BSM, iWRAP, BGScript and WRAP THOR are trademarks of
Bluegiga Technologies.

The trademark and logo are registered trademarks and are owned by the Bluetooth SIG, Inc.Bluetooth
ARM and ARM9 are trademarks of ARM Ltd.
Linux is a trademark of Linus Torvalds.
All other trademarks listed herein belong to their respective owners.

TABLE OF CONTENTS

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2. Getting started with Bluegiga Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Powering up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.1 Access Point connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.2 Access Server AX4 connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1.3 Access Server connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2 Connecting to Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2.1 Using UPnP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2.2 Using WrapFinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3 Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Access Device software bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3. Connecting Access Device to network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.2 Using 2G and 3G modems for Internet connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3 Using Wi-Fi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3.1 Using Wi-Fi as Client (Managed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3.2 Using Wi-Fi as Access Point (Master) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.4 Shell prompt access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.4.1 Management console (Access Server 229x only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.4.2 Transferring files to/from Access Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4. Using services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1 Default services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.2 Managing software components (wpkgd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.3 Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.4 Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.5 System time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.5.1 Real time clock (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.5.2 Network time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.5.3 Time zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.6 Using remote file shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.6.1 Using NFS mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.6.2 Using CIFS mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.6.3 Mounting at boot time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.7 Factory reset and complete system upgrade (reflash) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.7.1 Resetting default system configuration with factory reset button . . . . . . . . . . . . . . . . . . . . . . 23

4.7.2 Complete system upgrade (reflash) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.7.3 Kernel, filesystem and configuration restore with "Factory Reset" memory dongle . . . . . . . . 24

5. Using utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.1 Wrapid - Bluegiga Access Device System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.2 Changing the Bluetooth Range and EDR Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.3 Badctl - Bluegiga Access Device Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.4 Finder - Bluegiga Access Device Finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.4.1 Finder Service and Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.4.2 Finder Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.5 Smsgw - Bluegiga SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.6 Watchdog - Bluegiga User Level Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6. Using 3rd Party Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6.1 Using USB, Compact Flash or microSD Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6.2 Using USB sound cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.3 Using USB webcams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7. Licenses, Warranty, Certification Information and WEEE Compliance . . . . . . . . . . . . . . . . . . . . . . . . . 33

7.1 Access Point Certification Information and WEEE Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

7.1.1 WEEE Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.2 Access Server Certification Information and WEEE Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.2.1 WEEE Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8. Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.1 Access Device directory tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.2 Tested 3rd Party Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8.3 Available Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

8.4 Enabled Busybox Applets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9. Contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

1 Introduction

Bluegiga Access Server product family offers cutting-edge wireless ® routers, Access Points andBluetooth
management tools - enabling you to create efficient and scalable networks. The open and adaptable platform
enables you to meet your applications' and customers' needs.

Bluegiga Access Server AX4 is a powerful Linux based wireless connectivity platform targeted for eHealth,
point-of-sale, proximity marketing, captive portal, and long range connectivity applications. The AX4Bluetooth
integrates three high performance class 1 radios, 802.11b/g radio and optional 2G or 3G modem.Bluetooth

Bluegiga Access Point 3241 is designed for various health and medical applications, proximityBluetooth
marketing, industrial telemetry applications, point of sales systems and digital pens. It provides with +20dBm

output power and a low noise amplifier 1000 meters long range between other Access Point 3241 or Bluetooth
device with matching output power and receiver sensitivity. Improved receiver sensitivy extends rangeBluetooth

also with class 2 devices like mobile phones.Bluetooth
Bluegiga Access Point 3201 is a size-optimized access device targeted at business applications. The product is

designed to fit into wireless applications where network performance, reliability, scalability and easyBluetooth
management are important design drivers.

Access Point 3201 is an evolution from Bluegiga's extremely reliable and successful Access Server product
family. Access Point product software and user interface make it compatible with Bluegiga Access Servers.
Access Points can be remotely managed from a centralized location with Bluegiga Solution Manager (BSM), a
web-based remote management and monitoring platform.

Access Server is a cutting edge wireless router. It supports multiple communication standardsBluetooth
including ethernet, WiFi, and GSM/GPRS/3G enabling full media-independent TCP/IP connectivity. Access
Server is easy to deploy and manage in existing wired and wireless networks without compromising speed or
security. For rapid deployment, Access Server configurations can easily be copied from one device to another by
using USB memory dongles. The device can be fully managed and upgraded remotely over SSH secured links.
Large numbers of Access Servers can easily be controlled using Bluegiga Solution Manager (BSM).

Usage scenarios and applications:

Medical and health device gateways
Proximity marketing
Point-of-sale and retail systems
Telemetry and machine-to-machine systems
Industrial gatewaysBluetooth

Key features:

Open Linux platform for adding local customer applications
Turn-key applications for networking and proximity marketingBluetooth Bluetooth
Supported profiles: SPP, ObjP, FTP, PAN, LAP, DI, HDPBluetooth
Software-configurable range to up to 100 meters (up to 1000 meters with Access Point 3241 or Access
Server AX4)
External and internal antenna options
Supports all key communication medias:

Bluetooth

Ethernet
WiFi, 2G/3G and NFC supported via USB (Access Server supports also via Compact Flash, AX4
has built-in support for WiFi and 2G/3G)

USB and RS232
Fast and easy to install
Uncompromised security: SSH, firewall, and 128 bit encryptionBluetooth
Bluetooth, CE, FCC and IC certified
Compliant with 1.1, 1.2 and 2.0 Specification (2.1 support with eHealth software)Bluetooth

Copyright © 2000-2011 Bluegiga Technologies Page 4 of 61

2 Getting started with Bluegiga Access Device

Access Point and Access Server can be controlled in four ways:

by using Bluegiga Solution Manager (see for details)BSM documentation
by using the WWW interface
by entering commands and using applications at the shell prompt
by sending and/or retrieving files to/from the device.

The default username is and the default password is .root buffy

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 Devices will also use Zeroconf (also known as Zero Configuration Networking or Automatic Private IP
Addressing) to get a 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 and AX4, also a direct ethernet cable works.

If you need to configure the network settings manually and cannot connect Access Server first by using Zeroconf, you can
do it by using the management console. Access Point and AX4, however, do not provide user access to the management
console. You can configure static network settings by sending the settings in a management packet for example using a
USB memory dongle.

2.1.1 Access Point connectors

The physical interface locations of Access Point 3201 and 3241 are shown below.

Copyright © 2000-2011 Bluegiga Technologies Page 5 of 61

In addition, Access Point 3241 has a hole in the bottom of the unit. Trough that hole user can press a button. If
that button is pressed while the unit is powered on, configuration is reset to factory defaults.

There is no power switch in Access Point 3201 or 3241. The adapter is the disconnection device; the socket-outlet shall be
installed near the equipment and shall be easily accessible. Unplug and plug the power adapter to switch the power on and
off. The power led in figure above is on when the power adapter is connected.

All the blue status leds are turned off and the status led number 1 blinks on four second intervals when the boot
procedure is finished and the unit is ready to be connected. Led number 2 is led which blinks quicklyBluetooth
every 30 seconds indicating service activity.Bluetooth

2.1.2 Access Server AX4 connectors

The physical interface locations of Access Server AX4 are described in figures below.

There is no power switch in Access Server AX4. The adapter is the disconnection device; the socket-outlet shall be
installed near the equipment and shall be easily accessible. Unplug and plug the power adapter to switch the power on and
off. The power led in figure below is on when the power adapter is connected.

All the blue status leds are turned off and the status led number 1 blinks on four second intervals when the boot
procedure is finished and the unit is ready to be connected. Bluetooth led, (led number 4) blinks quickly every 30
seconds indicating service activity.Bluetooth

Access Server AX4 has microSD card slot, factory reset button and SIM card slot (for optional, integrated

Figure : Physical interfaces of Bluegiga Access Point1

Figure : Physical interfaces of Bluegiga Access Server AX42

Figure : Access Server AX4 leds3

Copyright © 2000-2011 Bluegiga Technologies Page 6 of 61

modem) under a cover in the bottom of the unit. See the picture below.

2.1.3 Access Server connectors

The physical interface locations of Access Server 229x are described in figures below.

There is no power switch in Access Server. The adapter is the disconnection device; the socket-outlet shall be installed
near the equipment and shall be easily accessible. Unplug and plug the power adapter to switch the power on and off. The
power led in figure above is on when the power adapter is connected.

Figure : Connectors below Access Server AX4 bottom cover4

Figure : Physical interfaces of Bluegiga Access Server 229x5

Copyright © 2000-2011 Bluegiga Technologies Page 7 of 61

All the blue status leds are turned off and the rightmost blue led (closest to the power led) blinks on four second
intervals when the boot procedure is finished and the unit is ready to be connected. Bluetooth led, (blue led
furthest away from power led in Access Server) blinks quickly every 30 seconds indicating Bluetooth service
activity.

2.2 Connecting to Access Device

In order to manage your Bluegiga Access Device you need to be able to connect to it over the network. This can
be done in two ways: either by having the Access Device directly connected to the PC via a crossover ethernet
cable or by attaching the device to a switch in your local area network using a standard ethernet cable.

In the latter case, before continuing please make sure that your Access Device is powered on and properly
connected to your network. Notice that, by default all Access Devices are configured to acquire their IP
configuration from a DHCP server which must be present in the LAN. On the other hand, when PC and Access
Device are connected directly, both will use a random zeroconf address in the range 169.254.x.x/16 given the
lack of DHCP server in the simple network, and provided that also the PC is configured for dynamic IP
configuration. Anyway, also in this case the two devices will be in the same LAN and will be able to
communicate together.

Bluegiga Access Device can be managed either through a web browser or from the command line using SSH by
advanced users. Both methods require you to know the IP address of your device, and this can be found by
following the methods described below.

2.2.1 Using UPnP

To use the Universal Plug'n'Play feature for connecting Bluegiga Access Device web interface you need to have
Windows Vista or Windows 7 operating system. Go to . Now you should be able toStart - Computer - Network
see Access Devices appearing under group:Other devices

Figure : Leds and Compact Flash card slot of Access Server 229x6

Copyright © 2000-2011 Bluegiga Technologies Page 8 of 61

1.

2.

Bluegiga Access Devices will have name "Access Point/Server Wserial number" where the serial number
corresponds to the serial number in the sticker underneath the unit. To connect to Bluegiga Access Device web
interface you can either double click the icon of the correct device or right click the icon and select View device

.webpage

2.2.2 Using WrapFinder

A second way to discover the IP address of your Bluegiga Access Device is to use the Bluegiga Wrapfinder 2.0
application. The application is available from the . It allows you toBluegiga Wrapfinder Bluegiga Tech Forum
scan and find all Bluegiga Access Devices that are present in your local network.

Once you have downloaded the Wrapfinder file from the you need toBluegiga Tech Forum

Extract the .zip file to desired location
Launch Wrapfinder2.exe

Figure : Windows 7 listing UPnP devices7

Figure : Connecting to web setup using UPnP8

Copyright © 2000-2011 Bluegiga Technologies Page 9 of 61

After you have started the Wrapfinder software you might be prompted by the firewall applications to allow the
use of certain ports by Wrapfinder. There are cases in which it is wise to temporarily disable completely the
software firewall running in the PC, if any. Once the Wrapfinder utility has started it automatically runs a search
through the local network and lists all found Bluegiga Access Devices. You can refresh the search by clicking

-button. Sometimes on slow networks two consecutive presses are needed.Find Devices

To access Bluegiga Access Device you can either double click it or select the one you want to connect to and
click -button.Open web interface

Figure : Wrapfinder 2.0 started listing Access Devices within local network9

Copyright © 2000-2011 Bluegiga Technologies Page 10 of 61

2.3 Web interface

When you have accessed the Bluegiga Access Device web interface using either of the methods described in
previous chapter you should get main WWW page shown below:

If you see a login prompt instead of this page, you have already eHealth software bundle installed. See eHealth software

for more information.user guide

From the top-level page, click to log in to the configuration interface. The default username is and theSetup root
default password is :buffy

After logging in, you can configure several system and application settings:

Copyright © 2000-2011 Bluegiga Technologies Page 11 of 61

For details of WWW interface components, see .Default web interface and iWRAP Bluetooth user guide

2.4 Access Device software bundles

Access Device application use cases may require additional software packages to be installed for full
functionality. For key applications, these are also available in software bundles. A bundle is a single update
packet which contains all software packages for certain application. You can order Access Devices with a bundle
of your choice pre-installed. Currently available bundles are listed below:

Bundles other than which comes inside system upgrade reflash packet are available onobexsenderbundle
Access Device DVD in directory or installable with command . See wpk wpkgd install bundlename Managing

for installation instructions.Software Components (wpkgd)

Table : Software bundles for Access Devices1

Bundle name Description Notes

obexsenderbundle ObexSender Built in and installed by default if no other bundle was ordered. See

separate ObexSender documentation.

ehealthbundle eHealth

software
bundle

Only available for Access Point 3201 and 3241 in SW version 4.3.
See separate eHealth user guide.

captiveportalbundle Captive Portal

bundle

See Captive Portal documentation.

oggplayerbundle Ogg Player

bundle

Available for testing purposes.

Copyright © 2000-2011 Bluegiga Technologies Page 12 of 61

3 Connecting Access Device to network

This chapter describes Access Device network interfaces and WiFi and modem configuration. For additional
documentation, see separate "Networking Guide" document.

3.1 Network interfaces

The network interfaces used in Access Devices are described in table below:

3.2 Using 2G and 3G modems for Internet connectivity

Access Server and Access Point can be connected to Internet over 2G/3G using USB modems from several
vendors. Access Server 229x can also connect to Internet using a GSM/GPRS Compact Flash card or an
external modem connected to its serial port. The supported devices are listed in Tested 3rd Party Peripherals
document.

Some Access Server AX4 models ship with integrated 2G or 3G modem.
Software packages required to use modem to connect to Internet are installed by default.
The operating system automatically identifies supported USB or Compact Flash modem devices and loads

correct drivers when they are inserted.
You can enable the modem and configure its settings, such as the modem device and connection script details,

by using the application or its WWW interface at setup Setup - Network settings - Enable modem interface

A reboot is needed for the new settings to take effect. From WWW Setup, you can do this at Setup - Advanced settings -

.Reboot system (confirm)

When modem connection to Internet is enabled, by default Access Device tries to establish Internet connection
with modem only once when the device boots up.

Table : Access Device network interfaces and their description2

Interface Description

nap Dynamic virtual ethernet ("cable") device. This is the device having an IP address. All the

programs should use this device instead of eth0.
nap:9 Alias interface of nap device for zero configuration networking.
eth0 The real ethernet device, which is dynamically linked to the nap device. Do not use this device,

use nap instead.
wlan0 Wi-Fi device. In the client mode (default), this device has its own IP address. In the access

point mode, it is dynamically linked to the nap device (the default interface).
wifi0 Virtual control device for wlan0. Do not use this device.
gn Virtual device for iWRAP PAN-GN connections.Bluetooth
bnep# These devices are used for incoming and outgoing iWRAP PAN connections. TheseBluetooth

devices are created, deleted and linked (to nap or gn) dynamically.
ppp# These devices are used for incoming and outgoing iWRAP LAP connections or for aBluetooth

modem Internet connection. In LAP use, these devices are created and deleted dynamically

and traffic coming from them is masqueraded to the nap device. When modem is enabled, all

traffic to ppp interfaces is also masqueraded.
lo Local loopback interface.

Copyright © 2000-2011 Bluegiga Technologies Page 13 of 61

It is therefore recommended to enable option Setup - Network settings - Modem settings - Force connection

.open

With this enabled, modem Internet connection is checked every 10 minutes with the command. If the checkping
fails, modem connection is restarted.

Some modems power up in mass storage mode. Supported modems will be switched to modem mode automatically.
Switching from mass storage mode to modem mode might take so long that first attempt to make a connection fails and
there are no further tries if option is turned off. Even if it is turned on, it can take up to 10 minutesForce connection open
before connection is properly established.

By default, uses host 194.100.31.45 (bluegiga.com) for checking that the modem InternetForce connection open
connection is working. You might want to specify a reliable host closer to your system in Setup - Network settings -

. The test host must respond to ICMP ECHO_REQUEST packetsModem settings - IP address used in force check

generated by command, otherwise the modem connection is reset every ten minutes.ping

If you also want to use the ethernet connection, you must remove it from the default interface ( ) bridge and configure itsnap
network settings individually using the application while keeping the default interface network settings in their defaultsetup
(dynamic) state.

3.3 Using Wi-Fi

AX4 is delivered with integrated Wi-Fi. All Access Devices support several USB Wi-Fi dongles. The supported
devices are listed in document.Tested 3rd Party Peripherals

Ad hoc mode is not supported.

WPA/WPA2 passphrase length must be 8..63 characters.

3.3.1 Using Wi-Fi as Client (Managed)

USB Wi-Fi client device support (including for WPA or WPA2 encryption support) is installed bywpa-supplicant
default.

Enable Wi-Fi interface using the application or its WWW interface at setup Setup - Network settings - Enable

.Wi-Fi interface

When the correct kernel modules are installed and Wi-Fi interface enabled, Access Device notices when a
supported Wi-Fi card is inserted and tries to use it in the client mode, without encryption. So, if there is an open
Wi-Fi access point in range, you will automatically connect to it.

To change Wi-Fi settings, use the application or its WWW interface at setup Setup - Network settings - Wi-Fi

. is used to manage Wi-Fi connections. Supported encryption methods are WEP andsettings Wpa-supplicant

WPA/WPA2. Use the menu option to change network SSID and encryption method.Edit configuration file
Use following configurations to enable unencrypted, WEP or WPA/WPA2 encrypted connections:

no encryption

network = {
# no encryption
ssid="Bluegiga"
key_mgmt=NONE
}

Copyright © 2000-2011 Bluegiga Technologies Page 14 of 61

WEP

network = {
# WEP encryption
ssid="Bluegiga"
key_mgmt=NONE
wep_key0="ASCII WEP key"
#wep_key0=0123456789
wep_tx_keyidx=0
}

ASCII WEP key is given in quotes (e.g. "abcde" or "abcdeabcdeabc")
hex digits are given without quotes (e.g. 0123456789 or 01234567890123456789012345)

WPA/WPA2

network = {
# WPA/WPA2 encryption
ssid="Bluegiga"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WPA shared key"
}

shared key length must be 8..63 characters

A reboot is needed for the new settings to take effect. From WWW Setup, you can do this at Setup - Advanced settings -

Reboot system (confirm)

The current software version does not support Wi-Fi bridging in the client (managed) mode, which means that traffic from
Wi-Fi cannot be forwarded to wired ethernet.

To debug Wi-Fi issues, you can collect and review Wi-Fi diagnostics information using application or itssetup
WWW interface at .Setup - Network settings - Wi-Fi settings - Collect Wi-Fi diagnostics

In addition, a standard set of command line wireless utilities is provided to fine-tune your Wi-Fi configuration:

iwconfig
iwlist
iwpriv

For more information on these utilities, see: http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html

3.3.2 Using Wi-Fi as Access Point (Master)

Please refer to document to see which USB Wi-Fi dongles support access pointTested 3rd Party Peripherals
mode. The required software packages are installed by default.

Enable Wi-Fi interface using the application or its WWW interface at setup Setup - Network settings - Enable

.Wi-Fi interface

To change Wi-Fi settings, use the application or its WWW interface at setup Setup - Network settings - Wi-Fi

.settings

To begin with, change the setting to . is used by default to manageAct as a Wi-Fi Access Point yes Hostapd
Wi-Fi access point mode.

To change settings, use the application or its WWW interface at hostapd setup Setup - Network settings Wi-Fi

Copyright © 2000-2011 Bluegiga Technologies Page 15 of 61

. settings is used to change hostapd driver backend, SSIDsettings - Basic configuration Basic configuration
of your network, hardware mode, country code, Wi-Fi channel or maximum simultaneous client number. Default
values should work with most of USB Wi-Fi dongles.

Depending on used encryption, use menu option and change the following lines:Edit configuration file

No encryption
Change nothing more.

Typical WPA2 encryption (WPA2-CCMP (AES))

wpa=2
wpa_passphrase=verysecretpassphrase
rsn_pairwise=CCMP

Other encryptions:

WEP encryption

wep_default_key=0
wep_key0="mysecretkey

WPA-TKIP

wpa=1
wpa_passphrase=verysecretpassphrase

WPA2-TKIP

wpa=2
wpa_passphrase=verysecretpassphrase

WPA-TKIP and WPA2-TKIP

wpa=3
wpa_passphrase=verysecretpassphrase

WPA-CCMP (AES)

wpa=1
wpa_passphrase=verysecretpassphrase
wpa_pairwise=CCMP

WPA2-CCMP (AES)

wpa=2
wpa_passphrase=verysecretpassphrase
rsn_pairwise=CCMP

WPA-CCMP and WPA2-CCMP (AES)

wpa=3
wpa_passphrase=verysecretpassphrase
wpa_pairwise=CCMP
rsn_pairwise=CCMP

Copyright © 2000-2011 Bluegiga Technologies Page 16 of 61

1.

2.

3.

4.

5.

6.

7.

8.

3.4 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 SSH. When you are connected to the same LAN
network with your Access Server or Access Point, you can find its IP address using uPnP or wrapfinder
application (see ).Getting started with Bluegiga Access Device

You can use SSH to get shell prompt access also using Bluetooth LAN Access or PAN profile. Access Devices
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 and AX4 have three Bluetooth basebands,
any of which can be connected).

After you have connected to the server (no PIN code, username or password is needed), establish an SSH
connection to the device at the other end of the connection. Again, you can use the application towrapfinder
find the IP address.

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 the file (available on-line at enable-pan.noarch.wpk

) to Access Device by using Bluetooth Object Push profile orhttp://update.bluegiga.com/as/4.3/misc/enable-pan.noarch.wpk

by inserting a USB memory dongle with the file in its root directory to Access Device's USB port.

3.4.1 Management console (Access Server 229x only)

If you do not have a Bluetooth LAN/PAN client and if Access Server is not connected to your LAN, or if you do
not know the IP address given to Access Server, you can get the first shell prompt access by using 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. After you have configured the network settings by using the management
console, all further controlling activities can be performed remotely using SSH sessions over ethernet or
Bluetooth LAN/PAN connection.

To setup the management console, proceed as follows:

Have a PC with a free COM port.
Power off Access Server.
Configure your terminal application, such as in Windows, to use the settings below forHyperTerminal
your computer's free COM port

Connect the serial cable shipped with Access Server to your PC's free COM port.
Connect the serial cable to the management (user) port in Access Server (see Figure 1-2).
Power on Access Server.
Enter letter in the terminal application during the first five seconds.b
The management console is now activated and you can see the boot log in your terminal window.

Table : Management console serial port settings3

Setting Value

Speed 115200bps
Data Bits 8
Parity None
Stop Bits 1
Flow Control None

Copyright © 2000-2011 Bluegiga Technologies Page 17 of 61

8.

9.

10.

11.

The boot process may stop at the following prompt:U-Boot

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 to activate the console. You will be logged in as root in directory :Enter /root

[root@wrap root]

You can now control Access Server from the management console.

3.4.2 Transferring files to/from Access Device

You can transfer files to and from Access Server and Access Point by using, for example:

SCP (secure copy over SSH).
SFTP (secure FTP connection over SSH).
FTP (plain FTP connection). FTP is disabled by default for security reasons. Use SFTP instead.Note:
FTP server is not installed by default. You can install it from software package .ftpd
Bluetooth OBEX (Object Push and File Transfer Profiles) to/from directory in Access Server or/tmp/obex
Access Point.
NFS (mount an NFS share from a remote computer as a part of Access Server's or Access Point's file
system).
SSHFS (mount an Access Server or Access Point directory over SSH as a part of any other Linux host
file system).
To download and install SSHFS, visit .http://fuse.sourceforge.net/sshfs.html
CIFS (mount a Common Internet File System share from a remote computer as a part of Access Server's
or Access Point's file system). A CIFS client, available in a separate software packet , iscifs-client
required.
USB memory dongle.
Xmodem/Ymodem/Zmodem (use commands from the management console). You canrz/rx/rb/sz/sx/sb
install these commands from software package .rzsz

The management console is only available for Access Server 229x.

Copyright © 2000-2011 Bluegiga Technologies Page 18 of 61

4 Using services

This chapter contains documentation of the default system services available in Access Devices.

4.1 Default services

Access Device services are started automatically at system power-up or when another server daemon needs
them. You can check which servers are currently installed and/or configured to start at system power-up with
command or navigating in WWW Setup to chkconfig --list Setup - Applications - Default startup

.applications

The servers and their purposes are described briefly below:

Server Description

bluetooth Bluegiga iWRAP Server, which is described its own user guide.Bluetooth
connector Bluegiga Connector, which automatically opens and maintains connections to specified Bluetooth

devices. This server is configurable using the application and its WWW interface.setup

crond A daemon to execute scheduled commands. This server is configurable through the

file or the command in the same way as any Linux crond./var/spool/cron/crontabs/root crontab

dhcpd This server is a DHCP daemon for providing automatic network configuration for clients in the

network. Notice that, by default, this server is only enabled for the interface, used by iWRAP gn

PAN Generic Networking profile. You can enable it for interface by usingBluetooth nap

command or from WWW Setup at chkconfig dhcpd on Setup - Applications - Default startup

. You will then need to configure static network settings at applications Setup - Network

and ensure you have matching DHCP server settings inSettings - Default interface settings

file ./etc/udhpcd-nap.conf
finder Bluegiga WRAP Finder Service. See Finder - Bluegiga Access Device Finder
httpd

Web server. Another Web server, , is available as a separate software component, alsolighttpd

installed and used by and .captiveportalbundle ehealthbundle
inetd Internet services daemon. Notice that this server is disabled by default. Use the WWW interface

of application or the command to enable it. To configure , edit itssetup chkconfig inetd on inetd

configuration file ./etc/inetd.conf
ntpd Network Time Protocol (NTP) daemon.
obexsender Bluegiga ObexSender server. See separate documentation for detailed information.
pppd

Point to Point Protocol daemon. Modem network connections are established using , andpppd

iWRAP server uses it with Lan Access Profile.Bluetooth
serialport Bluegiga iWRAP Serial Port Profile server. iWRAP Bluetooth user guide for moreBluetooth

information.
sshd SSH daemon.
syslogd

System logging daemon. This server can be configured by using the application or itssetup

WWW interface.
telnetd Telnet protocol server. Notice that this server is disabled by default for security reason. Use the

application or the command to enable it.setup chkconfig telnetd on
udhcpcd DHCP client daemon for automatic network configuration.
watchdog Bluegiga user level watchdog.
wpkgd Bluegiga package management system daemon.
zcip Zero configuration networking service.

Copyright © 2000-2011 Bluegiga Technologies Page 19 of 61