This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs. |
Full TCP/IP stack for IPv6 packets (QNX Neutrino)
io-net ... -p tcpip tcpip_options ...
The tcpip_options are one or more of the following, separated by commas without whitespace:
The value of num can assume the following values with the associated meanings:
The fastforward=1 alone implicitly enables forward.
io-net -i1 -ptcpip prefix=/alt SOCK=/alt ifconfig -a
This version of the TCP/IP stack is the default if you install the Extended Networking Technology Development Kit (TDK); npm-tcpip.so is a symbolic link to npm-tcpip-v6.so. If you haven't installed the TDK, npm-tcpip.so is a symbolic link to the npm-tcpip-v4.so module.
This npm-tcpip-v6.so module includes all the features in the standard stack, plus the functionality targeted at the new generation of mobile and secure communications. This stack provides full IPv6 and IPSec (both IPv4 and IPv6) support through KAME extensions, as well as support for VPNs over IPsec tunnels. This dual-mode stack supports IPv4 and IPv6< simultaneously and includes IPv6 support for autoconfiguration, which allows device configuration in plug-and-play network environments. IPv6 support includes IPv6-aware utilities and RIP/RIPng to support dynamic routing.
An Advanced Socket API is also provided to supplement the standard socket API to take advantage of IPv6 extended-development capabilities. IPsec support allows secure communication between hosts or networks, providing data confidentiality via strong encryption algorithms and data authentication features. IPsec support also includes the IKE (ISAKMP/Oakley) key management protocol for establishing secure host associations.
You'll likely enable the pfil_ipsec option (with no arguments) with this utility when your network configuration
The pfil_ipsec option affects the processing order of IPSec and IP filtering in the TCP/IP stack for outgoing packets -- by applying IP filtering and NAT to the outgoing traffic before it's sent on the IPsec tunnel.
You can't umount Qnet and the full TCP/IP. You may, however, create an io-net producer module that supports unmounting. |
The following io-net command uses the NE-2000 driver (devn-ne2000.so), and the networking stack with IPSec and forwarding enabled. The ifconfig command configures the ethernet interface to an IP address of 10.0.0.163 and the route command set the default gateway to 10.0.0.25:
io-net -dne2000 -ptcpip ipsec,forward ifconfig en0 10.163 route add default 10.25
If running multiple stacks, a particular instance is targeted by clients with the SOCK environment variable, as follows:
io-net -i1 -ptcpip prefix=/alt SOCK=/alt ifconfig -a
You can enable only forward by the following:
io-net -ptcpip forward,fastforward=0
/etc/autoconnect, dd, /etc/hosts, ifconfig, io-net, netstat, npm-tcpip.so, npm-tcpip-v4.so, ping, ping, pppd, /etc/resolv.conf, route, sysctl
"Network drivers (devn-*)" and "Network protocol modules (npm-*)" in the Utilities Summary
getsockopt(), ioctl(), setsockopt(), and ROUTE in the Library Reference TCP/IP Networking in the Neutrino User's Guide