proxy(1M)

Requires Optional LAN/X.25 Software

NAME

proxy − manipulates the NS Probe proxy table

SYNOPSIS

proxy on

proxy off

proxy add nodename domain ip_address medium

proxy append nodename domain ip_address medium

proxy delete nodename

proxy show nodename

proxy flush

proxy list

DESCRIPTION

proxy enables or disables Probe proxy server capability on a node on a LAN or WAN. proxy also adds entries to the Probe proxy table or deletes entries from the Probe proxy table on a node. A probe proxy server enables NS through a LAN-to-LAN, LAN-to-WAN, WAN-to-WAN gateway when used with the route(1M) command. NS uses the probe protocol for name-to-IP-Address-resolution. By itself, the probe protocol can only obtain information about nodes on the same network or subnetwork. The probe proxy server provides IP address information about nodes on remote connected networks. The Probe proxy server can be a gateway node or any other node on the LAN. Note: The Probe protocol is not supported over X.25 links. In order to initiate NS over a connection path whose first hop is an X.25 link, the initiating node must be a Probe proxy server, and must include an entry for the target node in its Probe proxy table.

Options

on Enables Probe proxy on a node. This option must be used before invoking any other proxy option. Requires super-user capability.

off Disables the Probe proxy server. The Probe proxy table is not flushed. Requires super-user capability.

add Adds a new entry to the Probe proxy table. Requires super-user capability. The following parameters are required:

nodename A fully-qualified NS node name, including domain and organization. See nodename(1) for details.

domain Internet domain. The only supported domain is HPDSN.

ip_address An IP address of the remote node being mapped to by nodename. The IP address must be in internet “dot” format. See inet(3N) for details on internet dot format.

medium The physical link medium, either ieee, ether, or x.25.

append Appends an additional path report to an existing Probe proxy table entry. Use this option if a remote node supports more than one among IEEE 802.3 (ieee), Ethernet (ether), and X.25 (x.25) links, or if a remote node contains more than one network interface. append requires the same parameters as the add option described above. Requires super-user capability.

delete nodename Deletes nodename and all path reports associated with nodename from the Probe proxy table. Requires super-user capability.

flush Clears the Probe proxy table, deleting all entries. Requires super-user capability.

show nodename Sends path report information for nodename to standard output. For each path report associated with nodename, the following information is returned: node name, IP address or addresseses, medium, services, and transports. The services and transports field will always contain the value FFFF, meaning that all services and transports are enabled.

list Returns information for all entries in the Probe proxy table. proxy list is equivalent to issuing a proxy show command for all node names in the Probe proxy table.

DIAGNOSTICS

proxy server not yet enabled −
must do so before issuing any other proxy commands

Other proxy options attempted before proxy on issued.

proxy on: proxy server was already enabled
proxy on issued after proxy server already enabled.

proxy off: proxy server was already disabled
Super-user tried to turn off an already disabled proxy server.

proxy add: entry already exists
Super-user tried to add to the proxy table an entry which already exists.

proxy: out of memory for path reports
Probe proxy memory account is depleted.

proxy add: no space left in hash table buckets
Super-user tried to add too many entries that hash to the same bucket in the proxy table.

proxy append: entry does not exist
Super-user tried to append to a proxy table entry which had not been added.

proxy delete: entry does not exist
Super-user tried to delete an entry in the proxy table which had never been added.

proxy show: no entry for nodename
Requested nodename had no entry in proxy table.

WARNINGS

Reciprocal route commands must be executed on the local proxy requestor, the destination host, and all intermediate hosts before NS routing can succeed. See route(1M) and routing(7) for details.

Proxy entries are hashed for storage. Each hash bucket contains room for only five entries. There are 19 hash buckets for a potential total of 95 entries.

AUTHOR

proxy was developed by HP

Museum

Related Articles