Internet
is all about names and numbers. Host names and IP addresses and
service names and port numbers are two name/number pairs that are
important for
AlmostVPN user.
Known Services
Let us deal with service names first.
Essentially, the service name is just a human-friendly way to refer to
a port number allocated for a particular service. We have already
mentioned a few of the more often used services in this manual(like:
pop3,
telnet, http, to name a few). A special organization,
Internet Assigned Numbers
Authority(IANA),
is responsible for registering newly invented services to prevent them
from "stepping on each other". IANA is a good idea, but, for one
reason or
another, it does not know about every single service in the world (for
example, they still have not heard about BitTorrent port 6881). To
make a long story short, it is very probable that at some point you
will
want to deal with a port number that does not have well-known
name. If it ever happens to you, you will have two choices:
- Use the port number and do not worry about assigning a name to it;
- Invent a special name for this port and use the Known Services Manager to map this
name into the number.
You can open the
Known Services
Manager
by clicking on the

next to any
service-related combo box (
Service on
the
AlmostVPN Connections Manager
and
From and
To ports on the
Tunnels
Manager )
As you can see, this Manager knows about some of the more popular
services "out of the box". You can use the

button to add new services and the

button to delete existing services. You can change the service
name
or number by typing in the appropriate table cells. Click the

button when you have finished to close this dialog.
Known Servers
Another set of names and numbers, which is
very
important for
AlmostVPN user,
deals with the host name to IP address
mapping. Every host has to have a somewhat unique IP address to make it
possible to access this port over the net. The "somewhat" qualification
comes from the fact that an IP address' uniqueness is mandatory only
inside
single subnet. It is perfectly legal to have multiple identical
IP addresses in multiple different subnets. If you want to access
a host from outside of a subnet it belongs to, then the "somewhat
unique"
usually is not good enough and you have to get an Internet unique IP
address and register an Internet unique name for it (If you want to
know
more about this you can read about
DNS and
ICANN
on wikipedia). The important point here is that quite often the host
name
to IP address mapping for hosts on private network is, well... private
and unknown to the outside world. As long as most of the time
people use
AlmostVPN to
access
private networks, it is quite possible that the host names assigned to
hosts on such networks are "un-resolvable" (you can not use DNS
to get the IP address for such a name). There are many ways to
deal
with this problem. The
AlmostVPN way
is to use the
Known Servers Manager.
You can open the
Known Servers Manager
by clicking on the

next to any
server-related combo box (
Host Name
on
Accounts Manager,
AlmostVPN Connections Manager,
Drives
Manager and
Tunnels Manager )
You can use the

button to add a new server, the

button to delete an existing server. You can
change
the server name or address by typing in the appropriate table cells.
Click the

button when you
have finished to close this dialog. One of
the simplest ways to keep the host name to IP address mapping is via an
/etc/hosts
file. If you are using it you can import it's content in
Known Servers Manager by clicking
the

button.
Known Servers Manager remembers
only information explicitly entered by user. In screenshot above, you
may see that different entries are displayed in different colors.
This is what these colors mean:
- leapingrodent (greay IP adddress). "leapingrodent" host name is
resolvable in current environment and it's IP address is "1.2.3.4",
- crawlingvarmint (orange IP address). "crawlingvarmint" host name
is resolvable in current environment but user have entered IP address
which is different from IP address to which it gets resolved,
- slidingpenguins (red host name, <unknown> IP address).
"slidingpenguins" host name is NOT resolvable in current environment
and user have not provided an IP address
- jumpinguser (black IP address). "jumpinguser" host name is NOT resolvable in current environment and user have provided an IP address (0.0.0.0).
NOTE: "0.0.0.0"
is special placeholder IP address. If you have situation when you need
to use host name which is NOT resolvable on your side of SSH tunnel,
but resolvable on "other" side. And you do not like to have this host
name painted red in Known Servers Manager window. Than you can use "0.0.0.0" as a placeholder.