Axcess Network Receiver Installation Guide - Manual (Page 53)

Network Receiver
© 2002, AXCESS Inc. 750.001.005 R0000 53
To set the hostname only to, type: hostname tini1
This commands allows you to display or configure the TINI's network settings. With
no arguments, the command will display the current network configuration.
If you are changing current information and have any slush network servers running
(Telnet or FTP), this command will bring down those servers, make the network
configuration updates, then bring up the servers again. If you call this command to
set information from a Telnet session, you will be disconnected.
You must have admin privileges to use this command.
Usage: ipconfig [OPTIONS]
where options include:
[-a xx.xx.xx.xx] Set the IP address. Must be used with the -m option.
[-n domainname] Set the domain name
[-m xx.xx.xx.xx] Set the subnet mask. Must be used with –a option.
[-g xx.xx.xx.xx] Set the gateway address.
[-p xx.xx.xx.xx] Set the primary DNS address
[-s xx.xx.xx.xx] Set the secondary DNS address
[-d] Use DHCP to lease an IP address
[-r] Release currently held DHCP IP address
[-x] Show all Interface data
[-h xx.xx.xx.xx] Set mailhost
[-C] Commit current network configuration to flash
[-D] Disable restoration from flash
[-f] Don't prompt for confirmation
Example:
To set your IP address, subnet mask, and gateway, type:
ipconfig -f -a 192.168.1.10 -g 192.168.1.1 -m 255.255.255.0
To tell slush to initiate DHCP, type: ipconfig -f -d
To commit the current network settings to flash memory type: ipconfig -C
java
This commands allows you to execute a Java class (.tini) file. This will launch
another process to begin executing the file. If you do not specify to run the program
in the background (i.e. give a '&' at the end of the command) then you will not be
returned a slush prompt until your program finishes executing. See the 'kill'
command for information on how to stop a running process.
If you are running from a Telnet session and run a program in the background, you
will see the output from your program as well as the slush prompts from your current
Telnet session. However, because of serial port sharing issues, if you run a program
in the background from a Serial Session prompt, you will not see the output of your
program. Either run your program in the foreground on the serial server, or redirect
the output of that program to a file.