System Administration Guide, Volume 3
[ Previous ][ Fast Back ]Chapter 1. Managing IPv6 Concepts[ Fast Forward ][ Next ]

inetd Internet Services Daemon

An IPv6 enabled server is one that can handle IPv4 or IPv6 addresses depending on what the corresponding client is using. The /etc/inet/inetd.conf file contains the list of servers that inetd(1M) invokes when it receives an Internet request over a socket. Each socket-based Internet server entry is composed of a single line that uses the following syntax:
service_name socket_type proto flags user server_pathname args

See the inetd.conf(4) man page for a description of the possible values for each field. For the Solaris environment, the interaction of IPv6 with /etc/inet/inetd.conf uses a protocol of tcp6 or udp6 to indicate that an IPv6 socket should be created by inetd for the server. Thus, an IPv6-enabled server inheriting only an AF_INET6 socket type and using udp would list the filed proto value as udp6. This server can communicate with clients that use IPv4 or IPv6.

The following entry in the inetd.conf file depicts a server (myserver) that can communicate with both IPv4 and IPv6 client applications.

Example 1-3. Example 1--inetd.conf IPv6 Entry
myserver   dgram   udp6	wait	root	/usr/sbin/myserver	myserver

If an IPv6-enabled server is written in such a way that it can inherit an AF_INET or an AF_INET6 socket from inetd, it would have two lines in the /etc/inet/inetd.conf file as illustrated in the following example. See the "Network Interface Programming Guide" for details on protocol-independent servers. (EXTERNAL LINK TBD.)

Example 1-4. Example 2--inetd.conf IPv6 Entry
myserver   dgram   udp   wait	root	/usr/sbin/myserver	myserver
myserver   dgram   udp6   wait	root	/usr/sbin/myserver	myserver

With IPv6, most Solaris bundled servers that are socket based use AF_INET6 sockets. Examples of these are /usr/sbin/in.rlogind and /usr/sbin/in.tftpd which provide service to rlogin and telnet clients. The default /etc/inet/inetd.conf entries for these services list the proto value as tcp6 and udp6 respectively.

Note - Do not interchange tcp6 with tcp (and udp6 with udp) for these servers; unexpected side effects can result.

See IPv6 extensions to the Socket API in "Network Interface Programming Guide" for more details on writing IPv6 enabled servers using sockets.(EXTERNAL LINK TBD.)

[ Previous ][ Home ][ Next ]
in.ripngd Daemon[ Up ]Extensions to Existing Utilities