-------------------------------------------------------------------------------
NCD Xterminal information and notes
-------------------------------------------------------------------------------
Boot from different subnet..

  I included the name servers for our systems and the addresses
  of the gateway that our NCD boot system is on in the tcpip-arp-cache.

  tcpip-arp-cache = {
          { 1 08:00:2b:2b:08:6d x.y.162.2 dynamic 0 }
          { 2 08:00:2b:39:72:b0 x.y.162.7 dynamic 0 }
          { 3 00:00:0c:05:ab:c6 x.y.162.1 dynamic 0 }
  }

  Then set the initial-default-gateway-# (1,2) for the gateways
  that you want to use, one being the subnet that the actual
  NCD terminals are on and the other being the subnet that
  the actual boot system is on.

  ip-extended-routing-diagnostics = true
  ip-initial-default-gateway-1 = x.y.162.1
  ip-initial-default-gateway-2 = x.y.166.1
  ip-respond-to-broadcast-icmp = false
  ip-subnet-mask = 0xffff0000
  ip-use-address-discovery = false
  ip-use-proxy-arp = false
  ip-use-router-discovery = true
  ip-use-router-solicit = true

  ip-broadcast-address = x.y.255.255

-------------------------------------------------------------------------------
IP address never stored in NVRAM

The "searching for IP Address" problem is directly related to the
"ip-use-address-discovery" parameter.  If this parameter is set to
true, the terminal will ignore any IP parameters you have specified
for the terminal, so it may be that the parameters are being saved but
are ignored because of this flag.  I don't have any experience on 2.4 boot
proms, but the above works with every boot prom/NCDware case I've seen.

-------------------------------------------------------------------------------
Seting up "simple network" Ports (Solaris)

  This step sets up a pseudo-terminal device to talk to the
  serial port on the NCD.

     Attach a tcpcon process (a Sun4 binary is found in the directory
     bin.Sun4-4.1.1 in the tcpcon distribution) to a pseudo-terminal
     with the nd program. Note that this attaches to a pseudo-terminal
     and that each pseudo-terminal has two devices associated with
     it: /dev/pty* and /dev/tty* (see the man pages on pty for some
     idea of what these are). You must use the pty device in the
     tcpcon command in order to use the tty device to access the
     NCD serial port.

     The command to attach tcpcon is:

          nd -\& -r tcpcon -l /dev/pty<??> <ncdname> 87

     The "\" acts as an escape for the "&" so it is not
     read by the shell. Replace <??> with the pseudo-terminal
     number (e.g. /dev/ptyqf) and <ncdname> with the host name
     or IP address of the NCD terminal.

     The tty driver (e.g. /dev/ttyqf for the example just given)
     can now be used to access the device on the NCD serial port.

-------------------------------------------------------------------------------