Fire Door! Common 1.0beta1, 11 March 1996
Copyright ©1996 by Equivalence, equival@ozemail.com.au

Online Help


Getting Started

If you've just installed Fire Door, you're probably keen to get something (anything!) going!

IMPORTANT NOTE
BEFORE YOU DO ANYTHING ELSE, CHANGE THE FIRE DOOR PASSWORD AS DETAILED IN THE INSTALLATION INSTRUCTIONS. FAILURE TO DO SO MAY ALLOW SOMEONE TO CHANGE YOUR SITE CONFIGURATION.

Follow these steps to install a minimum configuration which will get you cruising the 'Web as soon as possible:
1. Make sure that the Windows/NT host on which you wish to run Fire Door has the TCP/IP procotol and Remote Access installed. Help
2. Make sure that the client machines which will be using Fire Door to access the Internet have the TCP/IP protocol installed. Help

If you are using a direct connection (i.e. not a dialup connection) to your Internet Service provider, go straight to step 5.

3. Ensure Remote Access on your Fire Door host can dial and autoconnect to your Service Provider Help
4. Add the name of the Remote Access configuration found in step 3 to the list of remote systems using the Dialup Configuration page Help
5. Find the IP address of the Domain Name Service (DNS) Name Server provided by your Internet service provider . Help
6. Add a Fire Door relay for the "name/tcp" service which connects to the name server IP address found in step 3 using the Relay Agents page. Help
7. Configure a SOCKS enabled browser (e.g. Netscape Navigator) Help
or non-SOCKS browser (Microsoft Internet Explorer) Help
8. Add security restrictions for all local clients Help

You're done!

You should now be able to run your Internet browser on any client machine and have Fire Door automatically dial your service provider.

Note that only one user at a time will be able to access this feature unless you register your copy of Fire Door.


Make sure the Fire Door host is running TCP/IP

If you have already been using your Fire Door host to access the Internet, then it you can ignore this section as TCP/IP must already be installed. You will need to know the IP number which has been assigned to this machine on the local network for later steps, so be sure to find this out.

If you are on a Unix host, then you will have TCP/IP installed. For Windows/NT you may have to install TCP/IP via the Control Panel using the Network applet. Consult your Windows/NT manuals for more information on configuring a Windows/NT TCP/IP network.


Make sure the Fire Door clients are running TCP/IP

All client machines which will be used with Fire Door will need to have the TCP/IP networking protocol installed. See the software manuals for your machines for instructions on how to do this.

When installing the client software, be sure to assign the IP address of the Fire Door host as the Domain Name Service (DNS) server. If you have another machine that is already a DNS server then that should remain the DNS server for the clients. However, the dial on demand feature may not work properly in this environment.

It is recommended that all of your client machine be allocated IP addresses on the 10.x.x.x network. These IP addresses have been specifically set aside for local networks and using them will improve the security of your network.


Making Remote Access connect and dial your ISP

If you have already been using your Fire Door host to access the Internet, then it you have probably already got this going. The only additional restriction is that the log in is automatic, that is you are not using a terminal or manually typing in usernames or passwords etc.

If the Remote Access System is not already installed on Windows/NT, you will have to install it via the Control Panel using the Network applet. Consult your Windows/NT manuals for more information on configuring a Windows/NT Remote Access System.

When setting up a Remote Access host, make sure that it can log in without user intervention. This usually involves setting up the SWITCH.INF file to script the log in sequence. If you can simply press the Dial button in the RAS Dialler program to connect to you ISP, then this will be suitable for Fire Door.


Adding the Dialup Host to Fire Door

From the
Fire Door Home Page, select on the hyperlink to the Dialup Configuration page. Click on the hyperlink in the last line of the dialup host list which has the text "Add new remote". A Dialup Host Parameters page will appear. Select the name of Remote Access entry you wish to use to connect to your service provider in the field labelled "Name:". The rest of the parameters can be left at their default values.

Press the button labelled "Accept", and a new page will be displayed confirming that the new configuration has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.

See also Help on Dialup Parameters


Finding the IP number of your ISP name server

To find the IP number of the name server provided by your Internet Service Provider, try asking your office 'Net guru. If that person doesn't know (or you are the office net guru and you don't know!), your service provider will be able to supply it.

Adding a name server (DNS) relay

From the
Fire Door Home Page, select on the hyperlink to the Relay Agents page and go to the Add Relay Agent form. In the field labelled "New relay service", enter the text "name/tcp". In the field labelled "New relay destination", enter the IP number of the name server provided by your Internet Service Provider.

Press the button labelled "Accept", and a new page will be displayed confirming that the new relay has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.

NOTE - you should not install a DNS relay agent if your Fire Door host is already running a DNS server.

See also Relay Agent Help.


Configuring a SOCKS client (for Netscape Navigator and other SOCKS enabled browsers)

This section will describe how to configure Netscape Navigator to use the SOCKS protocol. Other browsers should require similar procedures

Select "Options" from the Netscape Navigator menubar, and then select the "Network Preferences" item. A tabbed dialog box will then appear. Select the "Proxies" tab.

On the 'Proxies" dialog, make sure then "Manual Proxy Configuration" radio button is set, and then select the "View..." button. In the field labelled "SOCKS host", type the IP number of the Fire Door host. In the adjacent "Port" field, enter the value "1080".

Press the "Ok" button to dismiss the "Proxies" dialog, and then the "Ok" button to dismiss the "Network Preferences" dialog.

You may use the name of the Fire Door host instead of the IP number, but only if that name is in the clients local hosts file. If this is not the case then the system will attempt a DNS look up, resulting in a superfluous dial up of the ISP to consult its DNS server, which will not know that name!

See also Relay Agent Help and Relays for World Wide Web clients


Add a "www/tcp" relay (for Microsoft Internet Explorer and other non-SOCKS enabled browsers)

From the
Fire Door Home Page, select on the hyperlink to the Relay Agents page and go to the Add Relay Agent form. In the field labelled "New relay service", enter the text "www/tcp". In the field labelled "New relay destination", enter the IP number of the Web server or proxy server provided by your Internet service provider.

Press the button labelled "Accept", and a new page will be displayed confirming that the new relay has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.

If the system refuses to accept the www/tcp service name you can either use 80/tcp instead or edit you services file (eg C:\WINNT\SYSTEM32\DRIVER\ETC\SERVICES) and add the www service name to it, setting it to the value 80.

See also Relay Agent Help and Relays for World Wide Web clients


Add security restrictions for all local clients

To preserve the security of your local network, you should add Access Restrictions for all local clients which will be using Fire Door to prevent unwanted access to your local machines. Leaving the Access Restrictions list empty will allow any machine to use your Fire Door gateway, including machines not on your local network when you are connected to the Internet.

If you have used the recommended practice of allocating IP addresses in the 10.x.x.x address space for your clients, then you will need to add a single access restriction of the form:

10.255.255.255  :  255.255.255.255
If you have assigned other IP addresses, then you will need to add explicit restrictions for each client address.

From the Fire Door Home Page, select on the hyperlink to the Security page and go to the Add New Access Restriction form. In the field labelled "Originator", enter the IP address of client, or a wildcard specification specifying multiple clients. In the field labelled "Destination", enter the wildcard value "255.255.255.255" to allow access to all Internet addresses, or any other IP address to the restrict access to that particular host (for example, your service provider proxy server).

Press the button labelled "Accept", and a new page will be displayed confirming that the Access Restriction has been added. Use the "Back" button on your browser to return to the Security page and confirm that the new retriction has been added to the Restriction List.

See also Security Help