From contact@spykeeworld.com Wed Aug 12 15:03:10 2009 Received: from smtp1.infomaniak.ch ([84.16.68.89]) by isp.att.net (frfwmxc06) with ESMTP id <20090812150310M0600p5ddee>; Wed, 12 Aug 2009 15:03:10 +0000 X-Originating-IP: [84.16.68.89] Received: from chrisimac-2.gostai.com (102-210-144-213.altitudetelecom.fr [213.144.210.102] (may be forged)) (authenticated bits=0) by smtp1.infomaniak.ch (8.14.2/8.14.2) with ESMTP id n7CF39Qd005085; Wed, 12 Aug 2009 17:03:09 +0200 Message-Id: <4F64C718-3993-4F3C-A2BC-1CBE039349B9@spykeeworld.com> From: "contact@spykeeworld.com" To: Derek Tombrello Dear Derek, You're right, our server is used as a DNS to connect to your robot only using its name. We provide a solution to connect directly to users encountering problems with our server. Our service is made to last but if it ever happened that we had to stop it, the alternative connection method would assure you that you can connect without us. Concrening the open source, we had several requests about it and we're still waiting information about it. Best regards I give you the alternative method description below. -- Spykee Team : : contact@spykeeworld.com Le 12 août 09 à 05:54, Derek Tombrello a écrit : > After several hours, I finally able to get my new Spykee connect > AdHoc, > local and remotely, but I have a question about the remote aspect. > While > registering my robot with your web site, it occurred to me that the > reason for registering is because your site is acting as the DNS > server > for the Spykee robots. Correct? > > Now what happens if/when your company no longer provides this service? > Will the robots then only work locally, or will we still be able to > access the bots over the internet? Maybe a firmware update that would > allow direct access? > > Also, I understand that the Spykee is built around the open-source > software license. Where can I find the source code and do you have an > SDK development kit available? > > Thank you.... > > This alternative method is not exposed in the spykee documentation. This could solve a ot of problems but is only a second choice solution for people which material block spykee's distant connection. Note that this method will not allow you to run two Spykees on the same wifi network. 1.1 Autorize distant connection - Select the distant connection tab - Check the authorize distant connection checkbox - Uncheck the use forwarding on the following port - You don't have to enter a port number there. - Select the my Spykee tab - Note the IP address of your Spykee, these are the first numbers mention it the adresse IP field (for example192.168.1.8) - Click on OK to quit the configuration window 1.2 Forward ports in your router - Refer to your router manual or call your internet service provider to forward the ports. These elements will be useful: - The IP address you want to forward the ports to. This is the IP address you noted before. - The input ports : 9001 - the output ports : 9001 - If these port are asked twice, enter this number two times Once you've completed the port forwarding, you'll then be able to launch the spykee interface and enter this in the Distant robot field : If you are at home (in your local network wifi): The local IP address of your spykee. This is the IP address you noted a few minutes ago and was mention in the my spykee tab of the configuration window. If you are not at home (outside of your local netork): The extern IP address of your router. This is the address of your router on the internet. Some website allow you to know your extern IP address like www.myipaddress.com, for example. You can also contact your internet provider to get your router external IP address. Ensure that you've got a fixed external IP, this would prevent you to see it change when you rest or reboot your router. You should now be able to connect to Spykee. Just enter the Admin login and the password you've chosen.