Novell NETWARE 6-DOCUMENTATION Manual page 2204

Specifying Hostnames and IP Addresses
Controlling Access to Your Server Using Local Database or LDAP Modes 275
SSL: Uses the client certificate to authenticate the user. If you use
this method, SSL must be turned on for the server. If you have
encryption on, you can combine basic and SSL methods.
Other: Uses a custom method you create using the access control
API.
Authentication Database: Allows you to select a database that the server
uses to authenticate users. The default setting means the server looks for
users and groups in either the local database or an LDAP directory,
depending on the setting specified in the Administration Server.
However, you can configure individual ACLs to use different databases.
You can specify different databases and LDAP directories in the file
server_root/USERDB/DBSWITCH.CONF and then choose the database
you want to use in the ACL by selecting it in the drop-down list. If you
use the access control API to use a custom database (for example, to use
an Oracle or Informix database), you can type the name of the database in
the Other field in the Users & Groups form.
You can restrict access to your Web site based on which computer the request
comes from. You specify this restriction by using wildcard patterns that match
the computers' hostnames or IP addresses.
To specify users from hostnames or IP addresses, follow the general directions
for restricting access. Restricting by hostname is more flexible than by IP
address; if a user's IP address changes, you won't have to update this list.
Restricting by IP address, however, is more reliable; if a DNS lookup fails for
a connected client, hostname restriction cannot be used.
The hostname and IP addresses should be specified with a wildcard pattern or
a comma-separated list. The wildcard notations you can use are specialized;
you can only use an asterisk (*). Also for the IP address, the asterisk must
replace an entire byte in the address. For example, 198.95.251.* is
acceptable, but 198.95.251.3* is not. When the asterisk appears within an
IP address, it must be the right-most character. For example, 198.* is
acceptable, but 198.*.251.30 is not.
For hostnames, the asterisk must also replace an entire component of the
name. For example, *.novell.com is acceptable, but
*sers.novell.com is not. When the asterisk appears in a hostname, it
must be the left-most character. For example, *.novell.com is acceptable,
but users.*.com is not.