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. 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.
  2. iWRAP password [buffy]

    The password required to be entered before any commands when communicating
    with iWRAP (the Bluetooth server). 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. You must either remember it or change it again to
    something you do remember.
    Use "-" to disable iWRAP password.
  3. Do not require iWRAP password from local clients [Yes]

    Ask iWRAP password only from remote clients, not from local (127.0.0.1).
  4. Bluetooth PIN code []

    This PIN code used when establishing connections. Up to 16 characters are
    significant.
    If there is no default PIN code set, Access Server does not require
    a PIN code when establishing connections.
    However, if there is no default PIN code set, but the other device
    requests a PIN code, "1234" is replied.
  5. wpkgd autoinstall password []

    This is optional password to authenticate wpk autoinstall packets (wpk
    packets sent to the autoinstall directory, /tmp/obex by default).
    The password is shown encrypted here, if set. By default, it is not set.
    To change the password, clear the field, enter a new password and click Save.
    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 "-" 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. wpkgd hotplug password []

    This is optional password to authenticate wpk installation packets
    automatically run from USB memory dongles or Compact Flash memory cards.
    The password is shown encrypted here, if set. By default, it is not set.
    To change the password, clear the field, enter a new password and click Save.
    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
  7. Root user password for FTP [buffy]

    Password of the "root" user for FTP connections.
  8. Allow anonymous FTP login [Yes]

    Whether "anonymous" FTP login is allowed or not.
  9. 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".
    More than one username can be defined for the same "/dir"
    by adding multiple lines.
    By default, this file specifies that only user "root" with password
    "buffy" is allowed to access the WWW Setup.

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. You must either remember it or change it again to
    something you do remember.
  2. Use local syslog service [Yes]

    This option determines whether the System Logger (syslogd) logs
    locally to /var/log/messages or not.
    Set this to No if you want to log to a remote syslog server.
  3. IP address of the remote syslog server [192.168.42.1]

    The IP address of the device in the network to which the System Logger
    should log to.
    The remote device must be configured to accept syslogd connections from
    this Access Server. See the system logger documentation on the remote device
    for more information on how to configure that.

B.3. Network settings

Submenu containing network settings.

  1. Hostname of the unit [wrap]

    The hostname of Access Server. Local applications will see this
    name. This name may be changed by dynamic network configuration.
  2. Domain of the unit [localdomain]

    The domain name of Access Server. Local applications will see this
    name. This name may be changed by dynamic network configuration.
  3. Enable Ethernet cable interface [Yes]

    Set this option to Yes if you want to have the Ethernet cable interface
    enabled.
    If you don't use this interface, you may disable it to slightly increase
    security and system boot speed.
  4. Enable Wi-Fi interface [Yes]

    Set this option to Yes if you want to have the Wi-Fi interface enabled
    (you can use the Wi-Fi interface with a supported Compact Flash Wi-Fi
    card or USB Wi-Fi dongle).
    If you don't use this interface, you may disable it to slightly increase
    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. Zeroconf interface [nap]

    Defines the interface in which Zeroconf is running.
    Possible interface names are "nap", "gn" and "none".

B.3.1. Default interface settings

Default interface settings. By default, Ethernet and Bluetooth
PAN-NAP interfaces are assigned to this interface.

  1. Use dynamic network configuration [Yes]

    This option determines whether or not automatic configuration of the default
    network interface (nap) using DHCP should be attempted at boot. If set to
    no, you have to manually enter IP address and other network settings.
  2. IP address [192.168.42.3]

    The IP address of Access Server.
  3. Subnet mask [255.255.255.0]

    The network mask of Access Server.
  4. IP address of the default gateway [192.168.42.254]

    The IP address of the default gateway in the LAN to which Access Server
    is connected.
  5. List of name server IPs [192.168.42.1 192.168.42.2]

    The IP address(es) of the name servers, separated by space.

B.3.2. Ethernet cable settings

Ethernet cable settings.

  1. Assign to default interface [Yes]

    Assigns Ethernet (eth0) to default interface (nap) with settings
    specified in Default interface settings.
    Do NOT set this to No if you don't know what you are doing. There
    is a high risk that you end up with invalid network settings if you
    do so.
    If you need to set a static IP address to Access Server, do it
    in the Default interface settings.
  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.0]

    Network mask of the Ethernet interface when it is not assigned to the
    default interface and dynamic network configuration is not in use.

B.3.3. Wi-Fi settings

Wi-Fi settings.

  1. Act as a Wi-Fi Access Point [No]

    This option defines whether Access Server acts as a Wi-Fi Access
    Point when Wi-Fi is enabled.
  2. ESSID []

    Access point network name (Service Set ID).
  3. Nickname []

    The nickname, or station name. 
  4. WEP encryption key []

    WEP encryption key for Wi-Fi.
    Examples:
    10 hex digits:       "abcdef1234"
    26 hex digits:       "1234567890abcdef1234567890"
    or                   "1234-5678-90ab-cdef-1234-5678-90"
    5 ASCII characters:  "s:abcde"
    13 ASCII characters: "s:abcdefghijklm"   
  5. Extra commands for Access Point mode [/etc/sysconfig/ifup-wlan0]

    Extra commands for Access Point mode.
  6. Assign to default interface [No]

    Assigns Wi-Fi to default interface with settings specified in
    Default interface settings. 
  7. Use dynamic network configuration [Yes]

    Use dynamic network configuration (DHCP) for Wi-Fi interface.
  8. IP address [192.168.44.3]

    IP address of Wi-Fi interface.
  9. Subnet mask [255.255.255.0]

    Subnet mask of Wi-Fi interface.

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:   blue
    Sonera/Finland:  blue
    Wataniya/Kuwait: blue
    Etisalat/UAE:    Mnet
    See also: http://www.kh-gps.de/gprsset.htm
  4. Password [giga]

    Password for GPRS network. Contact your GSM operator for correct value.
    Some examples:
    Elisa/Finland:   giga
    Sonera/Finland:  giga
    Wataniya/Kuwait: giga
    Etisalat/UAE:    Mnet
    See also: http://www.kh-gps.de/gprsset.htm
  5. Internet APN [internet]

    Internet APN for GPRS network. Contact your GSM operator for correct value.
    Some examples:
    Elisa/Finland:   internet
    Sonera/Finland:  internet
    Wataniya/Kuwait: action.wataniya.com
    Etisalat/UAE:    mnet
    See also: http://www.kh-gps.de/gprsset.htm
  6. Extra parameters for pppd []

    Optional extra parameters for pppd. Use only if you know what you are doing.

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.
    Use empty to disable autoinstall.
  2. Password for autoinstall packages []

    This is optional password to authenticate wpk autoinstall packets (wpk
    packets sent to the autoinstall directory, /tmp/obex by default).
    The password is shown encrypted here, if set. By default, it is not set.
    To change the password, clear the field, enter a new password and click Save.
    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 "-" 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
  3. Delete processed autoinstall packages [Yes]

    If this option is set Yes, the wpk autoinstall packets are deleted
    after they have been processed.
  4. Process hotplug packages [Yes]

    If this option is set to Yes, wpk packets are automatically processed
    from USB memory sticks or Compact Flash memory cards when they are
    plugged into Access Server.
  5. Password for hotplug packages []

    This is optional password to authenticate wpk installation packets
    automatically run from USB memory dongles or Compact Flash memory cards.
    The password is shown encrypted here, if set. By default, it is not set.
    To change the password, clear the field, enter a new password and click Save.
    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. Delete processed hotplug packages [No]

    If this option is set Yes, the wpk packets are deleted
    after they have been processed.
  7. Extra parameters for wpkgd []

    Optional extra command line parameters for wpkgd.
    Please see wpkgd --help for detailed information on the options.

B.4.2. FTP server settings

Submenu containing settings for FTP server application.

  1. Root user password [buffy]

    Password of the "root" user for FTP connections.
  2. Root user directory [/]

    Root directory of the "root" user for FTP connections.
  3. Root user instances [5]

    Maximum number of simultaneous logins of the "root" user for FTP
    connections.
  4. Allow anonymous login [Yes]

    Whether "anonymous" FTP login is allowed or not.
  5. Anonymous user password [*]

    Password of the "anonymous" user for FTP connections.
    Use "*" to allow everything (aka anonymous login).
  6. Anonymous user directory [/tmp/obex]

    Root directory of the "anonymous" user for FTP connections.
  7. Anonymous user instances [5]

    Maximum number of simultaneous logins of the "anonymous" user for FTP
    connections.
  8. Allow anonymous user to do everything [No]

    Whether "anonymous" user is allowed to do everything (all below) or not.
  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. Allow anonymous user to erase [No]

    Whether "anonymous" user is allowed to erase files and directories or not.
  14. Edit configuration file [/etc/ftpd.conf]

    Edit the self documented configuration file of the FTP server. Here you
    can change more advanced settings.

B.4.3. ObexSender settings

Submenu containing settings for ObexSender application.

  1. Bluetooth friendly name [W$S_$p]

    The name shown when this device is found when inquired about by other
    Bluetooth devices. Following meta tags are available:
    $S : Hardware serial number, all ten digits
    $s : Hardware serial number, last three digits
    $P : Server port
    $p : Server port, last digit
    $H : Fully Qualified Domain Name (FQDN)
    $h : hostname
    $$ : $
    For example, "Server_$p" would set the Bluetooth friendly name as
    "Server_1" for 1st baseband, "Server_2" for 2nd baseband and
    "Server_3" for 3rd baseband.
  2. Delay between inquiries [10]

    Delay between inquiries (Bluetooth device discoveries) in seconds.
  3. Delay between reply scans [10]

    Determines how often (in seconds) OBEX incoming directory (/tmp/obex)
    is scanned for remote requests. A low value increases CPU usage.
  4. If previous was ok, timeout before sending again [36000]

    If a file has been successfully sent to a device, this timeout
    (in seconds) defines when content can be sent again to the same device.
  5. If previous was reject, timeout before trying again [86400]

    If a file transmission to a device has failed or user has declined
    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. Delay after scanning [5]

    When a remote request from user has been received, this setting
    determines how long (in seconds) ObexSender will wait until the
    response file is sent back to the user.
    Default value is 5 seconds, because some mobile phones are not
    able to receive files over Bluetooth until at least 5 seconds
    has passed from sending.
  8. Delay between multiple files [40]

    If ObexSender has been configured to send multiple files, this
    configuration sets the delay (in seconds) between the file
    transmissions.
  9. Minimum RSSI value before sending [-65]

    The working range of ObexSender can be configured or limited with
    this setting. When ObexSender searches for devices, the RSSI
    (Receiver Signal Strength Indicator) value is also measured.
    This value ranges from -128 to -1.
    -128 means the signal strength is very weak. A connection attempt would
    very likely fail.
    -65 means the signal strength is ok. Connection can be created.
    With Class 2 devices, like most mobile phones, this means the
    phone is 10-20 meters away. A Class 1 device can be even more
    than 100 meters away.
    -30 to -1 means the signal is very strong. The devices are most likely
    very close to each other (less than a meter away).
  10. Logfile name [-]

    Defines the path and name of the ObexSender log file
    (for example "/usr/local/obexsender/obexsender.log").
    Log file contains information about successful and unsuccessful
    transmissions, timestamps and information about sent files.
    You can also use an IP address of a log server, which must be another
    Access Server running ObexSender.
    Type "-" to use syslog.
  11. Log prefix [-]

    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.conf]

    This link opens ObexSender configuration file
    (/etc/obexsender.conf) and allows you to edit it manually.
    It also allows you to change the settings that are not
    configurable with Setup application.
  16. Upload a new file [/usr/local/obexsender]

    This link allows you to upload files into the ObexSender file directory.
  17. List files [/usr/local/obexsender]

    This link allows you to browse files on the ObexSender file system.
  18. View log [-]

    This link allows you to view ObexSender log file if it exists.
    By default a summary of the logged events is displayed.
    Detailed information is available by clicking the date links.
    

B.4.3.1. Delete log (confirm)

This link will delete the current log file after confirmation.

  1. Delete log now! [/bin/true]

    Delete ObexSender log file immediately!
    WARNING: There is no confirmation for this!
    

B.4.4. SMS gateway settings

Submenu containing settings for SMS gateway application.

  1. Modem device [/dev/ttyS0]

    Modem device for SMS gateway.
    /dev/ttyAT1 for user uart
    /dev/ttyS0 for CF slot
  2. Log file name [-]

    The file to which the SMS gateway (smsgw) logs all traffic. Use /dev/null
    for none, - for syslog, /var/log/smsgw.log if you want to save this
    information. Be careful, however, not to fill the RAM file system (use a
    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. iWRAP password [buffy]

    The password required to be entered before any commands when communicating
    with iWRAP (the Bluetooth server). 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. You must either remember it or change it again to
    something you do remember.
    Use "-" to disable iWRAP password.
  2. Do not require iWRAP password from local clients [Yes]

    Ask iWRAP password only from remote clients, not from local (127.0.0.1).
  3. Friendly name [W$S_$p]

    The name shown when this device is found when inquired about by other
    Bluetooth devices. Following meta tags are available:
    $S : Hardware serial number, all ten digits
    $s : Hardware serial number, last three digits
    $P : Server port
    $p : Server port, last digit
    $H : Fully Qualified Domain Name (FQDN)
    $h : hostname
    $$ : $
    For example, "Server_$p" would set the Bluetooth friendly name as
    "Server_1" for 1st baseband, "Server_2" for 2nd baseband and
    "Server_3" for 3rd baseband.
  4. Connectable and discoverable mode [3]

    This setting specifies whether this device is connectable and/or
    discoverable or not by other Bluetooth devices.
    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. Possible values for all combinations of these
    settings are:
    0 : Not connectable, not discoverable
    1 : Not connectable, discoverable
    2 : Connectable, not discoverable
    3 : Connectable and discoverable (default)
  5. Master/slave role switch policy [1]

    This setting specifies how local Bluetooth device should decide
    it's role. When a Bluetooth device calls another Bluetooth device,
    it is master by default and the answering device is slave. When the
    connection is being built, a role switch can be made. Normally,
    access point devices need to be the master, and therefore they
    require a master-slave switch when a new device is connecting.
    This is also how Access Server is configured by default. Otherwise
    Access server couldn't host the maximum number of slaves (7).
    Other possible combinations are:
    0 : Allow switch when calling, don't request it when answering
    1 : Allow switch when calling, request it when answering (default)
    2 : Don't allow switch when calling, request it when answering
    If you have problems with connecting to Access Server, it might be
    because your client device does not support the master/slave switch.
    In this case, set this setting to 0.
  6. Default PIN code []

    This PIN code used when establishing connections. Up to 16 characters are
    significant.
    If there is no default PIN code set, Access Server does not require
    a PIN code when establishing connections.
    However, if there is no default PIN code set, but the other device
    requests a PIN code, "1234" is replied.
  7. Power save mode and parameters [4]

    The power save mode used by default for all connections. Possible settings
    are:
    0 : Active.
    1 : Park: Round-robin.
    2 : Park: Idle.
    3 : Sniff: All
    4 : Sniff: Idle (default).
    "Active" means that no power saving is in use.
    "Sniff: All" means that the connections are kept in sniff mode always.
    "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. Optional command line parameters []

    Optional extra command line startup parameters for the iWRAP servers.
  10. Edit startup script [/etc/bluetooth.conf]

    Opens iWRAP configuration file (/etc/bluetooth.conf) for editing.
    You can append extra iWRAP commands to that file. iWRAP servers process
    the file each time they start. See the User's and Developer's Guide
    for iWRAP command reference.

B.5.1. Bluetooth profiles

Submenu for the settings of all supported Bluetooth profiles.

  1. Enable lan access profile [No]

    Whether or not the LAN Access Profile is enabled.
  2. Enable PAN user profile [No]

    Whether or not the PAN User Profile is enabled.
  3. Enable PAN generic networking profile [No]

    Whether or not the PAN Generic Networking Profile is enabled.
  4. Enable PAN network access point profile [No]

    Whether or not the PAN Network Access Point Profile is enabled.
  5. Enable object push profile [Yes]

    Whether or not the Object Push Profile is enabled.
  6. Enable file transfer profile [Yes]

    Whether or not the File Transfer Profile is enabled.

B.5.1.1. Lan access profile settings

Submenu containing LAN Access Profile settings.

  1. Login name and password []

    The login name and password required from LAN access clients. Must be entered
    as a single string, separated with a space. For example: guest buffy
    If empty (default), no login is required.
  2. Service name (shown in SDP) [Lan Access]

    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: Do not alter defaultroute (default)
    1: When acting as a LAP client, set defaultroute according to the LAP server
    2: When acting as a LAP server, set defaultroute according to the LAP client
    3: Set defaultroute according to the LAP server/client connected
  4. First IP for LAP clients [192.168.160.0]

    This defines the C-class of IP addresses to be used in point-to-point
    connections between Access Server and LAP clients.
    Full C-class is required: use "x.y.z.0".

B.5.1.2. PAN user profile settings

Submenu containing Personal Area Network User Profile settings.

  1. Service name (shown in SDP) [PAN User]

    The name of the PAN User Profile service shown in the Service Discovery.
  2. Enable zeroconf when calling [No]

    Enable ZeroConf protocol for outgoing PANU connections.
  3. Enable zeroconf when answering [No]

    Enable ZeroConf protocol for incoming PANU connections.

B.5.1.3. PAN generic networking profile settings

Submenu containing Personal Area Network Generic Networking Profile
settings.

  1. Service name (shown in SDP) [Generic Networking]

    The name of the PAN Generic Networking Profile service shown in
    the Service Discovery.
  2. Use dynamic network configuration for local IP address [No]

    Whether or not DHCP is used for configuring local IP Address. Enable only if
    you are connecting this PAN-GN to another PAN-GN that will provide the IP
    configuration.
  3. Local GN interface IP address [192.168.161.1]

    The IP address for the local GN interface.
  4. Local GN interface subnet mask [255.255.255.0]

    The netmask for the local GN interface.
  5. Start DHCP server for remote users [Yes]

    Whether or not this device should start DHCP for remote devices connecting
    to this PAN-GN. Disabled if "Use dynamic network configuration for local IP
    address" is used.
  6. First IP for lease block [192.168.161.2]

    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. Service name (shown in SDP) [Network Access]

    The name of the Bluetooth PAN Network Access Point Profile service
    shown in the Service Discovery.

B.5.1.5. Serial port profile settings

Submenu containing the Bluetooth Serial Port Profile settings.
The profile itself is enabled and disabled by switching "serialport"
application "on" or "off" from the menu:
Setup -> Applications -> Default bootup applications.

  1. Act as the calling device [No]

    Whether this device should act as the calling device (DevA) or the answering
    device (DevB).
  2. BPS rate [115200]

    The bits-per-second rate of the connection. Possible values are:
    300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400, and 460800.
  3. Data bits [8]

    The number of data bits in the connection. Possible values are:
    5, 6, 7, and 8.
  4. Parity [0]

    The parity bit setting of the connection. Possible values are:
    0: No Parity (default)
    1: Odd Parity
    2: Even Parity
  5. Stop bits [1]

    The number of stop bits in the connection. Possible values are 1 and 2.
  6. Hardware flow control (RTS/CTS) [Yes]

    Whether or not the hardware flow control is used. 
  7. Software flow control (XON/XOFF) [No]

    Whether or not the software flow control is used.
  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. Service name (shown in SDP) [Serial Port]

    The name of the Bluetooth Serial Port Profile service shown in the Service
    Discovery.
  11. Optional command line parameters []

    Optional extra parameters for the Access Server Serial Port profile
    application. Currently the supported parameters are:
    --device dev     Device, if not the user port (/dev/ttyS0 for CF Card)
    --msc            Enables transmitting of DCD/DSR Modem Status Control signals.
    --nobuffer       Discard data if no Bluetooth connection, do not buffer it.

B.5.1.6. Object push profile settings

This submenu contains Bluetooth Object Push Profile settings.

  1. Service name (shown in SDP) [Object Push]

    The name of the Object Push Profile service shown in the Service Discovery.

B.5.1.7. File tranfer profile settings

This submenu contains Bluetooth File Transfer Profile settings.

  1. Service name (shown in SDP) [File Transfer]

    The name of the File Transfer Profile shown in the Service Discovery.

B.6. Advanced settings

Submenu containing advanced settings of Access Server.

  1. System startup script [/etc/rc.d/rc.local]

    This is the last initialization script executed at system startup.
    By default, the script /etc/rc.d/rc.local just turns off all LEDs to
    indicate the startup has finished. If you want to initialize something
    automatically at every boot, or start up your own applications,
    you should add the required commands to this file.
    Remember to start your programs to the background. Example:
    /usr/local/bin/myapp &
    If you do not start the programs to the backgroud, you will not able
    to access the management console using a serial cable.
  2. Default user profile [/etc/profile]

    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".
    More than one username can be defined for the same "/dir"
    by adding multiple lines.
    By default, this file specifies that only user "root" with password
    "buffy" is allowed to access the WWW Setup.
  4. Setup access [/etc/setup.conf]

    The "/etc/setup.conf" file can be used to give different access rights to
    different users of the WWW Setup.
    The file consist of lines in following format:
    example.tag +user1 +user2 -user3 -user4
    This will allow (+) access to tag "example.tag" for "user1" and "user2"
    and denies (-) access from "user3" and "user4". You can find the tags
    from the output of
    Setup -> Advanced -> System Information -> Collect info for support request
    For example, the tag of this setting is advanced.setupconf. If you
    have created another user "guest" in /etc/httpd.conf that can access
    "/setup", you can deny that user from changing the Setup access settings
    with following line in this file:
    advanced.setupconf -guest
  5. Edit other configuration files []

    From this menu you can edit any files located in Access Server file system.
    You can for example create "/var/spool/cron/crontabs/root" file for
    configuring the cron daemon.
  6. Browse files []

    Browse files stored in Access Server.
  7. Find other Access Servers [/usr/sbin/finder]

    Find other Access Servers.
  8. Inquiry for Bluetooth devices [/usr/bin/btcli inquiry]

    Inquiry for other Bluetooth devices.
  9. Upload a software update [/tmp/obex]

    Upload a software update file (*.wpk).
    Access Server supports a special management packet format (wpk), which
    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. List installed software components [/usr/bin/dpkg -l]

    Lists currenty installed software components and their version numbers.
  3. List running processes [/bin/ps ww]

    Lists running processes.
  4. List memory status [/usr/bin/free]

    Lists memory status.
  5. List free disk space [/bin/df -h]

    Lists free disk space.
  6. Show system log file [/var/log/messages]

    Shows system log file.
  7. Show system boot log file [/var/log/dmesg]

    Shows system boot log.
  8. Collect info for support request [/usr/sbin/supportinfo]

    This page contains collectively all the system status and configuration
    information.
    Include this information when sending a support request to
    [email protected]
    WARNING: All classified information, like passwords, should be automatically
    excluded. It is still recommended to manually check that all such information
    is really removed.

B.6.2. Reboot system (confirm)

Reboot Access Server. Confirmation will be asked.

  1. Reboot now! [/sbin/reboot]

    Reboot Access Server immediately!
    WARNING: There is no confirmation for this!

B.7. Summary of Setup Options

Security settings
    Root password                         [$1$rUj/KWS1$v3FZcBP.6HiN4f5PaATMq1]
    iWRAP password                        [buffy]
    Do not require iWRAP password from local clients          [Yes]
    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]
Generic settings
    Root password                         [$1$rUj/KWS1$v3FZcBP.6HiN4f5PaATMq1]
    Use local syslog service              [Yes]
    IP address of the remote syslog server          [192.168.42.1]
Network settings
    Hostname of the unit                  [wrap]
    Domain of the unit                    [localdomain]
    Default interface settings
        Use dynamic network configuration           [Yes]
        IP address                        [192.168.42.3]
        Subnet mask                       [255.255.255.0]
        IP address of the default gateway           [192.168.42.254]
        List of name server IPs           [192.168.42.1 192.168.42.2]
    Enable Ethernet cable interface       [Yes]
    Ethernet cable settings
        Assign to default interface       [Yes]
        Use dynamic network configuration           [Yes]
        IP address                        [192.168.43.3]
        Subnet mask                       [255.255.255.0]
    Enable Wi-Fi interface                [Yes]
    Wi-Fi settings
        Act as a Wi-Fi Access Point       [No]
        ESSID                             []
        Nickname                          []
        WEP encryption key                []
        Extra commands for Access Point mode        [/etc/sysconfig/ifup-wlan0]
        Assign to default interface       [No]
        Use dynamic network configuration           [Yes]
        IP address                        [192.168.44.3]
        Subnet mask                       [255.255.255.0]
    Enable GPRS interface                 [No]
    GPRS settings
        Dial on demand                    [Yes]
        SIM card PIN code                 []
        Username                          [blue]
        Password                          [giga]
        Internet APN                      [internet]
        Extra parameters for pppd         []
    Time server (rdate)                   []
    Zeroconf interface                    [nap]
Applications
    Default startup applications          []
    wpkgd settings
        wpkgd's autoinstall directory     [/tmp/obex]
        Password for autoinstall packages           []
        Delete processed autoinstall packages       [Yes]
        Process hotplug packages          [Yes]
        Password for hotplug packages     []
        Delete processed hotplug packages           [No]
        Extra parameters for wpkgd        []
    FTP server settings
        Root user password                [buffy]
        Root user directory               [/]
        Root user instances               [5]
        Allow anonymous login             [Yes]
        Anonymous user password           [*]
        Anonymous user directory          [/tmp/obex]
        Anonymous user instances          [5]
        Allow anonymous user to do everything       [No]
        Allow anonymous user to download  [Yes]
        Allow anonymous user to upload    [No]
        Allow anonymous user to overwrite           [No]
        Allow anonymous user to multiple login      [No]
        Allow anonymous user to erase     [No]
        Edit configuration file           [/etc/ftpd.conf]
    ObexSender settings
        Bluetooth friendly name           [W$S_$p]
        Delay between inquiries           [10]
        Delay between reply scans         [10]
        If previous was ok, timeout before sending again      [36000]
        If previous was reject, timeout before trying again   [86400]
        Delay between retrying call       [120]
        Delay after scanning              [5]
        Delay between multiple files      [40]
        Minimum RSSI value before sending           [-65]
        Logfile name                      [-]
        Log prefix                        [-]
        If sending was failure, log it too          [Yes]
        Register to watchdog daemon       [Yes]
        iWRAP password                    [-]
        Edit configuration file           [/etc/obexsender.conf]
        Upload a new file                 [/usr/local/obexsender]
        List files                        [/usr/local/obexsender]
        View log                          [-]
        Delete log (confirm)
            Delete log now!               [/bin/true]
    SMS gateway settings
        Modem device                      [/dev/ttyS0]
        Log file name                     [-]
        SMSC number                       [+358405202000]
        Edit configuration file           [/etc/smsgw.conf]
Bluetooth settings
    iWRAP password                        [buffy]
    Do not require iWRAP password from local clients          [Yes]
    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.0]
        Enable PAN user profile           [No]
        PAN user profile settings
            Service name (shown in SDP)   [PAN User]
            Enable zeroconf when calling  [No]
            Enable zeroconf when answering          [No]
        Enable PAN generic networking profile       [No]
        PAN generic networking profile settings
            Service name (shown in SDP)   [Generic Networking]
            Use dynamic network configuration for local IP address      [No]
            Local GN interface IP address           [192.168.161.1]
            Local GN interface subnet mask          [255.255.255.0]
            Start DHCP server for remote users      [Yes]
            First IP for lease block      [192.168.161.2]
            Last IP for lease block       [192.168.161.254]
            Subnet of lease block         [255.255.255.0]
            Lease time                    [86400]
        Enable PAN network access point profile     [No]
        PAN network access point profile settings
            Service name (shown in SDP)   [Network Access]
        Serial port profile settings
            Act as the calling device     [No]
            BPS rate                      [115200]
            Data bits                     [8]
            Parity                        [0]
            Stop bits                     [1]
            Hardware flow control (RTS/CTS)         [Yes]
            Software flow control (XON/XOFF)        [No]
            Bluetooth address of the remote device  [00:07:80:80:bf:01]
            Service channel               [2]
            Service name (shown in SDP)   [Serial Port]
            Optional command line parameters        []
        Enable object push profile        [Yes]
        Object push profile settings
            Service name (shown in SDP)   [Object Push]
        Enable file transfer profile      [Yes]
        File tranfer profile settings
            Service name (shown in SDP)   [File Transfer]
Advanced settings
    System startup script                 [/etc/rc.d/rc.local]
    Default user profile                  [/etc/profile]
    WWW passwords                         [/etc/httpd.conf]
    Setup access                          [/etc/setup.conf]
    Edit other configuration files        []
    Browse files                          []
    Find other Access Servers             [/usr/sbin/finder]
    Inquiry for Bluetooth devices         [/usr/bin/btcli inquiry]
    Upload a software update              [/tmp/obex]
    System information
        Hardware information
        List installed software components          [/usr/bin/dpkg -l]
        List running processes            [/bin/ps ww]
        List memory status                [/usr/bin/free]
        List free disk space              [/bin/df -h]
        Show system log file              [/var/log/messages]
        Show system boot log file         [/var/log/dmesg]
        Collect info for support request  [/usr/sbin/supportinfo]
    Reboot system (confirm)
        Reboot now!                       [/sbin/reboot]