Modifying -your current setup for ethernet

You can also use the Quick -ethernet configuration.

Install -WinPcap

WinPcap is used by Symbian platform to send -and receive ethernet frames to Windows OS. We recommend version 4.0 of this -program
Edit your current comms -database as described in the following section. The CED, CEDDUMP and -tools should be used to securely modify comms database entries; see Comms -database configuration tools.
Run the Configchange.pl script.

Editing comms -database settings for Ethernet

Symbian platform stores many communication -settings in its communications database. This database is used both in the -emulator and real devices. It is primarily used by the communication subsystems -within Symbian platform.

The comms database is made up of a number -of tables. Several tables are required to connect the emulator to the Internet -via ethernet.

Edit your current comms database as described below. -The CED and CEDDUMP tools should be used to securely modify -comms database entries; see Comms database configuration tools.

LAN Bearer table

The LAN bearer table contains information -about physical connections to networks. The start of the LAN bearer table -is indicated by the text [LANBearer]. It may be followed -by a number of connections. One may be suitable for the emulator, otherwise -add a new connection in a new ADD_SECTION...END_ADD section.

If -you are using Symbian platform with the EKA1 kernel then there should be a -connection like the one below:

ADD_SECTION - Name=EKA1 Emulator Ethernet - Agent=nullagt.agt - IfName=ethint - LDDFilename=ethercard - LDDName=Ethercard - PDDFilename=etherwins - PDDName=Ethercard.wins - PacketDriverName=EtherPkt.drv - LastSocketActivityTimeout=-1 - LastSessionClosedTimeout=-1 - LastSocketClosedTimeout=-1 - FIELD_COUNT=11 -END_ADD

If you are using EKA2 kernel then there should be a -connection like this:

ADD_SECTION - Name=EKA2 Emulator Ethernet - Agent=nullagt.agt - IfName=ethint - LDDFilename=enet - LDDName==Ethernet - PDDFilename=ethernet - PDDName=Ethernet.Wins - PacketDriverName=EtherPkt.drv - LastSocketActivityTimeout=-1 - LastSessionClosedTimeout=-1 - LastSocketClosedTimeout=-1 - FIELD_COUNT=11 -END_ADD

The Symbian platform version number will tell you which -kernel you are using. Version 7 or less indicates EKA1. Versions 8.0 and 8.1 -are written with a letter after them. An 'a' indicates EKA1 and a 'b' -indicates EKA2. Versions 9.0 and later are EKA2. The version number is commonly -available in /epoc32/data/BuildInfo.txt.

LAN Service table

The LAN Service table contains -address information. The start of the LAN service table is indicated by the -text [LANService]. This may be followed by address information -for one or more networks. You will need information for each network to which -you want to connect.

Ethernet with dynamic -IP address

Use this when your network uses DHCP. It allows the -network to automatically allocate an IP address for the emulator every time -it connects. Your network administrator will tell you whether you can use -DHCP.

In the [LANService] table, make sure there -is a ADD_SECTION...END_ADD section in the table identical -to the following. In particular, set the IpAddrFromServer and IpDNSAddrFromServer fields -to TRUE, and set the two ConfigDaemon fields -as shown in the following:
ADD_SECTION - Name=Ethernet using DCHP - IfNetworks=ip - IpNetMask= - IpGateway= - IpAddrFromServer=TRUE - IpAddr= - IpDNSAddrFromServer=TRUE - IpNameServer1= - IpNameServer2= - ConfigDaemonManagerName=NetCfgExtnDhcp - ConfigDaemonName=DhcpServ - FIELD_COUNT=11 -END_ADD
Note: before v9.0, the value of ConfigDaemonManagerName was ConfigDaemonManager.
Ethernet with static -IP address on networks without DHCP

This describes how to set -all your network settings manually. This will be necessary on networks that -do not use DHCP. If your network uses DHCP then you can still set your settings -manually if you wish.

In the [LANService] table, -make sure there is a ADD_SECTION...END_ADD section in the -table similar to the one below:
- Set the IpAddrFromServer and IpDNSAddrFromServer fields -to FALSE, and leave the two ConfigDaemon fields -empty
- Set the fields in the -following table to suitable values:
  - - - -Field -Description - - - - -
  IpAddr
  -
  IP address
  - - -
  IpNetMask
  -
  IP subnet mask
  - - -
  IpGateway
  -
  Gateway IP address
  - - -
  IpNameServer1 and IpNameServer2
  -
  Primary and secondary DNS server addresses
  - - - -
  
  Your network administrator may be able to supply you with an IP -address. It must be in the same range of addresses as the other computers -on the network, and it must not be in use already.
  
  For the other parameters, -you can normally use the same values that Windows uses on your PC. To show -Window's configuration, type the following from a command prompt:
  
  ipconfig -/all
Here is an example table:
ADD_SECTION - Name=Ethernet Static IP - IfNetworks=ip - IpNetMask=255.255.255.0 - IpGateway=10.23.162.254 - IpAddrFromServer=FALSE - IpAddr=10.23.162.200 - IpDNSAddrFromServer=FALSE - IpNameServer1=10.16.59.515 - IpNameServer2=10.23.58.12 - ConfigDaemonManagerName= - ConfigDaemonName= - FIELD_COUNT=11 -END_ADD
Ethernet with static -IP address on DHCP networks

This describes how to choose your -own IP address, but to set all the other network settings (subnet mask, gateway -and DNS servers) automatically when you connect. Your network must use DHCP -for this.

Some DHCP servers do not support this configuration. -Before using it, please ensure that your network's DHCP server supports the -'INFORM' message.
In the [LANService] table, -make sure there is a ADD_SECTION...END_ADD section in the -table similar to the one in the following:
- Set the IpDNSAddrFromServer fields -to FALSE and set the two ConfigDaemon fields -as shown in the example below
- Set the IpAddrFromServer to TRUE and -set IpAddr to an IP address for the emulator. Your network -administrator may be able to supply you with an IP address. It must be in -the same range of addresses as the other computers on the network, and it -must not be in use already.
Here is an example table:
ADD_SECTION - Name=Ethernet Static IP - IfNetworks=ip - IpNetMask= - IpGateway= - IpAddrFromServer=FALSE - IpAddr=192.168.20.13 - IpDNSAddrFromServer=TRUE - IpNameServer1= - IpNameServer2= - ConfigDaemonManagerName=NetCfgExtnDhcp - ConfigDaemonName=DhcpServ - FIELD_COUNT=11 -END_ADD
Note: before v9.0, the value of ConfigDaemonManagerName was ConfigDaemonManager.

Internet Access Point table

In the previous two -sections you created a physical connection in the [LANBearer] table -for either the EKA1 or EKA2 kernel, and you created your network's address -information in the LAN Service table. Now you must link the two together in -an Internet Access Point (IAP). The combination of the two is all the -emulator needs to connect to the network.

The IAP table defines a -number of IAPs. You must ensure that there is one suitable for the emulator -on your network. The start of the IAP table is indicated by the text [IAP]. -After this there will be a number of sections defining IAPs. If there is not -a suitable IAP already then you must create one similar to the following:

[IAP] -ADD_SECTION - Name=Emulator Lan IAP - IAPService=2 - IAPServiceType=LANService - IAPBearer=4 - IAPBearerType=LANBearer - IAPNetwork=1 - IAPNetworkWeighting=0 - Location=1 - FIELD_COUNT=8 -END_ADD

In each IAP, the IAPBearer and IAPService parameters -define the sections to link. You need to enter a number in each of these fields:

Go to the LAN Service -table and find the address information for your network. It will be in an ADD_SECTION...END_ADD table -entry. Count the number of table entries from the beginning of the table until -you reach your entry. Enter this number in the IAP's IAPService field.

Note: -the first entry in the table is number one, not zero.
Repeat the same for -your network connection in the [LANBearer] table, entering -the number into the IAPBearer field of the IAP.

The example above links the second network address section in the -LAN Service table with the fourth physical connection in the [LANBearer] table.

Copy -the rest of the fields as shown above.

Connection Preferences table

The Internet Access -Point (IAP) table defines a number of method to connect to networks and the -Internet. When a phone or the emulator wants to connect to a network, the -Connection Preferences table defines how a IAP is chosen.

The start -of the connection preferences table is indicated by the text [ConnectionPreferences]. -After this there will be a number of sections defining your preferences.

You -have two options:

Ask which IAP to -use each time you connect

If the table contains a section like -the one below then Symbian platform will ask you to choose an IAP before it -connects. A dialog box will be displayed allowing you to make your choice. -This is useful if you often connect to more than one network.

You -can ignore the BearerSet and IAP fields, -but you must copy the others as shown:
ADD_SECTION - Ranking=1 - Direction=OUTGOING - DialogPref=PROMPT - BearerSet=LAN - IAP=1 - FIELD_COUNT=5 -END_ADD
Note the Ranking=1 field. This indicates -that this is the highest priority connection preference.

Any sections -with Ranking=0 are ignored. Think of setting Ranking=0 as -'commenting out' a connection preference.
Always connect with -the same IAP Define the IAP to use

You can define the -default IAP in the connection preferences table. When Symbian platform wants -to connect, it always uses the IAP that you define here. No dialog box will -appear on screen and you will not be able to choose an IAP before you connect.

This -is useful when you always connect to the same network.

Add a section -to the table like this:
ADD_SECTION - Ranking=1 - Direction=OUTGOING - DialogPref=DONOTPROMPT - BearerSet=LAN - IAP=1 - FIELD_COUNT=5 -END_ADD
where the IAP field must be set to -the desired IAP number. In this example we connect to the first IAP, which -is the first ADD_SECTION...END_ADD after the text [IAP]. -Copy the other fields as shown.

You can specify a second, backup connection -preference. If the first connection attempt fails then the backup connection -is tried. Define a backup connection in a section similar to the following:
ADD_SECTION - Ranking=2 - Direction=OUTGOING - DialogPref=DONOTPROMPT - BearerSet=LAN - IAP=3 - FIELD_COUNT=5 -END_ADD
Note the Ranking=2 field. This indicates -that this is the second highest priority connection preference after the section -with Ranking=1. Any sections with Ranking=0 are -ignored by Symbian platform.

+ + + + + +Modifying +your current setup for ethernetSet up ethernet to incorporate ethernet with comms database settings. +

You can also use the Quick +ethernet configuration.

Install +WinPcap

WinPcap is used by Symbian platform to send +and receive ethernet frames to Windows OS. We recommend version 4.0 of this +program
Edit your current comms +database as described in the following section. The CED, CEDDUMP and +tools should be used to securely modify comms database entries; see Comms +database configuration tools.
Run the Configchange.pl script.

Editing comms +database settings for Ethernet

Symbian platform stores many communication +settings in its communications database. This database is used both in the +emulator and real devices. It is primarily used by the communication subsystems +within Symbian platform.

The comms database is made up of a number +of tables. Several tables are required to connect the emulator to the Internet +via ethernet.

Edit your current comms database as described below. +The CED and CEDDUMP tools should be used to securely modify +comms database entries; see Comms database configuration tools.

LAN Bearer table

The LAN bearer table contains information +about physical connections to networks. The start of the LAN bearer table +is indicated by the text [LANBearer]. It may be followed +by a number of connections. One may be suitable for the emulator, otherwise +add a new connection in a new ADD_SECTION...END_ADD section.

If +you are using Symbian platform with the EKA1 kernel then there should be a +connection like the one below:

ADD_SECTION + Name=EKA1 Emulator Ethernet + Agent=nullagt.agt + IfName=ethint + LDDFilename=ethercard + LDDName=Ethercard + PDDFilename=etherwins + PDDName=Ethercard.wins + PacketDriverName=EtherPkt.drv + LastSocketActivityTimeout=-1 + LastSessionClosedTimeout=-1 + LastSocketClosedTimeout=-1 + FIELD_COUNT=11 +END_ADD

If you are using EKA2 kernel then there should be a +connection like this:

ADD_SECTION + Name=EKA2 Emulator Ethernet + Agent=nullagt.agt + IfName=ethint + LDDFilename=enet + LDDName==Ethernet + PDDFilename=ethernet + PDDName=Ethernet.Wins + PacketDriverName=EtherPkt.drv + LastSocketActivityTimeout=-1 + LastSessionClosedTimeout=-1 + LastSocketClosedTimeout=-1 + FIELD_COUNT=11 +END_ADD

The Symbian platform version number will tell you which +kernel you are using. Version 7 or less indicates EKA1. Versions 8.0 and 8.1 +are written with a letter after them. An 'a' indicates EKA1 and a 'b' +indicates EKA2. Versions 9.0 and later are EKA2. The version number is commonly +available in /epoc32/data/BuildInfo.txt.

LAN Service table

The LAN Service table contains +address information. The start of the LAN service table is indicated by the +text [LANService]. This may be followed by address information +for one or more networks. You will need information for each network to which +you want to connect.

Ethernet with dynamic +IP address

Use this when your network uses DHCP. It allows the +network to automatically allocate an IP address for the emulator every time +it connects. Your network administrator will tell you whether you can use +DHCP.

In the [LANService] table, make sure there +is a ADD_SECTION...END_ADD section in the table identical +to the following. In particular, set the IpAddrFromServer and IpDNSAddrFromServer fields +to TRUE, and set the two ConfigDaemon fields +as shown in the following:
ADD_SECTION + Name=Ethernet using DCHP + IfNetworks=ip + IpNetMask= + IpGateway= + IpAddrFromServer=TRUE + IpAddr= + IpDNSAddrFromServer=TRUE + IpNameServer1= + IpNameServer2= + ConfigDaemonManagerName=NetCfgExtnDhcp + ConfigDaemonName=DhcpServ + FIELD_COUNT=11 +END_ADD
Note: before v9.0, the value of ConfigDaemonManagerName was ConfigDaemonManager.
Ethernet with static +IP address on networks without DHCP

This describes how to set +all your network settings manually. This will be necessary on networks that +do not use DHCP. If your network uses DHCP then you can still set your settings +manually if you wish.

In the [LANService] table, +make sure there is a ADD_SECTION...END_ADD section in the +table similar to the one below:
- Set the IpAddrFromServer and IpDNSAddrFromServer fields +to FALSE, and leave the two ConfigDaemon fields +empty
- Set the fields in the +following table to suitable values:
  + + + +Field +Description + + + + +
  IpAddr
  +
  IP address
  + + +
  IpNetMask
  +
  IP subnet mask
  + + +
  IpGateway
  +
  Gateway IP address
  + + +
  IpNameServer1 and IpNameServer2
  +
  Primary and secondary DNS server addresses
  + + + +
  
  Your network administrator may be able to supply you with an IP +address. It must be in the same range of addresses as the other computers +on the network, and it must not be in use already.
  
  For the other parameters, +you can normally use the same values that Windows uses on your PC. To show +Window's configuration, type the following from a command prompt:
  
  ipconfig +/all
Here is an example table:
ADD_SECTION + Name=Ethernet Static IP + IfNetworks=ip + IpNetMask=255.255.255.0 + IpGateway=10.23.162.254 + IpAddrFromServer=FALSE + IpAddr=10.23.162.200 + IpDNSAddrFromServer=FALSE + IpNameServer1=10.16.59.515 + IpNameServer2=10.23.58.12 + ConfigDaemonManagerName= + ConfigDaemonName= + FIELD_COUNT=11 +END_ADD
Ethernet with static +IP address on DHCP networks

This describes how to choose your +own IP address, but to set all the other network settings (subnet mask, gateway +and DNS servers) automatically when you connect. Your network must use DHCP +for this.

Some DHCP servers do not support this configuration. +Before using it, please ensure that your network's DHCP server supports the +'INFORM' message.
In the [LANService] table, +make sure there is a ADD_SECTION...END_ADD section in the +table similar to the one in the following:
- Set the IpDNSAddrFromServer fields +to FALSE and set the two ConfigDaemon fields +as shown in the example below
- Set the IpAddrFromServer to TRUE and +set IpAddr to an IP address for the emulator. Your network +administrator may be able to supply you with an IP address. It must be in +the same range of addresses as the other computers on the network, and it +must not be in use already.
Here is an example table:
ADD_SECTION + Name=Ethernet Static IP + IfNetworks=ip + IpNetMask= + IpGateway= + IpAddrFromServer=FALSE + IpAddr=192.168.20.13 + IpDNSAddrFromServer=TRUE + IpNameServer1= + IpNameServer2= + ConfigDaemonManagerName=NetCfgExtnDhcp + ConfigDaemonName=DhcpServ + FIELD_COUNT=11 +END_ADD
Note: before v9.0, the value of ConfigDaemonManagerName was ConfigDaemonManager.

Internet Access Point table

In the previous two +sections you created a physical connection in the [LANBearer] table +for either the EKA1 or EKA2 kernel, and you created your network's address +information in the LAN Service table. Now you must link the two together in +an Internet Access Point (IAP). The combination of the two is all the +emulator needs to connect to the network.

The IAP table defines a +number of IAPs. You must ensure that there is one suitable for the emulator +on your network. The start of the IAP table is indicated by the text [IAP]. +After this there will be a number of sections defining IAPs. If there is not +a suitable IAP already then you must create one similar to the following:

[IAP] +ADD_SECTION + Name=Emulator Lan IAP + IAPService=2 + IAPServiceType=LANService + IAPBearer=4 + IAPBearerType=LANBearer + IAPNetwork=1 + IAPNetworkWeighting=0 + Location=1 + FIELD_COUNT=8 +END_ADD

In each IAP, the IAPBearer and IAPService parameters +define the sections to link. You need to enter a number in each of these fields:

Go to the LAN Service +table and find the address information for your network. It will be in an ADD_SECTION...END_ADD table +entry. Count the number of table entries from the beginning of the table until +you reach your entry. Enter this number in the IAP's IAPService field.

Note: +the first entry in the table is number one, not zero.
Repeat the same for +your network connection in the [LANBearer] table, entering +the number into the IAPBearer field of the IAP.

The example above links the second network address section in the +LAN Service table with the fourth physical connection in the [LANBearer] table.

Copy +the rest of the fields as shown above.

Connection Preferences table

The Internet Access +Point (IAP) table defines a number of method to connect to networks and the +Internet. When a phone or the emulator wants to connect to a network, the +Connection Preferences table defines how a IAP is chosen.

The start +of the connection preferences table is indicated by the text [ConnectionPreferences]. +After this there will be a number of sections defining your preferences.

You +have two options:

Ask which IAP to +use each time you connect

If the table contains a section like +the one below then Symbian platform will ask you to choose an IAP before it +connects. A dialog box will be displayed allowing you to make your choice. +This is useful if you often connect to more than one network.

You +can ignore the BearerSet and IAP fields, +but you must copy the others as shown:
ADD_SECTION + Ranking=1 + Direction=OUTGOING + DialogPref=PROMPT + BearerSet=LAN + IAP=1 + FIELD_COUNT=5 +END_ADD
Note the Ranking=1 field. This indicates +that this is the highest priority connection preference.

Any sections +with Ranking=0 are ignored. Think of setting Ranking=0 as +'commenting out' a connection preference.
Always connect with +the same IAP Define the IAP to use

You can define the +default IAP in the connection preferences table. When Symbian platform wants +to connect, it always uses the IAP that you define here. No dialog box will +appear on screen and you will not be able to choose an IAP before you connect.

This +is useful when you always connect to the same network.

Add a section +to the table like this:
ADD_SECTION + Ranking=1 + Direction=OUTGOING + DialogPref=DONOTPROMPT + BearerSet=LAN + IAP=1 + FIELD_COUNT=5 +END_ADD
where the IAP field must be set to +the desired IAP number. In this example we connect to the first IAP, which +is the first ADD_SECTION...END_ADD after the text [IAP]. +Copy the other fields as shown.

You can specify a second, backup connection +preference. If the first connection attempt fails then the backup connection +is tried. Define a backup connection in a section similar to the following:
ADD_SECTION + Ranking=2 + Direction=OUTGOING + DialogPref=DONOTPROMPT + BearerSet=LAN + IAP=3 + FIELD_COUNT=5 +END_ADD
Note the Ranking=2 field. This indicates +that this is the second highest priority connection preference after the section +with Ranking=1. Any sections with Ranking=0 are +ignored by Symbian platform.

\ No newline at end of file