|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-88E89E94-7C9E-5583-827C-84FADD50F97E" xml:lang="en"><title>Modifying |
|
13 your current setup for ethernet</title><shortdesc>Set up ethernet to incorporate ethernet with comms database settings.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>You can also use the <xref href="GUID-3C6935E1-66C9-5115-901E-D3B1D0C2E783.dita">Quick |
|
15 ethernet configuration</xref>. </p> |
|
16 <ol id="GUID-F0D337D1-1E90-5FB9-B1BC-676042F792C7"> |
|
17 <li id="GUID-3C2F7DF5-62C6-5B4E-8B66-CCAE76BBE96A"><p> <xref href="GUID-CDD1E761-6B28-5F69-BBEF-756DF45E59A2.dita">Install |
|
18 WinPcap</xref> </p> <p> <i>WinPcap</i> is used by Symbian platform to send |
|
19 and receive ethernet frames to Windows OS. We recommend version 4.0 of this |
|
20 program </p> </li> |
|
21 <li id="GUID-7D079E8F-BDFC-5E96-959D-2DA53DFDB294"><p>Edit your current comms |
|
22 database as described in the following section. The <i>CED</i>, <i>CEDDUMP</i> and |
|
23 tools should be used to securely modify comms database entries; see Comms |
|
24 database configuration tools. </p> </li> |
|
25 <li id="GUID-9730B75A-0278-5D8E-BA95-DB123691E70A"><p>Run the <xref href="GUID-7B114A67-356A-5FCE-B57B-761F5477A2B2.dita">Configchange.pl</xref> script. </p> </li> |
|
26 </ol> |
|
27 <section id="GUID-21ED581C-3623-4BC9-A00F-A7D46C1AC59C"><title>Editing comms |
|
28 database settings for Ethernet</title> <p>Symbian platform stores many communication |
|
29 settings in its communications database. This database is used both in the |
|
30 emulator and real devices. It is primarily used by the communication subsystems |
|
31 within Symbian platform. </p> <p>The comms database is made up of a number |
|
32 of tables. Several tables are required to connect the emulator to the Internet |
|
33 via ethernet. </p> <p>Edit your current comms database as described below. |
|
34 The <i>CED</i> and <i>CEDDUMP</i> tools should be used to securely modify |
|
35 comms database entries; see Comms database configuration tools. </p> </section> |
|
36 <section id="GUID-191C55A1-B55C-4311-B956-C3AF2957A69F"><title>LAN Bearer table</title><p>The LAN bearer table contains information |
|
37 about physical connections to networks. The start of the LAN bearer table |
|
38 is indicated by the text <codeph>[LANBearer]</codeph>. It may be followed |
|
39 by a number of connections. One may be suitable for the emulator, otherwise |
|
40 add a new connection in a new <codeph>ADD_SECTION...END_ADD</codeph> section. </p> <p>If |
|
41 you are using Symbian platform with the EKA1 kernel then there should be a |
|
42 connection like the one below: </p> <codeblock id="GUID-DF5AB7B9-2D29-52C7-97F5-4EE568422901" xml:space="preserve">ADD_SECTION |
|
43 Name=EKA1 Emulator Ethernet |
|
44 Agent=nullagt.agt |
|
45 IfName=ethint |
|
46 LDDFilename=ethercard |
|
47 LDDName=Ethercard |
|
48 PDDFilename=etherwins |
|
49 PDDName=Ethercard.wins |
|
50 PacketDriverName=EtherPkt.drv |
|
51 LastSocketActivityTimeout=-1 |
|
52 LastSessionClosedTimeout=-1 |
|
53 LastSocketClosedTimeout=-1 |
|
54 FIELD_COUNT=11 |
|
55 END_ADD</codeblock> <p>If you are using EKA2 kernel then there should be a |
|
56 connection like this: </p> <codeblock id="GUID-AE57D4FA-90FE-5A74-BB85-0B7DB2398280" xml:space="preserve">ADD_SECTION |
|
57 Name=EKA2 Emulator Ethernet |
|
58 Agent=nullagt.agt |
|
59 IfName=ethint |
|
60 LDDFilename=enet |
|
61 LDDName==Ethernet |
|
62 PDDFilename=ethernet |
|
63 PDDName=Ethernet.Wins |
|
64 PacketDriverName=EtherPkt.drv |
|
65 LastSocketActivityTimeout=-1 |
|
66 LastSessionClosedTimeout=-1 |
|
67 LastSocketClosedTimeout=-1 |
|
68 FIELD_COUNT=11 |
|
69 END_ADD</codeblock> <p>The Symbian platform version number will tell you which |
|
70 kernel you are using. Version 7 or less indicates EKA1. Versions 8.0 and 8.1 |
|
71 are written with a letter after them. An '<i>a</i>' indicates EKA1 and a '<i>b</i>' |
|
72 indicates EKA2. Versions 9.0 and later are EKA2. The version number is commonly |
|
73 available in <filepath>/epoc32/data/BuildInfo.txt</filepath>. </p></section> |
|
74 <section id="GUID-07D8E6DB-8E5A-4D24-B404-16D470B422F6"><title>LAN Service table</title><p>The LAN Service table contains |
|
75 address information. The start of the LAN service table is indicated by the |
|
76 text <codeph>[LANService]</codeph>. This may be followed by address information |
|
77 for one or more networks. You will need information for each network to which |
|
78 you want to connect. </p> <ul> |
|
79 <li id="GUID-0B6C8959-BDA2-5D5F-84C9-DA93BFD677F3"><p> <b>Ethernet with dynamic |
|
80 IP address</b> </p> <p>Use this when your network uses DHCP. It allows the |
|
81 network to automatically allocate an IP address for the emulator every time |
|
82 it connects. Your network administrator will tell you whether you can use |
|
83 DHCP. </p> <p>In the <codeph>[LANService]</codeph> table, make sure there |
|
84 is a <codeph>ADD_SECTION...END_ADD</codeph> section in the table identical |
|
85 to the following. In particular, set the <codeph>IpAddrFromServer</codeph> and <codeph>IpDNSAddrFromServer</codeph> fields |
|
86 to <codeph>TRUE</codeph>, and set the two <codeph>ConfigDaemon</codeph> fields |
|
87 as shown in the following: </p> <codeblock id="GUID-F3D835BE-796B-5422-9072-299409D030A9" xml:space="preserve">ADD_SECTION |
|
88 Name=Ethernet using DCHP |
|
89 IfNetworks=ip |
|
90 IpNetMask= |
|
91 IpGateway= |
|
92 IpAddrFromServer=TRUE |
|
93 IpAddr= |
|
94 IpDNSAddrFromServer=TRUE |
|
95 IpNameServer1= |
|
96 IpNameServer2= |
|
97 ConfigDaemonManagerName=NetCfgExtnDhcp |
|
98 ConfigDaemonName=DhcpServ |
|
99 FIELD_COUNT=11 |
|
100 END_ADD</codeblock> <p>Note: before v9.0, the value of <codeph>ConfigDaemonManagerName</codeph> was <codeph>ConfigDaemonManager</codeph>. </p> </li> |
|
101 <li id="GUID-0DA3C4DC-4951-59A1-9D23-3FABEC3D93DC"><p> <b>Ethernet with static |
|
102 IP address on networks without DHCP</b> </p> <p>This describes how to set |
|
103 all your network settings manually. This will be necessary on networks that |
|
104 do not use DHCP. If your network uses DHCP then you can still set your settings |
|
105 manually if you wish. </p> <p>In the <codeph>[LANService]</codeph> table, |
|
106 make sure there is a <codeph>ADD_SECTION...END_ADD</codeph> section in the |
|
107 table similar to the one below: </p> <ul> |
|
108 <li id="GUID-5FE2A935-0F33-5223-ABB2-6D2A4540F81E"><p>Set the <codeph>IpAddrFromServer</codeph> and <codeph>IpDNSAddrFromServer</codeph> fields |
|
109 to <codeph>FALSE</codeph>, and leave the two <codeph>ConfigDaemon</codeph> fields |
|
110 empty </p> </li> |
|
111 <li id="GUID-55441AA2-8F31-5A81-8580-A5414E87D4E2"><p>Set the fields in the |
|
112 following table to suitable values: </p> <table id="GUID-AE300CB8-55DC-5A20-8E1C-E2F7B7A8586B"> |
|
113 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
114 <thead> |
|
115 <row> |
|
116 <entry>Field</entry> |
|
117 <entry>Description</entry> |
|
118 </row> |
|
119 </thead> |
|
120 <tbody> |
|
121 <row> |
|
122 <entry><p>IpAddr </p> </entry> |
|
123 <entry><p>IP address </p> </entry> |
|
124 </row> |
|
125 <row> |
|
126 <entry><p>IpNetMask </p> </entry> |
|
127 <entry><p>IP subnet mask </p> </entry> |
|
128 </row> |
|
129 <row> |
|
130 <entry><p>IpGateway </p> </entry> |
|
131 <entry><p>Gateway IP address </p> </entry> |
|
132 </row> |
|
133 <row> |
|
134 <entry><p>IpNameServer1 and IpNameServer2 </p> </entry> |
|
135 <entry><p>Primary and secondary DNS server addresses </p> </entry> |
|
136 </row> |
|
137 </tbody> |
|
138 </tgroup> |
|
139 </table> <p>Your network administrator may be able to supply you with an IP |
|
140 address. It must be in the same range of addresses as the other computers |
|
141 on the network, and it must not be in use already. </p> <p>For the other parameters, |
|
142 you can normally use the same values that Windows uses on your PC. To show |
|
143 Window's configuration, type the following from a command prompt: </p> <p><userinput>ipconfig |
|
144 /all</userinput> </p> </li> |
|
145 </ul> <p>Here is an example table: </p> <codeblock id="GUID-F2B36B36-09F9-5B5C-BEC5-BE29E7A39EBA" xml:space="preserve">ADD_SECTION |
|
146 Name=Ethernet Static IP |
|
147 IfNetworks=ip |
|
148 IpNetMask=255.255.255.0 |
|
149 IpGateway=10.23.162.254 |
|
150 IpAddrFromServer=FALSE |
|
151 IpAddr=10.23.162.200 |
|
152 IpDNSAddrFromServer=FALSE |
|
153 IpNameServer1=10.16.59.515 |
|
154 IpNameServer2=10.23.58.12 |
|
155 ConfigDaemonManagerName= |
|
156 ConfigDaemonName= |
|
157 FIELD_COUNT=11 |
|
158 END_ADD</codeblock> </li> |
|
159 <li id="GUID-C32365C7-E4E9-5FE1-8AA8-7A6515C50ACD"><p> <b>Ethernet with static |
|
160 IP address on DHCP networks</b> </p> <p>This describes how to choose your |
|
161 own IP address, but to set all the other network settings (subnet mask, gateway |
|
162 and DNS servers) automatically when you connect. Your network must use DHCP |
|
163 for this. </p> <p> <note> Some DHCP servers do not support this configuration. |
|
164 Before using it, please ensure that your network's DHCP server supports the |
|
165 '<i>INFORM</i>' message. </note></p>In the <codeph>[LANService]</codeph> table, |
|
166 make sure there is a <codeph>ADD_SECTION...END_ADD</codeph> section in the |
|
167 table similar to the one in the following: <ul> |
|
168 <li id="GUID-3B0120F9-63F0-5759-9673-B56C87B2C06E"><p>Set the <codeph>IpDNSAddrFromServer</codeph> fields |
|
169 to <codeph>FALSE</codeph> and set the two <codeph>ConfigDaemon</codeph> fields |
|
170 as shown in the example below </p> </li> |
|
171 <li id="GUID-A7F1091C-E88F-51A0-B3D6-795DCEC5351B"><p>Set the <codeph>IpAddrFromServer</codeph> to <codeph>TRUE</codeph> and |
|
172 set <codeph>IpAddr</codeph> to an IP address for the emulator. Your network |
|
173 administrator may be able to supply you with an IP address. It must be in |
|
174 the same range of addresses as the other computers on the network, and it |
|
175 must not be in use already. </p> </li> |
|
176 </ul> <p>Here is an example table: </p> <codeblock id="GUID-374BD714-F158-52E8-BCDB-FCC5A46E8D52" xml:space="preserve">ADD_SECTION |
|
177 Name=Ethernet Static IP |
|
178 IfNetworks=ip |
|
179 IpNetMask= |
|
180 IpGateway= |
|
181 IpAddrFromServer=FALSE |
|
182 IpAddr=192.168.20.13 |
|
183 IpDNSAddrFromServer=TRUE |
|
184 IpNameServer1= |
|
185 IpNameServer2= |
|
186 ConfigDaemonManagerName=NetCfgExtnDhcp |
|
187 ConfigDaemonName=DhcpServ |
|
188 FIELD_COUNT=11 |
|
189 END_ADD</codeblock> <p>Note: before v9.0, the value of <codeph>ConfigDaemonManagerName</codeph> was <codeph>ConfigDaemonManager</codeph>. </p> </li> |
|
190 </ul></section> |
|
191 <section id="GUID-E46108D2-03E9-4B6C-A004-61A0A983EFE8"><title>Internet Access Point table</title><p>In the previous two |
|
192 sections you created a physical connection in the <codeph>[LANBearer]</codeph> table |
|
193 for either the EKA1 or EKA2 kernel, and you created your network's address |
|
194 information in the LAN Service table. Now you must link the two together in |
|
195 an <i>Internet Access Point (IAP)</i>. The combination of the two is all the |
|
196 emulator needs to connect to the network. </p> <p>The IAP table defines a |
|
197 number of IAPs. You must ensure that there is one suitable for the emulator |
|
198 on your network. The start of the IAP table is indicated by the text <codeph>[IAP]</codeph>. |
|
199 After this there will be a number of sections defining IAPs. If there is not |
|
200 a suitable IAP already then you must create one similar to the following: </p> <codeblock id="GUID-66CD685D-1193-54C8-85EC-9EED9E56E54F" xml:space="preserve">[IAP] |
|
201 ADD_SECTION |
|
202 Name=Emulator Lan IAP |
|
203 IAPService=2 |
|
204 IAPServiceType=LANService |
|
205 IAPBearer=4 |
|
206 IAPBearerType=LANBearer |
|
207 IAPNetwork=1 |
|
208 IAPNetworkWeighting=0 |
|
209 Location=1 |
|
210 FIELD_COUNT=8 |
|
211 END_ADD</codeblock> <p>In each IAP, the <codeph>IAPBearer</codeph> and <codeph>IAPService</codeph> parameters |
|
212 define the sections to link. You need to enter a number in each of these fields: </p> <ul> |
|
213 <li id="GUID-CFB52AF7-B05E-5D5B-A8C2-CBB22F9B3B95"><p>Go to the LAN Service |
|
214 table and find the address information for your network. It will be in an <codeph>ADD_SECTION...END_ADD</codeph> table |
|
215 entry. Count the number of table entries from the beginning of the table until |
|
216 you reach your entry. Enter this number in the IAP's <codeph>IAPService</codeph> field. </p> <p>Note: |
|
217 the first entry in the table is number one, not zero. </p> </li> |
|
218 <li id="GUID-C7F2A24B-3491-59A5-8BCE-F430F9A1F74D"><p>Repeat the same for |
|
219 your network connection in the <codeph>[LANBearer]</codeph> table, entering |
|
220 the number into the <codeph>IAPBearer</codeph> field of the IAP. </p> </li> |
|
221 </ul> <p>The example above links the second network address section in the |
|
222 LAN Service table with the fourth physical connection in the <codeph>[LANBearer]</codeph> table. </p> <p>Copy |
|
223 the rest of the fields as shown above. </p></section> |
|
224 <section id="GUID-A1AF1DD2-C20E-4301-A210-307CAB47A41F"><title>Connection Preferences table</title><p>The Internet Access |
|
225 Point (IAP) table defines a number of method to connect to networks and the |
|
226 Internet. When a phone or the emulator wants to connect to a network, the |
|
227 Connection Preferences table defines how a IAP is chosen. </p> <p>The start |
|
228 of the connection preferences table is indicated by the text <codeph>[ConnectionPreferences]</codeph>. |
|
229 After this there will be a number of sections defining your preferences. </p> <p>You |
|
230 have two options: </p> <ul> |
|
231 <li id="GUID-1D0F662E-B4F3-57FE-8FA2-EED2E8F1ADFB"><p> <b>Ask which IAP to |
|
232 use each time you connect</b> </p> <p>If the table contains a section like |
|
233 the one below then Symbian platform will ask you to choose an IAP before it |
|
234 connects. A dialog box will be displayed allowing you to make your choice. |
|
235 This is useful if you often connect to more than one network. </p> <p>You |
|
236 can ignore the <codeph>BearerSet</codeph> and <codeph>IAP</codeph> fields, |
|
237 but you must copy the others as shown: </p> <codeblock id="GUID-B9C41F22-30C6-5F11-831B-6F0C97179C1D" xml:space="preserve">ADD_SECTION |
|
238 Ranking=1 |
|
239 Direction=OUTGOING |
|
240 DialogPref=PROMPT |
|
241 BearerSet=LAN |
|
242 IAP=1 |
|
243 FIELD_COUNT=5 |
|
244 END_ADD</codeblock> <p>Note the <codeph>Ranking=1</codeph> field. This indicates |
|
245 that this is the highest priority connection preference. </p> <p>Any sections |
|
246 with <codeph>Ranking=0</codeph> are ignored. Think of setting <codeph>Ranking=0</codeph> as |
|
247 'commenting out' a connection preference. </p> </li> |
|
248 <li id="GUID-2F7DFB97-C0A6-563B-B41D-9337749C9525"><p> <b>Always connect with |
|
249 the same IAP</b> <b>Define the IAP to use</b> </p> <p>You can define the |
|
250 default IAP in the connection preferences table. When Symbian platform wants |
|
251 to connect, it always uses the IAP that you define here. No dialog box will |
|
252 appear on screen and you will not be able to choose an IAP before you connect. </p> <p>This |
|
253 is useful when you always connect to the same network. </p> <p>Add a section |
|
254 to the table like this: </p> <codeblock id="GUID-5DA76D4E-7305-5EFD-AD85-928B241C0BC0" xml:space="preserve">ADD_SECTION |
|
255 Ranking=1 |
|
256 Direction=OUTGOING |
|
257 DialogPref=DONOTPROMPT |
|
258 BearerSet=LAN |
|
259 IAP=1 |
|
260 FIELD_COUNT=5 |
|
261 END_ADD</codeblock> <p>where the <codeph>IAP</codeph> field must be set to |
|
262 the desired IAP number. In this example we connect to the first IAP, which |
|
263 is the first <codeph>ADD_SECTION...END_ADD</codeph> after the text <codeph>[IAP]</codeph>. |
|
264 Copy the other fields as shown. </p> <p>You can specify a second, backup connection |
|
265 preference. If the first connection attempt fails then the backup connection |
|
266 is tried. Define a backup connection in a section similar to the following: </p> <codeblock id="GUID-7BBEE6A6-F723-56B1-A54E-8FC2C3E30469" xml:space="preserve">ADD_SECTION |
|
267 Ranking=2 |
|
268 Direction=OUTGOING |
|
269 DialogPref=DONOTPROMPT |
|
270 BearerSet=LAN |
|
271 IAP=3 |
|
272 FIELD_COUNT=5 |
|
273 END_ADD</codeblock> <p>Note the <codeph>Ranking=2</codeph> field. This indicates |
|
274 that this is the second highest priority connection preference after the section |
|
275 with <codeph>Ranking=1</codeph>. Any sections with <codeph>Ranking=0</codeph> are |
|
276 ignored by Symbian platform. </p> </li> |
|
277 </ul></section> |
|
278 </conbody></concept> |