Differences

This shows you the differences between two versions of the page.

Link to this comparison view

tipsandtricks:ddns [2011/11/13 14:00]
joeljoel
tipsandtricks:ddns [2011/12/29 22:10] (current)
Line 24: Line 24:
  - turn on the "enable non-relay port forwarding" on same setting page  - turn on the "enable non-relay port forwarding" on same setting page
  (UPDATE)  (UPDATE)
- - in reality, you can leave relay on ... this gives you both relay and non-relay access to your plug ... if you intend to use a mobile phone app, you MUST leave relay on+ - in reality, you can leave relay on ... this gives you both relay and non-relay access to your plug 
 +   if you intend to use a mobile phone app, you MUST leave relay on
  
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Line 33: Line 34:
  - enter or select HTTP for the application  - enter or select HTTP for the application
  - enter the IP address of the tonido plug (mine is 192.168.0.100)  - enter the IP address of the tonido plug (mine is 192.168.0.100)
- * optional but suggested: go to the DHCP section of and make the lease on your tonido's address never expire+ * optional but suggested: go to the DHCP section of and  
 +   make the lease on your tonido's address never expire
  - enter a public port of 80, and a private port of 10001  - enter a public port of 80, and a private port of 10001
  - enter or select the TCP protocol  - enter or select the TCP protocol
Line 48: Line 50:
  
  * DDNS services are nothing more than redirectors that keeps track of your cable modem's current IP address   * DDNS services are nothing more than redirectors that keeps track of your cable modem's current IP address 
- ... that's it nothing else ... no data is routed through them ... it's a a simple address cross-reference/lookup service+ ... that's it nothing else ... no data is routed through them 
 + ... it's a a simple address cross-reference/lookup service
  (frankly, i think tonido needs to offer this as an alternative to the fullblown relay service)  (frankly, i think tonido needs to offer this as an alternative to the fullblown relay service)
  
  - most if not all newer router support DDNS  - most if not all newer router support DDNS
- - if your router doesn't support DDNS, you need to either buy a new one or use an always-on PC to make this happen+ - if your router doesn't support DDNS, you need to either buy a new one or  
 +   use an always-on PC to make this happen
  (scratch that - just make it easy on yourself and buy a new router)  (scratch that - just make it easy on yourself and buy a new router)
  - login to the router and find the section for DDNS  - login to the router and find the section for DDNS
  - choose a DDNS provider the router supports or enter one manually if allowed  - choose a DDNS provider the router supports or enter one manually if allowed
- - if it's a dlink router, i recommend and use dlinkdns.com - it's a FREE, super easy to config, front-end to dyndns.com+ - if it's a dlink router, i recommend and use dlinkdns.com - it's a FREE, super easy to config,  
 +   front-end to dyndns.com
  - leave this setup page open  - leave this setup page open
  
Line 68: Line 73:
  - it will probably already know your IP address but if not, enter it from section 3 above  - it will probably already know your IP address but if not, enter it from section 3 above
  - if it asks for an address to start with, enter the same address again  - if it asks for an address to start with, enter the same address again
- - once you submit this, starting IMMEDIATELY, any browser visit to "waffles.dlinkdns.com" will redirect the visitor to the IP address (of your modem) that is on file+ - once you submit this, starting IMMEDIATELY, any browser visit to "waffles.dlinkdns.com" will  
 +   redirect the visitor to the IP address (of your modem) that is on file
  
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 6. Back to the setup page you left open in section 4 6. Back to the setup page you left open in section 4
  
- - now you need to enter the full host (i.e. waffles.dlinkdns.com) and your username and password to the DDNS service + - now you need to enter the full host (i.e. waffles.dlinkdns.com) and  
- (this allows the router to periodically send to the DDNS service your current outside IP address... the DDNS service updates it's table with whatever it is so WAFFLES.DYNDNS.COM always finds its way back to your modem & router) +   your username and password to the DDNS service 
- - since by default, your web browser is really going to:  waffles.dlinkdns.com:80   the "80" is the port that we redirected to your tonido plug's HTTP service + (this allows the router to periodically send to the DDNS service your current  
- this is why the port forwarding / virtual service piece is key ... router reads port, points traffice to internal 192.168.0.100:10001 in my case+  outside IP address... the DDNS service updates it's table with whatever it  
 +  is so WAFFLES.DYNDNS.COM always finds its way back to your modem & router) 
 + - since by default, your web browser is really going to:  waffles.dlinkdns.com:80    
 + the "80" is the port that we redirected to your tonido plug's HTTP service 
 + this is why the port forwarding / virtual service piece is key ... router reads port,  
 + points traffice to internal 192.168.0.100:10001 in my case
   
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 7. OPTIONAL: Friendly up your web address (i.e.  make cloud.waffles.com = waffles.dlinkdns.com) 7. OPTIONAL: Friendly up your web address (i.e.  make cloud.waffles.com = waffles.dlinkdns.com)
  
- - you could stop at section 6 or if you prefer and have your own domain, why not make it really easy for visitors + - you could stop at section 6 or if you prefer and have your own domain, 
 +   why not make it really easy for visitors 
  - OPTION 1 (enhance your DNS):    - OPTION 1 (enhance your DNS):  
  -- login to your domain control panel   -- login to your domain control panel 
- -- in the DNS settings section, add a URL redirect entry that points cloud.waffles.com to cloud.dlinkdns.com+ -- in the DNS settings section, add a URL redirect entry that  
 +    points cloud.waffles.com to cloud.dlinkdns.com
  - OPTION 2 (simple webpage redirector):  - OPTION 2 (simple webpage redirector):
  -- create a subfolder called "cloud" (or whatever you like)  -- create a subfolder called "cloud" (or whatever you like)
  -- create a file called index.htm  -- create a file called index.htm
  -- put this in the file (replacing waffles and cloud with YOUR information)  -- put this in the file (replacing waffles and cloud with YOUR information)
- <html><head><meta http-equiv="refresh" content="0;url=http://www.waffles.com/cloud"/></head></html>+  
 + <html><head><meta http-equiv="refresh" content="0;url=http://www.waffles.com/cloud"/></head></html>
  
  
Line 98: Line 112:
 Simply add an entry to your DNS as a URL redirector to your router's IP address.   Simply add an entry to your DNS as a URL redirector to your router's IP address.  
 It's a bit risky but at least where I live, my IP address hasn't changed ever even though it's not static. It's a bit risky but at least where I live, my IP address hasn't changed ever even though it's not static.
-Personally, I do both ... use DDNS and add a separate entry to your host DNS for the IP address (i.e. cloud.waffles.com and cloud2.waffles.com)+Personally, I do both ... use DDNS and add a separate entry to your host DNS for the  
 + IP address (i.e. cloud.waffles.com and cloud2.waffles.com)
 </code> </code>