|
Content
|
|
|
|
1. Introduction
|
The purpose of this program is, to work as a replacement for dynamic DNS.
It makes your current IP address available from a password protected website.
|
|
2. Setting up the Software
|
|
2.1 Registration
|
You need to register at the DynWebLink website first.
Please follow the link below, if you haven't done it already.
DynWebLink Register New Account
After registration you receive an e-mail with your activation key.
|
|
2.2 Installation
|
Download the DynWebLink package, create a new directory and decompress the package into it.
Download Java Version
The program will ask for the activation on the first start.
Just copy the key from the mail.
|
|
3. How to use the program
|
|
3.1 The content of the archive
|
|
|
agreement.txt
|
The DynWebLink User agreement
(in English)
|
|
agreement_de.txt
|
The DynWebLink User agreement
(in German)
|
|
dwl.jar
|
The Java archive
|
dynweblink
dynweblink.bat
|
Batch file (for Unix and MS-DOS), to use DynWebLink.
Usually you will control DynWebLink with this file.
|
dwld
dwld.bat
|
Batch file, to control the service part (daemon) of DynWebLink directly.
|
dwl
dwl.bat
|
Batch file, to control the client part of DynWebLink directly.
|
|
|
3.2 The 'dynweblink' batch file
|
With this batch file you can run DynWebLink on a Unix or Windows machine.
It implements the following commands:
|
Command
|
Purpose
|
|
start
|
start the service. This creates a daemon process running in the background
|
|
stop
|
stop the service. This will shutdown the daemon process
|
|
pause
|
disconnect from the DynWebLink server, the service continues to run
|
|
resume
|
the previously paused service will reconnect to the DynWebLink server
|
|
status
|
request the current status from the running service
|
|
|
3.3 Using the Java classes directly
|
If the prepared 'dynweblink' batch file is not working for you,
you can use the Java classes directly instead.
DynWebLink consists of two parts.
The service part, this is the daemon process running in the background,
and the client part, this is the tool to control the service.
These parts are implemented with two Java classes.
The class 'dwld' is the service and the class 'dwl' is the client.
Call the classes either directly, with a 'java' command, or thru the 'dwl' and 'dwld' batch files.
Here are the example java commands for both classes.
The option '-?' is used to display the available options and commands
for the class.
java -cp dwl.jar com.dynweblink.client.dwl -?
java -cp dwl.jar com.dynweblink.client.dwld -?
|
In order to run the commands as shown, 'java' needs to be in the
current command search path and the 'dwl.jar' archive-file needs to
be in the current directory.
Please note that the call to dwld will not return,
therefore you need to put it into the background (e.g. prefix 'start /B'
on Windows or suffix '&' on Unix).
|
|
4. Using the Website
|
|
4.1 Login Modes
|
The website has two login modes. 'Status View' mode and 'Edit' mode.
Therefore you have picked two passwords during registration.
'Status View' mode is what you will use most of the time.
It is used to show your current IP address and the specified links.
You can give the password to other people, so they can connect to your server.
'Edit' mode is for your private use only.
In this mode you can change the account data and the specified links.
|
|
4.2 Specify WebLinks
|
In order to specify a weblink, for server programs that are accessible from a browser
(WWW-Server etc.). You need to log into 'Edit' mode first and then select
'Edit Links' from the status page.
Specify a link, just like you would type it into the browsers address field.
Instead of the server name, which is changing with your
IP address, simply type #. This placeholder is automatically
replaced with your current IP address.
There are examples on the 'Edit Links'-page.
|
|
5. Customized Settings
|
Normally you don't have to change the DynWebLink configuration.
If you cannot use the default configuration, create a XML-file with the changed settings.
This file must be named 'config.xml' and stored in the DynWebLink directory.
Use the following frame around the settings :
<?xml version="1.0" encoding="UTF-8"?>
<setting>
<set name="client">
your client settings
</set>
<set name="service">
your service settings
</set>
</setting>
|
Even though the specified encoding is UTF-8, you can save the file as ANSI,
since no special characters are used.
|
|
5.1 Available Client Settings
|
|
|
Name
|
ServiceHost
|
|
Purpose
|
Name or IP address of the computer running the service.
|
|
Data type
|
string
|
|
Default
|
localhost
|
|
Example
|
<entry name="ServiceHost" datatype="string">
192.168.1.7
</entry>
|
|
|
|
Name
|
ServicePort
|
|
Purpose
|
This is the TCP/IP-port, where the service is accepting connections from the client tool.
You need to specify the new port here, if you have changed it in the
service settings.
|
|
Data type
|
int
|
|
Default
|
52137
|
|
Example
|
<entry name="ServicePort" datatype="int">
56001
</entry>
|
|
|
5.2 Available Service Settings
|
|
|
Name
|
UpdateTimeOut
|
|
Purpose
|
This is the time (milliseconds), the service will wait between sending
live signals to the server. A higher value means, the server will take
longer to recognize unexpectedly dropped connections. A higher value
also means less network traffic. Please note that the lower limit is
set by the server (currently 30000) and cannot be overwritten.
|
|
Data type
|
int
|
|
Default
|
0
thus the value set by the server will be used
|
|
Example
|
<entry name="UpdateTimeOut" datatype="int">
60000
</entry>
|
|
|
|
Name
|
ServicePort
|
|
Purpose
|
This is the TCP/IP-port, where the service is accepting connections from the client tool.
Please note if you change this you need to change it in the
client settings too.
|
|
Data type
|
int
|
|
Default
|
52137
|
|
Example
|
<entry name="ServicePort" datatype="int">
56001
</entry>
|
|
|
|
Name
|
ServicePortMask
|
|
Purpose
|
This mask is used to restrict access from the network to the service,
only matching IP addresses may access the service.
|
|
Data type
|
string
|
|
Default
|
255.255.255.0
|
|
Example
|
<entry name="ServicePortMask" datatype="string">
255.255.128.0
</entry>
|
|
|
5.3 Complete Example
|
A complete config file could look like this :
<?xml version="1.0" encoding="UTF-8"?>
<setting>
<set name="client">
<entry name="ServicePort" datatype="int">
56001
</entry>
</set>
<set name="service">
<entry name="UpdateTimeOut" datatype="int">
60000
</entry>
<entry name="ServicePort" datatype="int">
56001
</entry>
<entry name="ServicePortMask" datatype="string">
255.255.128.0
</entry>
</set>
</setting>
|
|
|
6. More Information
|
|
For further questions, please refer to our Questions and Answers list:
FAQ
If something is not covered by the Questions and Answers list, please contact our support:
support@dynweblink.com
|