18 |
P a g e
But when Bob is not at home he wants to access his Gateway using BobsHome.homeDNS.org. So he
makes this his secondary IP address. Now when he is out of range of his home network – he is outside
his firewall - the connection is made using the mobile device 3G/4G connection or from some wireless
hotspot. The application converts “BobsHome.homeDNS.org” to an IP address and then connects to
the Gateway.
Tip: This all works because Bob has an account with DynDNS.org. More on that later in this user guide.
Why couldn’t Bob just use “myhome.homeDNS.org” as the one and only IP address? Because of the
way his internet access works it just doesn’t allow this. The “BobsHome.homeDNS.org” resolves to the
address of his DSL modem – as it should – and then the modem gets confused by a home-side
reference to its own address. This may or may not be similar to your situation and it is offered only as
an example.
Tip: Near the end of this user guide is information on “port forwarding”. Understanding and
configuring the router for this is necessary for the above example to work.
In addition to supplying the IP address of the Gateway by either a four part address or as a DNS lookup
name, you can also set the option "By Discovery”. In this case the IP address of the Gateway is found
and used to connect. This will only work if your mobile device (phone or tablet) is on the same network
subnet as the Gateway.
When this option is enabled, while the connection is being made a "Looking for Gateway" popup
shows that the discovery process in underway. If the Gateway is located then the username and
password of the primary connection is used to connect.
In addition to the Gateway Settings you can also configure the User Interface Settings. These let you
customize the colors used for the interface.
