Installation Guide FreeBSD 2, BSDI 2.1

# System Requirements FreeBSD 2.X, BSDI 2.1

### OPERATING SYSTEMS

UNIX

FreeBSD 2.X or BSDI 2.1

WIN95/WINDOWS/DOS

WIN95,NT,WINDOWS 3.1, WINDOWS FOR WORKGROUPS 3.1. MS-DOS 5.0, 6.2 ,

NETWARE

NOVELL NetWare 3.11, 3.12, 4.1

VLM VER 1.2 rev A or NETX.COM VER 3.33 or later

LSL.COM VER v2.16 04/17/95 or later

IPXODI.COM VER v3.01 104/17/95 or later.

Note: DOS, WINDOWS and WINDOWS FOR WORKGROUPS require NetWare 4.1 Client VLMs 1.20 Rev A. The entire Client Kit can be Downloaded from NOVFILES or from Novell's FTP site or netwire.novell.com. For Windows 95 you must use the Novell 32 Bit client for Windows 95.

### MEMORY

16MB Minimum, Recommended 32MB or 1MB per network user client. Memory must be sufficient to prevent swapping.

### DISK SPACE

6 MB (2MB Software, plus Documentation). 500MB Recommended for entire O/S installation

### HARDWARE

Standard X86 ISA,EISA,VL,PCI 386/486/Pentium. With CDROM, 3.5" FDD, US Robotics v.34 modem.

### LAN ADAPTERS UNIX

SMC/WD, NE2000 and Compatible clones, Intel EtherExpress Ethernet adapter. Other adapters may work but have not been tested.

### LAN ADAPTERS DOS

Any Ethernet adapter supporting Novell ODI or Microsoft NDIS interface.

# Installation Information

For Stand-alone NetCon installations (NO NOVELL SERVER) go to "Installing NetCon FreeBSD 2.1"

> 1. Verify that NetWare is running on an Ethernet network, that the UNIX systems network card is installed, properly configured and running with TCP/IP and connected to the same physical network as the NetWare server.

> 2. From a DOS client, login to the Netware server as "supervisor" and execute "syscon", select "Supervisors Options", "Edit System Autoexec File", the file will display and should resemble the following example.

     SYSCON  3.62               Thursday  April 6, 1995  9:52 am
              User SUPERVISOR On File Server KALI

                     System AUTOEXEC File

    file server name KALI
    ipx internal net 4
    load c:\wdplussv port=380 mem=d0000 int=5 frame=ethernet_II
    bind ipx wdplussv net=1
    load c:\token port=a20 mem=d8000 mem1=cc000 int2
    bind ipx token net=2

Figure 1, Typical Netware 3.11 AUTOEXEC.NCF file, showing the server name "KALI", TYPE II Ethernet on network "1".

> From this file you need to determine the following information.

> Type Of Network [802.3, Ethernet TYPE II or Token-Ring].

> Find the line that starts with "load DRIVER_NAME" for the card to which you will be attaching the UNIX system to. If the end of that line contains "frame=ethernet_II" you have an Ethernet TYPE II network otherwise it is a Novell standard 802.3 or Token-Ring if you are using a Token-Ring card.

> Network type [Ethernet TYPE II] [802.3] [Token-Ring]

Note: If TCP/IP is running anywhere on the network the network must be configured for TYPE II Ethernet. See the NetWare documentation for complete details on changing from 803.3 to TYPE II Ethernet or refer to the "Changing Network type to TYPE II Ethernet" in the Trouble Shooting Guide.

# Installing NetCon FreeBSD 2.X, BSDI 2.1

NOTE: If NetCon is already installed see the section "Removing NetCon" later in this manual to completely remove NetCon before installing a NEW version.

> 1. Login as root. Verify that the "/usr" directory is accessible and that the network adapter is installed with TCP/IP and both are fully operational.

> 2. Copy or download the distribution file bsd60.tgz or bsdi60.tar to temporary directory or change directory to the CDROM or other location containing the distribution file.

FreeBSD

> # pkg_add bsd60.tgz (Return)

BSDI 2.1

> # cd /

> # tar xvf /tmp/bsdi60.tar

> # /tmp/ncinstall

The "/tmp/ncinstall" script calls "installsw" which will display the installation progress and the Following dialog.

    Installing NetCon 6.0 Client and Server for BSDI... (package 1 of 1).........
    Uncompressing files...
    Updating System  files...
    Backing up kernel and boot files...

    Enter NOVELL Network type;[Std 802.3, TYPEII Ethernet 8137, Token-Ring]
    Enter s for Std 802.3, e for Ethernet TypeII 8137, t for Token-Ring >>

Enter the correct network type [s, e, t]

    Enter the Network DRIVER you wish to use with NetConLT
         ne0  -  First NE2000 network card @ 360.
         we0  -  First SMC network card @ 280,5,d0000 [Default].
         ex0  -  First Intel EtherExpress network card @ 260
    Default [we0]

Enter the correct Driver.

    Is this a STANDALONE NetCon server (No other NetWare Servers on NetWork)
    [Y/N] Default [N]:

If this is the only NetWare server on the network enter Y otherwise N.

The following is only displayed if you DO NOT have a standalone system. This information is used as an example of how to auto-mount the NetWare server during boot. It is also used to obtain access control information such as group membership.

    Enter NetWare Server's Name (IN CAPS):

NW312

Enter the name of the NetWare server you wish to mount.

    Enter NetWare Server's Volume to mount[SYS] (IN CAPS):

SYS

Enter the Volume on the NetWare server you wish to mount.

    Enter NetWare Server's Directory to mount[/]:

/

Enter The NetWare server's subdirectory to mount.

    Enter Unix Directory to mount NetWare[/netware]:

/netware

Enter the Unix driectory mount point.

    Enter NetWare Server's Supervisor Password(IN CAPS):

Enter the NetWare Server's Supervisor Password of the example mount.

    extracting NetCon6.0 man pages....
    extracting NetCon6.0 winsock.dll and Applications....
    cd libsmsa; make
    cc -c -DSTANDALONE -DAT386 `-DDEFAULTBOOT="/bsd"' -O -I../.. -I. -I.. -DLOWMEM=0x4000 -DBOOTREL=0x1F0000 boot.c
    cd libsa; make
    cd libunzip; make
    ld -e __start -N -T 1F0000 -o boot relsrt0.o boot.o libsa/libsa.a libunzip/libunzip.a
    test -d //usr/bootstraps || mkdir -p //usr/bootstraps
    test -d //stand || mkdir -p //stand
    install -c -s boot /
    cp wdboot bootwd biosboot fdboot fdboot.debug fd5boot  bootfd bootfd.debug ahaboot bootaha eahaboot booteaha bootbios //usr/bootstraps
    cp boot cat copy ls //stand

If this is a BINARY version of BSDI (no source code) then a new kernel and boot file will be copied to the root directory ("/bsd and /boot) the original file will be backed up to "/bsd.org" and "/boot.org". If source code is included you will be prompted to rebuild the kernel.

    Enter the of the Kernel configuration to use as a model to build a new NetCon Kernel;[GENERIC]
    GENERIC

If you have created a custom configuration file for the bsdi kernel enter the name of that file othewise use the default [GENERIC]

    Do you want to rebuild and install a kernel now? (y/n);[y]
    y

You Must rebuild the Kernel to make NetCon operational.

    Before the NetCon software can become operational you MUST;.
    1) Reboot the system and brand the software with netcbrand.
    2) Reboot the system again after branding the software.
    Installation complete, Thank you for using NetCon!

    All packages were installed successfully.

FreeBSD

The "pkg_add" utility will display the Following dialog.

    Uncompressing files...
    Updating System  files...

    Select your Novell Network type

(*) e Ethernet TYPEII Novell type 8137.

( ) s Standard Novell 802.3.

( ) t Token-Ring or 802.2.

Enter the correct network type [s, e, t]

    Is this the First and Only NetWare server on your NetWork

(*) N No there are other Novell NetWare servers on my network.

() Y Yes this is the First and only NetWare server on my network.

If this is the only NetWare server on the network enter Y otherwise N.

The following is only displayed if you DO NOT have a standalone system. This information is used as an example of how to auto-mount the NetWare server during boot.

    Enter NetWare Server's Name (IN CAPS):

NW312

Enter the name of the NetWare server you wish to mount.

    Enter NetWare Server's Volume to mount[SYS] (IN CAPS):

SYS

Enter the Volume on the NetWare server you wish to mount.

    Enter NetWare Server's Directory to mount[/]:

/

Enter The NetWare server's subdirectory to mount.

    Enter Unix Directory to mount NetWare[/netware]:

/netware

Enter the Unix driectory mount point.

    Enter NetWare Server's Supervisor Password(IN CAPS):

Enter the NetWare Server's Supervisor Password of the example mount.

    Enter the Kernel configuration to use as a model to build a new NetCon Kernel
    [GENERIC]

If you have a custom kernel configuration file enter that name otherwise use [GENERIC]

    Do you want to rebuild and install a NEW NETCON kernel now? (y/n)

y

You Must rebuild the Kernel to make NetCon operational.

    Before the NetCon software can become operational you MUST;.
    1) Reboot the system and brand the software with netcbrand.
    2) Reboot the system again after branding the software.
    Installation complete, Thank you for using NetCon!

                          RESTRICTED RIGHTS LEGEND

      Use,  duplication, or disclosure by the Government is subject  to   restrictions as set forth in subdivision (b)(3)(ii) of the Rights  in Technical Data and Computer Software clause at 252.227-7013.
            Copyright (c) 1986, 1996 NetCon Corporation                                            NetCon Corporation
              2435 Trapp Avenue                                                                           Miami, Fl 33133

    All rights reserved. This product and related documentation is protected by copyright and/or U.S. Patents issued and pending and is distributed under licenses restricting its use, copying, distribution and decompliation.

> 3. Reboot the system to start NetCon.

# reboot

> 4. After the reboot you should see the following display before or right after the login: prompt:

> New IPX Address: ed1 AF=6 <net:XXXXXXXX, host:XX-XX-XX-XX-XX-XX, port:0>

> Verify that the "net" matches the network address of your Netware Server. If this is a stand-alone system with no other NetWare server the Net address will be "1".

> Make a note of the "host:" and use it to obtain your activation key from your NetCon supplier or NetCon web site "www.netcon.com". Once you have obtained your Activation Key, login as "root" and use;

# netcbrand Activation_Key (Return)

> to brand the programs. To verify that netcbrand has properly branded all the NetCon software packages type the following;

# netcbrand (Return)

> You should see the following display; The number of connections and the branding of "nclogin.exe" will depend on the type of license you have obtained.

`netcvt: SkAKIWgmKNDFGNDN (SCV active). 255 conns. Perm. L=Y`

Address verified.

netcserv: SkAKIWgmKNDFGNDN (SCV active). 255 conns. Perm. L=Y

Address verified.

netcpass: SkAKIWgmKNDFGNDN (SCV active). 255 conns. Perm. L=Y

Address verified.

netcmount: SkAKIWgmKNDFGNDN (SCV active). 255 conns. Perm. L=Y

Address verified.

nclogin.exe: verified.

> and reboot. After the second reboot NetCon should be fully operational. If this is a standalone system with no other NetWare or NetCon servers on the network the installation is now complete.

> If you have other NetWare or NetCon servers on the network go to "Completing the NetCon Installation" for information on how to to add the default passwords, additional users and mount points etc...

# Completing the NetCon Installation

> To complete the installation of Netcon you must add the default user passwords and any mount points you wish to use with the NetCon Client.

### Adding Default Passwords NetCon Client

In this release of NetCon the NeCon menu utility is not available. Therefore the password mapping is in the "/usr/lib/netcon/netcpasswd" file.

Default example entries were added during installation. To add additional servers, users or groups edit the "/usr/lib/netcon/netcpasswd" file and add the entries, use the example as a guide. You must have defaultentries for each NetWare server you wish to connect to, either for printing or file services. Each server must have a default user and group entry and a optional world entry. The default user must be root/ supervisor in order to mount the NetWare volume or print to the printer.

Example: "/usr/lib/netcon/netcpasswd" file.

`#`

# netcpasswd file used by /usr/bin/netcpass daemon

# NW-srv is the name of the Novell NetWare Server.

# NW-Login-name => is the Netware Login Name on the Netware Server

# NW-Passwd=> is the password on the Server (a `-' says no passwd)

# unix-username=> is the unix login name of the user

# type = either `user', `group' or `world'

# The flags field contains:

# `default' for the default machine name login

# An Entry with flags of default is required.

#

#

#[<UPPER CASE ONLY>]

# NW-srv NW-Login-name NW-passwd unix-name type flags

#

NETWARE SUPERVISOR PASS root user default

NETWARE EVERYONE - wheel group default

NETWARE OTHER - nobody world

NOTE: You may mount a NetWare server volume as any Unix user and use any NetWare valid users login and password provided that the NetWare user has a valid password and is a trustee on the volume you wish to mount.

### Mapping a DOS Drive To A NetCon Server for the First Time.

> To map a DOS drive to a NetCon Server: First re-boot the DOS P/C and login to the NetWare server. At the DOS prompt enter the map command:

Example:

C:> map k:=netcon/sys:\

Enter user name for server NETCON: root

Enter password for user ROOT on server NETCON: xxxxxx

Your station is attached to server NETCON:

DRIVE K: = NETCON\SYS: \

C:>

> In the above example the DOS drive K: was mapped to the NetCon server called NETCON, SYS: volume. The DOS user logged into the NetCon server as the Unix user root with the root password. The password is automatically added to the NetCon BINDERY as a NetWare encrypted password the first time the user logs in. These passwords can be maintained with the "netcpasswd" command. See the "System Administration" sections of the NetCon Manual for complete details.

# DOS/WINDOWS Client Installation

If this is not a Stand-alone installation you need only verify that you are running the ODI driver and Shell versions specified in the "System Requirements" section of this manual. ODI Drivers may be obtained from your NetWare supplier, CompuServe (NOVLIB or MSKB), network card supplier, or NetCon supplier. You can continue to use the standard NetWare commands to access the file and print services of NetCon.

For Standalone installations.

> 1. Copy the ODI driver set to the boot directory of your hard disk usually "C:\". The ODI driver set consists of the following files "LSL.COM", "IPXODI.COM", "NETX.COM" "VLM.COM", "NET.CFG" and your network card driver. Edit the "NET.CFG" file and enter the correct driver configuration parameters and frame type, if you are using VLM's enter the first drive letter also.

> 2. Edit your "CONFIG.SYS" file and add the following line.

For NETX.

         LASTDIRVE=I

For VLM's.

         LASTDIRVE=Z

> We recommend the "LASTDRIVE" be set to "I" to avoid any possible future conflicts with other network operating systems. You may set "LASTDRIVE" to any drive that is greater than your last local drive. The next drive after "LASTDRIVE" will be your NetCon login drive if you are using VLM's the "First Network Drive" in the "NET.CFG" file will be your login drive.

    3.      Edit your start-up file "AUTOEXEC.BAT" and add the following lines.      LSL
              NE2000
              IPXODI
              NETX or VLM
              J:
              NCLOGIN

Also add "J:\PUBLIC" to your PATH variable.

> In the above example we are using "I" as our "LASTDRIVE" and an "NE2000" card driver. Replace the "J" and "NE2000" with your next drive after "LASTDRIVE" and card driver.

> 4. Modify or create the "NET.CFG" file and add the correct configuration values for your network card. Follow the card manufacturers recommendations.

# WIN95 and Windows 3.1

NetCon supports Windows 95 when used with Novell NetWare 32 Bit Client for Windows 95.

After the installation of the 32 Bit NetWare client is complete, you now can use "NetWare Login" or the "Windows Explorer to login to NetCon, map drives and capture printers from within Windows.

# Installing Winsock.dll for WIN95/Windows3.1/NT

NetCon provides a unique PATENTED proxy winsock.dll/wsock32.dll for IPX/SPX protocols. What this means is that you can run any Windows TCP/IP application that conforms to the Windows Socket specification version 1.1 without adding TCP/IP or assigning an IP address to each workstations.

How this works; NetCon provides a simple Windows utility "SPINSOCK.EXE" that connects the NetCon "winsock.dll" to the NetCon server using SPX protocols. Once the connection is made, any SOCKET requests that are issued by a Windows TCP/IP application will be transferred to the NetCon server for execution. The NetCon server then executes the request in a multi-threaded UNIX environment where SOCKETs and TCP/IP are native. The results are then returned to the Windows application over SPX.

The NetCon winsock.dll/wsock32.dll, winsock.ini, spinsock.exe and sample application programs and files are in the spinsock.tar file or the "/sys/public/spinsock" directory on the NetCon server. Map a drive on the Windows machine to the NetCon server and run setup.exe. If you don't find the spinsock.tar file or the /sys/public/spinsock directory you may download the file for our web/ftp site www.netcon.com or ftp netcon.com the file is /pub/netcon6.0/spinsock.tar

Example:

On Unix Extract the "spinsock.tar" file into /sys/public/spinsock directory if it is not already there.

         # mkdir /sys/public/spinsock
         # cd /sys/public/spinsock
         # tar xvf /tmp/spinsock.tar

From Windows

         map j:=netcon/sys:\
         or Use the Window 95 Explorer

From Windows Run

          j:\public\spinsock\setup.exe

The setup program will setup a new program group with both the 16 bit and 32bit versions of winsock.dll/wsock32.dll.

Setup will also prompt you for the NetCon server name; This is the name of the NetCon Proxy server you want to connect to. Additionally you will be asked if you to Auto-start Spinsock for Windows 3.1. You should answer [Y] Yes, this will add spinsock.exe to the Windows 3.1 "Startup.grp" Startup group. Every time Windows 3.1 starts, spinsock.exe will connect to the NetCon server. You can add or remove Spinsock.exe from the startup program group at any time to turn on or off the Auto-start. Windows 95 will Auto-start and Connect to the NetCon server the first time an application loads NetCon's wsock32.dll the startup.grp entry is not necessary on Windows 95.

Most of the applications provided with NetCon Spinsock are pre-configured. They are ready for use after SPinsock has been installed, and a successful connection to the NetCon Proxy server has been established.

Before you can use any of the applications, a connection must be established with your NetCon SPinsock Proxy server.

The following application requires some user configuration before use:

Pegasus email

# CONNECTING TO THE NeCon PROXY SERVER

To establish a connection and login to the NetCon Proxy server:

1. During setup.exe if you entered the correct NetCon server name and anwsered [Y] to the AutoStart prompt NetCon Spinsock should connect the the NetCon server every time Windows starts. On Windows 95 the connection will be established the first time an application loads NetCon wsock32.dll. To start the Connection manually, Load the SPinsock application by double-clicking on the SPinsock icon in the SPinsock Program Group.

Windows 95 NOTE: Use SPsock32 instead, to edit Connection information as described in the next step.

2. Review or edit the Proxy server Connection information by selecting the File menu, Edit Connection Info.

This is the information you entered during SPinsock installation. It is saved in the SPINSOCK.INI file in your windows directory.

3. To connect to the Proxy server, select the Connection menu, Connect.

If the connection is successful, SPinsock will minimize and display its icon at the bottom of your screen. You may now start any of your internet applications.

Windows 95 NOTES: It is not necessary to make a connection first with SPsock32. You may simply start your 32-bit application alone.

IMPORTANT:

The WSOCK32.DLL file installed in your SPinsock directory, (C:/SPINSOCK by default) must be in the SAME directory as your 32-bit application.

4. When finished working over the network, restore the SPinsock program by double-clicking its minimized icon at the bottom of the screen.

5. Select the Connection menu, Disconnect. This disconnects you from the NetCon Proxy server. Then select the File menu, Exit.

CONFIGURING PEGASUS MAIL FOR USE

The initial required user configuration steps for PEGASUS MAIL are as follows:

Open the Pegasus Mail application by double-clicking on the Pmail icon in the SPinsock Program Group, then perform the following steps:

1. Select the first choice: configure for one person.

2. Select the default directory path presented to you for your user mailbox. You may change the directory if you prefer, but it must be different than the Pmail install directory.

3. Select the File menu, Preferences, Advanced Settings; then check ALWAYS load the winsock.dll. Click OK.

4. Select the File menu, Exit.

5. Re-start the Pmail application as before.

6. Select the File menu, Network Configuration.

7. On the Network Configuration screen,

Fill in the following four fields with your email server information:

Relay host: This is your SMTP server.

Host: Your POP server.

(May be the same as SMTP server.)

User: Your POP server login name.

Password: Your POP server password.

After entering this information, select OK.

The Pegasus Mail package should now be ready for sending and receiving mail. See your system administrator for the server information needed above.

We have tested the following application;

NCSA Mosaic 2.0.0

NetScape Browser (All)

Word Internet Assistant

StartNet's Micro X-Win

The Following application are also reported to work, other winsock applications should also work. Please report any problems with application to NetCon support.

FTP

WS_FTP

IRC

IRCII 2.6 for Windows

IRC4WIN

Telnet

yawtel

Microsoft Telnet

EWAN

Mail

Eudora

News

winvn

X-Windows

StarNet Micro-X (Also known as xwindemo)

# Using a WEB Browser with NetCon

To use any WEB Browser with NetCon you must first connect to the NetCon server with "SPINSOCK.EXE" see the previous section for details. Once the connection is made, just start the Browser program and it should function normally. NetCon has tested and supports the NetScape, NCSA Mosaic and Word Internet assistant Browsers.

# Using X Windows with NetCon

To use StarNet Micro X-WIN or other X Windows servers supporting the winsock.dll specification you must first connect to the NetCon server with the SPINSOCK.EXE program see previous section. Once the connection is made then you must add a port re-mapping file to your home directory on the NetCon server.

Example:

    Unix file "/usr/tony/.spinsock"
    [Mappings]
    6000=6007,6019

The above example is for UNIX user "tony" whose home directory is "/usr/tony", the entry maps the X Window port 6000 to 6007 through 6019. In other words DISPLAY "0" is now mapped to DISPLAY "7"

    The next step is to configure the X Windows program to connect to the NetCon server. The following example is for StarNet Micro X-Win but the general principals are the same for any X Windows program and they are;

1.) There is no need to set the HOST name or address for the PC as it will use the NetCon server IP address and name.

2.) You should use the remote execution daemon "rexec".

3.) On Sun systems you should execute "/usr/openwin/bin/xterm"

4.) Your DISPLAY name will be NetCon server name:DISPLAY Number set in the port Mapping step in the previous paragraph, "netcon:7"

Example: StarNet Micro X-WIN

Start X-Win select Sessions, Edit Sessions, New Session,

Session Name: NetCon

rexec

Host Name: netcon

Login: tony

Command:/usr/openwin/bin/xterm -ls -display netcon:7 &

In this example the NetCon server name is "netcon" the user name is "tony" and the command will use the remote execution services of the NetCon server to execute the "xterm" program and display it on DISPLAY "netcon:7"

If you wish to use OLWM (Sun's OPEN LOOK Window Manager) not Window as your X Windows manger select Options, Window Mode, Single Window Mode and make sure Enable screen :0.1 is NOT selected.

Example: C:\WINDOWS\MXWIN.INI

    [MicroX]
    SaveUnder=no
    directory=C:\XWIN\LIB
    panning=1
    screen1enable=0
    debug=0
    network=winsock
    single=1
    width=632
    height=452

    [font]
    fontpath=D:\XWIN\LIB\FONTS\MISC,D:\XWIN\LIB\FONTS\75DPI

    [sessions]
    XDMCP -broadcast=4
    XDMCP - query=4:192.1.1.1
    netcon=2:netcon:tony::/usr/openwin/bin/xterm -ls  -display netcon:7 &

### Adding Additional mount point

To add an additional mount point that will automatically mount a NetWare server a boot time, you must edit the "/usr/local/bin/netcon.rc" NetCon start-up file, and add a line similar to the following example.

Example:

    ###mount
         /usr/bin/netcmount NETWARE:SYS:/ /netware

In the above example the NetWare Server "NETWARE" "SYS" volume, "/" root directory is mount to the Unix directory "/netware".

### Command line Utilities

The Following command line utilities have been added to this distribution to replace some of the functionality of the "netcon menu utility" which is not available on this platform.

Example: To list NetWare servers

# netcslist

To list Groups.

# netcglist

To list users.

# netculist

To list routing gateways.

# netcgwlist

To list print queues.

# netcpqlist

To list statistical information.

# netstat -i

# Installation Notes

During the installation, the following changes were made;

> /usr/local/lib/netcon/netcexport

> a. The following volumes are exported to be mapped by DOS or other NetCon Clients.

Volume Name Unix Directory

SYS = /usr/local/sys

vol1 = /

vol2 = /usr

> (ie. install creates the '/sys' directory and assigns it to volume "SYS").

> /usr/bin/netcon.rc

> a. The network interfaces are configured.

> /etc/rc.local.

> a. Commands to start and stop NetCon client and server.

> /usr/src/sys/sys/vnode.h

> /usr/src/sys/sys/mount.h

> /usr/include/sys/vnode.h

> /usr/include/sys/mount.h

> /usr/src/sys/conf/files

> /sys/i386/conf/NETCON

> /usr/src/sys/kern/vfs_conf.c

> /usr/src/sys/kern/vfs_subr.c

> /usr/src/sys/i386/stand/Makefile

> a. The files were modified to add the NetCon IPX/SPX protocol stack and TFS NetWare Compatible vfs caching file system to the kernel. The original files were copied the file_name.org they will be restored with pkg_delete.

During start-up NetCon's auto-configuration utility automatically configures the network, sets up default users for each server it finds on the network and configures each UNIX printer as a NetWare print queue and print server, for access by DOS or Other NetCon Clients. See the Users Guide for complete information on using the printers.

Stand-alone installations will have all the DOS executable files copied to:

/sys/public

/sys/login

# Starting NetCon Services

The NetCon Network Services are started and stopped automatically during boot and shutdown of the UNIX system.

The following Shell script is used to start NetCon

`/usr/bin/netcon.rc start`

The following Shell script is used to stop NetCon

`/usr/bin/netcon.rc stop`

NOTE: You SHOULD NOT START and STOP NetCon manually it should be loaded and started at boot time this is to keep the kernel server/user tables and network addressing in sysnc.

The following commands are executed by this script to start the Network Client Services:

/sbin/ifconfig (configure the network driver for IPX/SPX and network type).

/sbin/route (Maintains the IPX/SPX network routing tables).

netcpass (User and password mapping daemon).

netcmount (Mounts Network directories).

The following daemons, provide the Network File, Print and Terminal Server Services:

netcvt (SPX MultiScreen terminal/Proxy server).

netcserv (NetCon SuperServer File Print Sap Rip servers ).

When FreeBSD boots NetCon utilizes the following standard FreeBSD MACROS.

DOMAIN_SET(ns) (Add IPX/SPX address family NS 6 (Xerox Network System) to the domain switch tables.

VFS_SET(TFS_vfs_vfsops) (Add TFS vfs file system to vfs switch table).

VNODEOP_SET(TFS_vnodeop_opv_desc) (Add TFS vnode operations to vnodeop switch table)

# Removing NetCon

To completely remove NetCon login as root and reboot the system into single user mode. Or if you like you can unmount any mounted NetWare servers and use "netcon.rc stop" to shut down NetCon. (Failure to unmount a NetWare server before removing NetCon may cause a "panic").

FreeBSD

         # pkg_delete NetCon6.0

BSDI

         # installsw -L -D -m floppy -c /usr/netcon

Ignore any errors.

# Distribution

The following files are included in this distribution of NetCon 6.0 :

File Name Description

/usr/local/bin/netcvt MultiScreen terminal/Proxy server

/usr/local/bin/netcprint Network print utility

/usr/local/bin/netcmount Network mount utility

/usr/local/bin/netcpass User/Group password daemon

/usr/local/bin/netcserv SuperServer file, print, sap, rip

/usr/local/bin/netcon.rc NetCon start-up file

/usr/local/bin/netcrestart Restarts netcserv

/usr/local/lib/netcon/netcexport Volume export file

/usr/local/lib/netcon/ncterm.exe DOS terminal emulator

/usr/local/lib/netcon/setcolor.exe DOS setcolor for ncterm.exe

/usr/local/lib/netcon/nclogin.exe DOS login utility.

/usr/local/lib/netcon/ncmap.exe DOS drive mapper.

/usr/local/lib/netcon/ncslist.exe DOS server listing.

/usr/local/lib/netcon/ncapture.exe DOS printing redirector.

/usr/local/lib/netcon/nclogout.exe DOS logout utility.

/usr/local/lib/netcon/ncterm.pif WINDOWS pif file for ncterm.

/usr/local/lib/netcon/ncterm.ico WINDOWS icon for ncterm.

/usr/local/lib/netcon/keymap Example setkey for ncterm.

/usr/local/lib/netcon/ncpr Network printer setup script

/sys/netns/NETCON.o NetCon kernel module IPX/TFS.

/usr/local/bin/rmnetcon NetCon removal utility

/usr/local/bin/netcslist Network object listing utility

/usr/local/lib/netcon/netcpasswd Unix to Netware password mapping file

/usr/local/lib/netcon/printd.bsd NetWare spooler examples

/usr/local/bin/netchost Proxy Server

/usr/local/bin/netcpatch Running Kernel patch utility for debugging.

/usr/local/bin/netcps Lists running NetCon processes.

# Setting Up Internet Access Control

### Introduction

NetCon provides a rules based Internet access control system to ALLOW or DENY access to the Internet for NetWare Users and Groups. When a workstation connects to the NetCon server the NetWare User information is transfered to the NetCon server program "netchost". The server program then obtains other User information from the NetWare Bindery/NDS such as Group membership. Every time the workstation attempts to Connect to a Internet site the Access control system searches two databases. The first is the ALLOW database "/usr/local/lib/netcon/netchosts.allow" then the DENY database is searched "/usr/local/lib/netcon/netchosts.deny". The databases are searched by PROTOCOL/SERVICE (as in "/etc/services") if the NetWare User name, Group Names, Internet Address or Host Name match an entry in the databases then access will be ALLOWed or DENied depending on which database the entry is found in.

### RULES

> If no databases exist access is granted.

> ALLOW database is searched first, if a match is found access is granted.

DENY database is searched after ALLOW, if a match is found access is denied.

Databases are searched by PROTOCOL/SERVICE. The PROTOCOL/SERVICE name must be the same as found in "/etc/services". The PROTOCOL/SERVICE name must match the name of the service, which is the first name on each line in the "/etc/services" file.

PROTOCOL/SERVICE name must be the first item on each new line, followed by a ":" ie "ftp:" or "http:".

NetWare Users and Group names should be UPPERCASE.

Internet Address should be in ip address dotted format ie: "204.7.133.2".

Host names should be lower case ie: "netcon.com".

### Configuration

To configure NetCon Access Control;

1.) Verify the a valid entry exist in the password mapping file for the NetWare server or servers that the workstation(s) are logged into.

File; "/usr/lib/netcon/netcpasswd"

Example:

    NETWARE SUPERVISOR PASSWORD root user default
    NETWARE EVERYONE      -     wheel group default

In the example server NETWARE user SUPERVISOR is mapped to UNIX user root and is the default, NetWare group EVERYONE is mapped to UNIX group wheel and is the default. Each NetWare server that workstation(s) login to must have at least a default user and group mapped before group lookups can occure.

2.) If you want to check NetWare Groups the "netchost" daemon must be started with the "-g" groups option. Edit the "/usr/local/bin/netcon.rc file and add the "-g" option to the "netchost" startup line. You may also kill and restart "netchost -g" from the command line as root.

Example:

    (sleep 3;/usr/local/bin/netchost -g > /dev/null 2>&1) &

3.) Create the database file and add the correct entries.

ALLOW database "/usr/local/lib/netcon/netchosts.allow"

DENY database "/usr/local/lib/netcon/netchosts.deny"

Example: "/usr/local/lib/netcon/netchosts.deny"

ALL:ALL This denies all protocols/services to all users and groups unless permitted access by entries in the allow file.

http:EVERYONE This denies NetWare group EVERYONT access to ALL http sites.

Example: "/usr/local/lib/netcon/netchosts.allow"

ALL:TONY DEVELOPMENT This give NetWare user TONY and group DEVELOPMENT access to everything.

http:netcon.com 205.7.133.25 This allows access to netcon.com and 205.7.133.5 to all users.

### Known Problems with this release