|
|
|
|
TCP/IP for QNX 2.x
The connection to heterogeneous networks
|
TCP/IP for QNX 2.x makes it possible to efficiently connect a
QNX 2 computer to a TCP/IP network while keeping the typical
QNX functionality and speed.
-
Compatibility is emphasized. The whole functionality
of QNX including network capabilities is preserved.
-
TCP/IP services are supported across the whole range.
This encompasses client and server functionality.
-
Efficiency and reasonable costs are guaranteed due to
high throughput and compatibility with NE2000 networking cards.
-
Application Programming Libraries help to develop
customized TCP/IP applications.
Compatibility and Resource Usage
TCP/IP for QNX 2.x runs on all machines on which QNX 2.x can be installed
in protected mode. Memory usage depends on the number of services. The basic
driver uses less than 500 KB of RAM. Disk usage of the whole system
is less than 2 MB.
PCI support
The new version 3.1 supports ISA and PCI cards.
Efficiency
Even on a 386 processor at 33MHz, TCP/IP for QNX 2.x supports telnet
sessions at up to 200 KB/s without noticably slowing down the machine.
On a Pentium 200 MHz is it even up to 800 KB/s.
Functionality
All the important programs for remote control and data transfer are provided
in their client and server forms. These include ftp, ftpd,
telnet, in_telnetd, rcp, rsh, netstat,
route, arp, ping etc.
Application Programming Libraries
With the help of the Socket library custom applications can be built. All the
crucial funtions like connect, accept, listen, send,
receive, get...name, htonl etc. are included.
Support
A manual, our phone support, updates and continuous development of the system
help you to integrate TCP/IP into your system without hassles and to realize complex customizations.
Range of Programs
TCP/IP for QNX 2.x supports all programs that are necessary for data transmission
and remote control. The number of functions is growing continuously and new tools are
made available in short intervals. Currently the package contains the following programs:
-
arp for manual address resolution and control as well as
to resolve address conflicts.
-
hostname to get and set the host's name
-
inetd to make server services available on a QNX 2.x computer
-
ping to check routing, reachability and performance
-
finger, fingerd and
ruptime to request user information
-
netstat for hardware and protocol information
-
nslookup for querying Internet domain servers
-
rcp, ftp,
ftps, rcpd
and ftpd for data transfer
-
telnet, rsh,
telnetd, in_telnetd
and rshd for remote control and remote login
-
route to manipulate routing tables
Library Functions
The application programming library complies with the BSD standard
except when conflicts with QNX names occur. Custom TCP/IP applications can be
developed using the CII compiler for QNX 2.x in the static large memory model.
The library comprises the following functions:
-
accept to establish incoming connections
-
bind to bind a name to an unknown socket
-
htonl, htons,
ntohl, ntohs
to convert between 16 bit and 32 bit values and different byte orders
-
connect to establish stream or datagram connections
-
gethostbyname, gethostbyaddr,
sethostent, endhostent
to request and set host structures
-
getpeername to request the name of a peer that is connected to a socket
-
getsockname to request the name of a socket
-
inet_addr, inet_network,
inet_ntoa, inet_makeaddr,
inet_lnaof, inet_netof
to request network numbers and Internet addresses
-
listen to listen for connections on a socket
-
getnetent, getnetbyname,
getnetbyaddr, setnetent,
endnetent to request and set network properties and structures
-
getprotoent, getprotobyname,
getprotobynumber, setprotoent,
endprotoent to request and set protocol properties
-
rcmd, rresvport,
ruserok to execute remote commands
-
rcv, recvfrom,
so_recv to receive messages from a socket
-
res_query, res_search,
res_mkquery, res_send,
res_init, dn_comp,
dn_expand to generate, interpret, send and reply to
messages from an Internet domain name server
-
rexec to execute a command on a remote host
-
select for multiplexing socket I/O calls to the library
-
s_send, sendto to send messages to other sockets
-
getservent, getservbyname,
getservbyport, setservent,
endservent for the manipulation of service entries
-
shutdown to terminate a connection
-
socket to establish a connection endpoint
-
getsockopt, setsockopt to request and set socket options
 More detailed info and demos from the manufacturer
Catalogue entry
|
|
|
