MDR Inet_Dial.html

DOCUMENTATION v3.7

INTRODUCTION

MDR INET_DIAL provides software designed to run continuously `in the background' and is integrated with a Web Browser (AWEB-II,VOYAGER or IBROWSE), Mailer (YAM) and optional Control software. INET_DIAL puts control of your outgoing and incoming internet connections, mail and your environment in the hands of your "point and click" Web Browser. The preferred method of operation is to leave your Amiga running permanently, only turning off the VDU screen when not in use.

INET_DIAL has been developed over a number of years and has maintained compatibility with the current operating system, at present OS3.6.

Sufficient memory (RAM) is required to enable INET_DIAL (1 Mb approx), YAM (1 Mb approx) and BROWSER (6 Mb approx) to run at the same time. With the AMIGA OS3.6 operating system taking approximately 6 Mb; a minimum memory size would be typically 18 Mb. Additional memory is required as necessary to run your other applications. You will probably already have an accelerator in order to effectively browse the WEB! Your BROWSER graphics display should ideally be set to a minimum of 800 x 600 pixels. 1024 x 768 pixels is to be preferred.

INET_DIAL runs on top of a TCP/IP Protocol Stack, either AMITCP or MIAMI and MIAMI DeLuxe. INET_DIAL can be used to connect to the Internet or by direct dial to a remote computer; remote drives can be imported and appear on your machine using NetFS Amiga networking software (included with INET_DIAL). INET_DIAL can also provide a `dial-in' service to enable remote computers to link into your computer.

The INET_DIAL installer sets up the various files and drawers that are required for the system to run. A basic configuration is set up at installation, certain details will need to be entered before an unregistered version will operate. Certain other files in your existing set up will also need to be altered (see below for your particular configuration).

The Amiga Networking software allows disk drives on a remote machine to appear on your machine, the speed of access being determined by the type of your connection. A facility also exists for rebooting remote machines.

Finally PLEASE take time to read the documentation and enable the software step by step. INET_DIAL is designed to help you in a calm way, not to overcomplicate your life! Whether you configure it to be complicated or not is up to you! Enjoy!

INDEX

INTRODUCTION
EXAMPLE SESSIONS
SECURITY
STATUS DISPLAY
CONFIGURATION
SERIAL PORTS
AMITCP
MIAMI
MIAMI DeLuxe
APACHE
AWEB-II
VOYAGER
IBROWSE
YAM
BACKUP
CONTROL
AREXX
CURRENT STATUS and HISTORY
ACKNOWLEDGEMENTS

EXAMPLE SESSIONS

There follows a brief description of how INET_DIAL operates. All actions are logged:

Startup	Computer boots up Apache started (required only if using control function) AMITCP or MIAMI started YAM started BROWSER started INET_DIAL started
Standby	Mount Local Network Drives INET_DIAL resets and carries out all pre-programmed functions up to current time Modem configured If Server enabled then modem placed on auto-answer If Control System enabled then start monitoring and control functions
WWW Connection	Configure modem for WWW Connect to WWW via ISP Bring SLIP interface online WWW `online' on browser Initiate Mailcheck Monitor connection (disconnect if lost contact)
Remote Computer Connection	Configure modem for Remote Computer Connect to Remote Computer (direct dial) Bring SLIP interface online Enable heartbeat to remote computer Mount remote drives Remote Computer `online' on browser Monitor connection (disconnect if lost contact)
`Dial-in' Server	Configure modem as auto-answer Monitor modem - detect incoming computer call Answer call and approve logon and password Bring SLIP interface online Monitor heartbeat Disconnect when session completed or lost contact

...back to INDEX

SECURITY

INET_DIAL operates behind the security systems and remote access control afforded by registered versions of AMITCP or MIAMI and APACHE.

In addition, INET DIAL forces remote computers `dialling-in' or connected via the Internet or by a Local Area Network to logon and enter a User ID and password. `login' passwords are held in file MDR:logs/mdr_passwords in the format "anyname|test". In this example "anyname" is the User ID and "test" is the password separated by a "|". User ID and Passwords are case sensitive. Each User ID and password combination should be on a separate line of the file.

Your local computer is automatically given login approval when INET_DIAL is started. `Dial-in' users are also automatically logged in once they have entered a correct Password and User ID. `Dial-in' users are logged out when the connection is dropped. Internet and Lan-users should be encouraged to "log out" when they have completed their tasks, otherwise another computer could potentially spoof them!

Passwords for remote access should only be disclosed if you are certain that they will not be abused! You have been warned!

Once the remote user has "logged in" using a valid User ID and Password combination, HTTP Control functions, such as turning equipment on or off, are permitted.

NETFS access is controlled by the AMITCP or MIAMI Stack Database settings. Access should be allowed for 100.100.100.2 (remote `dial-in') and denied to general access.

From the start it is recommended that you consciously adopt a policy of maximum security to avoid the hacking of your system by unauthorised users:

Use long User ID's and Passwords in mixed Upper and Lower case
Do not use words from the dictionary as your passwords
Close down any services which are not required
Check your HTTP Logs from time to time

STATUS DISPLAY

The main display of INET_DIAL is the STATUS Display. This provides links to all the functions. The purpose of each link is listed below.

Function

Description

To force Modem to hang up

To select display of mail received and forwarded

To enter configuration section

To select documentation

To remove auto-answer modem function and then close down INET_DIAL system

To connect to WWW

To connect to remote computer

To reboot a remote computer

SYSTEM LOGS

Log of Backups and whether successful or failed

Log of time online and to whom connected

Log of control commands

Log of Video timing

Log of HTTP access and HTTP errors

Log of errors recorded by INET_DIAL

Log of security events

...back to INDEX

CONFIGURATION

A reference is provided below for each part of the INET_DIAL configuration

Function name	Description	Example
Authorisation	Information provided on registration, not required to operate as unregistered	ABC123 etc
Serial Number	Information provided on registration, not required to operate as unregistered	123 etc
Local Site Name	The name you wish others to know you by	MDR-CENTRAL
Local IP Address	Your IP address provided by your Internet Service Provider	195.222.74.2
Modem	COM1: (modem serial port) settings, speed, parity, data bits, stop bits, hardware handshaking, disable software handshaking X-ON/X-OFF, buffer 32768 bytes	115200,N,8,1,H,X,B32768
Localbus MDR	COM2: (MDR serial port) settings, speed, even parity, data bits, stop bits, disable software handshaking X-ON/X-OFF, buffer 1000 bytes	1200,E,7,1,X,B1000
Localbus X-10	COM3: (X-10 serial port) settings, speed, no parity, data bits, stop bits, disable software handshaking X-ON/X-OFF, buffer 1000 bytes	4800,N,8,1,X,B1000
Number of redials	Number of attempts to dial your Internet Service Provider or a remote computer before giving up	1 to 10
Security frequency	Frequency with which INET_DIAL scans your control/security system	15
Startup delay	To avoid conflict with other programmes loading at the same time, this allows a delay to INET_DIAL before running	1
Rx short timer	Timeout Timer to wait for responses from during connection negotiation	20
Rx long timer	Timeout Timer to allow time for initial modem connection on dialup	60
Modem configuration timer	Timer to slow down configuration command to modem. AT &F command resets modem, but modem may not be quick enough to be ready for following command	5
Lost pings before disconnect	Your computer `pings' the remote computer to check that all is well. If more than the preset number of pings are lost then INET_DIAL will assume a fault and disconnect	5
Security & Control	Enables INET_DIAL control function
Browser	Shows Browser for use with INET_DIAL. Currently AWEB, VOYAGER and IBROWSE are supported	AWEB
Stack	Sets Protocol Stack. Currently AMITCP and MIAMI supported	AMITCP
`Dial-in' Server	Enables your computer as a Server for incoming `dial-in' from remote computers	ENABLED
Speech	Enables speech. Can only operate if narrator device and translator library installed. Install with Translator42.lha supplied	YES
	REMOTE SERVER & DRIVES
Remote server name	Name that will be seen on your computer to connect to. Warning! If you use name that incorporates "REBOOT" such as "MDR_REBOOT", then simply connecting to that site will cause the remote machine to be rebooted	MDR
Remote IP	WWW IP provided by your Internet Service Provider, the number of the machine to which you are connecting. For direct dial remote computer connections INET_DIAL automatically provides a preset IP number	195.222.74.1
Password	Password to gain access to remote site	remotepassword
Logon	Logon to gain access to remote site	remotelogon
Dial String	Number to dial for remote computer	08452120666
Drive 1,...	Name of drive on remote computer to be mounted when you have connected and gained access	SYS:
	LOCAL NETWORK DRIVES
Server name	Name that will be seen on your computer as connecting to.	HD-WORKBENCH-1
Remote IP	IP Address assigned to Server	195.222.74.1
Drive 1,...	Name of drive on remote computer to be mounted	SYS:
	PROGRAMME & MODEM CONFIGURATION
Plugin	Name of external programmes for mail,backup, etc	Automail
Programme	Location of external programme	MDR:BIN/Automail
Time	Time when programme should be launched	06:00:00
Modem configuration 1,...	Configuration string for modem. Types 1 and 2 are to set up modem as client (S0=0 do not answer). Type 3 is as server (S0=1 autoanswer). N.B. Ensure that the configuration ensures that the modem will NOT drop the line when INET_DIAL has made the initial connection. Usually this can be done by including the &D0 command (on Hayes compatible modems) in the configuration string.	AT &F &D0 S0=0
Logon message	text string to wait for from WWW Internet Service Provider (ISP) requesting login	login:
Password message	text string from ISP requesting password	password
Protocol message	text string from ISP requesting protocol	SLIP
Hello message	text string from ISP announcing hello	HELLO
O K message	text string from ISP completing login	OK
	INPUTS
Channel	Number of input channel and equivalent X-10 code	A1
Input Name	Your name to identify this input	Garden Gate
Input Protocol	Select protocol, MDR
AREXX	AREXX command to INET_DIAL to signal input (if AREXX input protocol selected)	I6ON
	OUTPUTS
Channel	Number of Output channel and equivalent X-10 code	A2
Output Name	Your name to identify this output	Central Heating
Output Protocol	Select protocol, MDR, AREXX or X-10	MDR
AREXX	AREXX [on] or [off] command to be sent out to (e.g. PALOMATV AREXX PORT) by INET_DIAL if `output' turned [on] or [off] and AREXX Output protocol selected	PALOMATV CHANNEL BBC1

...back to INDEX

SERIAL PORTS

INET_DIAL currently uses up to 3 serial ports depending on how the software is configured.

For simple Internet and Remote Connection only one serial port is used COM1: (serial.device UNIT 0).

If the control function is used with MDR protocol then a second serial port is used COM2: (serial.device UNIT 1).

If the control function is used with X-10 then a third serial port is required COM3: (serial.device UNIT 2).

A standard Amiga is provided with one serial port. If an expansion board is fitted with additional serial ports then this will normally be provided with software to `map' one port to another.

e.g. incorporate at the start of your startup-sequence (S:user-startup) mapsoftware serial.device unit 0 to expansion.device unit 1

Please refer to the manual provided with your particular expansion board.

Please note that MDR protocol includes parity checking (Even Parity). Some expansion boards do not appear to support Even Parity and this should be checked with the manufacturer.

For MIAMI users COM1: must also be configured using the MIAMI interface settings. These MUST match the INET_DIAL settings!

...back to INDEX

AMITCP with NETFS

Please ensure that you have a REGISTERED version of AMITCP installed.

AMITCP should be installed with its startup-sequence in file: sys:s/user-startup

File AMITCP:DB/INETD.CONF please add the following lines to EACH MACHINE on your local network

# NetFS, a networking support between Amigas
amiganetfs stream tcp nowait root MDR:TCPIP/netfs-server
# MDR services - required
mdrcli stream tcp dos bin - execute MDR:TCPIP/remotecli
mdrawebview stream tcp dos bin - execute MDR:TCPIP/remoteview
mdrarexx stream tcp dos bin - execute MDR:TCPIP/remotearexx prt:

File AMITCP:DB/SERVICES please add the following lines to EACH MACHINE on your local network. Please note that these numbers accord with port numbering registered by IANA (Internet Assigned Number Authority).

#Amiga NetFS
amiganetfs 2100/tcp
# MDR services
mdrcli 50093/tcp
mdrawebview 50095/tcp
mdrarexx 50096/tcp

File AMITCP:DB/INTERFACES please add the following lines

cslip0 DEV=MDR:TCPIP/rhcslip.device UNIT=0
cslip1 DEV=MDR:TCPIP/rhcslip.device UNIT=1
cslip2 DEV=MDR:TCPIP/rhcslip.device UNIT=2

...back to INDEX

MIAMI with NetFS

Please ensure that you have installed a REGISTERED version of MIAMI.
Please add the following lines to your file: sys:s/user-startup

Assign MIAMI: YOURDRIVE:Miami
Run >nil: Miami:Miami
Please configure MIAMI and be sure that it is fully operational. The modem speed should be set to the same speed as in the INET_DIAL configuration.
Recommended settings:

MIAMI option	setting	Comment
EVENTS
Events	Hide GUIs	Hide when you are sure that system is working!
Auto-online	NO
TCP/IP
Use ICMP	NO
Use DCHP	NO
Verify DNS servers	NO
Fake IP	NO
T/TCP	YES	Turn OFF if your ISP does not support this feature
Ping Flood protection	OFF
Get time	OFF	Use local time or INET_DIAL will be confused!
Dynamic	OFF
Auto-add domain	YES
Down when off-line	YES
PPP
Quick reconnect	DISABLED
Callback	NONE
Get DNS from IPCP	NO
VJC	OFF
Term req	OFF
INTERFACE
Serial Driver	PPP/CSLIP/IP
Speed		Set the same as for INET_DIAL COM1:
Serial mode	8N1	Set the same as for INET_DIAL COM1:
EOF mode	AUTO
IP type	STATIC
Multicasts	DISABLED
MTU	552
USE CD	ON
INACTIVITY	DO NOTHING
Get DNS from IPCP	OFF
WINDOWS
Always show Quit Requestor	ON

DATABASE SERVICES please ADD the following entries. Please note that these numbers accord with port numbering registered by IANA (Internet Assigned Number Authority).

TEMP	NAME	ID	PROTOCOL
	amiganetfs	2100	tcp

DATABASE INETD please ADD the following entries

TEMP SERVICE SOCKET PROTOCOL WAIT USER SERVER NAME ARGS
amiganetfs stream tcp nowait root MDR:TCPIP/netfs-server

...back to INDEX

MIAMI DeLuxe with NetFS

Please ensure that you have installed a REGISTERED version of MIAMI DeLuxe.
Please add the following lines to your file: sys:s/user-startup

Assign MIAMI: YOURDRIVE:Miami
Run >nil: Miami:Miamidx
Please configure MIAMI DeLuxe and be sure that it is fully operational. The modem speed should be set to the same speed as in the INET_DIAL configuration.
Recommended settings - these settings have been shown to work, but can be altered later once your system has been proven!:

DTR mode

MIAMI DeLuxe option	setting	Comment
EVENTS
Start Events	Hide GUI	Hide when you are sure that system is working!
Auto-online	NO
TCP/IP
Default host name	localhost
Current host name	localhost
Gateway	YES
Ping Flood protection	YES
T/TCP	YES
Allow source routing	YES
LAN-Connect
sl0 Interface	Internet
sl1 Interface	Internet
ppp0 Interface	Internet
SocksD	Disabled
IP-NAT	Disabled
Firewall	Disabled
INTERFACES
Name	sl1	Add additional serial interface definition sl1 (required)
Alias	INETDIAL
Type	(C)SLIP dial-out
Hardware	SER
Priority	10
Dialer	MDR
IP type	static
IP address	...	Your IP address
Gateway type	dynamic/fake
Gateway	blank
Priority	10	Must exceed other local interface gateway priorities
Multicasts	disabled
Multicast pri	10
Auto-connect	none
Auto-disconnect	none
Name	ppp1	Add additional serial interface definition ppp1 (optional - only required if your ISP uses PPP and you are not using ppp0 interface)
Alias	INETDIAL
Type	PPP dial-out
Hardware	SER
Priority	10
Dialer	MDR
IP type	static/dynamic	Note: Using "dynamic" currently prohibits remote control via WWW
IP address	...	Your IP address
Gateway type	dynamic/fake
Gateway	blank
Priority	10	Must exceed other local interface gateway priorities
Multicasts	disabled
Multicast pri	10
Auto-connect	none
Auto-disconnect	none
INTERFACE TCP/IP SETTINGS
Use ICMP	NO
Fake IP	NO
Priority	0
Get dynamic DNS servers	ignore
Preferred offline state	offline
Get time	NO
DHCP	disabled
INTERFACE EVENTS
Active offline	Hide GUI	Hide when you are sure your system is working
Online	Hide GUI	Hide when you are sure your system is working
Start auto-online	no
Passive offline	none
Failed on-line	none
DIALER
Dialer definition	MDR	Add dialer definition "MDR" - all entries BLANK
HARDWARE
Name	SER
Type	serial
Hardware definition
Name	SER
Type	builtin serial driver
Speed	****	Same speed setting as in INET_DIAL!
Use CD	yes
MTU	552
Modem settings
ignore	all other modem settings BLANK!
SOCKS
Enable SOCKS	NO
WINDOWS
Always show Quit Requestor	ON

DATABASE SERVICES please ADD the following entries. Please note that these numbers accord with port numbering registered by IANA (Internet Assigned Number Authority).

NAME	ID	PROTOCOL
amiganetfs	2100	tcp
mdrcli	50093	tcp
mdrawebview	50095	tcp
mdrarexx	50096	tcp

DATABASE INETD please ADD the following entries

SERVICE	SOCKET	PROTOCOL	WAIT	USER	SERVER	NAME
amiganetfs	stream	tcp	nowait	root	MDR:TCPIP/netfs-server
mdrcli	stream	tcp	dos	root	execute	MDR:TCPIP/remotecli
mdrawebview	stream	tcp	dos	root	execute	MDR:TCPIP/remoteview
mdrarexx	stream	tcp	dos	root	execute	MDR:TCPIP/remotearexx

...back to INDEX

AWEB-II

Assuming that you have a registered version of AWEB-II v3.3 installed in the assigned drive AWEB3:, AWEB-II will be automatically loaded by the file sys:s/user-startup after a reboot.

If you have the OS3.5 version of AWEB-II called AWeb3SE then, assuming that AWeb3SE has been installed on your SYS: disk in the drawer named `Internet' then add the following line to the file sys:s/user-startup.

Assign AWEB3: SYS:Internet/AWeb3SE
Please alter AWEB's Network Settings - Cache - `Home Page' to:

file://localhost/ram:mdr_aweb_input_status.html
AWEB-II is necessary for the INET_DIAL software to run. AWEB-II may be closed down, but INET_DIAL will then automatically reload AWEB-II if it deems necessary to inform the user of some event or action such as an email check. It may therefore be advisable to leave AWEB-II running.
Please set all AWEB CCTRL `localhost caching' to Disable All Caching.
Please set AWEB Browser settings `use Javascript' to ON
If you do not have APACHE installed, please set AWEB Programme settings - options - `allow shell commands in links' to ON

...back to INDEX

VOYAGER

Support for Voyager is partially included in INET_DIAL. However VOYAGER does not currently have all the functionality of AWEB-II, and therefore to use VOYAGER you also need to install and have running APACHE on your machine.
Set the Home page in VOYAGER to file://localhost/ram:mdr_aweb_input_status.html
Please note that the INET_DIAL clock (Javascript) function does not currently work with VOYAGER.
Please note that support for VOYAGER is not yet fully implemented!

...back to INDEX

IBROWSE

Support for IBROWSE is now included in INET_DIAL. However IBROWSE does not currently have all the functionality of AWEB-II and therefore to use IBROWSE you also need to install and have running APACHE on your machine.
Set the Home page in IBROWSE to file://localhost/ram:mdr_aweb_input_status.html
Please note that some window displays using IBROWSE v2.2 take a very long time to render, compared with other browsers! This is particularly the case with the INET DIAL CONFIGURATION screen. Rectification of this problem by the Developers of IBROWSE is in hand (20th August 2000).

...back to INDEX

YAM

Assuming that you have YAM installed in the assigned drive YAM:, YAM will be automatically loaded by the file sys:s/user-startup after a reboot. YAM should be preconfigured so that `GET' and `SEND' work correctly with your mail server.
Each time INET_DIAL is used to link to the WWW then AUTOMAIL is started if configured. AUTOMAIL instructs YAM to first send and then retrieve any waiting email.
If you have more than one Amiga located on your local network then AUTOMAIL can retrieve any outgoing emails from each machine and then distribute incoming emails back to the relevant computer (please note that this option is supported by AMITCP and MIAMI DeLuxe, but is not supported by MIAMI). For this to be effected, each machine must have YAM running. The file sys:s/user-startup on EACH MACHINE should have included:

RUN >NIL: YAM:YAM
To correctly distribute incoming mail the machine (`ethernethost') which connects to the WWW should have a drawer within YAM for each named person. YAM should be configured to filter incoming emails and move them to that person's drawer. The file MDR:PREFS/MDR_AUTOMAIL configures AUTOMAIL. Line one of that file is initially set as `ethernethost = your local ip', this should be changed if necessary to show the IP address of the machine that will be downloading and collecting email. The file should then include a line for each person, for example, the lines `ethernethost = 195.222.74.1' and `Giles = 195.222.74.2' would move emails from the drawer labelled `Giles' on 195.222.74.1 to the `incoming' drawer of machine 195.222.74.2. The `outgoing' drawer of machine 195.222.74.2 would also be checked for waiting outgoing mail when connecting to the WWW.

Please note that each machine on the network should have mounted a common drive "DSERVER:" where the emails are exchanged.

On `ethernethost' DSERVER: should be one of the physical drives, either named DSERVER or assigned as DSERVER. On all other machines on the network, DSERVER: should be remotely mounted using the remote drive configuration option in INET_DIAL.
Each machine on the local network can force an immediate local collection of email and email check on the WWW. Double clicking on `SEND NOW!' will start the process. SEND NOW! is stored in MDR:BIN/.

`SEND_NOW!' may be configured to show who or which machine issued the command for a Priority Mailcheck. Edit the file SEND_NOW! to include your name: e.g. `Priority_Mailcheck_Yourname' as well as the IP address of the machine which collects and sends the emails.
AUTOMAIL can be configured to automatically check for emails at set times of the day. Simply enter the times required in the general configuration.
It is important that YAM is available at all times and so YAM configuration - miscellaneous - should be set so that `close gadget iconifies programme', i.e. that YAM is always available in the background to accept incoming email, even if visually `closed down'.

...back to INDEX

BACKUP

INET_DIAL is integrated with a remote backup programme. This can automatically backup to a remote computer any files which have not previously been backed up. The file mdr:backup/mdrbackup_controlfile sets up the various source and target drawers to be searched.

Example:

#Remote SLIP connection (required if backup is to a remote rather than local network system)
Connecttype = SLIP
#Up to 10 remote drives may be mounted
#e.g. Mount5
Mount5 = REMOTEDRIVE:
#Up to 200 drawers may be copied. Source 1-200
#e.g. Source10
Source10 = sys:tools/
Target10 = remotedrive:archive/

The above example would copy previously uncopied files from the local drive SYS:Tools/ to the remote drive REMOTEDRIVE:archive/

The Backup programme is automatically started by INET_DIAL, providing a time is entered in the INET_DIAL configuration, the local drives are first searched and then communications are automatically established to the remote computer (Computer number 1 on the list of remote computers). REMOTEDRIVE: is then mounted and the files are copied. The modem is then automatically disconnected.

...back to INDEX

CONTROL

Latest Version 1.3.12 31-Jan-2000

INET_DIAL can act as a control or security manager for your House or Office.

Using MDR or X-10 protocols equipment can be instructed to turn itself on or off, or, in the case of lighting, dim. These commands can be immediate or pre-programmed.

To carry out these tasks please first install the AMIGA-APACHE WEB SERVER and GEEKS GADGETS on your computer and ADD the following lines to your sys:s/user-startup file after the startup commands for your TCPIP stack:

;BEGIN APACHE
assign APACHE: YourDrive:APACHE
assign HTTP: APACHE:
;
if exists "sys:s/delete_http_access.log"
echo "deleting HTTP Access.log"
delete "sys:s/delete_http_access.log"
if exists "http:logs/access.log"
delete "http:logs/access.log"
endif
endif
;
if exists "sys:s/delete_http_error.log"
echo "deleting HTTP Error.log"
delete "sys:s/delete_http_error.log"
if exists "http:logs/error.log"
delete "http:logs/error.log"
endif
endif
;
assign GG: YourDrive:GG
run >NIL: execute GG:sys/s/gg-startup
wait 5
run >NIL: execute apache:bin/starthttpd
echo "starting APACHE"
wait 5
;END APACHE

AREXX

With APACHE installed and configured, control can be actioned either locally on your Amiga or via any computer linked to the Local Network using a browser and HTTP.

Control can also be actioned via the Internet whilst your AMIGA is online to the Internet. For this to work your Internet connection must use a static address, otherwise a remote computer will not know how to find your AMIGA! A remote computer can control functions through your machine, assuming it knows its IP address, using most web browsers and HTTP.

INET_DIAL can also issue AREXX commands so that other functions can be activated, for example using INFRAREXX (infra red software for the AMIGA) opening up control to video recorders, tv receivers, etc..

If the control function is enabled then a control page is available both locally on your machine, via the internet, or via a `dial-in' remote computer. To turn a device on or off simply click on the relevant box. In a short time the page will update, thereby confirming that the command has been actioned. Note: In the event of a fault with the X-10 system, INET_DIAL will try up to 4 times to signal the X-10 Interface before checking for further instructions. A log file is maintained so that you can check how and when an instruction was received.

A VIDEO RECORDER (VCR) Control function is also provided. This assumes you have an infra red system (INFRAREXX) which you have separately configured. INET_DIAL will signal the VCR using the following protocol:

INET_DIAL COMMAND	EXAMPLE MESSAGE SENT TO 'INFRAREXX' AREXX PORT	COMMAND DESCRIPTION
VCR-RECORD	VID_STOP SAT_FAV SAT_2 VID_1 VID_RECORD	STOP VCR SELECT SATELLITE CHANNEL 2 SELECT VCR CHANNEL 1 START RECORDING
VCR-STOP	VID_STOP	STOP RECORDING

INET_DIAL also has an AREXX PORT MDR.1 which may be accessed for direct control of X-10 devices.

AREXX COMMAND	Description
ON.B5	Turn ON Lamp or Appliance module B5
OFF.F4	Turn OFF Lamp or Appliance module F4
DIMUP.G7.45	Dim UP Lamp module G7 by 45%
DIMDOWN.H1.30	Dim DOWN Lamp module H1 by 30%

Cable connections AMIGA DB25 plug to X-10 INTERFACE RJ11:

AMIGA DB25	DB9	X-10 RJ11
7	5	4
2	3	3
3	2	1
22	9	2

...back to INDEX

CURRENT INET_DIAL STATUS v3.7 August 2000

MDR Inet_Dial is being continuously updated and improved, click here for the latest upgrade.

date	version	comments
1st February 2000	v3.40	First general release
8th April 2000	v3.50	X-10 control included
2nd May 2000	v3.60	SAT and VCR control included. Support included for MIAMI DeLuxe.
8th May 2000	v3.63	added support for PPP and dynamic IP connections to WWW using MIAMI DeLuxe
5th July 2000	v3.68	added Login and Password protection
10th August 2000	v3.70	added support for IBROWSE

FUNCTION	AMITCP	MIAMI	MIAMI DE LUXE v1.0C	Notes
AWEB-II v3.3 Browser supported	yes	yes	yes
VOYAGER v3.2 Browser support	under test	under test	under test	Requires APACHE installed
IBROWSE v2.2 Browser supported	yes	yes	yes	Requires APACHE installed
APACHE v1.3.12 Web Server supported	yes	yes	yes
WWW Connection (client)	yes	yes	yes
Remote computer dial up (client)	yes	yes	yes
Remote computer dial in (server)	yes	yes	yes
Remote networking NetFS	yes	yes	yes
Automated mail collection from ISP	yes	yes	yes
Local network Mail redistribution and collection	yes	n/a	yes
Automated Backup to remote computer	yes	yes	yes
MDR control Protocol	yes	yes	yes
X-10 control Protocol	yes	yes	yes
Arexx Port control	yes	yes	yes
VCR control	yes	yes	yes
SAT control	yes	yes	yes
WebCam support	planned	planned	planned
Locale	planned	planned	planned

Note: "on test" means probably available in next release

...back to INDEX

ACKNOWLEDGEMENTS

All Trademarks are acknowledged

	(c)T ROSSI Thanks to *Timo Rossi* for allowing the inclusion of NetFS in this distribution and for assistance in implementation!
T Rossi

NSDI	(c)NSDI Thanks to NSDI and *Pekka Pessi* for permitting the inclusion of letnet in this distribution!

	Thanks to Joern-Erik Burkett and AMIGA-MAGAZIN for permission to use the Amiga-Apache logo
AMIGA MAGAZIN

...back to INDEX

Problems with configuration? For further assistance, INET_DIAL users please contact MDR