Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pk(4) [v7 man page]

PK(4)							     Kernel Interfaces Manual							     PK(4)

NAME
pk - packet driver DESCRIPTION
The packet driver implements a full-duplex end-to-end flow control strategy for machine-to-machine communication. Packet driver protocol is established by calling pkon(2) with a character device file descriptor and a desired packet size in bytes. The packet size must be a power of 2, 32<=size<=4096. The file descriptor must represent an 8-bit data path. This is normally obtained by setting the device in raw mode (see ioctl(2)). The actual packet size, which may be smaller than the desired packet size, is arrived at by negotiation with the packet driver at the remote end of the data link. The packet driver maintains two data areas for incoming and outgoing packets. The output area is needed to implement retransmission on errors, and arriving packets are queued in the input area. Data arriving for a file not open for reading is discarded. Initially the size of both areas is set to two packets. It is not necessary that reads and writes be multiples of the packet size although there is less system overhead if they are. Read opera- tions return the maximum amount of data available from the input area up to the number of bytes specified in the system call. The buffer sizes in write operations are not normally transmitted across the link. However, writes of zero length are treated specially and are reflected at the remote end as a zero-length read. This facilitates marking the serial byte stream, usually for delimiting files. When one side of a packet driver link is shut down by close(2)or pkoff (see pkon(2)), read(2) on the other side will return 0, and write on the other side will raise a SIGPIPE signal. SEE ALSO
pkon(2), pkopen(3) local PK(4)

Check Out this Related Man Page

IRIP(4) 						   BSD Kernel Interfaces Manual 						   IRIP(4)

NAME
irip -- Raw IP over ISDN network driver SYNOPSIS
pseudo-device irip count DESCRIPTION
The irip driver interfaces the IP subsystem of the operating system with the ISDN layer so that transport of IP packets over an ISDN link is possible. The driver just packs IP packets without anything appended or prepended into raw HDLC packets on the B channel and transfers them to a remote site. IP packets received from the remote site are queued into the local IP protocol stack. The format of the resulting packet on the B channel is: (HDLC opening flag) (IP-packet) (CRC) (HDLC closing flag) In the case where an IP packet for a remote site arrives in the driver and no connection has been established yet, the driver communicates with the isdnd(8) daemon to establish a connection. The driver has support for interfacing to the bpf(4) subsystem for using tcpdump(8) with the irip interfaces. The driver optionally (when compiled with the IRIP_VJ option) provides Van Jacobson header compression, under control of the link0 and link1 options to ifconfig(8): link0 Apply VJ compression to outgoing packets on this interface, and assume that incoming packets require decompression. link1 Check incoming packets for Van Jacobson compression; if they appear to be compressed, automatically set link0. The default values are on for link1 and off for link0. SEE ALSO
bpf(4), isdnd.rc(5), isdnd(8), tcpdump(8) AUTHORS
The irip device driver and this man page were written by Hellmuth Michaelis <hm@kts.org>. BSD
July 6, 1998 BSD
Man Page

3 More Discussions You Might Find Interesting

1. Cybersecurity

Personal Security

How can I be assured that my machine is secure against buffer overflows, remote packet sniffing, and brute force attacks? Why does the internet have to be so scary? Why can't we all just get along? (2 Replies)
Discussion started by: JoeTheGuy
2 Replies

2. IP Networking

Importance of LS length in DB exchange start packet (OSPF protocol)?

Is there any importance of LS length in DB exchange packet of OSPF protocol as its should be always be 20 bytes. Is this length to be ignored (2 Replies)
Discussion started by: cosmic_egg
2 Replies

3. UNIX for Advanced & Expert Users

Need help with configuring large packet size on Solaris 7 / e6500

We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096 bytes. Linux has /etc/network/interfaces. Does ANYONE remember the equivalent in Unix? When I do ifconfig eth0 mtu 4000, I get the error... (0 Replies)
Discussion started by: sharique
0 Replies