2.3.t (1639) | 2.3.t (18715) |
---|---|
1.\" Copyright (c) 1983, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)2.3.t 8.1 (Berkeley) 6/8/93 | 1.\" Copyright (c) 1983, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)2.3.t 8.1 (Berkeley) 6/8/93 |
33.\" $Id$ |
|
33.\" 34.sh "Interprocess communications 35.NH 3 36Interprocess communication primitives 37.NH 4 38Communication domains 39.PP 40The system provides access to an extensible set of --- 346 unchanged lines hidden (view full) --- 387.PP 388Sockets in the Internet domain have names composed of the 32 bit 389Internet address, and a 16 bit port number. 390Options may be used to 391provide IP source routing or security options. 392The 32-bit address is composed of network and host parts; 393the network part is variable in size and is frequency encoded. 394The host part may optionally be interpreted as a subnet field | 34.\" 35.sh "Interprocess communications 36.NH 3 37Interprocess communication primitives 38.NH 4 39Communication domains 40.PP 41The system provides access to an extensible set of --- 346 unchanged lines hidden (view full) --- 388.PP 389Sockets in the Internet domain have names composed of the 32 bit 390Internet address, and a 16 bit port number. 391Options may be used to 392provide IP source routing or security options. 393The 32-bit address is composed of network and host parts; 394the network part is variable in size and is frequency encoded. 395The host part may optionally be interpreted as a subnet field |
395plus the host on subnet; this is is enabled by setting a network address | 396plus the host on subnet; this is enabled by setting a network address |
396mask at boot time. 397.NH 4 398Access rights transmission 399.PP 400No access rights transmission facilities are provided in the Internet domain. 401.NH 4 402Raw access 403.PP 404The Internet domain allows the super-user access to the raw facilities 405of IP. 406These interfaces are modeled as SOCK_RAW sockets. 407Each raw socket is associated with one IP protocol number, 408and receives all traffic received for that protocol. 409This allows administrative and debugging 410functions to occur, 411and enables user-level implementations of special-purpose protocols 412such as inter-gateway routing protocols. | 397mask at boot time. 398.NH 4 399Access rights transmission 400.PP 401No access rights transmission facilities are provided in the Internet domain. 402.NH 4 403Raw access 404.PP 405The Internet domain allows the super-user access to the raw facilities 406of IP. 407These interfaces are modeled as SOCK_RAW sockets. 408Each raw socket is associated with one IP protocol number, 409and receives all traffic received for that protocol. 410This allows administrative and debugging 411functions to occur, 412and enables user-level implementations of special-purpose protocols 413such as inter-gateway routing protocols. |