Configuring Comms Database For Ethernet Connections in Comms Database Use Cases

This section explains how to configure the Comms database for ethernet connections. The Comms database stores the network configuration settings in Symbian OS. This document is aimed at developers writing applications that use ethernet connections. Refer to Comms Database Configuration Overview for more information on using the Comms database.

This section is a use case of the Comms database for connecting the emulator to the LAN using ethernet connection and explains the various tables that should be configured. You can configure tables in any order, but we recommend that you follow the same order as listed here. The configuration settings are stored in an XML file as shown in the sample configuration file. This file can be edited using CED and CEDDUMP tools.

The following tables are needed when configuring Ethernet connections. Note that CED generates blank tables if any of the tables listed below is not configured.

There should be at least one record created for this table. This table contains the network name to be used by the software.

<NetworkTable>
    <Network operation="add">
        <Name>Intranet</Name>
    </Network>
    <Network operation="add">
        <Name>mRouter</Name>
    </Network>
</NetworkTable>

The sample network table contains two records one for the intranet and the second record specifying a mobile router. To connect the emulator to the intranet only the first record of the sample table is used.

There should be at least one record created for the IAP table but usually more than one record is used. There is one record created for each available IAP.

Ethernet using static IP address

<IAP operation="add">
        <Name>Ethernet No Daemon Static IP</Name>
        <IAPService>LANService.Ethernet No Daemon</IAPService>
        <IAPBearer>LANBearer.EKA2 Emulator Ethernet</IAPBearer>
        <IAPNetwork>Network.Intranet</IAPNetwork>
        <IAPNetworkWeighting>0</IAPNetworkWeighting>
        <LocationRef>Location.Office</LocationRef>
    </IAP>
<IAPTable>

The sample IAP table shows the IAP record for connecting to the ethernet with no daemon and using a static IP address. The table has reference to records in other tables like Network table, LANService table and Location table. The IAP records specify the access point settings and hence there are several records in this table for different access types used by the applications.

Ethernet using dynamic IP address

<IAPTable>
                <IAP operation="add">
        <Name>Ethernet with Daemon Dynamic IP</Name>
        <IAPService>LANService.Ethernet</IAPService>
        <IAPBearer>LANBearer.EKA2 Emulator Ethernet</IAPBearer>
        <IAPNetwork>Network.Intranet</IAPNetwork>
        <IAPNetworkWeighting>0</IAPNetworkWeighting>
        <LocationRef>Location.Office</LocationRef>
    </IAP>
</IAPTable>

This sample IAP table shows the IAP record for connecting to the ethernet with daemon and using a dynamic IP address. The table has got references to LANService table, LANBearer table, Network table and Location tables.

For full list of fields and possible values, Refer to Comms Database Reference

There should be at least one record created for this table.

<LANBearerTable>
    <LANBearer operation="add">
                        <Name>EKA1 Target Ethernet</Name>
                        <Agent>nullagt.agt</Agent>
                        <IfName>ethint</IfName>
                        <LDDFilename>ethercard</LDDFilename>
                        <LDDName>EtherCard</LDDName>
                        <PDDFilename>EtherSmc</PDDFilename>
                        <PDDName>EtherCard.Smc</PDDName>
                        <PacketDriverName>EtherPkt.drv</PacketDriverName>
                        <LastSocketActivityTimeout>-1</LastSocketActivityTimeout>
                        <LastSessionClosedTimeout>-1</LastSessionClosedTimeout>
                        <LastSocketClosedTimeout>-1</LastSocketClosedTimeout>
    </LANBearer>
</LANBearerTable>

The LAN bearer table contains the details of the bearer settings and the device drivers used. There may be other bearers configured for different applications.

For full list of fields and possible values, Refer to Comms Database Reference

There should be at least one record created for this table. This record contains the details of the default gateway, DNS server, DHCP server and IP address.

<LANServiceTable>
    <LANService operation="add">
        <Name>Ethernet</Name>
        <IfNetworks>ip</IfNetworks>
        <IpNetMask>255.255.255.0</IpNetMask>
        <IpGateway>aaa.aaa.aaa.aaa</IpGateway>
        <IpAddr>aaa.aaa.aaa.aaa</IpAddr>
        <IpAddrFromServer>TRUE</IpAddrFromServer>
        <IpDNSAddrFromServer>TRUE</IpDNSAddrFromServer>
        <IpNameServer1>bbb.bbb.bbb.bbb</IpNameServer1>
        <IpNameServer2>ccc.ccc.ccc.ccc</IpNameServer2>
        <ConfigDaemonManagerName>ConfigDaemonManager</ConfigDaemonManagerName>
        <ConfigDaemonName>DhcpServ</ConfigDaemonName>
    </LANService>
</LANServiceTable>

For full list of fields and possible values, Refer to Comms Database Reference

There should be at least one record created for this table. The record containing the most preferred connection should have ranking 1 and the record containing the next preferred connection should have ranking 2. All other records created in this table should have the ranking 0. The record with ranking 1 is attempted first, if it fails the connection with ranking 2 is attempted.

<ConnectionPreferencesTable>
                <ConnectionPreferences operation="add">
        <Name>ConnectionPreferencesTable2</Name>
        <Ranking>1</Ranking>
        <Direction>OUTGOING</Direction>
        <DialogPref>PROMPT</DialogPref>
        <BearerSet>LAN</BearerSet>
        <IAPRef>IAP.Ethernet with Daemon Dynamic IP</IAPRef>
    </ConnectionPreferences>
</ConnectionPreferencesTable>

This sample record contains the settings for an outgoing connection. A Similar record can be created for incoming connections.

For full list of fields and possible values, Refer to Comms Database Reference

There should be only one record created for this table. The record should have valid references in the Modem bearer, Location and Network tables.

<GlobalSettingsTable>
    <GlobalSettings operation="add">
        <Name>GlobalSettingsTable1</Name>
        <WAPAccess>WAPAccessPoint.Default Dial In ISP</WAPAccess>
        <RedialAttempts>3</RedialAttempts>
        <SmsBearer>WAPSMSBearer.WAPSMSBearerTable1</SmsBearer>
        <SmsReceiveMode>2</SmsReceiveMode>
        <GPRSAttachMode>1</GPRSAttachMode>
        <AcceptIncomingGprs>1</AcceptIncomingGprs>
        <ConnectionAttempts>2</ConnectionAttempts>
        <ModemForDataAndFax>2</ModemForDataAndFax>
        <ModemForPhoneServicesAndSMS>2</ModemForPhoneServicesAndSMS>
        <LocationForDataAndFax>Location.Office</LocationForDataAndFax>
        <LocationForPhoneServicesAndSMS>Location.Office</LocationForPhoneServicesAndSMS>
        <GPRSClassCBearer>GSM</GPRSClassCBearer>
        <DefaultNetwork>Network.Intranet</DefaultNetwork>
        <BearerAvailabilityCheckTSY>mm</BearerAvailabilityCheckTSY>
    </GlobalSettings>
</GlobalSettingsTable>

For full list of fields and possible values, Refer to Comms DatabaseReference

There should be at least one record for this table with the location details.

<LocationTable>           
                <Location operation="add">
        <Name>Office</Name>
        <Mobile>FALSE</Mobile>
        <UsePulseDial>FALSE</UsePulseDial>
        <WaitForDialTone>FALSE</WaitForDialTone>
        <PauseAfterDialout>0</PauseAfterDialout>
        <IntlPrefixCode>00</IntlPrefixCode>
        <NatPrefixCode>0</NatPrefixCode>
        <NatCode>44</NatCode>
        <AreaCode>171</AreaCode>
        <DialOutCode>9,</DialOutCode>
        <DisableCallWaitingCode>9,</DisableCallWaitingCode>
    </Location>
</LocationTable>

For full list of fields and possible values, Refer to Comms Database Reference

Sample Ethernet configuration

Configuring Comms database for VPN connections

Configuring Comms Database For Circuit Switched Data (CSD) Connections

Configuring Comms Database For Packet Switched Data (PSD) Connections

Comms Database Reference