User Manual
Table Of Contents
- Access Server
- Table of Contents
- List of Tables
- Chapter 1. Introduction to Access Server
- Chapter 2. Getting Started with Access Server
- Chapter 3. Using the System
- 3.1. Network Interfaces
- 3.2. Bluetooth
- 3.3. Compact Flash Cards
- 3.4. USB Memory Dongles and Compact Flash Memory Cards
- 3.5. Servers
- 3.5.1. Finder
- 3.5.2. ObexSender
- 3.5.3. SMS Gateway Server
- 3.5.4. User Level Watchdog
- 3.5.5. Remote Management
- 3.5.5.1. Overview
- 3.5.5.2. Management Packet Format
- 3.5.5.3. Management Packet Information File Format
- 3.5.5.4. Management Operation Example: Hello World
- 3.5.5.5. Management Operation Example: Software Update
- 3.5.5.6. Management Operation Example: IPQUERY
- 3.5.5.7. Management with USB Memory Dongle or Compact Flash Memory Card
- 3.5.6. FTP
- 3.5.7. Web Server
- 3.5.8. SNMP
- 3.5.9. OpenVPN
- 3.5.10. SSH
- 3.5.11. Telnet
- 3.5.12. NTP
- 3.6. Utilities
- 3.7. Real Time Clock
- 3.8. Time Zone
- 3.9. System ReInstall and Upgrade
- Chapter 4. SPPoverIP
- Chapter 5. Obexsender
- Chapter 6. Software Development Kit
- 6.1. Introduction to SDK
- 6.2. Installing SDK
- 6.3. Creating Applications
- Chapter 7. iWRAP Bluetooth Interface
- 7.1. Terms
- 7.2. Starting the iWRAP Servers
- 7.3. Writing iWRAP Applications
- 7.4. Commands Controlling iWRAP
- INFO
- QUIT
- SET
- SAVE
- LOAD
- PING
- PONG
- ECHO
- LOCK
- UNLOCK
- SHUTDOWN
- SLEEP
- 7.5. Finding Bluetooth Devices
- INQUIRY
- NAME
- 7.6. Making a Bluetooth Connection
- CALL
- CONNECT
- NO CARRIER
- RING
- RINGING
- CLOSE
- LIST
- STATUS
- 7.7. Service Discovery
- SDPSEARCH
- SDPATTR
- SDPQUERY
- SDP bdaddr
- SDP ADD
- SDP DEL
- SDP LIST
- 7.8. Example Sessions
- 7.9. Error Codes
- Chapter 8. I/O API
- Chapter 9. Advanced Use Cases for Access Server
- Chapter 10. Certification Information and WEEE Compliance
- Appendix A. Directory Structure
- Appendix B. Setup Options
- Appendix C. Open Source Software Licenses
- Appendix D. Supported Hardware
Chapter 3. Using the System
This chapter describes the basic features of a Bluegiga Access Server. This includes information
on using Access Server as a Bluetooth LAN/PAN Access Point or a Bluetooth Serial Port Cable
Replacer, using the Web Server, ObexSender, and WRAP Package Management System. The
various ways of uploading content for browsing and/or downloading are also included, as well
as getting familiar with the utility applications.
Using the features described in this chapter does not require Access Server Software Develop-
ment Environment to be installed.
Note: The default username is root and the default password is buffy.
Note: Most of the configuration files are in Linux text file format, where the lines end with a sin-
gle Line Feed (LF, "\n") character. Some applications will not work if the configuration file format is
changed to MS-DOS format (this happens, for example, if you transfer the files to Windows for edit-
ing with Notepad), where the lines end with both Carriage Return and Line Feed (CR+LF, "\r\n")
characters.
3.1. Network Interfaces
The Access Server network interfaces are described in Table 3-1.
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.
eth0 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 PAN-GN connections.
bnep# These devices are used for incoming and outgoing PAN connections. These
devices are created, deleted and linked (to nap or gn) dynamically.
ppp# These devices are used for incoming and outgoing LAP connections. These
devices are created and deleted dynamically. By default, data coming from
ppp# is masqueraded to the nap device.
Table 3-1. Access Server Network Interfaces
3.2. Bluetooth
The iWRAP servers (one server in Access Server 2291, three in Access Server 2293) are automat-
ically started at power-up. By default, the Object Push and File Transfer Profiles are activated.
The iWRAP servers can be accessed and controlled (by applications or even interactively with a
telnet client) through the iWRAP interface, described in Chapter 7. Currently, there can be up to
14 simultaneous Bluetooth connections between a single master iWRAP server and up to seven
simultaneous slaves.
19