| ppp.8 (6059) | ppp.8 (6735) |
|---|---|
| 1.\" manual page [] for ppp 0.93 2.\" $Id:$ | 1.\" manual page [] for ppp 0.94 beta2 + alpha 2.\" $Id: ppp.8,v 1.1.1.1 1995/01/31 06:29:58 amurai Exp $ |
| 3.\" SH section heading 4.\" SS subsection heading 5.\" LP paragraph 6.\" IP indented paragraph 7.\" TP hanging label 8.TH PPP 8 9.SH NAME 10ppp \- Point to Point Protocol (aka iijppp) 11.SH SYNOPSIS 12.B ppp 13[ 14.I -auto | -direct -dedicated 15] [ 16.I system 17] 18.SH DESCRIPTION 19.LP | 3.\" SH section heading 4.\" SS subsection heading 5.\" LP paragraph 6.\" IP indented paragraph 7.\" TP hanging label 8.TH PPP 8 9.SH NAME 10ppp \- Point to Point Protocol (aka iijppp) 11.SH SYNOPSIS 12.B ppp 13[ 14.I -auto | -direct -dedicated 15] [ 16.I system 17] 18.SH DESCRIPTION 19.LP |
| 20 This is user process \fIPPP\fR software package. Normally, \fIPPP\fR is implemented as a part of kernel and hard to debug and/or modify its behavior. However, in this implementation, \fIPPP\fR is implemented as a user process with the help of tunnel device driver. | 20This is user process \fIPPP\fR software package. Normally, \fIPPP\fR 21is implemented as a part of kernel and hard to debug and/or modify its 22behavior. However, in this implementation, \fIPPP\fR is implemented as 23a user process with the help of tunnel device driver. |
| 21.LP 22 23.SH Major Features 24 25.TP 2 | 24.LP 25 26.SH Major Features 27 28.TP 2 |
| 26o 27Provide interactive user interface. Using its command mode, user can easily enter commands to establish the connection with the peer, check the status of connection, and close the connection. 28 | 29o Provide interactive user interface. Using its command mode, user can 30easily enter commands to establish the connection with the peer, check 31the status of connection, and close the connection. And now, all 32functions has password protected if describe your hostname/password in 33secret file or exist secret file itself. 34 |
| 29.TP 2 | 35.TP 2 |
| 30o 31Supports both of manual and automatic dialing. Interactive mode has ``term'' command which enables you to talk to your modem directory. When your modem is connected to the peer, and it starts to speak \fIPPP\fR, \fIPPP\fR software detects it and turns into packet mode automatically. Once you have convinced how to connect with the peer, you can write chat script to define necessary dialing and login procedure for later convenience. | 36o Supports both of manual and automatic dialing. Interactive mode has 37``term'' command which enables you to talk to your modem 38directory. When your modem is connected to the peer, and it starts to 39speak \fIPPP\fR, \fIPPP\fR software detects it and turns into packet 40mode automatically. Once you have convinced how to connect with the 41peer, you can write chat script to define necessary dialing and login 42procedure for later convenience. 43 |
| 32.TP 2 | 44.TP 2 |
| 33o 34Supports on-demand dialup capability. By using auto mode, \fIPPP\fR program will act as a daemon and wait for the packet send to the peer. Once packet is found, daemon automatically dials and establish the connection. | 45o Supports on-demand dialup capability. By using auto mode, \fIPPP\fR 46program will act as a daemon and wait for the packet send to the peer. 47Once packet is found, daemon automatically dials and establish the 48connection. |
| 35 36.TP 2 37o | 49 50.TP 2 51o |
| 38Can act as server which accept incoming \fIPPP\fR connection. 39 | 52Can act as server which accept incoming \fIPPP\fR connection. 53 |
| 40.TP 2 41o 42Supports PAP and CHAP authentification. 43 44.TP 2 | 54.TP 2 55o 56Supports PAP and CHAP authentification. 57 58.TP 2 |
| 45o 46Supports packet filtering. User can define three kinds of filters; ifilter for incoming packet, ofilter for outgoing packet and dfilter to define dialing trigger packet. | 59o 60Supports Proxy Arp. |
| 47 48.TP 2 | 61 62.TP 2 |
| 49o 50Tunnel driver supports bpf. That is, user can use tcpdump to check packet flow over the \fIPPP\fR link. | 63o Supports packet filtering. User can define four kinds of filters; 64ifilter for incoming packet, ofilter for outgoing packet, dfilter to 65define dialing trigger packet and afilter to keep alive a connection 66by trigger packet. |
| 51 52.TP 2 | 67 68.TP 2 |
| 69o Tunnel driver supports bpf. That is, user can use tcpdump to check 70packet flow over the \fIPPP\fR link. 71 72.TP 2 |
|
| 53o 54Supports \fIPPP\fR over TCP capability. 55 56.TP 2 57o 58Supports IETF draft Predictor-1 compression. 59 60.TP 2 | 73o 74Supports \fIPPP\fR over TCP capability. 75 76.TP 2 77o 78Supports IETF draft Predictor-1 compression. 79 80.TP 2 |
| 61o 62Runs under BSDI-1.1 and FreeBSD-1.1. Patch for NeXTSTEP 3.2 is also available on the net. | 81o Runs under BSDI-1.1 and FreeBSD-1.1. Patch for NeXTSTEP 3.2 is also 82available on the net. |
| 63 64.SH MANUAL DIALING | 83 84.SH MANUAL DIALING |
| 65.LP | |
| 66 67 % ppp 68 User Process PPP written by Toshiharu OHNO. | 85 86 % ppp 87 User Process PPP written by Toshiharu OHNO. |
| 88 -- If you write your hostname and password in ppp.secret, 89 you can't do anything even quit command -- 90 ppp on tama> quit 91 what ? 92 ppp on tama> pass <password> |
|
| 69 -- You can specify modem and device name using following commands. | 93 -- You can specify modem and device name using following commands. |
| 70 ppp> set line /dev/cua01 71 ppp> set speed 38400 72 ppp> set parity even 73 ppp> show modem | 94 ppp ON tama> set line /dev/cua01 95 ppp ON tama> set speed 38400 96 ppp ON tama> set parity even 97 ppp ON tama> show modem |
| 74 -- Modem related parameters are shown in here | 98 -- Modem related parameters are shown in here |
| 75 ppp> | 99 ppp ON tama> |
| 76 -- Use term command to talk with your modem | 100 -- Use term command to talk with your modem |
| 77 ppp> term | 101 ppp ON tama> term |
| 78 at 79 OK 80 atdt123456 81 CONNECT 82 83 login: ppp 84 Password: 85 -- PPP started in remote side --- 86 87 -- When peer start to speak PPP, the program will detect it 88 -- automatically and back to command mode. | 102 at 103 OK 104 atdt123456 105 CONNECT 106 107 login: ppp 108 Password: 109 -- PPP started in remote side --- 110 111 -- When peer start to speak PPP, the program will detect it 112 -- automatically and back to command mode. |
| 89 ppp> | 113 ppp on tama> |
| 90 \fBPPP\fR> 91 92 -- NOW, you are get connected !! Note that prompt has changed to 93 -- capital letters | 114 \fBPPP\fR> 115 116 -- NOW, you are get connected !! Note that prompt has changed to 117 -- capital letters |
| 94 PPP> show lcp | 118 PPP ON tama> show lcp |
| 95 96 -- You'll see LCP status -- 97 | 119 120 -- You'll see LCP status -- 121 |
| 98 PPP> show ipcp | 122 PPP ON tama> show ipcp |
| 99 100 -- You'll see IPCP status -- 101 -- At this point, your machine has host route to the peer. 102 -- If your want to add default route entry, then enter 103 | 123 124 -- You'll see IPCP status -- 125 -- At this point, your machine has host route to the peer. 126 -- If your want to add default route entry, then enter 127 |
| 104 PPP> add 0 0 HISADDR | 128 PPP ON tama> add 0 0 HISADDR |
| 105 106 -- Here string `HISADDR' represents IP address of connected peer. 107 | 129 130 -- Here string `HISADDR' represents IP address of connected peer. 131 |
| 108 PPP> | 132 PPP ON tama> |
| 109 -- Use applications (i.e. ping, telnet, ftp) in other windows 110 | 133 -- Use applications (i.e. ping, telnet, ftp) in other windows 134 |
| 111 PPP> show log | 135 PPP ON tama> show log |
| 112 113 -- Gives you some logging messages 114 | 136 137 -- Gives you some logging messages 138 |
| 115 PPP> close | 139 PPP ON tama> close |
| 116 117 -- Connection is closed, and modem will be hanged. 118 | 140 141 -- Connection is closed, and modem will be hanged. 142 |
| 119 ppp> quit | 143 ppp ON tama> quit |
| 120 % 121.LP | 144 % 145.LP |
| 146 |
|
| 122.SH AUTOMATIC DIALING 123 124.LP | 147.SH AUTOMATIC DIALING 148 149.LP |
| 125To use automatic dialing, you must prepare Dial and Login chat script.See example definition found in ppp.conf.sample(Format of ppp.conf is pretty simple.) 126.LP | 150To use automatic dialing, you must prepare Dial and Login chat script. 151See example definition found in ppp.conf.sample (Format of ppp.conf is 152pretty simple.) |
| 127 128.TP 2 129o 130Each line contains one command, label or comment. 131 132.TP 2 133o 134Line stating with # is treated as a comment line. 135 136.TP 2 137o 138Label name has to start from first column and should be followed by colon (:). 139 140.TP 2 141o 142Command line must contains space or tab at first column. 143 144.LP | 153 154.TP 2 155o 156Each line contains one command, label or comment. 157 158.TP 2 159o 160Line stating with # is treated as a comment line. 161 162.TP 2 163o 164Label name has to start from first column and should be followed by colon (:). 165 166.TP 2 167o 168Command line must contains space or tab at first column. 169 170.LP |
| 145If ppp.conf is ready, specify destination label name when you invoke ppp. Commands associated with destination label is executed when ppp command is invoked. Note that commands associated with ``default'' label is ALWAYS executed. | 171If ppp.conf is ready, specify destination label name when you invoke 172ppp. Commands associated with destination label is executed when ppp 173command is invoked. Note that commands associated with ``default'' 174label is ALWAYS executed. |
| 146 147Once connection is made, you'll find that prompt is changed to 148 149 capital \fIPPP\fR>. 150 151 % ppp pm2 152 ... | 175 176Once connection is made, you'll find that prompt is changed to 177 178 capital \fIPPP\fR>. 179 180 % ppp pm2 181 ... |
| 153 ppp> dial | 182 ppp ON tama> dial |
| 154 dial OK! 155 login OK! | 183 dial OK! 184 login OK! |
| 156 PPP> | 185 PPP ON tama> |
| 157 | 186 |
| 158If ppp.linkup file is available, its contents are executed when \fIPPP\fR link is connected. See example which add default route. The string HISADDR matches with IP address of connected peer. 159.LP | 187If ppp.linkup file is available, its contents are executed when 188\fIPPP\fR link is connected. See example which add default route. 189The string HISADDR matches with IP address of connected peer. |
| 160 | 190 |
| 191 |
|
| 161.SH DAIL ON DEMAND 162 163.LP | 192.SH DAIL ON DEMAND 193 194.LP |
| 164 To play with demand dialing, you must use -auto option. Also, you must specify destination label with proper setup in ppp.conf. It must contain ``ifaddr'' command to define peer's IP address. (refer /etc/ppp/ppp.conf.sample) 165.LP | 195 To play with demand dialing, you must use -auto option. Also, you 196must specify destination label with proper setup in ppp.conf. It must 197contain ``ifaddr'' command to define peer's IP address. (refer 198/etc/ppp/ppp.conf.sample) |
| 166 | 199 |
| 200 |
|
| 167 % ppp -auto pm2demand 168 ... 169 % 170 171.LP | 201 % ppp -auto pm2demand 202 ... 203 % 204 205.LP |
| 172When -auto is specified, \fIPPP\fR program works as a daemon. But, you are still able to use command features to check its behavior. 173.LP | 206When -auto is specified, \fIPPP\fR program works as a daemon. But, 207you are still able to use command features to check its behavior. |
| 174 | 208 |
| 209 |
|
| 175 % telnet localhost 3000 176 ... | 210 % telnet localhost 3000 211 ... |
| 177 PPP> show ipcp | 212 PPP on tama> show ipcp |
| 178 .... 179 180.LP | 213 .... 214 215.LP |
| 181 Each ppp has associated port number, which is computed as "3000 + tunnel_device_number". If 3000 is not good base number, edit defs.h. When packet toward to remote network is detected, \fIPPP\fR will take dialing action and try to connect with the peer. If dialing is failed, program will wait for 30 seconds. Once this hold time expired, another trigger packet cause dialing action. Note that automatic re-dialing is NOT implemented. 182.LP | 216 Each ppp has associated port number, which is computed as "3000 + 217tunnel_device_number". If 3000 is not good base number, edit defs.h. 218When packet toward to remote network is detected, \fIPPP\fR will take 219dialing action and try to connect with the peer. If dialing is failed, 220program will wait for 30 seconds. Once this hold time expired, another 221trigger packet cause dialing action. Note that automatic re-dialing is 222NOT implemented. |
| 183 | 223 |
| 224 |
|
| 184 To terminate program, use 185 | 225 To terminate program, use 226 |
| 186 PPP> close | 227 PPP on tama> close |
| 187 \fBppp\fR> quit all 188 189.LP 190 Simple ``quit'' command will terminates telnet connection, but \fIPPP\fR program itself is not terminated. You must use ``quit all'' to terminate the program running as daemon. 191.LP 192 193.SH PACKET FILTERING 194 --- 91 unchanged lines hidden (view full) --- 286 287.LP 288 To disable CCP/predictor function completely, use ``disable pred'' and ``deny pred'' command. 289.LP 290 291.SH Controlling IP address 292 293.LP | 228 \fBppp\fR> quit all 229 230.LP 231 Simple ``quit'' command will terminates telnet connection, but \fIPPP\fR program itself is not terminated. You must use ``quit all'' to terminate the program running as daemon. 232.LP 233 234.SH PACKET FILTERING 235 --- 91 unchanged lines hidden (view full) --- 327 328.LP 329 To disable CCP/predictor function completely, use ``disable pred'' and ``deny pred'' command. 330.LP 331 332.SH Controlling IP address 333 334.LP |
| 294 \fIPPP\fR uses IPCP to negotiate IP addresses. Each side of node informs IP address that willing to use to the peer, and if requested IP address is acceptable, \fIPPP\fR returns ACK to requester. Otherwise, \fIPPP\fR returns NAK to suggest the peer to use different IP address. When both side of nodes agrees to accept the received request (and send ACK), IPCP is reached to open state and network level connection is established. 295.LP | 335 \fIPPP\fR uses IPCP to negotiate IP addresses. Each side of node 336informs IP address that willing to use to the peer, and if requested 337IP address is acceptable, \fIPPP\fR returns ACK to 338requester. Otherwise, \fIPPP\fR returns NAK to suggest the peer to use 339different IP address. When both side of nodes agrees to accept the 340received request (and send ACK), IPCP is reached to open state and 341network level connection is established. |
| 296 | 342 |
| 343 |
|
| 297.LP | 344.LP |
| 298 To control, this IPCP behavior, this implementation has ``set ifaddr'' to define MY and HIS IP address. 299.LP | 345 To control, this IPCP behavior, this implementation has ``set 346ifaddr'' to define MY and HIS IP address. |
| 300 | 347 |
| 348 |
|
| 301.TP3 302ifaddr src_addr dst_addr 303 304.LP | 349.TP3 350ifaddr src_addr dst_addr 351 352.LP |
| 305 Where, src_addr is the IP address that my side is willing to use, and dst_addr is the IP address which his side should use. | 353Where, src_addr is the IP address that my side is willing to use, and 354dst_addr is the IP address which his side should use. |
| 306.LP 307 308.TP3 309ifaddr 192.244.177.38 192.244.177.2 310 311For example, above specification means 312 313.TP | 355.LP 356 357.TP3 358ifaddr 192.244.177.38 192.244.177.2 359 360For example, above specification means 361 362.TP |
| 314o 315I strongly want to use 192.244.177.38 as my side. I'll disagree when peer suggest me to use other addresses. | 363o I strongly want to use 192.244.177.38 as my side. I'll disagree when 364peer suggest me to use other addresses. |
| 316 317.TP 2 | 365 366.TP 2 |
| 318o 319I strongly insists peer to use 192.244.177.2 as his side address. I don't permit him to use any IP address but 192.244.177.2. When peer request other IP address, I always suggest him to use 192.244.177.2. | 367o I strongly insists peer to use 192.244.177.2 as his side address. I 368don't permit him to use any IP address but 192.244.177.2. When peer 369request other IP address, I always suggest him to use 192.244.177.2. |
| 320 321.LP 322 This is all right, when each side has pre-determined IP address. | 370 371.LP 372 This is all right, when each side has pre-determined IP address. |
| 323However, it is often the case one side is acting as a server which 324controls IP address and the other side should obey the direction from him. 325In order to allow more flexible behavior, `ifaddr' command allows user to specify IP address more loosely. 326.LP | 373However, it is often the case one side is acting as a server which 374controls IP address and the other side should obey the direction from 375him. In order to allow more flexible behavior, `ifaddr' command 376allows user to specify IP address more loosely. |
| 327 | 377 |
| 378 |
|
| 328.TP 2 329ifaddr 192.244.177.38/24 192.244.177.2/20 330 | 379.TP 2 380ifaddr 192.244.177.38/24 192.244.177.2/20 381 |
| 331 Number followed by slash (/) represents number of bits significant in IP address. That is, this example means | 382 Number followed by slash (/) represents number of bits significant in 383IP address. That is, this example means |
| 332 333.TP 2 | 384 385.TP 2 |
| 334o 335I'd like to use 192.244.177.38 as my side address, if it is possible. But I also accept any IP address between 192.244.177.0 and 192.244.177.255. | 386o I'd like to use 192.244.177.38 as my side address, if it is 387possible. But I also accept any IP address between 192.244.177.0 and 388192.244.177.255. |
| 336 337.TP 2 | 389 390.TP 2 |
| 338o 339I'd like to make him to use 192.244.177.2 as his side address. But I also permit him to use any IP address between 192.244.176.0 and 192.244.191.255. | 391o I'd like to make him to use 192.244.177.2 as his side address. But 392I also permit him to use any IP address between 192.244.176.0 and 393192.244.191.255. |
| 340 341 Notes: 342 343.TP 2 | 394 395 Notes: 396 397.TP 2 |
| 344o 345As you may have already noticed, 192.244.177.2 is equivalent to say 192.244.177.2/32. | 398o As you may have already noticed, 192.244.177.2 is equivalent to say 399192.244.177.2/32. |
| 346 347.TP 2 | 400 401.TP 2 |
| 348o 349As an exception, 0 is equivalent to 0.0.0.0/0. Means, I have no idea about IP address and obey what he says. | 402o As an exception, 0 is equivalent to 0.0.0.0/0. Means, I have no idea 403about IP address and obey what he says. |
| 350 351.TP 2 | 404 405.TP 2 |
| 352o 353192.244.177.2/0 means that I'll accept/permit any IP address but I'll try to insist to use 192.244.177.2 at first. | 406o 192.244.177.2/0 means that I'll accept/permit any IP address but 407I'll try to insist to use 192.244.177.2 at first. |
| 354 355.SH Connecting with service provider 356 357.LP 358 1) Describe provider's phone number in DialScript. Use ``set dial'' or 359 ``set phone'' command. 360 361 2) Describle login procedure in LoginScript. Use ``set login'' command. --- 21 unchanged lines hidden (view full) --- 383.B disable chap (or disable pap) 384.TP 3 385.B set authname MyName 386.TP 3 387.B set authkey MyPassword 388.TP 3 389 390.LP | 408 409.SH Connecting with service provider 410 411.LP 412 1) Describe provider's phone number in DialScript. Use ``set dial'' or 413 ``set phone'' command. 414 415 2) Describle login procedure in LoginScript. Use ``set login'' command. --- 21 unchanged lines hidden (view full) --- 437.B disable chap (or disable pap) 438.TP 3 439.B set authname MyName 440.TP 3 441.B set authkey MyPassword 442.TP 3 443 444.LP |
| 391Please refer /etc/ppp/example/ppp.conf.iij for some real examples. | 445Please refer /etc/ppp/ppp.conf.iij for some real examples. |
| 392.LP 393 394.SH Logging facility 395 396.LP | 446.LP 447 448.SH Logging facility 449 450.LP |
| 397 \fI\fIPPP\fR\fR is able to generate following level log info as /var/log/ppp.log 398.LP | 451 \fI\fIPPP\fR\fR is able to generate following level log info as 452/var/log/ppp.log |
| 399 | 453 |
| 454 |
|
| 400.TP 401.B Phase 402Phase transition log output 403.TP 404.B Chat 405Generate Chat script trace log 406.TP 407.B LQM 408Generate LQR report 409.TP 410.B LCP 411Generate LCP/IPCP packet trace 412.TP 413.B TCP/IP 414Dump TCP/IP packet 415.TP | 455.TP 456.B Phase 457Phase transition log output 458.TP 459.B Chat 460Generate Chat script trace log 461.TP 462.B LQM 463Generate LQR report 464.TP 465.B LCP 466Generate LCP/IPCP packet trace 467.TP 468.B TCP/IP 469Dump TCP/IP packet 470.TP |
| 416HDLC | 471.B HDLC |
| 417Dump HDLC packet in hex 418.TP 419.B Async 420Dump async level packet in hex 421 422.LP | 472Dump HDLC packet in hex 473.TP 474.B Async 475Dump async level packet in hex 476 477.LP |
| 423 ``set debug'' command allows you to set logging output level, 424and multiple levels can be specified. 425Default is equivalent to ``set debug phase lcp''. | 478``set debug'' command allows you to set logging output level, and 479multiple levels can be specified. Default is equivalent to ``set 480debug phase lcp''. |
| 426 427.SH For more details 428 429.TP 2 430o 431Please read Japanese doc for complete explanation. 432Well, it is not useful for non-japanese readers, 433but examples in the document may help you to guess. --- 10 unchanged lines hidden (view full) --- 444o 445NetBSD and BSDI-1.0 has been supported in previous release, 446but no longer supported in this release. 447Please contact to author if you need old driver code. 448 449.SH FILES 450.LP 451\fIPPP\fR may refers three files, ppp.conf, ppp.linkup and ppp.secret. | 481 482.SH For more details 483 484.TP 2 485o 486Please read Japanese doc for complete explanation. 487Well, it is not useful for non-japanese readers, 488but examples in the document may help you to guess. --- 10 unchanged lines hidden (view full) --- 499o 500NetBSD and BSDI-1.0 has been supported in previous release, 501but no longer supported in this release. 502Please contact to author if you need old driver code. 503 504.SH FILES 505.LP 506\fIPPP\fR may refers three files, ppp.conf, ppp.linkup and ppp.secret. |
| 452These files are placed in /etc/ppp, 453but user can create his own files under HOME directory as .ppp.conf, 454.ppp.linkup and .ppp.secret. 455the ppp always try to consult to user's personal setup first. | 507These files are placed in /etc/ppp, but user can create his own files 508under HOME directory as .ppp.conf,.ppp.linkup and .ppp.secret.the ppp 509always try to consult to user's personal setup first. |
| 456 457.TP | 510 511.TP |
| 458.B $HOME/ppp/.ppp.[linkup|secret] | 512.B $HOME/ppp/.ppp.[conf|linkup|secret] |
| 459User depend configuration files. 460 461.TP 462.B /etc/ppp/ppp.conf 463System default configuration file. 464 465.TP 466.B /etc/ppp/ppp.secret --- 9 unchanged lines hidden (view full) --- 476.B /var/log/ppp.log 477Logging and debug information file. 478 479.TP 480.B /var/spool/lock/Lck..* 481tty port locking file. 482 483.SH BUGS | 513User depend configuration files. 514 515.TP 516.B /etc/ppp/ppp.conf 517System default configuration file. 518 519.TP 520.B /etc/ppp/ppp.secret --- 9 unchanged lines hidden (view full) --- 530.B /var/log/ppp.log 531Logging and debug information file. 532 533.TP 534.B /var/spool/lock/Lck..* 535tty port locking file. 536 537.SH BUGS |
| 484A Proxy arp is not support, yet. 485The TTS is little bit longer than pppd2.1, it's under improving ;-) | |
| 486 487.SH HISTORY | 538 539.SH HISTORY |
| 488This programm has deliverd into core since FreeBSD-2.1 489by Atsushi Murai (amurai@spec.co.jp). | 540This programm has deliverd into core since FreeBSD-2.1 by Atsushi 541Murai (amurai@spec.co.jp). |
| 490 491.SH AUTHORS 492Toshiharu OHNO (tony-o@iij.ad.jp) | 542 543.SH AUTHORS 544Toshiharu OHNO (tony-o@iij.ad.jp) |