Changes between Version 2 and Version 3 of MapGuideRfc118

Timestamp:

Jul 4, 2011, 2:15:30 AM (13 years ago)

Author:

wuma

Comment:

--

MapGuideRfc118

@@ -41 +41 @@
  2. '''Port the IP address validation logic'''.
 There is existing logic to validate if the IP address specified in the configuration file is valid. But the logic always assumes the IP address is in v4 format. We need port the logic to consider both v4 format and v6 format. One example is like below in
-in {{{\Common\MapGuideCommon\Util\IpUtil.cpp}}}.
+in '''{{{\Common\MapGuideCommon\Util\IpUtil.cpp}}}'''.
 {{{
 void MgIpUtil::ValidateAddress(CREFSTRING address, bool strict)
@@ -63 +63 @@
 }
 }}}
-It treats the character ''':''' as invalid. But for IPv6, ''':''' is used as a splitter for the address segments. 
+It treats the character '''{{{":"}}}''' as invalid. But for IPv6, '''{{{":"}}}''' is used as a splitter for the address segments. 
 
+ 3. Make MapGuide Server listen to IPv6 address
+When the service of MapGuide Server starts, it uses following code to listen to the client, site and admin ports:
+'''''{{{Server\src\Core\Server.cpp}}}'''''
+{{{
+ACE_INET_Addr clientAddr((u_short)pServerManager->GetClientPort));
+ACE_INET_Addr adminAddr((u_short)pServerManager->GetAdminPort());
+ACE_INET_Addr siteAddr((u_short)pServerManager->GetSitePort());
+}}}
+But this way it always listens to IPv4 address no matter if IPv6 is available. Then the 3 '''{{{ACE_INET_Addr}}}''' instances need be created by another constructor:
+{{{
+ACE_INET_Addr (u_short port_number,
+               const wchar_t host_name[],
+               int address_family = AF_UNSPEC);
+}}}
+
+by passing in an IPv6 address as '''{{{host_name}}}''', MapGuide Server can listen to the IPv6 address instead of IPv4 address. 
+But if the given '''{{{host_name}}}''' is a specific IP Address, the Client (Web Extension, Support Server, Admin etc.) has to connect to the Server through the given IP Address. 
+E.g. if there is a computer whose IP Addresses are:
+
+{{{
+IPv4    127.0.0.1
+        192.168.0.10
+IPv6    ::1
+        fe80::9c4b:2cb5:5cda:5c3f%11
+}}}
+
+MapGuide Server should be able to be connected with either '''{{{127.0.0.1}}}''' or '''{{{192.168.0.10}}}''' for IPv4 and either '''{{{::1}}}''' or '''{{{fe80::9c4b:2cb5:5cda:5c3f%11}}}''' for IPv6. But if we pass '''{{{127.0.0.1}}}''' as the '''{{{host_name}}}''', MapGuide Server will NOT listen to '''{{{192.168.0.10}}}'''. The same for IPv6. 
+The solution is: we don’t pass in a specific IP Address, instead:
+ * For IPv4, we pass in '''{{{0.0.0.0}}}'''. Then it will listen to all IPv4 addresses. 
+ * For IPv6, we pass in '''{{{::}}}'''. Then it will listen to all IPv6 address. 
 
 == Implications ==