€•u     Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ*/translations/zh_CN/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/zh_TW/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/it_IT/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/ja_JP/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/ko_KR/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/sp_SP/networking/ppp_generic”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒD/var/lib/git/docbuild/linux/Documentation/networking/ppp_generic.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ(PPP Generic Driver and Channel Interface”h]”hŒ(PPP Generic Driver and Channel Interface”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒblock_quote”“”)”}”(hŒ/Paul Mackerras
paulus@samba.org

   7 Feb 2002
”h]”(hŒ	paragraph”“”)”}”(hŒPaul Mackerras
paulus@samba.org”h]”(hŒPaul Mackerras
”…””}”(hhÑhžhhŸNh NubhŒ	reference”“”)”}”(hŒpaulus@samba.org”h]”hŒpaulus@samba.org”…””}”(hhÛhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:paulus@samba.org”uh1hÙhhÑubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhhËubhÊ)”}”(hŒ7 Feb 2002
”h]”hÐ)”}”(hŒ
7 Feb 2002”h]”hŒ
7 Feb 2002”…””}”(hhõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K
hhñubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K
hhËubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÐ)”}”(hŒ‰The generic PPP driver in linux-2.4 provides an implementation of the
functionality which is of use in any PPP implementation, including:”h]”hŒ‰The generic PPP driver in linux-2.4 provides an implementation of the
functionality which is of use in any PPP implementation, including:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ&the network interface unit (ppp0 etc.)”h]”hÐ)”}”(hj&  h]”hŒ&the network interface unit (ppp0 etc.)”…””}”(hj(  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj$  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒ$the interface to the networking code”h]”hÐ)”}”(hj=  h]”hŒ$the interface to the networking code”…””}”(hj?  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒhPPP multilink: splitting datagrams between multiple links, and
ordering and combining received fragments”h]”hÐ)”}”(hŒhPPP multilink: splitting datagrams between multiple links, and
ordering and combining received fragments”h]”hŒhPPP multilink: splitting datagrams between multiple links, and
ordering and combining received fragments”…””}”(hjV  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhjR  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒ6the interface to pppd, via a /dev/ppp character device”h]”hÐ)”}”(hjl  h]”hŒ6the interface to pppd, via a /dev/ppp character device”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khjj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒ$packet compression and decompression”h]”hÐ)”}”(hjƒ  h]”hŒ$packet compression and decompression”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒ+TCP/IP header compression and decompression”h]”hÐ)”}”(hjš  h]”hŒ+TCP/IP header compression and decompression”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj˜  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒCdetecting network traffic for demand dialling and for idle timeouts”h]”hÐ)”}”(hj±  h]”hŒCdetecting network traffic for demand dialling and for idle timeouts”…””}”(hj³  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒsimple packet filtering
”h]”hÐ)”}”(hŒsimple packet filtering”h]”hŒsimple packet filtering”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhjÆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j  hŸh³h Khh¶hžhubhÐ)”}”(hX3  For sending and receiving PPP frames, the generic PPP driver calls on
the services of PPP ``channels``.  A PPP channel encapsulates a
mechanism for transporting PPP frames from one machine to another.  A
PPP channel implementation can be arbitrarily complex internally but
has a very simple interface with the generic PPP code: it merely has
to be able to send PPP frames, receive PPP frames, and optionally
handle ioctl requests.  Currently there are PPP channel
implementations for asynchronous serial ports, synchronous serial
ports, and for PPP over ethernet.”h]”(hŒZFor sending and receiving PPP frames, the generic PPP driver calls on
the services of PPP ”…””}”(hjæ  hžhhŸNh NubhŒliteral”“”)”}”(hŒ``channels``”h]”hŒchannels”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjæ  ubhXÍ  .  A PPP channel encapsulates a
mechanism for transporting PPP frames from one machine to another.  A
PPP channel implementation can be arbitrarily complex internally but
has a very simple interface with the generic PPP code: it merely has
to be able to send PPP frames, receive PPP frames, and optionally
handle ioctl requests.  Currently there are PPP channel
implementations for asynchronous serial ports, synchronous serial
ports, and for PPP over ethernet.”…””}”(hjæ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhÐ)”}”(hX  This architecture makes it possible to implement PPP multilink in a
natural and straightforward way, by allowing more than one channel to
be linked to each ppp network interface unit.  The generic layer is
responsible for splitting datagrams on transmit and recombining them
on receive.”h]”hX  This architecture makes it possible to implement PPP multilink in a
natural and straightforward way, by allowing more than one channel to
be linked to each ppp network interface unit.  The generic layer is
responsible for splitting datagrams on transmit and recombining them
on receive.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K#hh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒPPP channel API”h]”hŒPPP channel API”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj  hžhhŸh³h K+ubhÐ)”}”(hŒ’See include/linux/ppp_channel.h for the declaration of the types and
functions used to communicate between the generic PPP layer and PPP
channels.”h]”hŒ’See include/linux/ppp_channel.h for the declaration of the types and
functions used to communicate between the generic PPP layer and PPP
channels.”…””}”(hj'  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K-hj  hžhubhÐ)”}”(hŒdEach channel has to provide two functions to the generic PPP layer,
via the ppp_channel.ops pointer:”h]”hŒdEach channel has to provide two functions to the generic PPP layer,
via the ppp_channel.ops pointer:”…””}”(hj5  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K1hj  hžhubj  )”}”(hhh]”(j#  )”}”(hXÃ  start_xmit() is called by the generic layer when it has a frame to
send.  The channel has the option of rejecting the frame for
flow-control reasons.  In this case, start_xmit() should return 0
and the channel should call the ppp_output_wakeup() function at a
later time when it can accept frames again, and the generic layer
will then attempt to retransmit the rejected frame(s).  If the frame
is accepted, the start_xmit() function should return 1.
”h]”hÐ)”}”(hXÂ  start_xmit() is called by the generic layer when it has a frame to
send.  The channel has the option of rejecting the frame for
flow-control reasons.  In this case, start_xmit() should return 0
and the channel should call the ppp_output_wakeup() function at a
later time when it can accept frames again, and the generic layer
will then attempt to retransmit the rejected frame(s).  If the frame
is accepted, the start_xmit() function should return 1.”h]”hXÂ  start_xmit() is called by the generic layer when it has a frame to
send.  The channel has the option of rejecting the frame for
flow-control reasons.  In this case, start_xmit() should return 0
and the channel should call the ppp_output_wakeup() function at a
later time when it can accept frames again, and the generic layer
will then attempt to retransmit the rejected frame(s).  If the frame
is accepted, the start_xmit() function should return 1.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K4hjF  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjC  hžhhŸh³h Nubj#  )”}”(hX:  ioctl() provides an interface which can be used by a user-space
program to control aspects of the channel's behaviour.  This
procedure will be called when a user-space program does an ioctl
system call on an instance of /dev/ppp which is bound to the
channel.  (Usually it would only be pppd which would do this.)
”h]”hÐ)”}”(hX9  ioctl() provides an interface which can be used by a user-space
program to control aspects of the channel's behaviour.  This
procedure will be called when a user-space program does an ioctl
system call on an instance of /dev/ppp which is bound to the
channel.  (Usually it would only be pppd which would do this.)”h]”hX;  ioctl() provides an interface which can be used by a user-space
program to control aspects of the channelâ€™s behaviour.  This
procedure will be called when a user-space program does an ioctl
system call on an instance of /dev/ppp which is bound to the
channel.  (Usually it would only be pppd which would do this.)”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K<hj^  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjC  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h K4hj  hžhubhÐ)”}”(hŒ;The generic PPP layer provides seven functions to channels:”h]”hŒ;The generic PPP layer provides seven functions to channels:”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KBhj  hžhubj  )”}”(hhh]”(j#  )”}”(hŒïppp_register_channel() is called when a channel has been created, to
notify the PPP generic layer of its presence.  For example, setting
a serial port to the PPPDISC line discipline causes the ppp_async
channel code to call this function.
”h]”hÐ)”}”(hŒîppp_register_channel() is called when a channel has been created, to
notify the PPP generic layer of its presence.  For example, setting
a serial port to the PPPDISC line discipline causes the ppp_async
channel code to call this function.”h]”hŒîppp_register_channel() is called when a channel has been created, to
notify the PPP generic layer of its presence.  For example, setting
a serial port to the PPPDISC line discipline causes the ppp_async
channel code to call this function.”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KDhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hŒ¨ppp_unregister_channel() is called when a channel is to be
destroyed.  For example, the ppp_async channel code calls this when
a hangup is detected on the serial port.
”h]”hÐ)”}”(hŒ§ppp_unregister_channel() is called when a channel is to be
destroyed.  For example, the ppp_async channel code calls this when
a hangup is detected on the serial port.”h]”hŒ§ppp_unregister_channel() is called when a channel is to be
destroyed.  For example, the ppp_async channel code calls this when
a hangup is detected on the serial port.”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KIhj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hŒppp_output_wakeup() is called by a channel when it has previously
rejected a call to its start_xmit function, and can now accept more
packets.
”h]”hÐ)”}”(hŒŽppp_output_wakeup() is called by a channel when it has previously
rejected a call to its start_xmit function, and can now accept more
packets.”h]”hŒŽppp_output_wakeup() is called by a channel when it has previously
rejected a call to its start_xmit function, and can now accept more
packets.”…””}”(hjÁ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KMhj½  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hŒNppp_input() is called by a channel when it has received a complete
PPP frame.
”h]”hÐ)”}”(hŒMppp_input() is called by a channel when it has received a complete
PPP frame.”h]”hŒMppp_input() is called by a channel when it has received a complete
PPP frame.”…””}”(hjÙ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KQhjÕ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hŒ¢ppp_input_error() is called by a channel when it has detected that a
frame has been lost or dropped (for example, because of a FCS (frame
check sequence) error).
”h]”hÐ)”}”(hŒ¡ppp_input_error() is called by a channel when it has detected that a
frame has been lost or dropped (for example, because of a FCS (frame
check sequence) error).”h]”hŒ¡ppp_input_error() is called by a channel when it has detected that a
frame has been lost or dropped (for example, because of a FCS (frame
check sequence) error).”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KThjí  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hX	  ppp_channel_index() returns the channel index assigned by the PPP
generic layer to this channel.  The channel should provide some way
(e.g. an ioctl) to transmit this back to user-space, as user-space
will need it to attach an instance of /dev/ppp to this channel.
”h]”hÐ)”}”(hX  ppp_channel_index() returns the channel index assigned by the PPP
generic layer to this channel.  The channel should provide some way
(e.g. an ioctl) to transmit this back to user-space, as user-space
will need it to attach an instance of /dev/ppp to this channel.”h]”hX  ppp_channel_index() returns the channel index assigned by the PPP
generic layer to this channel.  The channel should provide some way
(e.g. an ioctl) to transmit this back to user-space, as user-space
will need it to attach an instance of /dev/ppp to this channel.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KXhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubj#  )”}”(hŒ’ppp_unit_number() returns the unit number of the ppp network
interface to which this channel is connected, or -1 if the channel
is not connected.
”h]”hÐ)”}”(hŒ‘ppp_unit_number() returns the unit number of the ppp network
interface to which this channel is connected, or -1 if the channel
is not connected.”h]”hŒ‘ppp_unit_number() returns the unit number of the ppp network
interface to which this channel is connected, or -1 if the channel
is not connected.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K]hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjŠ  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h KDhj  hžhubhÐ)”}”(hXT  Connecting a channel to the ppp generic layer is initiated from the
channel code, rather than from the generic layer.  The channel is
expected to have some way for a user-level process to control it
independently of the ppp generic layer.  For example, with the
ppp_async channel, this is provided by the file descriptor to the
serial port.”h]”hXT  Connecting a channel to the ppp generic layer is initiated from the
channel code, rather than from the generic layer.  The channel is
expected to have some way for a user-level process to control it
independently of the ppp generic layer.  For example, with the
ppp_async channel, this is provided by the file descriptor to the
serial port.”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kahj  hžhubhÐ)”}”(hXã  Generally a user-level process will initialize the underlying
communications medium and prepare it to do PPP.  For example, with an
async tty, this can involve setting the tty speed and modes, issuing
modem commands, and then going through some sort of dialog with the
remote system to invoke PPP service there.  We refer to this process
as ``discovery``.  Then the user-level process tells the medium to
become a PPP channel and register itself with the generic PPP layer.
The channel then has to report the channel number assigned to it back
to the user-level process.  From that point, the PPP negotiation code
in the PPP daemon (pppd) can take over and perform the PPP
negotiation, accessing the channel through the /dev/ppp interface.”h]”(hXU  Generally a user-level process will initialize the underlying
communications medium and prepare it to do PPP.  For example, with an
async tty, this can involve setting the tty speed and modes, issuing
modem commands, and then going through some sort of dialog with the
remote system to invoke PPP service there.  We refer to this process
as ”…””}”(hjI  hžhhŸNh Nubjï  )”}”(hŒ``discovery``”h]”hŒ	discovery”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjI  ubhX  .  Then the user-level process tells the medium to
become a PPP channel and register itself with the generic PPP layer.
The channel then has to report the channel number assigned to it back
to the user-level process.  From that point, the PPP negotiation code
in the PPP daemon (pppd) can take over and perform the PPP
negotiation, accessing the channel through the /dev/ppp interface.”…””}”(hjI  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khhj  hžhubhÐ)”}”(hX  At the interface to the PPP generic layer, PPP frames are stored in
skbuff structures and start with the two-byte PPP protocol number.
The frame does *not* include the 0xff ``address`` byte or the 0x03
``control`` byte that are optionally used in async PPP.  Nor is there
any escaping of control characters, nor are there any FCS or framing
characters included.  That is all the responsibility of the channel
code, if it is needed for the particular medium.  That is, the skbuffs
presented to the start_xmit() function contain only the 2-byte
protocol number and the data, and the skbuffs presented to ppp_input()
must be in the same format.”h]”(hŒ–At the interface to the PPP generic layer, PPP frames are stored in
skbuff structures and start with the two-byte PPP protocol number.
The frame does ”…””}”(hji  hžhhŸNh NubhŒemphasis”“”)”}”(hŒ*not*”h]”hŒnot”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jq  hji  ubhŒ include the 0xff ”…””}”(hji  hžhhŸNh Nubjï  )”}”(hŒ``address``”h]”hŒaddress”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hji  ubhŒ byte or the 0x03
”…””}”(hji  hžhhŸNh Nubjï  )”}”(hŒ``control``”h]”hŒcontrol”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hji  ubhX¬   byte that are optionally used in async PPP.  Nor is there
any escaping of control characters, nor are there any FCS or framing
characters included.  That is all the responsibility of the channel
code, if it is needed for the particular medium.  That is, the skbuffs
presented to the start_xmit() function contain only the 2-byte
protocol number and the data, and the skbuffs presented to ppp_input()
must be in the same format.”…””}”(hji  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kthj  hžhubhÐ)”}”(hXÐ  The channel must provide an instance of a ppp_channel struct to
represent the channel.  The channel is free to use the ``private`` field
however it wishes.  The channel should initialize the ``mtu`` and
``hdrlen`` fields before calling ppp_register_channel() and not change
them until after ppp_unregister_channel() returns.  The ``mtu`` field
represents the maximum size of the data part of the PPP frames, that
is, it does not include the 2-byte protocol number.”h]”(hŒwThe channel must provide an instance of a ppp_channel struct to
represent the channel.  The channel is free to use the ”…””}”(hj¯  hžhhŸNh Nubjï  )”}”(hŒ``private``”h]”hŒprivate”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj¯  ubhŒ= field
however it wishes.  The channel should initialize the ”…””}”(hj¯  hžhhŸNh Nubjï  )”}”(hŒ``mtu``”h]”hŒmtu”…””}”(hjÉ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj¯  ubhŒ and
”…””}”(hj¯  hžhhŸNh Nubjï  )”}”(hŒ
``hdrlen``”h]”hŒhdrlen”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj¯  ubhŒu fields before calling ppp_register_channel() and not change
them until after ppp_unregister_channel() returns.  The ”…””}”(hj¯  hžhhŸNh Nubjï  )”}”(hŒ``mtu``”h]”hŒmtu”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj¯  ubhŒ field
represents the maximum size of the data part of the PPP frames, that
is, it does not include the 2-byte protocol number.”…””}”(hj¯  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj  hžhubhÐ)”}”(hX¯  If the channel needs some headroom in the skbuffs presented to it for
transmission (i.e., some space free in the skbuff data area before the
start of the PPP frame), it should set the ``hdrlen`` field of the
ppp_channel struct to the amount of headroom required.  The generic
PPP layer will attempt to provide that much headroom but the channel
should still check if there is sufficient headroom and copy the skbuff
if there isn't.”h]”(hŒ¸If the channel needs some headroom in the skbuffs presented to it for
transmission (i.e., some space free in the skbuff data area before the
start of the PPP frame), it should set the ”…””}”(hj  hžhhŸNh Nubjï  )”}”(hŒ
``hdrlen``”h]”hŒhdrlen”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj  ubhŒï field of the
ppp_channel struct to the amount of headroom required.  The generic
PPP layer will attempt to provide that much headroom but the channel
should still check if there is sufficient headroom and copy the skbuff
if there isnâ€™t.”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K‡hj  hžhubhÐ)”}”(hŒÐOn the input side, channels should ideally provide at least 2 bytes of
headroom in the skbuffs presented to ppp_input().  The generic PPP
code does not require this but will be more efficient if this is done.”h]”hŒÐOn the input side, channels should ideally provide at least 2 bytes of
headroom in the skbuffs presented to ppp_input().  The generic PPP
code does not require this but will be more efficient if this is done.”…””}”(hj%  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj  hžhubeh}”(h]”Œppp-channel-api”ah ]”h"]”Œppp channel api”ah$]”h&]”uh1h´hh¶hžhhŸh³h K+ubhµ)”}”(hhh]”(hº)”}”(hŒBuffering and flow control”h]”hŒBuffering and flow control”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj;  hžhhŸh³h K•ubhÐ)”}”(hX¼  The generic PPP layer has been designed to minimize the amount of data
that it buffers in the transmit direction.  It maintains a queue of
transmit packets for the PPP unit (network interface device) plus a
queue of transmit packets for each attached channel.  Normally the
transmit queue for the unit will contain at most one packet; the
exceptions are when pppd sends packets by writing to /dev/ppp, and
when the core networking code calls the generic layer's start_xmit()
function with the queue stopped, i.e. when the generic layer has
called netif_stop_queue(), which only happens on a transmit timeout.
The start_xmit function always accepts and queues the packet which it
is asked to transmit.”h]”hX¾  The generic PPP layer has been designed to minimize the amount of data
that it buffers in the transmit direction.  It maintains a queue of
transmit packets for the PPP unit (network interface device) plus a
queue of transmit packets for each attached channel.  Normally the
transmit queue for the unit will contain at most one packet; the
exceptions are when pppd sends packets by writing to /dev/ppp, and
when the core networking code calls the generic layerâ€™s start_xmit()
function with the queue stopped, i.e. when the generic layer has
called netif_stop_queue(), which only happens on a transmit timeout.
The start_xmit function always accepts and queues the packet which it
is asked to transmit.”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K—hj;  hžhubhÐ)”}”(hXg  Transmit packets are dequeued from the PPP unit transmit queue and
then subjected to TCP/IP header compression and packet compression
(Deflate or BSD-Compress compression), as appropriate.  After this
point the packets can no longer be reordered, as the decompression
algorithms rely on receiving compressed packets in the same order that
they were generated.”h]”hXg  Transmit packets are dequeued from the PPP unit transmit queue and
then subjected to TCP/IP header compression and packet compression
(Deflate or BSD-Compress compression), as appropriate.  After this
point the packets can no longer be reordered, as the decompression
algorithms rely on receiving compressed packets in the same order that
they were generated.”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K£hj;  hžhubhÐ)”}”(hX  If multilink is not in use, this packet is then passed to the attached
channel's start_xmit() function.  If the channel refuses to take
the packet, the generic layer saves it for later transmission.  The
generic layer will call the channel's start_xmit() function again
when the channel calls  ppp_output_wakeup() or when the core
networking code calls the generic layer's start_xmit() function
again.  The generic layer contains no timeout and retransmission
logic; it relies on the core networking code for that.”h]”hX  If multilink is not in use, this packet is then passed to the attached
channelâ€™s start_xmit() function.  If the channel refuses to take
the packet, the generic layer saves it for later transmission.  The
generic layer will call the channelâ€™s start_xmit() function again
when the channel calls  ppp_output_wakeup() or when the core
networking code calls the generic layerâ€™s start_xmit() function
again.  The generic layer contains no timeout and retransmission
logic; it relies on the core networking code for that.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kªhj;  hžhubhÐ)”}”(hX{  If multilink is in use, the generic layer divides the packet into one
or more fragments and puts a multilink header on each fragment.  It
decides how many fragments to use based on the length of the packet
and the number of channels which are potentially able to accept a
fragment at the moment.  A channel is potentially able to accept a
fragment if it doesn't have any fragments currently queued up for it
to transmit.  The channel may still refuse a fragment; in this case
the fragment is queued up for the channel to transmit later.  This
scheme has the effect that more fragments are given to higher-
bandwidth channels.  It also means that under light load, the generic
layer will tend to fragment large packets across all the channels,
thus reducing latency, while under heavy load, packets will tend to be
transmitted as single fragments, thus reducing the overhead of
fragmentation.”h]”hX}  If multilink is in use, the generic layer divides the packet into one
or more fragments and puts a multilink header on each fragment.  It
decides how many fragments to use based on the length of the packet
and the number of channels which are potentially able to accept a
fragment at the moment.  A channel is potentially able to accept a
fragment if it doesnâ€™t have any fragments currently queued up for it
to transmit.  The channel may still refuse a fragment; in this case
the fragment is queued up for the channel to transmit later.  This
scheme has the effect that more fragments are given to higher-
bandwidth channels.  It also means that under light load, the generic
layer will tend to fragment large packets across all the channels,
thus reducing latency, while under heavy load, packets will tend to be
transmitted as single fragments, thus reducing the overhead of
fragmentation.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K³hj;  hžhubeh}”(h]”Œbuffering-and-flow-control”ah ]”h"]”Œbuffering and flow control”ah$]”h&]”uh1h´hh¶hžhhŸh³h K•ubhµ)”}”(hhh]”(hº)”}”(hŒ
SMP safety”h]”hŒ
SMP safety”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjŒ  hžhhŸh³h KÄubhÐ)”}”(hX¾  The PPP generic layer has been designed to be SMP-safe.  Locks are
used around accesses to the internal data structures where necessary
to ensure their integrity.  As part of this, the generic layer
requires that the channels adhere to certain requirements and in turn
provides certain guarantees to the channels.  Essentially the channels
are required to provide the appropriate locking on the ppp_channel
structures that form the basis of the communication between the
channel and the generic layer.  This is because the channel provides
the storage for the ppp_channel structure, and so the channel is
required to provide the guarantee that this storage exists and is
valid at the appropriate times.”h]”hX¾  The PPP generic layer has been designed to be SMP-safe.  Locks are
used around accesses to the internal data structures where necessary
to ensure their integrity.  As part of this, the generic layer
requires that the channels adhere to certain requirements and in turn
provides certain guarantees to the channels.  Essentially the channels
are required to provide the appropriate locking on the ppp_channel
structures that form the basis of the communication between the
channel and the generic layer.  This is because the channel provides
the storage for the ppp_channel structure, and so the channel is
required to provide the guarantee that this storage exists and is
valid at the appropriate times.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÆhjŒ  hžhubhÐ)”}”(hŒ=The generic layer requires these guarantees from the channel:”h]”hŒ=The generic layer requires these guarantees from the channel:”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÒhjŒ  hžhubj  )”}”(hhh]”(j#  )”}”(hŒThe ppp_channel object must exist from the time that
ppp_register_channel() is called until after the call to
ppp_unregister_channel() returns.
”h]”hÐ)”}”(hŒThe ppp_channel object must exist from the time that
ppp_register_channel() is called until after the call to
ppp_unregister_channel() returns.”h]”hŒThe ppp_channel object must exist from the time that
ppp_register_channel() is called until after the call to
ppp_unregister_channel() returns.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÔhj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubj#  )”}”(hŒ×No thread may be in a call to any of ppp_input(), ppp_input_error(),
ppp_output_wakeup(), ppp_channel_index() or ppp_unit_number() for a
channel at the time that ppp_unregister_channel() is called for that
channel.
”h]”hÐ)”}”(hŒÖNo thread may be in a call to any of ppp_input(), ppp_input_error(),
ppp_output_wakeup(), ppp_channel_index() or ppp_unit_number() for a
channel at the time that ppp_unregister_channel() is called for that
channel.”h]”hŒÖNo thread may be in a call to any of ppp_input(), ppp_input_error(),
ppp_output_wakeup(), ppp_channel_index() or ppp_unit_number() for a
channel at the time that ppp_unregister_channel() is called for that
channel.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KØhjÔ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubj#  )”}”(hŒ~ppp_register_channel() and ppp_unregister_channel() must be called
from process context, not interrupt or softirq/BH context.
”h]”hÐ)”}”(hŒ}ppp_register_channel() and ppp_unregister_channel() must be called
from process context, not interrupt or softirq/BH context.”h]”hŒ}ppp_register_channel() and ppp_unregister_channel() must be called
from process context, not interrupt or softirq/BH context.”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KÝhjì  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubj#  )”}”(hŒ‚The remaining generic layer functions may be called at softirq/BH
level but must not be called from a hardware interrupt handler.
”h]”hÐ)”}”(hŒThe remaining generic layer functions may be called at softirq/BH
level but must not be called from a hardware interrupt handler.”h]”hŒThe remaining generic layer functions may be called at softirq/BH
level but must not be called from a hardware interrupt handler.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kàhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubj#  )”}”(hŒ©The generic layer may call the channel start_xmit() function at
softirq/BH level but will not call it at interrupt level.  Thus the
start_xmit() function may not block.
”h]”hÐ)”}”(hŒ¨The generic layer may call the channel start_xmit() function at
softirq/BH level but will not call it at interrupt level.  Thus the
start_xmit() function may not block.”h]”hŒ¨The generic layer may call the channel start_xmit() function at
softirq/BH level but will not call it at interrupt level.  Thus the
start_xmit() function may not block.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kãhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubj#  )”}”(hŒRThe generic layer will only call the channel ioctl() function in
process context.
”h]”hÐ)”}”(hŒQThe generic layer will only call the channel ioctl() function in
process context.”h]”hŒQThe generic layer will only call the channel ioctl() function in
process context.”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kçhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj¹  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h KÔhjŒ  hžhubhÐ)”}”(hŒ<The generic layer provides these guarantees to the channels:”h]”hŒ<The generic layer provides these guarantees to the channels:”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KêhjŒ  hžhubj  )”}”(hhh]”(j#  )”}”(hŒ‘The generic layer will not call the start_xmit() function for a
channel while any thread is already executing in that function for
that channel.
”h]”hÐ)”}”(hŒThe generic layer will not call the start_xmit() function for a
channel while any thread is already executing in that function for
that channel.”h]”hŒThe generic layer will not call the start_xmit() function for a
channel while any thread is already executing in that function for
that channel.”…””}”(hjg  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kìhjc  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj`  hžhhŸh³h Nubj#  )”}”(hŒŒThe generic layer will not call the ioctl() function for a channel
while any thread is already executing in that function for that
channel.
”h]”hÐ)”}”(hŒ‹The generic layer will not call the ioctl() function for a channel
while any thread is already executing in that function for that
channel.”h]”hŒ‹The generic layer will not call the ioctl() function for a channel
while any thread is already executing in that function for that
channel.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kðhj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj`  hžhhŸh³h Nubj#  )”}”(hŒöBy the time a call to ppp_unregister_channel() returns, no thread
will be executing in a call from the generic layer to that channel's
start_xmit() or ioctl() function, and the generic layer will not
call either of those functions subsequently.

”h]”hÐ)”}”(hŒôBy the time a call to ppp_unregister_channel() returns, no thread
will be executing in a call from the generic layer to that channel's
start_xmit() or ioctl() function, and the generic layer will not
call either of those functions subsequently.”h]”hŒöBy the time a call to ppp_unregister_channel() returns, no thread
will be executing in a call from the generic layer to that channelâ€™s
start_xmit() or ioctl() function, and the generic layer will not
call either of those functions subsequently.”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kôhj“  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj`  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h KìhjŒ  hžhubeh}”(h]”Œ
smp-safety”ah ]”h"]”Œ
smp safety”ah$]”h&]”uh1h´hh¶hžhhŸh³h KÄubhµ)”}”(hhh]”(hº)”}”(hŒInterface to pppd”h]”hŒInterface to pppd”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¹  hžhhŸh³h KûubhÐ)”}”(hXc  The PPP generic layer exports a character device interface called
/dev/ppp.  This is used by pppd to control PPP interface units and
channels.  Although there is only one /dev/ppp, each open instance of
/dev/ppp acts independently and can be attached either to a PPP unit
or a PPP channel.  This is achieved using the file->private_data field
to point to a separate object for each open instance of /dev/ppp.  In
this way an effect similar to Solaris' clone open is obtained,
allowing us to control an arbitrary number of PPP interfaces and
channels without having to fill up /dev with hundreds of device names.”h]”hXe  The PPP generic layer exports a character device interface called
/dev/ppp.  This is used by pppd to control PPP interface units and
channels.  Although there is only one /dev/ppp, each open instance of
/dev/ppp acts independently and can be attached either to a PPP unit
or a PPP channel.  This is achieved using the file->private_data field
to point to a separate object for each open instance of /dev/ppp.  In
this way an effect similar to Solarisâ€™ clone open is obtained,
allowing us to control an arbitrary number of PPP interfaces and
channels without having to fill up /dev with hundreds of device names.”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Kýhj¹  hžhubhÐ)”}”(hXã  When /dev/ppp is opened, a new instance is created which is initially
unattached.  Using an ioctl call, it can then be attached to an
existing unit, attached to a newly-created unit, or attached to an
existing channel.  An instance attached to a unit can be used to send
and receive PPP control frames, using the read() and write() system
calls, along with poll() if necessary.  Similarly, an instance
attached to a channel can be used to send and receive PPP frames on
that channel.”h]”hXã  When /dev/ppp is opened, a new instance is created which is initially
unattached.  Using an ioctl call, it can then be attached to an
existing unit, attached to a newly-created unit, or attached to an
existing channel.  An instance attached to a unit can be used to send
and receive PPP control frames, using the read() and write() system
calls, along with poll() if necessary.  Similarly, an instance
attached to a channel can be used to send and receive PPP frames on
that channel.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj¹  hžhubhÐ)”}”(hXÈ  In multilink terms, the unit represents the bundle, while the channels
represent the individual physical links.  Thus, a PPP frame sent by a
write to the unit (i.e., to an instance of /dev/ppp attached to the
unit) will be subject to bundle-level compression and to fragmentation
across the individual links (if multilink is in use).  In contrast, a
PPP frame sent by a write to the channel will be sent as-is on that
channel, without any multilink header.”h]”hXÈ  In multilink terms, the unit represents the bundle, while the channels
represent the individual physical links.  Thus, a PPP frame sent by a
write to the unit (i.e., to an instance of /dev/ppp attached to the
unit) will be subject to bundle-level compression and to fragmentation
across the individual links (if multilink is in use).  In contrast, a
PPP frame sent by a write to the channel will be sent as-is on that
channel, without any multilink header.”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj¹  hžhubhÐ)”}”(hX  A channel is not initially attached to any unit.  In this state it can
be used for PPP negotiation but not for the transfer of data packets.
It can then be connected to a PPP unit with an ioctl call, which
makes it available to send and receive data packets for that unit.”h]”hX  A channel is not initially attached to any unit.  In this state it can
be used for PPP negotiation but not for the transfer of data packets.
It can then be connected to a PPP unit with an ioctl call, which
makes it available to send and receive data packets for that unit.”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj¹  hžhubhÐ)”}”(hŒáThe ioctl calls which are available on an instance of /dev/ppp depend
on whether it is unattached, attached to a PPP interface, or attached
to a PPP channel.  The ioctl calls which are available on an
unattached instance are:”h]”hŒáThe ioctl calls which are available on an instance of /dev/ppp depend
on whether it is unattached, attached to a PPP interface, or attached
to a PPP channel.  The ioctl calls which are available on an
unattached instance are:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mhj¹  hžhubj  )”}”(hhh]”(j#  )”}”(hX\  PPPIOCNEWUNIT creates a new PPP interface and makes this /dev/ppp
instance the "owner" of the interface.  The argument should point to
an int which is the desired unit number if >= 0, or -1 to assign the
lowest unused unit number.  Being the owner of the interface means
that the interface will be shut down if this instance of /dev/ppp is
closed.
”h]”hÐ)”}”(hX[  PPPIOCNEWUNIT creates a new PPP interface and makes this /dev/ppp
instance the "owner" of the interface.  The argument should point to
an int which is the desired unit number if >= 0, or -1 to assign the
lowest unused unit number.  Being the owner of the interface means
that the interface will be shut down if this instance of /dev/ppp is
closed.”h]”hX_  PPPIOCNEWUNIT creates a new PPP interface and makes this /dev/ppp
instance the â€œownerâ€ of the interface.  The argument should point to
an int which is the desired unit number if >= 0, or -1 to assign the
lowest unused unit number.  Being the owner of the interface means
that the interface will be shut down if this instance of /dev/ppp is
closed.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M"hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒÃPPPIOCATTACH attaches this instance to an existing PPP interface.
The argument should point to an int containing the unit number.
This does not make this instance the owner of the PPP interface.
”h]”hÐ)”}”(hŒÂPPPIOCATTACH attaches this instance to an existing PPP interface.
The argument should point to an int containing the unit number.
This does not make this instance the owner of the PPP interface.”h]”hŒÂPPPIOCATTACH attaches this instance to an existing PPP interface.
The argument should point to an int containing the unit number.
This does not make this instance the owner of the PPP interface.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M)hj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubj#  )”}”(hŒ„PPPIOCATTCHAN attaches this instance to an existing PPP channel.
The argument should point to an int containing the channel number.
”h]”hÐ)”}”(hŒƒPPPIOCATTCHAN attaches this instance to an existing PPP channel.
The argument should point to an int containing the channel number.”h]”hŒƒPPPIOCATTCHAN attaches this instance to an existing PPP channel.
The argument should point to an int containing the channel number.”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M-hjC  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hj  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h M"hj¹  hžhubhÐ)”}”(hŒOThe ioctl calls available on an instance of /dev/ppp attached to a
channel are:”h]”hŒOThe ioctl calls available on an instance of /dev/ppp attached to a
channel are:”…””}”(hja  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M0hj¹  hžhubj  )”}”(hhh]”(j#  )”}”(hX  PPPIOCCONNECT connects this channel to a PPP interface.  The
argument should point to an int containing the interface unit
number.  It will return an EINVAL error if the channel is already
connected to an interface, or ENXIO if the requested interface does
not exist.
”h]”hÐ)”}”(hX  PPPIOCCONNECT connects this channel to a PPP interface.  The
argument should point to an int containing the interface unit
number.  It will return an EINVAL error if the channel is already
connected to an interface, or ENXIO if the requested interface does
not exist.”h]”hX  PPPIOCCONNECT connects this channel to a PPP interface.  The
argument should point to an int containing the interface unit
number.  It will return an EINVAL error if the channel is already
connected to an interface, or ENXIO if the requested interface does
not exist.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M3hjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjo  hžhhŸh³h Nubj#  )”}”(hŒ¨PPPIOCDISCONN disconnects this channel from the PPP interface that
it is connected to.  It will return an EINVAL error if the channel
is not connected to an interface.
”h]”hÐ)”}”(hŒ§PPPIOCDISCONN disconnects this channel from the PPP interface that
it is connected to.  It will return an EINVAL error if the channel
is not connected to an interface.”h]”hŒ§PPPIOCDISCONN disconnects this channel from the PPP interface that
it is connected to.  It will return an EINVAL error if the channel
is not connected to an interface.”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M9hjŠ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjo  hžhhŸh³h Nubj#  )”}”(hX¹  PPPIOCBRIDGECHAN bridges a channel with another. The argument should
point to an int containing the channel number of the channel to bridge
to. Once two channels are bridged, frames presented to one channel by
ppp_input() are passed to the bridge instance for onward transmission.
This allows frames to be switched from one channel into another: for
example, to pass PPPoE frames into a PPPoL2TP session. Since channel
bridging interrupts the normal ppp_input() path, a given channel may
not be part of a bridge at the same time as being part of a unit.
This ioctl will return an EALREADY error if the channel is already
part of a bridge or unit, or ENXIO if the requested channel does not
exist.
”h]”hÐ)”}”(hX¸  PPPIOCBRIDGECHAN bridges a channel with another. The argument should
point to an int containing the channel number of the channel to bridge
to. Once two channels are bridged, frames presented to one channel by
ppp_input() are passed to the bridge instance for onward transmission.
This allows frames to be switched from one channel into another: for
example, to pass PPPoE frames into a PPPoL2TP session. Since channel
bridging interrupts the normal ppp_input() path, a given channel may
not be part of a bridge at the same time as being part of a unit.
This ioctl will return an EALREADY error if the channel is already
part of a bridge or unit, or ENXIO if the requested channel does not
exist.”h]”hX¸  PPPIOCBRIDGECHAN bridges a channel with another. The argument should
point to an int containing the channel number of the channel to bridge
to. Once two channels are bridged, frames presented to one channel by
ppp_input() are passed to the bridge instance for onward transmission.
This allows frames to be switched from one channel into another: for
example, to pass PPPoE frames into a PPPoL2TP session. Since channel
bridging interrupts the normal ppp_input() path, a given channel may
not be part of a bridge at the same time as being part of a unit.
This ioctl will return an EALREADY error if the channel is already
part of a bridge or unit, or ENXIO if the requested channel does not
exist.”…””}”(hj¦  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M=hj¢  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjo  hžhhŸh³h Nubj#  )”}”(hŒ¯PPPIOCUNBRIDGECHAN performs the inverse of PPPIOCBRIDGECHAN, unbridging
a channel pair.  This ioctl will return an EINVAL error if the channel
does not form part of a bridge.
”h]”hÐ)”}”(hŒ®PPPIOCUNBRIDGECHAN performs the inverse of PPPIOCBRIDGECHAN, unbridging
a channel pair.  This ioctl will return an EINVAL error if the channel
does not form part of a bridge.”h]”hŒ®PPPIOCUNBRIDGECHAN performs the inverse of PPPIOCBRIDGECHAN, unbridging
a channel pair.  This ioctl will return an EINVAL error if the channel
does not form part of a bridge.”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MIhjº  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjo  hžhhŸh³h Nubj#  )”}”(hŒEAll other ioctl commands are passed to the channel ioctl() function.
”h]”hÐ)”}”(hŒDAll other ioctl commands are passed to the channel ioctl() function.”h]”hŒDAll other ioctl commands are passed to the channel ioctl() function.”…””}”(hjÖ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MMhjÒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjo  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h M3hj¹  hžhubhÐ)”}”(hŒ\The ioctl calls that are available on an instance that is attached to
an interface unit are:”h]”hŒ\The ioctl calls that are available on an instance that is attached to
an interface unit are:”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MOhj¹  hžhubj  )”}”(hhh]”(j#  )”}”(hŒ„PPPIOCSMRU sets the MRU (maximum receive unit) for the interface.
The argument should point to an int containing the new MRU value.
”h]”hÐ)”}”(hŒƒPPPIOCSMRU sets the MRU (maximum receive unit) for the interface.
The argument should point to an int containing the new MRU value.”h]”hŒƒPPPIOCSMRU sets the MRU (maximum receive unit) for the interface.
The argument should point to an int containing the new MRU value.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MRhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hX`  PPPIOCSFLAGS sets flags which control the operation of the
interface.  The argument should be a pointer to an int containing
the new flags value.  The bits in the flags value that can be set
are:

      ================        ========================================
      SC_COMP_TCP             enable transmit TCP header compression
      SC_NO_TCP_CCID          disable connection-id compression for
                              TCP header compression
      SC_REJ_COMP_TCP         disable receive TCP header decompression
      SC_CCP_OPEN             Compression Control Protocol (CCP) is
                              open, so inspect CCP packets
      SC_CCP_UP               CCP is up, may (de)compress packets
      SC_LOOP_TRAFFIC         send IP traffic to pppd
      SC_MULTILINK            enable PPP multilink fragmentation on
                              transmitted packets
      SC_MP_SHORTSEQ          expect short multilink sequence
                              numbers on received multilink fragments
      SC_MP_XSHORTSEQ         transmit short multilink sequence nos.
      ================        ========================================

The values of these flags are defined in <linux/ppp-ioctl.h>.  Note
that the values of the SC_MULTILINK, SC_MP_SHORTSEQ and
SC_MP_XSHORTSEQ bits are ignored if the CONFIG_PPP_MULTILINK option
is not selected.
”h]”(hÐ)”}”(hŒÃPPPIOCSFLAGS sets flags which control the operation of the
interface.  The argument should be a pointer to an int containing
the new flags value.  The bits in the flags value that can be set
are:”h]”hŒÃPPPIOCSFLAGS sets flags which control the operation of the
interface.  The argument should be a pointer to an int containing
the new flags value.  The bits in the flags value that can be set
are:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MUhj  ubhÊ)”}”(hXo  ================        ========================================
SC_COMP_TCP             enable transmit TCP header compression
SC_NO_TCP_CCID          disable connection-id compression for
                        TCP header compression
SC_REJ_COMP_TCP         disable receive TCP header decompression
SC_CCP_OPEN             Compression Control Protocol (CCP) is
                        open, so inspect CCP packets
SC_CCP_UP               CCP is up, may (de)compress packets
SC_LOOP_TRAFFIC         send IP traffic to pppd
SC_MULTILINK            enable PPP multilink fragmentation on
                        transmitted packets
SC_MP_SHORTSEQ          expect short multilink sequence
                        numbers on received multilink fragments
SC_MP_XSHORTSEQ         transmit short multilink sequence nos.
================        ========================================
”h]”hŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j9  hj6  ubj:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K(uh1j9  hj6  ubhŒtbody”“”)”}”(hhh]”(hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÐ)”}”(hŒSC_COMP_TCP”h]”hŒSC_COMP_TCP”…””}”(hj^  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M[hj[  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjV  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ&enable transmit TCP header compression”h]”hŒ&enable transmit TCP header compression”…””}”(hju  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M[hjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjV  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_NO_TCP_CCID”h]”hŒSC_NO_TCP_CCID”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M\hj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ<disable connection-id compression for
TCP header compression”h]”hŒ<disable connection-id compression for
TCP header compression”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M\hj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_REJ_COMP_TCP”h]”hŒSC_REJ_COMP_TCP”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M^hjÉ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÆ  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ(disable receive TCP header decompression”h]”hŒ(disable receive TCP header decompression”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M^hjà  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÆ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_CCP_OPEN”h]”hŒSC_CCP_OPEN”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M_hj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjý  ubjZ  )”}”(hhh]”hÐ)”}”(hŒBCompression Control Protocol (CCP) is
open, so inspect CCP packets”h]”hŒBCompression Control Protocol (CCP) is
open, so inspect CCP packets”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M_hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjý  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒ	SC_CCP_UP”h]”hŒ	SC_CCP_UP”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mahj7  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj4  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ#CCP is up, may (de)compress packets”h]”hŒ#CCP is up, may (de)compress packets”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MahjN  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj4  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_LOOP_TRAFFIC”h]”hŒSC_LOOP_TRAFFIC”…””}”(hjq  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mbhjn  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjk  ubjZ  )”}”(hhh]”hÐ)”}”(hŒsend IP traffic to pppd”h]”hŒsend IP traffic to pppd”…””}”(hjˆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mbhj…  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjk  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_MULTILINK”h]”hŒSC_MULTILINK”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mchj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj¢  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ9enable PPP multilink fragmentation on
transmitted packets”h]”hŒ9enable PPP multilink fragmentation on
transmitted packets”…””}”(hj¿  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mchj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj¢  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_MP_SHORTSEQ”h]”hŒSC_MP_SHORTSEQ”…””}”(hjß  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MehjÜ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÙ  ubjZ  )”}”(hhh]”hÐ)”}”(hŒGexpect short multilink sequence
numbers on received multilink fragments”h]”hŒGexpect short multilink sequence
numbers on received multilink fragments”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mehjó  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÙ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_MP_XSHORTSEQ”h]”hŒSC_MP_XSHORTSEQ”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mghj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj	  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ&transmit short multilink sequence nos.”h]”hŒ&transmit short multilink sequence nos.”…””}”(hj-	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mghj*	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjQ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jO  hj6  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j4  hj1  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j/  hj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h MZhj  ubhÐ)”}”(hŒÐThe values of these flags are defined in <linux/ppp-ioctl.h>.  Note
that the values of the SC_MULTILINK, SC_MP_SHORTSEQ and
SC_MP_XSHORTSEQ bits are ignored if the CONFIG_PPP_MULTILINK option
is not selected.”h]”hŒÐThe values of these flags are defined in <linux/ppp-ioctl.h>.  Note
that the values of the SC_MULTILINK, SC_MP_SHORTSEQ and
SC_MP_XSHORTSEQ bits are ignored if the CONFIG_PPP_MULTILINK option
is not selected.”…””}”(hj`	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mjhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXž  PPPIOCGFLAGS returns the value of the status/control flags for the
interface unit.  The argument should point to an int where the ioctl
will store the flags value.  As well as the values listed above for
PPPIOCSFLAGS, the following bits may be set in the returned value:

      ================        =========================================
      SC_COMP_RUN             CCP compressor is running
      SC_DECOMP_RUN           CCP decompressor is running
      SC_DC_ERROR             CCP decompressor detected non-fatal error
      SC_DC_FERROR            CCP decompressor detected fatal error
      ================        =========================================
”h]”(hÐ)”}”(hX  PPPIOCGFLAGS returns the value of the status/control flags for the
interface unit.  The argument should point to an int where the ioctl
will store the flags value.  As well as the values listed above for
PPPIOCSFLAGS, the following bits may be set in the returned value:”h]”hX  PPPIOCGFLAGS returns the value of the status/control flags for the
interface unit.  The argument should point to an int where the ioctl
will store the flags value.  As well as the values listed above for
PPPIOCSFLAGS, the following bits may be set in the returned value:”…””}”(hjx	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mohjt	  ubhÊ)”}”(hXj  ================        =========================================
SC_COMP_RUN             CCP compressor is running
SC_DECOMP_RUN           CCP decompressor is running
SC_DC_ERROR             CCP decompressor detected non-fatal error
SC_DC_FERROR            CCP decompressor detected fatal error
================        =========================================
”h]”j0  )”}”(hhh]”j5  )”}”(hhh]”(j:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j9  hj	  ubj:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K)uh1j9  hj	  ubjP  )”}”(hhh]”(jU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_COMP_RUN”h]”hŒSC_COMP_RUN”…””}”(hj­	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Muhjª	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj§	  ubjZ  )”}”(hhh]”hÐ)”}”(hŒCCP compressor is running”h]”hŒCCP compressor is running”…””}”(hjÄ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MuhjÁ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj§	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hj¤	  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_DECOMP_RUN”h]”hŒSC_DECOMP_RUN”…””}”(hjä	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mvhjá	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÞ	  ubjZ  )”}”(hhh]”hÐ)”}”(hŒCCP decompressor is running”h]”hŒCCP decompressor is running”…””}”(hjû	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mvhjø	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjÞ	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hj¤	  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_DC_ERROR”h]”hŒSC_DC_ERROR”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mwhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj
  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ)CCP decompressor detected non-fatal error”h]”hŒ)CCP decompressor detected non-fatal error”…””}”(hj2
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mwhj/
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hj¤	  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒSC_DC_FERROR”h]”hŒSC_DC_FERROR”…””}”(hjR
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MxhjO
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjL
  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ%CCP decompressor detected fatal error”h]”hŒ%CCP decompressor detected fatal error”…””}”(hji
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mxhjf
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjL
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hj¤	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jO  hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j4  hjŠ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j/  hj†	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Mthjt	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXÖ  PPPIOCSCOMPRESS sets the parameters for packet compression or
decompression.  The argument should point to a ppp_option_data
structure (defined in <linux/ppp-ioctl.h>), which contains a
pointer/length pair which should describe a block of memory
containing a CCP option specifying a compression method and its
parameters.  The ppp_option_data struct also contains a ``transmit``
field.  If this is 0, the ioctl will affect the receive path,
otherwise the transmit path.
”h]”hÐ)”}”(hXÕ  PPPIOCSCOMPRESS sets the parameters for packet compression or
decompression.  The argument should point to a ppp_option_data
structure (defined in <linux/ppp-ioctl.h>), which contains a
pointer/length pair which should describe a block of memory
containing a CCP option specifying a compression method and its
parameters.  The ppp_option_data struct also contains a ``transmit``
field.  If this is 0, the ioctl will affect the receive path,
otherwise the transmit path.”h]”(hXn  PPPIOCSCOMPRESS sets the parameters for packet compression or
decompression.  The argument should point to a ppp_option_data
structure (defined in <linux/ppp-ioctl.h>), which contains a
pointer/length pair which should describe a block of memory
containing a CCP option specifying a compression method and its
parameters.  The ppp_option_data struct also contains a ”…””}”(hj¦
  hžhhŸNh Nubjï  )”}”(hŒ``transmit``”h]”hŒtransmit”…””}”(hj®
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj¦
  ubhŒ[
field.  If this is 0, the ioctl will affect the receive path,
otherwise the transmit path.”…””}”(hj¦
  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M{hj¢
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hŒdPPPIOCGUNIT returns, in the int pointed to by the argument, the unit
number of this interface unit.
”h]”hÐ)”}”(hŒcPPPIOCGUNIT returns, in the int pointed to by the argument, the unit
number of this interface unit.”h]”hŒcPPPIOCGUNIT returns, in the int pointed to by the argument, the unit
number of this interface unit.”…””}”(hjÐ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M„hjÌ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXs  PPPIOCSDEBUG sets the debug flags for the interface to the value in
the int pointed to by the argument.  Only the least significant bit
is used; if this is 1 the generic layer will print some debug
messages during its operation.  This is only intended for debugging
the generic PPP layer code; it is generally not helpful for working
out why a PPP connection is failing.
”•gA      h]”hÐ)”}”(hXr  PPPIOCSDEBUG sets the debug flags for the interface to the value in
the int pointed to by the argument.  Only the least significant bit
is used; if this is 1 the generic layer will print some debug
messages during its operation.  This is only intended for debugging
the generic PPP layer code; it is generally not helpful for working
out why a PPP connection is failing.”h]”hXr  PPPIOCSDEBUG sets the debug flags for the interface to the value in
the int pointed to by the argument.  Only the least significant bit
is used; if this is 1 the generic layer will print some debug
messages during its operation.  This is only intended for debugging
the generic PPP layer code; it is generally not helpful for working
out why a PPP connection is failing.”…””}”(hjè
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M‡hjä
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hŒ^PPPIOCGDEBUG returns the debug flags for the interface in the int
pointed to by the argument.
”h]”hÐ)”}”(hŒ]PPPIOCGDEBUG returns the debug flags for the interface in the int
pointed to by the argument.”h]”hŒ]PPPIOCGDEBUG returns the debug flags for the interface in the int
pointed to by the argument.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MŽhjü
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXÚ  PPPIOCGIDLE returns the time, in seconds, since the last data
packets were sent and received.  The argument should point to a
ppp_idle structure (defined in <linux/ppp_defs.h>).  If the
CONFIG_PPP_FILTER option is enabled, the set of packets which reset
the transmit and receive idle timers is restricted to those which
pass the ``active`` packet filter.
Two versions of this command exist, to deal with user space
expecting times as either 32-bit or 64-bit time_t seconds.
”h]”hÐ)”}”(hXÙ  PPPIOCGIDLE returns the time, in seconds, since the last data
packets were sent and received.  The argument should point to a
ppp_idle structure (defined in <linux/ppp_defs.h>).  If the
CONFIG_PPP_FILTER option is enabled, the set of packets which reset
the transmit and receive idle timers is restricted to those which
pass the ``active`` packet filter.
Two versions of this command exist, to deal with user space
expecting times as either 32-bit or 64-bit time_t seconds.”h]”(hXI  PPPIOCGIDLE returns the time, in seconds, since the last data
packets were sent and received.  The argument should point to a
ppp_idle structure (defined in <linux/ppp_defs.h>).  If the
CONFIG_PPP_FILTER option is enabled, the set of packets which reset
the transmit and receive idle timers is restricted to those which
pass the ”…””}”(hj  hžhhŸNh Nubjï  )”}”(hŒ
``active``”h]”hŒactive”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hj  ubhŒ† packet filter.
Two versions of this command exist, to deal with user space
expecting times as either 32-bit or 64-bit time_t seconds.”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M‘hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hX®  PPPIOCSMAXCID sets the maximum connection-ID parameter (and thus the
number of connection slots) for the TCP header compressor and
decompressor.  The lower 16 bits of the int pointed to by the
argument specify the maximum connection-ID for the compressor.  If
the upper 16 bits of that int are non-zero, they specify the maximum
connection-ID for the decompressor, otherwise the decompressor's
maximum connection-ID is set to 15.
”h]”hÐ)”}”(hX­  PPPIOCSMAXCID sets the maximum connection-ID parameter (and thus the
number of connection slots) for the TCP header compressor and
decompressor.  The lower 16 bits of the int pointed to by the
argument specify the maximum connection-ID for the compressor.  If
the upper 16 bits of that int are non-zero, they specify the maximum
connection-ID for the decompressor, otherwise the decompressor's
maximum connection-ID is set to 15.”h]”hX¯  PPPIOCSMAXCID sets the maximum connection-ID parameter (and thus the
number of connection slots) for the TCP header compressor and
decompressor.  The lower 16 bits of the int pointed to by the
argument specify the maximum connection-ID for the compressor.  If
the upper 16 bits of that int are non-zero, they specify the maximum
connection-ID for the decompressor, otherwise the decompressorâ€™s
maximum connection-ID is set to 15.”…””}”(hjB  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mšhj>  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXA  PPPIOCSNPMODE sets the network-protocol mode for a given network
protocol.  The argument should point to an npioctl struct (defined
in <linux/ppp-ioctl.h>).  The ``protocol`` field gives the PPP protocol
number for the protocol to be affected, and the ``mode`` field
specifies what to do with packets for that protocol:

      =============   ==============================================
      NPMODE_PASS     normal operation, transmit and receive packets
      NPMODE_DROP     silently drop packets for this protocol
      NPMODE_ERROR    drop packets and return an error on transmit
      NPMODE_QUEUE    queue up packets for transmit, drop received
                      packets
      =============   ==============================================

At present NPMODE_ERROR and NPMODE_QUEUE have the same effect as
NPMODE_DROP.
”h]”(hÐ)”}”(hX?  PPPIOCSNPMODE sets the network-protocol mode for a given network
protocol.  The argument should point to an npioctl struct (defined
in <linux/ppp-ioctl.h>).  The ``protocol`` field gives the PPP protocol
number for the protocol to be affected, and the ``mode`` field
specifies what to do with packets for that protocol:”h]”(hŒ¢PPPIOCSNPMODE sets the network-protocol mode for a given network
protocol.  The argument should point to an npioctl struct (defined
in <linux/ppp-ioctl.h>).  The ”…””}”(hjZ  hžhhŸNh Nubjï  )”}”(hŒ``protocol``”h]”hŒprotocol”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjZ  ubhŒN field gives the PPP protocol
number for the protocol to be affected, and the ”…””}”(hjZ  hžhhŸNh Nubjï  )”}”(hŒ``mode``”h]”hŒmode”…””}”(hjt  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjZ  ubhŒ; field
specifies what to do with packets for that protocol:”…””}”(hjZ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¢hjV  ubhÊ)”}”(hX‡  =============   ==============================================
NPMODE_PASS     normal operation, transmit and receive packets
NPMODE_DROP     silently drop packets for this protocol
NPMODE_ERROR    drop packets and return an error on transmit
NPMODE_QUEUE    queue up packets for transmit, drop received
                packets
=============   ==============================================
”h]”j0  )”}”(hhh]”j5  )”}”(hhh]”(j:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j9  hj“  ubj:  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K.uh1j9  hj“  ubjP  )”}”(hhh]”(jU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒNPMODE_PASS”h]”hŒNPMODE_PASS”…””}”(hj³  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M©hj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj­  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ.normal operation, transmit and receive packets”h]”hŒ.normal operation, transmit and receive packets”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M©hjÇ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj­  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjª  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒNPMODE_DROP”h]”hŒNPMODE_DROP”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mªhjç  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjä  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ'silently drop packets for this protocol”h]”hŒ'silently drop packets for this protocol”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Mªhjþ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjä  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjª  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒNPMODE_ERROR”h]”hŒNPMODE_ERROR”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M«hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ,drop packets and return an error on transmit”h]”hŒ,drop packets and return an error on transmit”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M«hj5  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjª  ubjU  )”}”(hhh]”(jZ  )”}”(hhh]”hÐ)”}”(hŒNPMODE_QUEUE”h]”hŒNPMODE_QUEUE”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¬hjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjR  ubjZ  )”}”(hhh]”hÐ)”}”(hŒ4queue up packets for transmit, drop received
packets”h]”hŒ4queue up packets for transmit, drop received
packets”…””}”(hjo  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¬hjl  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjR  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jT  hjª  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jO  hj“  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1j4  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j/  hjŒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h M¨hjV  ubhÐ)”}”(hŒMAt present NPMODE_ERROR and NPMODE_QUEUE have the same effect as
NPMODE_DROP.”h]”hŒMAt present NPMODE_ERROR and NPMODE_QUEUE have the same effect as
NPMODE_DROP.”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M°hjV  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hX*  PPPIOCGNPMODE returns the network-protocol mode for a given
protocol.  The argument should point to an npioctl struct with the
``protocol`` field set to the PPP protocol number for the protocol of
interest.  On return the ``mode`` field will be set to the network-
protocol mode for that protocol.
”h]”hÐ)”}”(hX)  PPPIOCGNPMODE returns the network-protocol mode for a given
protocol.  The argument should point to an npioctl struct with the
``protocol`` field set to the PPP protocol number for the protocol of
interest.  On return the ``mode`` field will be set to the network-
protocol mode for that protocol.”h]”(hŒPPPIOCGNPMODE returns the network-protocol mode for a given
protocol.  The argument should point to an npioctl struct with the
”…””}”(hjº  hžhhŸNh Nubjï  )”}”(hŒ``protocol``”h]”hŒprotocol”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjº  ubhŒS field set to the PPP protocol number for the protocol of
interest.  On return the ”…””}”(hjº  hžhhŸNh Nubjï  )”}”(hŒ``mode``”h]”hŒmode”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjº  ubhŒC field will be set to the network-
protocol mode for that protocol.”…””}”(hjº  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M³hj¶  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hX×  PPPIOCSPASS and PPPIOCSACTIVE set the ``pass`` and ``active`` packet
filters.  These ioctls are only available if the CONFIG_PPP_FILTER
option is selected.  The argument should point to a sock_fprog
structure (defined in <linux/filter.h>) containing the compiled BPF
instructions for the filter.  Packets are dropped if they fail the
``pass`` filter; otherwise, if they fail the ``active`` filter they are
passed but they do not reset the transmit or receive idle timer.
”h]”hÐ)”}”(hXÖ  PPPIOCSPASS and PPPIOCSACTIVE set the ``pass`` and ``active`` packet
filters.  These ioctls are only available if the CONFIG_PPP_FILTER
option is selected.  The argument should point to a sock_fprog
structure (defined in <linux/filter.h>) containing the compiled BPF
instructions for the filter.  Packets are dropped if they fail the
``pass`` filter; otherwise, if they fail the ``active`` filter they are
passed but they do not reset the transmit or receive idle timer.”h]”(hŒ&PPPIOCSPASS and PPPIOCSACTIVE set the ”…””}”(hjö  hžhhŸNh Nubjï  )”}”(hŒ``pass``”h]”hŒpass”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjö  ubhŒ and ”…””}”(hjö  hžhhŸNh Nubjï  )”}”(hŒ
``active``”h]”hŒactive”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjö  ubhX   packet
filters.  These ioctls are only available if the CONFIG_PPP_FILTER
option is selected.  The argument should point to a sock_fprog
structure (defined in <linux/filter.h>) containing the compiled BPF
instructions for the filter.  Packets are dropped if they fail the
”…””}”(hjö  hžhhŸNh Nubjï  )”}”(hŒ``pass``”h]”hŒpass”…””}”(hj"  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjö  ubhŒ% filter; otherwise, if they fail the ”…””}”(hjö  hžhhŸNh Nubjï  )”}”(hŒ
``active``”h]”hŒactive”…””}”(hj4  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jî  hjö  ubhŒQ filter they are
passed but they do not reset the transmit or receive idle timer.”…””}”(hjö  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h M¹hjò  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubj#  )”}”(hXo  PPPIOCSMRRU enables or disables multilink processing for received
packets and sets the multilink MRRU (maximum reconstructed receive
unit).  The argument should point to an int containing the new MRRU
value.  If the MRRU value is 0, processing of received multilink
fragments is disabled.  This ioctl is only available if the
CONFIG_PPP_MULTILINK option is selected.
”h]”hÐ)”}”(hXn  PPPIOCSMRRU enables or disables multilink processing for received
packets and sets the multilink MRRU (maximum reconstructed receive
unit).  The argument should point to an int containing the new MRRU
value.  If the MRRU value is 0, processing of received multilink
fragments is disabled.  This ioctl is only available if the
CONFIG_PPP_MULTILINK option is selected.”h]”hXn  PPPIOCSMRRU enables or disables multilink processing for received
packets and sets the multilink MRRU (maximum reconstructed receive
unit).  The argument should point to an int containing the new MRRU
value.  If the MRRU value is 0, processing of received multilink
fragments is disabled.  This ioctl is only available if the
CONFIG_PPP_MULTILINK option is selected.”…””}”(hjV  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÁhjR  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j"  hjþ  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jä  jå  uh1j  hŸh³h MRhj¹  hžhubhÐ)”}”(hŒLast modified: 7-feb-2002”h]”hŒLast modified: 7-feb-2002”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h MÈhj¹  hžhubeh}”(h]”Œinterface-to-pppd”ah ]”h"]”Œinterface to pppd”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kûubeh}”(h]”Œ(ppp-generic-driver-and-channel-interface”ah ]”h"]”Œ(ppp generic driver and channel interface”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”jY  Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j°  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j‹  jˆ  j8  j5  j‰  j†  j¶  j³  jƒ  j€  uŒ	nametypes”}”(j‹  ‰j8  ‰j‰  ‰j¶  ‰jƒ  ‰uh}”(jˆ  h¶j5  j  j†  j;  j³  jŒ  j€  j¹  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.