Access Server User’s and Developer’s Guide Bluegiga Technologies
Access Server: User’s and Developer’s Guide by Bluegiga Technologies Published 2007-01-22 (3.1) Copyright © 2001, 2002, 2003, 2004, 2005, 2006, 2007 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.
Table of Contents 1. Introduction to Access Server............................................................................................................1 1.1. Licenses and Warranty ............................................................................................................2 1.2. Bluegiga Technologies Contact Information ........................................................................2 2. Getting Started with Access Server.........................................................
3.5.6. FTP ...............................................................................................................................31 3.5.7. Web Server ..................................................................................................................31 3.5.8. SNMP ..........................................................................................................................31 3.5.9. OpenVPN.....................................................................................
6.3.1.2. Running Examples........................................................................................62 6.3.2. Creating a New Project .............................................................................................63 6.3.3. Building from the Command Line ..........................................................................64 6.3.4. Transferring an Application to Access Server .......................................................64 6.3.4.1.
SDP ADD ............................................................................................................................111 SDP DEL..............................................................................................................................112 SDP LIST .............................................................................................................................113 7.8. Example Sessions ...............................................................................
B.5.1.7. File tranfer profile settings ........................................................................151 B.6. Advanced settings ...............................................................................................................151 B.6.1. System information.................................................................................................153 B.6.2. Reboot system (confirm) ........................................................................................153 B.7.
List of Tables 2-1. The Management Console Port Settings ........................................................................................8 3-1. Access Server Network Interfaces.................................................................................................19 3-2. Access Server Servers......................................................................................................................25 3-3. Access Server Utilities.....................................................
Chapter 1. Introduction to Access Server Bluegiga’s WRAP™ product family offers for device manufacturers, integrators, companies and developers a simple and fast way to set-up wireless communication systems between standard or proprietary devices, networks, machines and instruments. Access Server is a cutting edge wireless Bluetooth router. It supports multiple communication standards including Ethernet, WiFi, and GSM/GPRS enabling full media-independent TCP/IP connectivity.
Chapter 1. Introduction to Access Server • Simple and secure mounting accessory available • Bluetooth, CE, and FCC certified • Compliant with Bluetooth 1.1, 1.2 and 2.0 Specification 1.1. Licenses and Warranty Warning Bluegiga Technologies is hereby willing to license the enclosed WRAP product and its documentation under the condition that the terms and conditions described in the License Agreement are understood and accepted.
Chapter 2. Getting Started with Access Server Access Server can be controlled in three ways: • by using the WWW interface • by entering commands and using applications at the Access Server shell prompt • by sending and/or retrieving files to/from Access Server. Note: The default username is root and the default password is buffy. 2.1. Powering Up To get started with Access Server, connect it to your local area network (LAN) by using an Ethernet cable, and connect the power adapter.
Chapter 2. Getting Started with Access Server Figure 2-2. Access Server LEDs All the blue status LEDs are turned off when the boot procedure is finished and Access Server is ready to be connected. 2.2. WWW Interface Most Access Server functionality can be controlled through the WWW interface by using any standard WWW browser. The wrapfinder application (see Figure 2-3), available for the Windows operating system from Bluegiga Techforum (http://www.bluegiga.
Chapter 2. Getting Started with Access Server UDP broadcast when it was launched. Note: Normally, there are two entries for each 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 Access Servers. A new scan can be done by clicking Rescan.
Chapter 2. Getting Started with Access Server Figure 2-5. 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 Access Server settings (see Figure 2-7). These are discussed in detail in Section 2.4.
Chapter 2. Getting Started with Access Server Figure 2-7. The WWW Configuration Interface of Access Server 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.
Chapter 2. Getting Started with Access Server 2.3.1. Management Console 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. To setup the management console, proceed as follows: 1. Have a PC with a free COM port. 2. Power off Access Server. 3.
Chapter 2. Getting Started with Access Server Section 2.2). If you cannot get the IP address by using the wrapfinder, another way to see the IP address of Access Server is to connect with a management console (see previous section), power on the unit and, after the system is up and running, give the ifconfig nap command. The inet addr field for the nap interface contains the IP address of Access Server. For example, in the following capture from the management console, the IP address is 192.168.42.3.
Chapter 2. Getting Started with Access Server 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.
Chapter 2. Getting Started with Access Server 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-9). Figure 2-9.
Chapter 2. Getting Started with Access Server Figure 2-10. 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.
Chapter 2. Getting Started with Access Server Figure 2-11. 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. • 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".
Chapter 2. Getting Started with Access Server • 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. • Toggling Yes/No and on/off links Clicking the Yes/No link (see Figure 2-12) immediately changes the setting and saves the change. Typically these links are used display or hide further settings. Figure 2-12.
Chapter 2. Getting Started with Access Server Figure 2-13. Selecting Default Bootup Applications in WWW Setup Note: To configure the default bootup 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-14).
Chapter 2. Getting Started with Access Server Figure 2-14. 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 −→ Browse files (see Figure 2-15).
Chapter 2. Getting Started with Access Server Figure 2-15. Browsing files via WWW Setup Click the directory names to navigate in the file system. 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.
Chapter 2. Getting Started with Access Server 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 you press Enter, you cannot navigate in the setup application. 2.7. Resetting a Configuration You can reset the default configuration with the setup -r command. The command requires rebooting of Access Server.
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.
Chapter 3. Using the System 3.2.1. iWRAP Password Protection The access to iWRAP can be password protected. The default password is buffy, but it can be set off or changed with the setup application (see Section 2.4). The password is case sensitive. The password must be typed in as the first command after the server has replied with "READY." 3.2.2. LAN Access Profile This profile is not automatically started at boot. The default settings can be changed with the setup application (see section Section 2.
Chapter 3. Using the System to the user devices with (short) serial cables. The cable between user device A and Access Server device A must be a cross-over cable. The cable between user device B and Access Server device B must be similar (direct or cross-over) to the one used in state A). If RTS/CTS handshaking is used to ensure correct data transfer, the serial cables must have these pins connected. Notice that this handshaking is "local": it takes place between the user device and Access Server.
Chapter 3. Using the System - as bdaddr and 1 as channel tells obexput that it will be launched by the iWRAP server, and that data connection is bound to standard input and output. 3.2.5. PAN Profiles Access Server has support for all PAN profile modes: Personal Area Network User (PANU), Network Access Point (NAP) and Generic Networking (GN). Accepting incoming PAN connections to any of these modes is disabled by default for security reasons.
Chapter 3. Using the System Usage: serialbluetooth [options] To see the command options, enter the serialbluetooth --help command. Basically, serialbluetooth takes commands from a serial port and forwards them to the iWRAP server. All the commands available through iWRAP are also available through serial port. There are two exceptions: 1. After making an outgoing RFCOMM data call, all input from the serial port is forwarded to the data socket, not to the control socket.
Chapter 3. Using the System 3.3.2. Compact Flash GPS Card The operating system automatically identifies the Compact Flash GPS card when it is inserted. At that time, the device file /dev/ttyS0 is created and the GPS card can be accessed by using that device with the serial port settings the GPS card uses. The supported Compact Flash cards are listed in Appendix D. 3.3.3. Compact Flash Wi-Fi Cards Access Server supports Prism II/III based CF Wi-Fi cards.
Chapter 3. Using the System Note: Always remember to unmount the memory dongle or memory card with command: [root@wrap /]$ umount /mnt/usb 3.5. Servers Access Server server applications are started automatically at system power-up or when an iWRAP server or the Internet services daemon needs them. The servers and their purposes are described in Table 3-2. Server Description bluetooth Access Server iWRAP Server, which is described in detail in Chapter 7. finder WRAP Finder Service.
Chapter 3. Using the System Server Description telnetd Telnet protocol server. Notice that this server is disabled by default. Use the setup application or the chkconfig telnetd on command to enable it. zcip Zero configuration networking service. ntpd Network Time Protocol (NTP) daemon. Table 3-2. Access Server Servers 3.5.1.
Chapter 3. Using the System SMS messages. By default, the Compact Flash card is used. The PIN code query of the SIM card at power-up must be disabled. WRAP SMS Gateway Server is disabled by default. To enable it, use the setup application’s WWW interface, as described in section Section 2.4. Enabling is done at Setup −→ Applications −→ Default bootup applications −→ smsgw.
Chapter 3. Using the System Figure 3-2. WRAP Remote Management Architecture A management action is performed using the following procedure: 1. A customer system prepares the management packet (*.wpk). 2. The management packet is delivered to Access Server, to the packaging daemon’s inbox directory. You can currently use Bluetooth, SCP, SFTP and plain FTP to do this. The packet can also be transmitted using a USB memory dongle, Compact Flash memory card or through the WWW Setup interface. 3.
Chapter 3. Using the System 3.5.5.3. Management Packet Information File Format The management packet information file (wpkg.pif) consists of tags and their data, described here: %wpkg-version: 2 Contains information for version checking. 2 is currently the only supported version. It is also the default value. %wpkg-prepare: [command line[s]] One or more commands (all commands are lines until the next tag is interpreted as a command line) to execute.
Chapter 3. Using the System echo Hello world This will generate a reply packet containing text "Hello world". You can generate the wpk file simply by giving the command tar czf hello.wpk wpkg.pif. 3.5.5.5. Management Operation Example: Software Update See below for a more complex example of wpkg.pif: %wpkg-version: 2 %wpkg-prepare: FOO=‘pwd‘ cd / tar xzf ${FOO}/files.tar.gz echo Done. This example will extract files from the included files.tar.gz file.
Chapter 3. Using the System 3.5.5.7. Management with USB Memory Dongle or Compact Flash Memory Card When an USB memory dongle or Compact Flash memory card is inserted, Access Server automatically tries to mount it (using VFAT type). If the mount is successful, Access Server scans the root for *.wpk packets. If a packet is found, the WRAP Package daemon handles it. Optional reply packets are saved back to the root folder (unless otherwise stated in the %wpkg-reply tag). 3.5.6.
Chapter 3. Using the System 3.5.10. SSH By default, users can use SSH to log in (or SCP and SFTP to transfer files) as user root with password buffy. The password can be changed on Access Server by using command passwd or with the setup application. 3.5.11. Telnet If you enable telnet, users can log in over telnet as user root with password buffy. The password can be changed on Access Server using the command passwd or with the setup application. Note: Do not enable telnet because it is insecure.
Chapter 3. Using the System Application Description chat Automated conversational script with a modem. chgrp Change group ownership. chkconfig Updates and queries runlevel information for system services. chmod Change file access permissions. chown Change file owner and group. chroot Run command or interactive shell with special root directory. clear Clear the terminal screen. cmp Compare two files. cp Copy files and directories. cpio Copy files to and from archives.
Chapter 3. Using the System Application Description getty Opens a tty, prompts for a login name, then invokes /bin/login. grep Print lines matching a pattern. gunzip Expand gzip compressed files. gzip Compress files into gzip format. head Output the first part of files. hexdump A filter which displays the specified files, or the standard input, if no files are specified, in a user specified format. hostid Print out a unique 32-bit identifier for the machine (not yet implemented).
Chapter 3. Using the System Application Description obexbrowser The WRAP obexbrowser. A command line OBEX client interface. obexget The WRAP OBEX tool for retrieving a file from a remote device with ObjP/FTP support. obexput The WRAP OBEX tool for sending a file to a remote device with ObjP/FTP support. pack_cis Convert a text description of a PCMCIA Card Information Structure (CIS) to its packed binary representation. passwd Update a user’s authentication token(s).
Chapter 3. Using the System Application Description supportinfo Output collectively all the system status and configuration information. sync Flush filesystem buffers. tail Output the last part of files. tar Tar archiving utility. tcpdump Utility for dumping traffic on a network. Available in a separate software package. telnet User interface to the TELNET protocol. test Check file types and compare values. time Run command and display its resource usage information when finished.
Chapter 3. Using the System 3.7. Real Time Clock The system clock is read from the battery operated real time clock during boot. The time between the system time and the real time clock is automatically synchronized when the system is rebooted using the reboot command. Synchronizing can also be done using the hwclock -systohc --utc command. Give command hwclock --help for more information about the hwclock utility. 3.8. Time Zone The default time zone in Access Server is UTC.
Chapter 4. SPP-over-IP SPP-over-IP is a special functionality of iWRAP Bluetooth servers running in Access Servers. It offers a transparent way to transmit data from Bluetooth Serial Port Profile (SPP) enabled devices to server computers or PCs. Several transport medium are supported, such as Ethernet, Wi-Fi or and GPRS. 4.1.
Chapter 4. SPP-over-IP Figure 4-1. SPP-over-IP Network Architecture All the server computer needs to do is to listen for incoming TCP connections from Access Server to a specified TCP port and receive/send the application data. 4.1.2. Repeater Operation The SPP-over-IP application can also be used in a so-called repeater mode.
Chapter 4. SPP-over-IP requires that Access Server is equipped with a working GSM/GPRS compact flash card. See Appendix D for supported cards. Figure 4-3. SPP-over-IP over GPRS Notice when using GPRS: • Data upload rate is around 8-12kbps (depending on GPRS card) • Data download rate is around 32-48kbps (depending on GPRS card) • Data transmission delays can be very high, sometimes even seconds • GPRS connection may be unreliable and break easily.
Chapter 4. SPP-over-IP Figure 4-4. Access Server Opening the Connections 4.1.5. SPP-over-IP and COM Ports SPP-over-IP can also be used together with Tactical Software’s Serial/IP® software. Serial/IP software simply converts the TCP connections into virtual COM ports on the host computer. This is very useful in applications, which do not have support for TCP/IP but support COM ports instead. Figure 4-5. SPP-over-IP with Serial/IP An evaluation version of Serial/IP can http://www.tacticalsoftware.
Chapter 4. SPP-over-IP 4.2.1. Preparations SPP-over-IP is easiest to configure through WWW setup, which allows you to access all the necessary configurations. First, you must figure out Access Server’s IP address (if it is connected to a TCP/IP network). This is easiest to do with the WRAPFinder software: 1. Start the WRAPFinder software 2. Scan your network for available Access Servers 3. Choose the correct Access Server 4.
Chapter 4. SPP-over-IP Figure 4-7. WWW Setup Login 6. Type in you user name and password and you get access to the main view of the setup: Figure 4-8. WWW Setup Main View Note: The "basic" Bluetooth Serial Port Profile must be disabled for SPP-over-IP to work. By default, this is the case. You can verify it by checking that serialport service (which implements the profile) is off in WWW Setup −→ Applications −→ Default startup Applications (see Figure 4-9).
Chapter 4. SPP-over-IP Figure 4-9. Checking that Bluetooth Serial Port Profile is disabled. 4.2.2. Preparations SPP-over-IP settings are modified in iWRAP servers’ configuration file /etc/bluetooth.confwhich can be edited by navigating in WWW Setup to Setup −→ Bluetooth settings −→ Edit startup script. To enable SPP-over-IP, add lines similar to following to the end of that file (lines starting with # are comments which can be left out): # Forward incoming connection to IP 192.168.42.
Chapter 4. SPP-over-IP The text "SPP-over-IP" is the name of the service shown in Bluetooth service discovery. Normally, there should be no need to specify a different name, but nobody forces you to use "SPPover-IP". In the example, connections are forwarded to a server listening for incoming connections to TCP port 7444 in host with IP address 192.168.42.99. You must change these to match your system. See Figure 4-10 for WWW Setup example of configuration. Figure 4-10.
Chapter 4. SPP-over-IP You must replace the Bluetooth address used in the example (00:07:80:80:bf:01) with the Bluetooth address of the Access Server, on which you want to receive the PAN connection. Note: The server receiving the PAN connection must have the PAN-NAP profile enabled. This is by default not the case, so in setup or its WWW interface, ensure that the setting at −→ Bluetooth settings −→ Bluetooth profiles −→ Enable PAN network access point profile says yes. No other configuration is needed.
Chapter 5. Obexsender Obexsender is one of the built-in applications in Access Server. It is dedicated to Bluetooth proximity marketing, content distribution, location based services, and much more. Access Server plus Obexsender provide the user with a ready platform to start content distribution including all the necessary Bluetooth functions from discovering the devices to transmitting the content.
Chapter 5. Obexsender 5.2. Use Cases This chapter describes some possible Obexsender use cases. 5.2.1. Content Push This is the standard functionality in Obexsender. In content push mode, Obexsender is scanning for devices and pushing it to clients who belong to the target group (not opted out by filtering). Figure 5-2. Obexsender Use Case: Content Push 5.2.2. Content Pull Obexsender can also be configured into a content pull mode. In this mode, the transaction is initiated by the user.
Chapter 5. Obexsender Figure 5-3. Obexsender Use Case: Content Pull 5.3. Configuration This chapter contains instructions from the most basic Obexsender configuration to the more advanced use cases. 5.3.1. Getting Started The easiest and fastest way to configure Obexsender is through the WWW setup. To do this, your Access Server must be connected to the same network as your PC or, alternatively, you can also use a direct Ethernet cross cable or a Bluetooth PAN connection (see Section 3.2.
Chapter 5. Obexsender Figure 5-4. WRAPFinder 2. Next, select the correct Access Server and press the Connect button in the WRAPFinder user interface. An internet browser window opens with the Access Server IP address in the address bar. Figure 5-5. Access Server WWW Setup 3. Click the Setup link. A login screen is opened. Enter a correct user name and password.
Chapter 5. Obexsender Figure 5-6. WWW Setup Main Page 4. After a successful login, you get access to the WWW setup main page. Note: At this point, you should check your access server software version. Obexsender works only with software version 2.2.0 and newer. At the bottom of the screen you should see a line saying: Access Server, S/N 0511170051 (wrap-2-2) - Copyright © Bluegiga Technologies Inc, 2001-2006 If the version is older than "wrap-2-2", you must first update your Access Server.
Chapter 5. Obexsender Figure 5-7. Latest Obexsender Main Menu 5.3.3. Ensuring Obexsender is Enabled By default, the Obexsender application is enabled, so as a first task you should of course enable it if. This is quite simply done from the following page in the WWW setup (Figure 5-8): Access Server - Setup - Applications - Default bootup applications Obexsender is enabled after a reboot. However, if you have not completed rest of the configuration, do not reboot Access Server yet.
Chapter 5. Obexsender Figure 5-8. Default Boot-up Applications Note: For Obexsender to start at all, you must define at least one file to be pushed to remote devices. You can do this in: Access Server - Setup - Applications - ObexSender settings - Edit configuration file For more information, see Section 5.3.6, chapter "Send these files in this order". 5.3.4. Basic Obexsender Configuration configuration. As a first step please go the to the WWW setup page in Setup −→ Applications −→ Obexsender settings.
Chapter 5. Obexsender click Upload. You will see a confirmation note, for example "File /usr/local/obexsender/Bike.jpg uploaded" . At the moment, you can only upload to /usr/local/obexsender directory using WWW setup. If you would like to upload to another directory, you must use secure FTP to accomplish that. (Normal FTP is disabled by default in Access Server for security reasons). For example WinSCP, available from http://www.winscp.org, is a good application that for secure FTP file transmissions. 5.3.
Chapter 5. Obexsender Example: scandir /tmp/obex file Specify full pathname(s) of file(s) to be sent, possibly at given time. If there are no files specified, ObexSender does not do inquiry. The files specified are sent in listed order. Syntax: file [timestamp] Example for sending tp1.gif first, then tp2.gif: file /usr/local/obexsender/tp1.gif file /usr/local/obexsender/tp2.
Chapter 5. Obexsender verbose Determines the verbosity level of ObexSender logging. The Level can be from 0 to 4, defined by the count of lines with uncommented term verbose. Level 0 means that there will be minimal logging and level 4 that there will be maximum amount of logging. Warning Full verbose logging (4) should be used only for debugging purposes, since it creates a lot of logs and the flash memory can be filled rather quickly.
Chapter 5. Obexsender 5.3.7. How to Store Files Sent to Access Server By default, all files sent over Object Push to Access Server are stored to the /tmp/obex folder and deleted after they have been processed. It is however possible to save the files to another directory. The following procedure shows how to automatically copy these files to an example folder /usr/local/remote_request. (NOTE: you must first create this folder!): 1. Create a copier script /usr/local/bin/copier.
Chapter 5. Obexsender Figure 5-9. Detailed Obexsender Log View If you want to see even more details about how Obexsender is performing, you can increase the verbosity level of logging. See Section 5.3.6, chapter "Be verbose (0-4)". Full verbose logging is usually needed in problem solving only. 5.5. Troubleshooting and Known Issues Troubleshooting: • Obexsender is not sending anything? Make sure you have at least one content file specified in the configuration file (obexsender.conf). See Section 5.3.
Chapter 5. Obexsender Known issues: • If you enter a non-existing path in "Log file name" configuration, Obexsender will fail to start. • If you have entered a password for the iWRAP (Bluetooth) interface and the same password is not set in the Obexsender configuration, Obexsender will fail to start. • If several log files are defined in obexsender.
Chapter 6. Software Development Kit 6.1. Introduction to SDK This manual describes how to create and use applications by using Access Server’s Software Development Environment. The relationships between the applications in the Access Server Software Platform are shown in Figure 6-1. Figure 6-1. Relationship Between Customer Applications and Access Server Software 6.2.
Chapter 6. Software Development Kit A PC with: • CD-ROM drive • The Linux operating system (the SDK has been tested with RedHat Enterprise Linux 3 and above, Fedora Core 2 and above; Suse and Ubuntu are reported to work too) make and gawk must be installed Devel libraries (especially zlib-devel, e2fsprogs-devel and ncurses-devel) must be installed modutils-2.4.
Chapter 6. Software Development Kit Note: If this is not the username of the developer for whom the Software Development Environment is being installed, the user will not have rights to use the development files and therefore can not develop any Access Server software. Install toolchain sources (default: no - unless the tools directory was changed) This value indicates whether the toolchain sources will be installed.
Chapter 6. Software Development Kit Example Usage Purpose forkserver SET BLUETOOTH LISTEN 11 /usr/bin/forkserver This is the simplest Bluetooth RFCOMM server example. Use, for example, btserver as a client to test this example. This example waits for a full line from the client, echoes is back and then exits. btlogger SET BLUETOOTH LISTEN 11 /usr/bin/btlogger /tmp/logfile This is a simple Bluetooth RFCOMM server example, which logs lines received from the connected client, and answers with "ACK".
Chapter 6. Software Development Kit Just give the make appwiz APP=dir/to/newapp command in the Development Environment’s top level directory (asdk/). A "hello world" example ANSI C project is then created. To use C++ compiler, replace $(do_link) with $(do_link_cc) in Makefile. The details of the compile process and variables you may need to modify before compiling your application, such as CFLAGS, LDFLAGS and CXXFLAGS, can be seen in file asdk/Rules.mak. Now you have a new project waiting for coding.
Chapter 6. Software Development Kit /path/to/myapp/myapp sftp> quit $ 100% 20KB 20.0KB/s 00:00 6.3.4.2. Using SSHFS With SSHFS, the Access Server filesystem can be securely mounted to be a part of the development host’s filesystem. To download and install SSHFS, visit http://fuse.sourceforge.net/sshfs.html.
Chapter 6. Software Development Kit 6.3.4.4. Using NFS Mount To use NFS mount, have a NFS share prepared in your development PC and mount the directory by using command mount -o nolock :/nfsshare /mnt/nfs. After this, you can access the share in directory /mnt/nfs. 6.3.5.
Chapter 6. Software Development Kit target remote : Example: target remote 192.168.42.3:6789 4. Run the program by using command continue. 6.3.7. Native SDK It is also possible compile applications for Access Server using native toolchain. To use it, copy files sdk.iso and sdkmount.wpk from directory lib in the Access Server SDK CD-ROM (or ISO image) to the root directory of an USB memory dongle, and insert it to Access Server’s USB port.
Chapter 7. iWRAP - Bluetooth Interface The Bluetooth service in Access Server is controlled through the TCP socket interface called iWRAP. The first iWRAP server is listening on port 10101. In the case of Access Server 2293, the second iWRAP server is listening on port 10102, and the third one is listening on port 10103. All commands to an iWRAP server and replies from the server are plain ASCII strings ending in CR+LF ("\r\n"). Commands and replies are not case sensitive.
7.3. Writing iWRAP Applications There are two approaches when writing a iWRAP server program (a program accepting incoming calls) for Access Server, both having different pros and cons: 1. Forklistener 2. iWRAP Client Note: When writing a client program (that is, a program making an outgoing call), you have to use iWRAP. 7.3.1. Forklistener This is a standard program reading data from standard input and writing output to standard output.
INFO 7.4. Commands Controlling iWRAP INFO INFO — Get basic info Synopsis INFO Description INFO is used to retrieve version information on the iWRAP server, in the same format as presented by the READY. prompt when the iWRAP connection is opened. Reply READY. (wrap-2-1-0 $Revision: 1.28 $ bt1.
QUIT QUIT — Close iWRAP connection Synopsis QUIT Description To close the connection to the iWRAP server, use the QUIT command. Reply There is no reply. Example READY.
SET SET — Change parameters Synopsis SET [variable [value] ] Description The SET command allows you to alter various Bluetooth and iWRAP parameters. The supported variables are listed in Table 7-1. Issuing a SET command without parameters lists the current settings. Variable Description BLUETOOTH BDADDR bdaddr Our bdaddr. This is a read-only value. BLUETOOTH NAME friendly_name You can set your Bluetooth friendly name with this command. Others can request this name with the NAME command.
SET Variable Description BLUETOOTH LAP value You can set the IAC LAP value with this command. The default value is 9e8b33 BLUETOOTH ROLE role {policy {timeout}} You can set the master/slave role switch preference with this command. Optionally, you can also set the link policy and link supervision timeout.
SET Variable Description BLUETOOTH PAGEMODE mode {page_timeout {page_repetition_mode {scan_activity_interval scan_activity_window {inquiry_activity_interval inquiry_activity_window}}}} Pagemode defines whether other devices can find and call you. There are four different modes: 0: No inquiry, no paging 1: Inquiry, no paging 2: No inquiry, paging 3: Inquiry and paging The page timeout is given in hex and the default value is 2000. The default page repetition mode is 2 (R2).
SET Variable Description BLUETOOTH AUTH bdaddr pin {authflags} This command sets the PIN code for bdaddr. Authflags are: --NEWPAIR Only if we do not have linkkey yet --REQUEST Request this PIN from remote, do not reply with this one --REPLY Reply to remote requests with this PIN --CALL Only if making an outgoing call --ANSWER Only when answering to an incoming call --RFCOMM Call FORK/PPP/...
SET Variable Description BLUETOOTH LISTEN channel cmd {mem {delay}} This command adds a fork-listener for the channel. When there is an incoming RFCOMM connection to the channel, the iWRAP server handles the connection by itself by forking "cmd". At least "mem" kilobytes of free memory must be available, or the connection will be rejected. After forking, the iWRAP server waits for "delay" timerticks (50ms) before transmitting any data.
SET Variable Description BLUETOOTH LINK mode params With this command, you can modify the slave’s powermode according to the "mode". "params" are optional and mode-dependent. The possible values for "mode" are: 0: Active. Params: None. 1: Park: Round-robin. Params: max_beacon min_beacon sleep_after_unpark sleep_after_round Defaults: 254 160 5 30 Sleeps are specified by timerticks (50ms). 2: Park: Idle.
SET Variable Description BLUETOOTH QOS service_type token_rate peak_bandwidth latency delay_variation This command sets default QoS values for a new connection. The parameters are in hex. See Bluetooth Specification for more information on params. Defaults: 01 00000000 00000000 000061a8 ffffffff L2CAP TIMEOUT flushto linkto With this command, you can define the FlushTimeout and LinkTimeout for L2CAP connections. See Bluetooth Specification for more information on params.
SET Variable Description PAN ENABLE bitmap This command controls incoming PAN connections. Bitmap: 1: Allow incoming PAN-PANU connections. 2: Allow incoming PAN-GN connections. 4: Allow incoming PAN-NAP connections. 8: Enable zeroconf for incoming PAN-PANU connections. 16: Enable zeroconf for outgoing PAN-PANU connections. The default value "6" is recommended for most cases. CONTROL AUTOEXEC cmd Run the CALL command, and rerun it when the call is disconnected.
SET Variable Description link_id PARK params With this command, you can set the powermode for link_id park. Required "params" are: avg_beacon or max_beacon min_beacon See Bluetooth Specification for more information on params. link_id HOLD params With this command, you can set the link’s powermode to hold. Required "params" are: avg max min See Bluetooth Specification for more information on params. link_id SNIFF params With this command, you can set the powermode for a link_id to sniff.
SET Reply When there are parameters, there is no reply. Example READY.
SAVE SAVE — Save iWRAP settings Synopsis SAVE {what} {filename} Description The SAVE command writes the current settings to a file. What Settings AUTH SET BLUETOOTH AUTH ... PAIR SET BLUETOOTH PAIR ... BTSET SET BLUETOOTH ..., but not AUTH or PAIR OTHERSET All but SET BLUETOOTH ALL Everything Table 7-1. SAVE parameters Reply There is no reply. Example READY. SAVE PAIR /etc/bluetooth.pair SAVE AUTH,PAIR /etc/bluetooth.
LOAD LOAD — Run iWRAP command script Synopsis LOAD {filename} Description The LOAD command runs commands from a file. This command is usually used with SAVE or SET CONTROL AUTOSAVE commands. Reply There is no reply. Example READY. LOAD /etc/bluetooth.security SET CONTROL AUTOSAVE AUTH,PAIR /etc/bluetooth.
PING PING — Ask if the connection is alive Synopsis PING Description The PING command can be used to check that the connection to the iWRAP server is alive. The iWRAP can also send the PING to the client application. In that case, you must reply with the PONG command. Reply PONG Example READY.
PONG PONG — Connection is alive Synopsis PONG Description The PONG command has to be sent back if you see a PING reply from the server. If you do not answer, the connection will be closed after a few seconds. Reply There is no reply. Example READY.
ECHO ECHO — Send a message to other iWRAP clients Synopsis ECHO {data} Description This command broadcasts its parameters to all iWRAP connections, including the one that sent the command. Reply ECHO data Example READY.
LOCK LOCK — Lock other iWRAP clients Synopsis LOCK Description This command locks all other iWRAP connections, allowing commands only from this one. This includes all the PINGs and PONGs too. Be polite and do not lock it for a long time. Reply There is no reply. Example READY.
UNLOCK UNLOCK — Unlock other iWRAP clients Synopsis UNLOCK Description This command opens the lock created by using the LOCK command. Reply There is no reply. Example READY.
SHUTDOWN SHUTDOWN — Close iWRAP server Synopsis SHUTDOWN Description To close the iWRAP server, you can use the SHUTDOWN command. This also immediately closes all active connections. Reply There is no reply. Example READY.
SLEEP SLEEP — Wait a second Synopsis SLEEP {seconds} Description The SLEEP command waits for a specified number of seconds before processing further commands. SLEEP is only usable in rc scripts (/etc/bluetooth.conf). Reply There is no reply. Example READY.
7.5. Finding Bluetooth Devices INQUIRY INQUIRY — Search for other devices Synopsis INQUIRY [timeout] [NAME] [LAP {lap}] Description The INQUIRY command is used to search for other Bluetooth devices. The timeout is defined in units of 1.25 seconds. The default timeout is 4 units. If an optional NAME parameter is provided, the NAME command will be automatically sent to all found devices. The LAP option specifies the used IAC LAP; the default value is 9e8b33 (GIAC).
INQUIRY 92
NAME NAME — Find a friendly name Synopsis NAME {bdaddr} Description You can ask for the friendly name of another Bluetooth device with the NAME command. Reply NAME bdaddr "friendly name" NAME ERROR bdaddr reason_code more_info Example READY.
7.6.
CALL Example READY.
CONNECT CONNECT — Connected to other device Synopsis This is not a command. Description CONNECT is not a command, but rather a reply broadcast to you when CALL successfully estab- lishes the connection. Remember to check that the link_id matches your CALL. On RFCOMM/L2CAP connections, there is an additional parameter called port. Port refers to the TCP socket port number, which is used to send and receive data to and from the remote device. Connect to the port just like you connected to the iWRAP server.
CONNECT CALL 00:07:80:80:bf:01 2 FORK /bin/login CALL 3 RINGING 3 CONNECT 3 FORK CALL 00:07:80:80:bf:01 PAN-NAP CALL 5 RINGING 5 CONNECT 5 PAN-NAP CALL 00:07:80:80:bf:02 PAN-NAP PAN-NAP CALL 6 RINGING 6 CONNECT 6 PAN-NAP 97
NO CARRIER NO CARRIER — Disconnected from other device Synopsis This is not a command. Description The NO CARRIER reply indicates that you or the remote device closed the active connection, or that your CALL failed for some reason. See Section 7.9 for the list of error codes. Field "more_info" is optional. If present, it gives you a human readable error code or some statistics about the closed connection. Reply NO CARRIER link_id ERROR reason NO CARRIER link_id Example READY.
RING RING — Another device is calling you Synopsis This is not a command. Description The RING reply indicates an incoming call from a remote device. As with CONNECT, on RFCOMM/L2CAP calls there is an additional "port" parameter. Open a socket to the port, if you want to serve this call. PPP and PAN calls are handled internally, which means that you do not have to do anything on them. The iWRAP server closes the connection if nobody grabs the call within 30 seconds.
RINGING RINGING — Call in progress Synopsis This is not a command. Description The RINGING reply indicates that a previously initiated outgoing CALL is in the state where a new outgoing CALL can be made. Reply RINGING link_id Example READY.
CLOSE CLOSE — Disconnect Synopsis CLOSE {link_id} Description The CLOSE command closes an active connection started with a CONNECT or RING. Note that closing the RFCOMM data socket connection also closes the Bluetooth connection. Reply There is no direct reply. NO CARRIER is replied when the connection actually closes. Example READY.
LIST LIST — List connections Synopsis LIST Description The LIST command reports active connections and some statistics. Reply LIST number_of_connections LIST link_id status type blocksize bytes_in bytes_out elapsed_time our_msc remote_msc bdaddr channel direction powermode role crypt child_pid hcihandle LIST link_id status type blocksize bytes_in bytes_out elapsed_time our_msc remote_msc bdaddr channel direction powermode role crypt child_pid hcihandle ...
LIST Hcihandle is the HCI handle for this connection. Example READY.
STATUS STATUS — Status of a connection Synopsis This is not a command. Description The STATUS reply is used to inform you about changes in connection status. See also the SET command. Reply STATUS link_id MSC value Example READY.
7.7. Service Discovery This section describes the commands used for Bluetooth service discovery and local SDP record manipulation. The commands and their replies use SDP UUID and attribute values, which are listed in the Bluetooth Assigned Numbers documentation. In the commands below, the most useful UUID and attribute values can, however, be replaced with keywords listed in Table 7-3.
SDPSEARCH identified with link_id. The command only supports searching for one UUID at a time (specified with the uuid parameter, 4 hex digits, or with a keyword), but several requests can be sent during the same SDP connection. However, you must wait for the reply to the previous reply before issuing a new SDPSEARCH command. Reply SDPSEARCH SDPSEARCH SDPSEARCH ... SDPSEARCH link_id number_of_handles link_id handle_1 link_id handle_2 link_id handle_n Example READY.
SDPATTR SDPATTR — Browse SDP Records Synopsis SDPATTR {link_id} {handle} {attribute} Description The SDPATTR command is used to send a Service Attribute Request to a connected SDP server, identified with the link_id. The command supports requesting for one attribute value (specified with the attribute parameter, 4 hex digits, or a keyword) in one previously retrieved service entry (specified with the handle parameter, 8 hex digits), but several requests can be sent during the same SDP connection.
SDPATTR SDPATTR 0 < I 0004 < < U 0100 > < U 0003 I 04 > > > CLOSE 0 NO CARRIER 0 ERROR 000 108
SDPQUERY SDPQUERY — Browse SDP Records Synopsis SDPQUERY {link_id} {uuid} {attribute} Description The SDPQUERY command is used to send a Service Search Attribute Request to a connected SDP server, identified with the link_id.
SDP bdaddr SDP bdaddr — Check devices SDP Synopsis SDP {bdaddr} {uuid} Description The SDP bddaddr command is the most useful command for retrieving SDP information from the remote device. The command opens the SDP connection, makes the SDP query, closes the connection and replies to the client in encrypted form. The format is described with the SDPATTR command. Reply SDP SDP SDP SDP ... SDP bdaddr bdaddr bdaddr bdaddr 0 ERROR reason number_of_entries info info bdaddr info Example READY.
SDP ADD SDP ADD — Add entry to local SDP Synopsis SDP ADD {uuid [:uuid2]} {channel} {description} Description This command adds a new entry to Access Server’s SDP record. Reply SDP handle SDP handle ERROR reason Example READY.
SDP DEL SDP DEL — Delete entry for local SDP Synopsis SDP DEL {handle} Description This command deletes one entry from Access Server’s SDP record. Reply There is no reply. Example READY.
SDP LIST SDP LIST — List local SDP Synopsis SDP LIST Description This command lists Access Server’s SDP record entries. Reply SDP SDP SDP ... SDP number_of_entries handle uuid channel description handle uuid channel description handle uuid channel description Example READY.
Chapter 7. iWRAP - Bluetooth Interface 7.8. Example Sessions Outgoing RFCOMM Call: READY. CALL 00:07:80:80:bf:01 1 RFCOMM CALL 2 RINGING 2 CONNECT 2 RFCOMM 1042 STATUS 2 MSC 8d CLOSE 2 NO CARRIER 2 ERROR 000 Incoming RFCOMM Call: READY. RING 2 00:07:80:80:bf:01 1 RFCOMM 1042 STATUS 2 MSC 8d NO CARRIER 2 ERROR 000 7.9. Error Codes Some commands may reply with an error code.
Chapter 7. iWRAP - Bluetooth Interface Code Textual Form Reason 906 BUSY Tried to issue SDPQUERY, but another SDP request was in progress. 907 NOT_CONNECTED Tried to CLOSE a connection handle that is not active. 908 BUSY Tried to issue SDPSEARCH, but another SDP request was in progress. 909 INVALID_ADDRESS Tried to NAME a device with a friendly name that cannot be found with the inquiry. 90a BUSY Tried to issue NAME, but another NAME was in progress. Table 7-5.
Chapter 7.
Chapter 7. iWRAP - Bluetooth Interface L2CAP Error Code L2CAP_ERR_REFUS_SEC_BLOCK 3 L2CAP_ERR_REFUS_NO_RESOURCE 4 L2CAP_ERR_TIMEOUT_EXTERNAL 0xee Table 7-8.
Chapter 8. I/O API The Bluegiga I/O API defines how to access Access Server’s LEDs, buzzer, and general purpose I/O. 8.1. Led and Buzzer API Access Server’s LEDs and buzzer can be accessed through the /dev/led device. You can check the status of the LEDs and the buzzer with the cat /dev/led command and set LEDs or the buzzer with the echo abcde > /dev/led command. An upper case letter means that the LED or buzzer is ON, a lower case letter means that the LED or buzzer is OFF.
Chapter 9. Advanced Use Cases for Access Server This chapter will give you advanced use cases for Access Server. The cases listed here are not so trivial, the simple cases are already listed mostly in Chapter 7. 9.1. Making Access Server Secure TBA 9.2. Saving Bluetooth Pairing Information Permanently By default, Access Server discards pairing information after 30 minutes and does not store pairing data permanently. Therefore, rebooting of Access Server removes all pairing information.
Chapter 9.
Chapter 9. Advanced Use Cases for Access Server Figure 9-1. OpenVPN GUI Options Menu In Access Server, the easiest way to install OpenVPN is through the WWW setup. Just enter the server IP address in you web browser and log in. If you do not know the IP address, you can use the WRAPfinder application to find out the IP address. WRAPfinder is located in the CD provided with the server. When in WWW setup, go to Advanced settings -> Upload a software update. There you can choose the openvpn-2.0.8-1.
Chapter 9. Advanced Use Cases for Access Server The build-ca builds the certificate authority (CA) certificate and key by invoking the interactive openssl command: ai:easy-rsa # ./build-ca Generating a 1024 bit RSA private key ............++++++ ...........++++++ writing new private key to ’ca.key’ ----You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN.
Chapter 9. Advanced Use Cases for Access Server build-dh The output is as follows: ai:easy-rsa # ./build-dh Generating DH parameters, 1024 bit long safe prime, generator 2 This is going to take a long time .................+........................................... ...................+.............+.................+......... ...................................... Now you can find the generated keys and certificates in the keys subdirectory.
Chapter 9. Advanced Use Cases for Access Server • Determines whether to use routed IP channel (tun) or an Ethernet tunnel, i.e. Ethernet bridging (tap). ’tap’ creates a virtual Ethernet adapter, while ’tun’ device is a virtual point-to-point IP link. We have chosen ’tun’ because of its better efficiency and scalability. ca "C:\\Program Files\\OpenVPN\\config\\ca.crt" • This is a so-called master Certificate Authority (CA) certificate.
Chapter 9. Advanced Use Cases for Access Server persist-key • Persist features try to avoid accessing certain resources on restart that may no longer be accessible. persist-tun • See above. status C:\\Program Files\\OpenVPN\\config\\Logs\\openvpn-status.log • OpenVPN outputs a short status description to this file showing current connections. This file is truncated and rewritten every minute. verb 3 • This sets the verbosity level of the log file.
Chapter 9. Advanced Use Cases for Access Server Figure 9-2. Server Configuration File 9.4.4.2. Client Configuration File Just like with the server configuration file, we’ll describe here the basic client settings needed in our example setup, see Figure 9-3: client • Here we specify that we are a client and that we will be pulling certain config file directives from the server. dev tun • This setting is the same as in the server configuration file. Use the same setting you’re using in the server.
Chapter 9. Advanced Use Cases for Access Server • This setting configures the hostname/IP and port of the server. resolv-retry infinite • Keep trying indefinitely to resolve the host name of the OpenVPN server. Very useful on machines which are not permanently connected to the internet, such as laptops. nobind • Most clients don’t need to bind to a specific local port number. persist-key • This setting is the same as in the server configuration file.
Chapter 9. Advanced Use Cases for Access Server Figure 9-3. Client Configuration File 9.4.5. Starting up VPN First, place the configuration files in the client and server. Like in the examples, the location for these files can be, for example, C:\Program Files\OpenVPN\config in Windows and /usr/local/openvpn/config in Linux. Next, copy the authentication files ( ca.crt, server.crt, server.key, client.crt and client.key) into the same directories. 9.4.5.1.
Chapter 9. Advanced Use Cases for Access Server A normal server startup should look like this (output will vary across platforms): Sun Sun Sun Sun Sun Sun Sun Sun Sun Sun Sun Sun Sun Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb 6 6 6 6 6 6 6 6 6 6 6 6 6 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 20:46:38 2005 2005 2005 2005 2005 2005 2005 2005 2005 2005 2005 2005 2005 OpenVPN 2.
Chapter 10. Certification Information and WEEE Compliance Access Server is CE approved and Bluetooth qualified v. 2.0 + EDR. It has been measured against the following specification standards: ETSI EN 300 328 v1.6.1 / EN 301 489-1/17 / EN 60950-1 / FCC parts 15.247, 15.209, 15.207, 15.109 and 15.107. Supported Bluetooth profiles are: GAP, SDAP, LAN client and server, SPP A and B, FTP client and server, ObjP client and server, PANPANU, PAN-GN and PAN-NAP.
Chapter 10. Certification Information and WEEE Compliance • Any transmitter installed in the CF card slot must not exceed 4 W of e.i.r.p. To check if a particular equipment complies with this restriction, you need to know its FCC ID number and visit the searching engine in the FCC web site in the following Internet address, where you can find the output power by the equipment in the grant of equipment: https://gullfoss2.fcc.gov/prod/oet/cf/eas/reports/GenericSearch.
Chapter 10. Certification Information and WEEE Compliance S Compact Flash card = 0.795774 mW/cm2 S Total = S Bluetooth + S Compact Flash card = 0.003481 mW/cm2 + 0.795774 mW/cm2 S Total = 0.799255 mW/cm2 < 1 mW/cm2 Example 10-2. Part 22 Compact Flash Card with maximum e.r.p. of 1.5 W (Category excluded of MPE evaluation according to §2.1091) Using Equation from page 18 of OET Bulletin 65, Edition 97-01 and considering that e.i.r.p. = 1.64 x e.r.p.: S Compact Flash card = Prad (e.i.r.p.
Appendix A. Directory Structure Directory Tree ============== / |-- bin |-- boot |-- dev | ‘-- shm | |-- etc | |-- tmp | | |-- obex | ‘-- var | |-- lock | | ‘-- subsys | |-- log | |-- run | ‘-- empty |-- etc | |-- init.d -> rc.d/init.d | |-- ppp | | ‘-- peers | |-- rc.d | | |-- init.d | | ‘-- rc3.d | |-- rc3.d -> rc.d/rc3.
Appendix A. Directory Structure | | | ‘-- var |-|-| | | | |-|-|-|-| | |-‘-- |-- l |-- v ‘-- x empty -> ../dev/shm/var/empty lib |-- b2b |-- dpkg ‘-- info ‘-- setup lock -> ../dev/shm/var/lock log -> ../dev/shm/var/log run -> ../dev/shm/var/run spool ‘-- cron ‘-- crontabs tmp -> ..
Appendix B. Setup Options B.1. Security settings Submenu containing most important security settings, like passwords. 1. Root password [$1$rUj/KWS1$v3FZcBP.6HiN4f5PaATMq1] Password of "root" user, shown in encrypted form. The default is "buffy". To change the password, clear the field, enter a new password and click Save. Saving an empty field keeps the old password. Please note that the new password is shown in plain text only right after you have saved it.
Appendix B. Setup Options you have saved it. Later it is only shown encrypted, and there is no way to decrypt it. You must either remember it or change it again to something you do remember. Use "-" do disable the password. The password must match the authentication parameter in the "wpkg.pif" file in the wpk packet. Otherwise the packet is not processed. Syntax in the "wpkg.pif" file: %wpkg-auth: auth 6.
Appendix B. Setup Options B.2. Generic settings Submenu containing generic settings. 1. Root password [$1$rUj/KWS1$v3FZcBP.6HiN4f5PaATMq1] Password of "root" user, shown in encrypted form. The default is "buffy". To change the password, clear the field, enter a new password and click Save. Saving an empty field keeps the old password. Please note that the new password is shown in plain text only right after you have saved it. Later it is only shown encrypted, and there is no way to decrypt it.
Appendix B. Setup Options security and system boot speed. 5. Enable GPRS interface [No] Set this option to Yes if you want to have the GPRS interface enabled. To use the interface, a supported Compact Flash GPRS card or a serial GPRS modem must be attached to Access Server. 6. Time server (rdate) [] Hostname or IP address of the time server to be connected at system boot to retrieve correct time using the Time Protocol (RFC 868). NTP client is running by default, so rdate should not be needed at all. 7.
Appendix B. Setup Options 2. Use dynamic network configuration [Yes] Use dynamic network configuration (DHCP) on Ethernet interface when it is not assigned to the default interface. 3. IP address [192.168.43.3] IP address of the Ethernet interface when it is not assigned to the default interface and dynamic network configuration is not in use. 4. Subnet mask [255.255.255.
Appendix B. Setup Options B.3.4. GPRS settings GPRS settings. 1. Dial on demand [Yes] If this option is set to Yes, the GPRS link is not opened at boot time but when there is data to be transferred. 2. SIM card PIN code [] PIN code of the SIM card in the GPRS modem. 3. Username [blue] Username for GPRS network. Contact your GSM operator for correct value. Some examples: Elisa/Finland: Sonera/Finland: Wataniya/Kuwait: Etisalat/UAE: blue blue blue Mnet See also: http://www.kh-gps.de/gprsset.htm 4.
Appendix B. Setup Options B.4. Applications Submenu containing settings of various applications. 1. Default startup applications [] Change which applications are to be started at startup and which don’t. B.4.1. wpkgd settings Submenu containing settings for wpkgd application. 1. wpkgd’s autoinstall directory [/tmp/obex] wpkgd will automatically check this directory for wpk files containing software update packets. Use "/tmp/obex" if you want to allow updates via Bluetooth Object Push.
Appendix B. Setup Options Please note that the new password is shown in plain text only right after you have saved it. Later it is only shown encrypted, and there is no way to decrypt it. You must either remember it or change it again to something you do remember. Use "-" to disable the password. The password must match the authentication parameter in the "wpkg.pif" file in the wpk packet. Otherwise the packet is not processed. Syntax in the "wpkg.pif" file: %wpkg-auth: auth 6.
Appendix B. Setup Options 9. Allow anonymous user to download [Yes] Whether "anonymous" user is allowed to download files or not. 10. Allow anonymous user to upload [No] Whether "anonymous" user is allowed to upload files and make directories or not. 11. Allow anonymous user to overwrite [No] Whether "anonymous" user is allowed to overwrite existing files or not. 12. Allow anonymous user to multiple login [No] Whether "anonymous" user is allowed to multiple logins or not. 13.
Appendix B. Setup Options the file, this timeout (in seconds) defines when ObexSender can send content to the same device again. 6. Delay between retrying call [120] When user doesn’t accept or reject the file, ObexSender will try to send the file again. This setting determines the timeout (in seconds) before resend occurs. Default value is 120 seconds. If you wish to disable this feature you can use the same value as in "ok delay" or "reject delay", i.e. the two previous settings. 7.
Appendix B. Setup Options This prefix is put in front of every event in the log file. Type "-" for none (default). 12. If sending was failure, log it too [Yes] If this is enabled failed transmissions will be logged too. 13. Register to watchdog daemon [Yes] If this is enabled, ObexSender will reboot Access Server automatically if Bluetooth basebands have stopped responding. 14. iWRAP password [-] iWRAP password. "-" for none (default). 15. Edit configuration file [/etc/obexsender.
Appendix B. Setup Options cron job to free disk space from time to time). 3. SMSC number [+358405202000] SMSC number. Contact your local GSM operator if you don’t know the correct value. +358405202000 for Sonera/Finland +358508771010 for Elisa/Finland 4. Edit configuration file [/etc/smsgw.conf] Edit the self documented configuration file of the SMS gateway. B.5. Bluetooth settings Submenu containing all Bluetooth related settings. 1.
Appendix B. Setup Options When a device is connectable, other Bluetooth devices can make a Bluetooth connection to it. Before making a connection, the calling device must know the Bluetooth address of the device it is connecting to. The Bluetooth addresses can be found by making an inquiry. When a device is discoverable, it shows up in inquiries.
Appendix B. Setup Options "Sniff: Idle" means that a connection is switched to sniff mode after it has not transmitted data for some time (2 seconds by default). When data transmission resumes, switch to active mode is made. Park modes are generally not useful. See User’s and Developer’s Guide and Bluetooth specification for more information. 8. Use literal replies in SDP [Yes] If enabled, some SDP result codes will have literal values instead of numeric values. 9.
Appendix B. Setup Options The name of the LAN Access Profile service shown in the Service Discovery. 3. Defaultroute modification policy [0] How the LAN Access Profile should modify the defaultroute in routing tables: 0: 1: 2: 3: Do not alter defaultroute (default) When acting as a LAP client, set defaultroute according to the LAP server When acting as a LAP server, set defaultroute according to the LAP client Set defaultroute according to the LAP server/client connected 4. First IP for LAP clients [192.
Appendix B. Setup Options First IP address of the lease block. 7. Last IP for lease block [192.168.161.254] Last IP address of the lease block. 8. Subnet of lease block [255.255.255.0] Subnet mask of the lease block. 9. Lease time [86400] Lease time in seconds. B.5.1.4. PAN network access point profile settings Submenu containing Personal Area Network Network Access Point Profile settings. 1.
Appendix B. Setup Options 8. Bluetooth address of the remote device [00:07:80:80:bf:01] The Bluetooth address of the device to be contacted. If the local device is configured as DevA, this is the DevB it tries to connect. 9. Service channel [2] In DevA (call) mode: The Bluetooth RFCOMM channel of the remote device. In DevB (answer) mode: The Bluetooth RFCOMM channel of the local device. 10.
Appendix B. Setup Options Edit the file containing the default user profile settings. 3. WWW passwords [/etc/httpd.conf] Access to WWW pages served by Access Server can be restricted using the configuration file "httpd.conf", editable from here. The file consists of lines in format "/dir:username:password". This specifies that to view the WWW page at address "http://as-ip/dir", you must enter username "username" and password "password".
Appendix B. Setup Options can be used to update Access Server software components or to install custom software and configuration files. Please consult User’s and Developer’s Guide for more information. B.6.1. System information This submenu contains tools to retrieve system status information. 1. Hardware information Displays hardware and software identification information (output of command "wrapid"). 2.
Appendix B. Setup Options iWRAP password [buffy] Do not require iWRAP password from local clients Bluetooth PIN code [] wpkgd autoinstall password [] wpkgd hotplug password [] Root user password for FTP [buffy] Allow anonymous FTP login [Yes] WWW passwords [/etc/httpd.conf] [Yes] Generic settings Root password [$1$rUj/KWS1$v3FZcBP.6HiN4f5PaATMq1] Use local syslog service [Yes] IP address of the remote syslog server [192.168.42.
Appendix B.
Appendix B. Setup Options Friendly name [W$S_$p] Connectable and discoverable mode [3] Master/slave role switch policy [1] Default PIN code [] Power save mode and parameters [4] Use literal replies in SDP [Yes] Optional command line parameters [] Edit startup script [/etc/bluetooth.conf] Bluetooth profiles Enable lan access profile [No] Lan access profile settings Login name and password [] Service name (shown in SDP) [Lan Access] Defaultroute modification policy [0] First IP for LAP clients [192.168.160.
Appendix B. Setup Options Advanced settings System startup script [/etc/rc.d/rc.local] Default user profile [/etc/profile] WWW passwords [/etc/httpd.conf] Setup access [/etc/setup.
Appendix C. Open Source Software Licenses Some Access Server software components are licensed under the terms and conditions of one or more open source licenses, listed in Table C-1 below. License Appreviation Description URL CMU/UCD Carnegie Mellon University & Regents of the University of California’s BSD style license (in net-snmp) GPL1 GNU General Public License Version 1, February 1989 http://www.fsf.org/licenses/ info/GPLv1.
Appendix C. Open Source Software Licenses Software Component Version License Source URL 2.6.17 GPL2 http://www.kernel.org/ Kernel Linux kernel The Access Server kernel, responsible for resource allocation, low-level hardware interfaces, security etc. kernel at91 patches 2.6.17 GPL2 http://maxim.org.za/AT91RM9200/2.6/ ARM-Linux patches for the Linux kernel. Userland bash 2.05b GPL1 & GPL2 http://www.gnu.org/software/bash/ bash.
Appendix C. Open Source Software Licenses Software Component Version License Source URL Administration tool for the Linux kernel IP packet filter. make 3.81 GPL2 http://www.gnu.org/software/make/ 1.2.0.07.6 BSD http://www.maradns.org/ 0.9.4 BSD http://www.tcpdump.org/ The Make. maradns DNS server. libpcap Provides portable framework for low-level network monitoring. Needed by tcpdump. lrzsz 0.12.20 GPL2 http://www.ohse.de/uwe/software/ lrzsz.html Provides X/Y/Zmodem download/upload tools.
Appendix C. Open Source Software Licenses Software Component Version License Source URL Point-to-Point Protocol userland driver. ppp-dhcpc for pppd 2.4.2 GPL2 ben at netservers.co.uk 4.3 GPL2 http://cnswww.cns.cwru.edu/php/ chet/readline/rltop.html DHCP plugin for PPP. readline GNU Readline library, providing set of functions for use by applications that allow users to edit command lines as they are typed in. strace 4.5.14 GPL2 http://www.liacs.nl/~wichert/strace/ System call trace, i.e.
Appendix D. Supported Hardware Connector Type Card Note CF GPRS Enfora GSM/GPRS Compact Flash Card (GSM 0110) Multislot class 8. CF GPRS Anycom GS-320 Tri-Band GPRS CF Card Multislot class 10. CF GPRS AudioVox RTM 8000 Multislot class 8, "same" HW as Fujitsu. CF GPRS Fujitsu Siemens Connect2Air 3GSM Multislot class 8, "same" HW as Audiovox. CF GPS Pretec CompactGPS™ CF WiFi Ambicom Wireless CompactFlash Card (WL1100C-CF) CF WiFi D-Link Air Wireless Network Seen shipping with 1.7.
