Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Imported Upstream version 3.7.2005-07-09

  • Loading branch information...
commit 4aa1c100d32a28e51365068db9417413b6ce8634 1 parent 949af90
Rolf Leggewie authored

Showing 92 changed files with 14,749 additions and 8,002 deletions. Show diff stats Hide diff stats

  1. +4 0 FAQ/.cvsignore
  2. +1 0  FAQ/i4lfaq-de.sgml
  3. +236 197 FAQ/i4lfaq.sgml
  4. +2 2 Makefile
  5. +1 0  Mini-FAQ/.cvsignore
  6. +2 2 act2000/configure.in
  7. +6 0 avmb1/.cvsignore
  8. +2 2 avmb1/configure.in
  9. +9 0 capi20/.cvsignore
  10. +1 1  capi20/Makefile.am
  11. +504 289 capi20/Makefile.in
  12. +959 982 capi20/aclocal.m4
  13. +80 9 capi20/capi20.c
  14. +64 5 capi20/capifunc.c
  15. +91 8 capi20/capiutils.h
  16. +136 0 capi20/compile
  17. +92 33 capi20/config.guess
  18. +49 8 capi20/config.sub
  19. +1,051 251 capi20/configure
  20. +24 1 capi20/configure.in
  21. +59 1 capi20/convert.c
  22. +2,047 769 capi20/ltmain.sh
  23. +191 21 capi20/missing
  24. +9 0 capifax/.cvsignore
  25. +11 6 capifax/Makefile.in
  26. +23 10 capifax/acinclude.m4
  27. +887 9 capifax/aclocal.m4
  28. +11 1 capifax/capi.c
  29. +5 1 capifax/config.h.in
  30. +160 44 capifax/configure
  31. +4 0 capifax/configure.in
  32. +9 0 capiinfo/.cvsignore
  33. +19 8 capiinfo/capiinfo.c
  34. +8 0 capiinit/.cvsignore
  35. +12 5 capiinit/Makefile.in
  36. +858 9 capiinit/aclocal.m4
  37. +6 1 capiinit/capiinit.c
  38. +54 48 capiinit/configure
  39. +5 1 capiinit/configure.in
  40. +12 1 doc/Configure.help
  41. +8 7 eicon/Makefile.in
  42. +4 2 eicon/configure.in
  43. +3 0  eurofile/.cvsignore
  44. +1 0  eurofile/src/eft/.cvsignore
  45. +2 2 hisax/configure.in
  46. +2 2 icn/configure.in
  47. +1 1  isdnctrl/configure.in
  48. +78 2 isdnlog/.country-alias
  49. +7 0 isdnlog/.cvsignore
  50. +19 0 isdnlog/ChangeLog
  51. +39 10 isdnlog/Makefile.in
  52. +5 0 isdnlog/bin/.cvsignore
  53. +8 1 isdnlog/configure
  54. +5 1 isdnlog/configure.in
  55. +33 3 isdnlog/country-de.dat
  56. +1 0  isdnlog/isdnconf/.cvsignore
  57. +6 0 isdnlog/isdnlog/.cvsignore
  58. +10 0 isdnlog/isdnlog/ChangeLog
  59. +13 3 isdnlog/isdnlog/isdnlog.8.in
  60. +43 4 isdnlog/isdnlog/isdnlog.c
  61. +3 0  isdnlog/isdnrep/.cvsignore
  62. +14 0 isdnlog/isdnrep/ChangeLog
  63. +14 2 isdnlog/isdnrep/isdnrep.1.in
  64. +41 10 isdnlog/isdnrep/opt_time.c
  65. +6 2 isdnlog/isdnrep/rep_main.c
  66. +4,669 1,446 isdnlog/rate-de.dat
  67. +2 0  isdnlog/samples/.cvsignore
  68. +26 20 isdnlog/samples/rate.conf.de
  69. +5 0 isdnlog/tools/.cvsignore
  70. +28 0 isdnlog/tools/ChangeLog
  71. +18 0 isdnlog/tools/cdb/.cvsignore
  72. +1 1  isdnlog/tools/dest.c
  73. +7 0 isdnlog/tools/dest/.cvsignore
  74. +2 1  isdnlog/tools/rate-files.man
  75. +122 43 isdnlog/tools/rate.c
  76. +199 0 isdnlog/tools/rate.conf.5.in
  77. +470 0 isdnlog/tools/rate_skip.c
  78. +46 0 isdnlog/tools/rate_skip.h
  79. +9 4 isdnlog/tools/tools.c
  80. +12 1 isdnlog/tools/tools.h
  81. +7 0 isdnlog/tools/zone/.cvsignore
  82. +26 26 isdnlog/tools/zone/de/code
  83. +1 1  pcbit/configure.in
  84. +1 0  pppdcapiplugin/.cvsignore
  85. +25 4 pppdcapiplugin/capiconn.c
  86. +6 0 rcapid/.cvsignore
  87. +5 5 rcapid/Makefile.in
  88. +1 1  rcapid/aclocal.m4
  89. +982 3,668 rcapid/configure
  90. +4 1 scripts/config.in
  91. +2 0  scripts/defconfig
  92. +3 3 vbox/src/vboxbeep.c
4 FAQ/.cvsignore
... ... @@ -0,0 +1,4 @@
  1 +config.*
  2 +*.html
  3 +*.txt
  4 +Makefile
1  FAQ/i4lfaq-de.sgml
@@ -647,6 +647,7 @@ mit den Patches von Karsten - Kernel 2.0.21, HiSax
647 647 Z.Zt. unterstützen folgende Karten das CAPI 2.0 Interface:
648 648 <itemize>
649 649 <item> die aktive Karte AVM B1.
  650 +<item> die aktiven DIVA Server Karten von Eicon.
650 651 <item> die aktiven Karten von Hypercope (HYSDN Champ2, HYSDN Ergo2,
651 652 HYSDN Metro4)
652 653 <item> die passive FritzCard von AVM. Dazu musst Du jedoch die als
433 FAQ/i4lfaq.sgml
@@ -4,7 +4,7 @@
4 4
5 5 <title>FAQ for isdn4linux
6 6 <author>Matthias Hessler (<tt><htmlurl url="mailto:hessler@isdn4linux.de" name="hessler@isdn4linux.de"></tt>)
7   -<date>v2.0.91, 31. October 2004
  7 +<date>v2.0.98, 8 July 2005
8 8 <abstract>
9 9 If you are reading this FAQ online, you may consider downloading the whole
10 10 thing, and reading it offline (much cheaper). To download the latest
@@ -17,7 +17,7 @@ A German translation of the FAQ is available at:
17 17 This FAQ answers questions that were frequently asked in the newsgroup
18 18 de.alt.comm.isdn4linux. It contains questions any user should
19 19 know about ISDN under Linux using isdn4linux, as well as hints on how
20   -to best make use of all the features isdn4linux provides.
  20 +to best make use of all the features isdn4linux provides.
21 21
22 22 Version 2 of the FAQ is derived from an earlier version which had become
23 23 outdated at the time of this writing. To obtain information on old versions
@@ -63,7 +63,7 @@ from Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
63 63 An electronic version is available from the author.
64 64 </abstract>
65 65
66   -<!-- Table of Content
  66 +<!-- Table of Content
67 67 -->
68 68
69 69 <toc>
@@ -237,7 +237,7 @@ name="fritz@isdn4linux.de"></tt>
237 237 <label id="feature_not">
238 238 <p>
239 239 Some ISDN features are device-specific and cannot be activated by
240   -isdn4linux for other devices, unless isdn4linux were to falsify
  240 +isdn4linux for other devices, unless isdn4linux were to falsify
241 241 the TEI (which would probably confuse the other device).
242 242 Such device-specific ISDN features are, among others: rejection of a
243 243 waiting call, caller id on/off, hold, conference calls, differing COLP/CLRP.
@@ -264,7 +264,7 @@ These encapsulations are possible:
264 264 <item>rawip
265 265 <item>ethernet
266 266 <item>Sync PPP
267   -<item>X.25 (requires 2.1 or newer)
  267 +<item>X.25 (requires 2.1 or newer)
268 268 <item>cisco and cisco-h
269 269 <item>cisco-hk (=cisco with keepalive; requires 2.1 or newer)
270 270 <item>plus a few specialities: have a look at the man pages.
@@ -293,14 +293,18 @@ the other way around. For configuration see question
293 293 <label id="feature_fax">
294 294 <p>
295 295 <itemize>
296   -<item><bf>For all passive cards (except from AVM): NO</bf>. There
297   -was a project working on this rather complicated problem. For more info on
298   -its status have a look at:
  296 +<item><bf>For passive cards: Yes</bf>. Since 2005 the GPL software ivcall
  297 +is able to send and receive voice calls and faxes even via passive cards.
  298 +It makes use of the spandsp library which is part of the Asterisk project.
  299 +You can find it on:
  300 +<tt><url url="http://0pointer.de/lennart/projects/ivcall/"></tt>
  301 +An alternative project working on this problem existed (i4lfax) but has not
  302 +made any progress since 1999. For more info on its status have a look at:
299 303 <tt><url url="http://user.cs.tu-berlin.de/~ulfi/osvisions/i4lsoftfax/i4lfax/"></tt>
300 304 Also, an idea exists to extend the new modular mISDN with layer 2 and layer 3
301 305 protocols for fax. Once this works (e.g. with the Sedlbauer Speedfax card)
302   -then the layer 1 protocol (modulation/demodulation) could be implemented via
303   -the spandsp library which is part of the Asterisk project.
  306 +then the layer 1 protocol (modulation/demodulation) could be also be
  307 +implemented via the spandsp library.
304 308 <item><bf>For passive cards from AVM: Yes</bf>. AVM recently released a
305 309 binary CAPI 2.0 driver which supports faxing. However, the setup is rather
306 310 complicated. Get a start on:
@@ -369,13 +373,20 @@ AT&amp;FS14=10S15=0S18=1&amp;E&lt;your_msn&gt;
369 373 <label id="feature_divert">
370 374 <p>
371 375 Call diversion features have been implemented recently. Use the new
372   -program <tt/divertctrl/. If you make use of capi4linux, then you find a
373   -similar program named <tt/capidivert/ at:
374   -<url url=" http://www.tp1.ruhr-uni-bochum.de/&tilde;kai/i4l/">.
375   -So far there is no howto and only little documentation, so for now this is
376   -something only for the more experienced user.
  376 +program <tt>divertctrl</tt> in conjunction with the HiSax driver.
  377 +
  378 +If you make use of capi4linux, then you find a similar program named
  379 +<tt>capidivert</tt> at:
  380 +<url url="http://www.tp1.ruhr-uni-bochum.de/&tilde;kai/i4l/">.
  381 +For now this is something only for the more experienced user, as so far there
  382 +is no howto and only little documentation, and it is not automatically included
  383 +in most distributions. However, it can be used with active ISDN cards.
377 384
378   -In the Netherlands, the keypad protocol can be used as an alternative.
  385 +In the Netherlands, the keypad protocol can be used as an alternative. To use
  386 +it you just dial with the usual dial command from an ttyI device:
  387 +<code>
  388 +atd*123*0123456789#
  389 +</code>
379 390
380 391 <sect1> feature_ipx: Can I route ipx/spx over ISDN with Linux?
381 392 <label id="feature_ipx">
@@ -392,13 +403,13 @@ broadcasts may cause a dod disaster (see question
392 403 <sect1> feature_2channel: Does isdn4linux support channel bundling?
393 404 <label id="feature_2channel">
394 405 <p>
395   -The current version of isdn4linux support 2 methods of channel
  406 +The current version of isdn4linux support 2 methods of channel
396 407 bundling:
397 408 <itemize>
398 409 <item><bf>MPPP</bf> (based on sync PPP)
399 410 <item><bf>Raw bundling</bf> (configured by so-called slave channels)
400 411 </itemize>
401   -Both variants have their own advantages and disadvantages.
  412 +Both variants have their own advantages and disadvantages.
402 413 See section <ref id="2channel" name="2channel">.
403 414 Bonding (16bit channel) is not supported,
404 415 since it can not work reliably when the dialup connections have deviating
@@ -436,10 +447,13 @@ talks about the dangers of unwanted dialouts: (<ref id="dod" name="dod">).
436 447 via ISDN?
437 448 <label id="feature_sms">
438 449 <p>
439   -Yes, you can use the program <tt/yaps/ to do this. However, due to some
  450 +Yes, you can use the program <tt>yaps</tt> to do this. However, due to some
440 451 pecularities in the SMS-callcenter's ISDN connection, you have to compile the
441   -kernel with the options <tt/Disable send complete/ and
442   -<tt/Disable sending llc/.
  452 +kernel with the options <tt>Disable send complete</tt> and
  453 +<tt>Disable sending llc</tt>. For the new CAPI 2.0 interface a patched
  454 +version of yaps, <tt>capi4yaps</tt>, is available on
  455 +<url url="http://sourceforge.net/projects/capi4yaps/">.
  456 +
443 457 Please note that mainly German providers support sending SMS via ISDN
444 458 connection, in other countries this might not work. Dutch as well as UK
445 459 SMS callcenters seem to not support this feature. Please let me know if
@@ -496,10 +510,10 @@ In dosemu.conf it is enough to enter a virtual com port,
496 510 (for example com2) that can be used with e.g. Telix or
497 511 Terminate: serial { com 2 device /dev/ttyI3 }
498 512 Access with Fossil is possible if fossil.com (included with
499   -dosemu) is started. Tested with the following configurations:
500   -- Kernel 2.0.21, Teles driver incl. Karsten's patches
  513 +dosemu) is started. Tested with the following configurations:
  514 +- Kernel 2.0.21, Teles driver incl. Karsten's patches
501 515 - Kernel 2.0.21, HiSax
502   -</quote>
  516 +</quote>
503 517
504 518 <sect1> feature_capi: Is there a CAPI interface available?
505 519 <label id="feature_capi">
@@ -507,6 +521,7 @@ dosemu) is started. Tested with the following configurations:
507 521 Currently, these cards support the CAPI 2.0 interface:
508 522 <itemize>
509 523 <item> the active card AVM B1.
  524 +<item> the active DIVA Server cards from Eicon.
510 525 <item> the active cards from Hypercope (HYSDN Champ2, HYSDN Ergo2,
511 526 HYSDN Metro4)
512 527 <item> the passive Fritz card from AVM. However, please note that you
@@ -575,7 +590,7 @@ question <ref id="isdnlog_reversedcard" name="isdnlog_reversedcard">.
575 590
576 591 Please note that you may also use the software ISDN Sniffer for this,
577 592 see the German web site
578   -<url url="http://krypt.cs.uni-sb.de/~osk/isdnosk.html">.
  593 +<url url="http://krypt.cs.uni-sb.de/projects/isdnsniffer/">.
579 594
580 595 <sect1> feature_chargeint: Can isdn4linux hang up just before the ISDN
581 596 provider would charge me for another unit?
@@ -643,7 +658,7 @@ Yes, this feature is now being supported by isdnlog. What it does is that
643 658 it allows isdnlog to choose your telephone provider when placing a call
644 659 through your ISDN card, depending on the time of day and the current rate
645 660 information. Since isdnlog 4.16 an external script is called (if configured)
646   -to change various ISP settings (e.g. DNS lookup, proxy setup,...).
  661 +to change various ISP settings (e.g. DNS lookup, proxy setup,...).
647 662
648 663 Note: the ABC-extensions (s. <ref id="docu_abc" name="docu_abc">) must be
649 664 installed. Also, isdnlog should always be running (otherwise your dialout
@@ -686,7 +701,7 @@ We'll see...
686 701 <sect1> docu_first: What documents should I read first?
687 702 <label id="docu_first">
688 703 <p>
689   -<itemize>
  704 +<itemize>
690 705 <item>ISDN kernel subsystem:
691 706 /usr/src/linux/Documentation/isdn/README
692 707 <item>ISDN cards:
@@ -730,18 +745,22 @@ HSCSD aussch&ouml;pfen</tt>
730 745 <item>ct 15/2002, page 204: <tt>Bei Anruf Internet: Handy-Anruf l&ouml;st
731 746 Internet-Einwahl aus</tt>
732 747 <item>ct 3/2004, page 182: <tt>Heimserver im Eigenbau - Teil 4: ISDN-Grundlagen
733   -f&uuml;r Linux</tt>(also contains information about the new mISDN driver).
  748 +f&uuml;r Linux</tt> (also contains information about the new mISDN driver).
734 749 An online version is available on:
735 750 <tt><url url="http://www.heise.de/ct/04/03/182/"></tt>
736 751 <item>ct 9/2004, page 100: <tt>Tux vermittelt - Linux als Telefonanlage mit
737   -VoIP</tt>(refers to software PBX4Linux)
  752 +VoIP</tt> (refers to software PBX4Linux)
  753 +<item>ct 12/2005, page 116: <tt>Guter Stern vom Amt - Asterisk: Linux als
  754 +professionelle Telefonanlage</tt> (refers to PBX software asterisk)
  755 +<item>ct 13/2005, page 216: <tt>Ein Pinguin als Sparfuchs - Linux-PC senkt
  756 +Handy-Geb&uuml;hren</tt> (refers to PBX software asterisk)
738 757 </itemize>
739 758
740 759 Also have a look at question <ref id="config_links" name="config_links"> for
741 760 helpful links on how to configure i4l (e.g. special help for SuSE, Red
742 761 Hat, or Mandrake users).
743 762
744   -<sect1> docu_website: Where is the official website for isdn4linux?
  763 +<sect1> docu_website: Where is the official website for isdn4linux?
745 764 <label id="docu_website">
746 765 <p>
747 766 The offical website can be found at:
@@ -753,7 +772,7 @@ The offical website can be found at:
753 772 You can find it on:
754 773 <url url="http://i4l.mediatronix.de/">
755 774
756   -<sect1> docu_newsgroup: Where is the newsgroup for isdn4linux?
  775 +<sect1> docu_newsgroup: Where is the newsgroup for isdn4linux?
757 776 <label id="docu_newsgroup">
758 777 <p>
759 778 The newsgroup was <tt>de.alt.comm.isdn4linux</tt>, however had been
@@ -811,7 +830,7 @@ Please note: there are about 20-50 messages per day on this mailing list.
811 830 To receive only one message per day, containing all postings, have a look
812 831 at question <ref id="docu_maillistdigest" name="docu_maillistdigest">.
813 832
814   -<sect1> docu_maillistdigest: How can I get a digest of the mailing list for
  833 +<sect1> docu_maillistdigest: How can I get a digest of the mailing list for
815 834 isdn4linux (only one message per day)?
816 835 <label id="docu_maillistdigest">
817 836 <p>
@@ -861,9 +880,9 @@ assume you have a passive card. More about the difference: see question
861 880 <ref id="hardware_activepassive" name="hardware_activepassive">.
862 881
863 882 Right now there is a driver for all passive card with certain Siemens
864   -chipsets (HiSax driver). Have a look at the <tt/README.HiSax/ that comes with
865   -the driver for the most up to date information on supported cards and which
866   -parameter to pass to Hisax.
  883 +chipsets (HiSax driver). Have a look at the <tt>README.HiSax</tt> that comes
  884 +with the driver for the most up to date information on supported cards and
  885 +which parameter to pass to Hisax.
867 886 Here the status from 1st February 2002 (constantly improving):
868 887 <itemize>
869 888 <item>Teles 8.0/16.0/16.3 and compatible ones (like: Dr. Neuhaus Niccy
@@ -953,15 +972,15 @@ specifications for their very proprietary hardware/protocols:
953 972 </itemize>
954 973
955 974 As for the Eumex 404, there is an unofficial binary driver for isdn4linux
956   -with Suse 6.3, which may or may not help you. Use it at your own risk:
  975 +with Suse 6.3, which may or may not help you. Use it at your own risk:
957 976 <url url="http://home.t-online.de/home/MetalMilitia/eumex.htm">
958 977
959   -<sect1> hardware_activepassive: What is the difference between an active and a
  978 +<sect1> hardware_activepassive: What is the difference between an active and a
960 979 passive ISDN card?
961 980 <label id="hardware_activepassive">
962 981 <p>
963   -An active ISDN card handles most of the ISDN connection protocols
964   -(dialing, accepting calls, etc.) itself. The card includes a kind
  982 +An active ISDN card handles most of the ISDN connection protocols
  983 +(dialing, accepting calls, etc.) itself. The card includes a kind
965 984 of minicomputer with its own software (firmware). With a passive card, the
966 985 computer in which the card is installed has to perform these functions.
967 986
@@ -1094,6 +1113,11 @@ The drivers for passive cards are currently not working under 64bit.
1094 1113 Obviously you can also not make use of binary drivers, unless you find a
1095 1114 binary compiled for 64bit.
1096 1115
  1116 +One external USB device based on the HFC-S chipset reported to work with
  1117 +isdn4linux is the Sitecom DC 104 with serial number greater than SN 46000202
  1118 +(olders are ST chipset based, they have the same box). Also "tiny USB TA"
  1119 +from Billion, and "surf mini usb" from Acer have been reported to work.
  1120 +
1097 1121 <sect1> hardware_alpha: Can I run isdn4linux on a DEC Alpha with Linux?
1098 1122 <label id="hardware_alpha">
1099 1123 <p>
@@ -1134,7 +1158,7 @@ compiled for 32 bit machines like all sun-4m machines.
1134 1158 Modern SUN-workstations and servers have a different busstructure
1135 1159 nowadays. The ULTRA series uses the PCI-bus.
1136 1160 Allthough some pc boards seem to be working in a SUN, there are NO
1137   -reports (yet) of properly functioning ISDN-PCI-boards in the SUN
  1161 +reports (yet) of properly functioning ISDN-PCI-boards in the SUN
1138 1162 environment. Please write me if anyone ever succeeds.
1139 1163
1140 1164 </enum>
@@ -1183,10 +1207,13 @@ mode like a leased line.
1183 1207
1184 1208 However, some special software named PBX4Linux has been written for this.
1185 1209 You may want to have a look at the German article in ct 9/2004 on how to use
1186   -PBX4Linux.
  1210 +PBX4Linux. You can also check the web site
  1211 +<tt><url url="http://isdn.jolly.de"></tt>.
  1212 +You may especially be interested in the information about card support for the
  1213 +NT mode with mISDN at: <tt><url url="http://isdn.jolly.de/cards.html"></tt>.
1187 1214
1188 1215 Another alternative for emulation of a PBX is Asterisk, to be found on:
1189   -<tt><url url="http://www.asterisk.org"></tt>
  1216 +<tt><url url="http://www.asterisk.org"></tt>.
1190 1217
1191 1218 Also, it is possible to give up one B-channel in exchange for reading the
1192 1219 complete D-channel protocol, which is great for isdnlog. The later can
@@ -1219,7 +1246,7 @@ the kernel 'k_i386' to run with older hardware).
1219 1246 <p>
1220 1247 Generally, ELSA supports the ISDN4LINUX developers quite well with
1221 1248 documentation on how to access their cards. Thus, these cards are well
1222   -supported and very recommendable for use under ISDN4LINUX. Also, the
  1249 +supported and very recommendable for use under ISDN4LINUX. Also, the
1223 1250 ELSA Quickstep 1000 PCI (new name Microlink PCI) is one of the only brands
1224 1251 of cards that are officially certified for use in Germany, and therefore
1225 1252 in EC (see question <ref id="country_certified" name="country_certified">
@@ -1238,7 +1265,7 @@ then exit with an intentional error (thus not occupying any memory).
1238 1265 To interface from ELSA's RJ11 plug to an RJ45 cable, use the following
1239 1266 cabling scheme:
1240 1267 <verb>
1241   - RJ11 - RJ45
  1268 + RJ11 - RJ45
1242 1269 pins 1234 12345678
1243 1270 Cable abcd --abcd--
1244 1271 </verb>
@@ -1280,7 +1307,7 @@ Class1SwitchingDelay: 75
1280 1307 The Sedlbauer Speedfax PCI is special in that it was produced just for
1281 1308 Linux - there is no driver for it under Windows.
1282 1309
1283   -<sect1> hardware_teles: What should I know about before buying an ISDN card
  1310 +<sect1> hardware_teles: What should I know about before buying an ISDN card
1284 1311 from Teles?
1285 1312 <label id="hardware_teles">
1286 1313 <p>
@@ -1296,7 +1323,7 @@ One of the most frequently asked questions for Teles cards: The Teles card
1296 1323 send packets with more than 1024 bytes it will not work
1297 1324 - unfortunately many CAPIs use 2048 bytes as default).
1298 1325 The latest Teles PCI card needs the <tt/netjet/ driver, the teles driver
1299   -will NOT work (that card identifies itself as 'TigerJet Tiger300' when doing a
  1326 +will NOT work (that card identifies itself as 'TigerJet Tiger300' when doing a
1300 1327 <tt>cat /proc/pci</tt>).
1301 1328
1302 1329 Now some comments about Teles in general (these are the personal opinions of
@@ -1360,7 +1387,7 @@ not work, then there could be an issue with the motherboard. See question
1360 1387
1361 1388 One very interesting thing: the Fritz! card is currently the only passive card
1362 1389 for which a capi driver exists. As a result, it can be configured to
1363   -fax. See question <ref id="feature_capi" name="feature_capi"> and
  1390 +fax. See question <ref id="feature_capi" name="feature_capi"> and
1364 1391 <url url="http://www.avm.de/ftp/cardware/fritzcrd/linux/index.htm">
1365 1392 for more information on this. Usage of the capi driver is completely optional,
1366 1393 you might as well stay with the standard driver if you do not need capi
@@ -1373,9 +1400,9 @@ This card supports many special features in its firmware and is very well
1373 1400 supported by its Linux driver. It's currently one of the only ISDN cards
1374 1401 that you can use to fax under ISDN4LINUX, or which supports the
1375 1402 CAPI 2.0 interface. You can get the newest driver from:
1376   -<url url="ftp://calle.in-berlin.de/pub/capi4linux/">.
  1403 +<url url="ftp://ftp.in-berlin.de/pub/capi4linux/">.
1377 1404 To get the firmware download the two perl scripts from:
1378   -<url url="ftp://calle.in-berlin.de/pub/capi4linux/firmware/">
  1405 +<url url="ftp://ftp.in-berlin.de/pub/capi4linux/firmware/">
1379 1406 They will download and extract the firmware from tar files on the avm
1380 1407 ftp server on: <url url="ftp://ftp.avm.de/cardware/b1/linux/">.
1381 1408
@@ -1489,7 +1516,7 @@ between 6 and 5 should be 40 V, 6 and 3 positive.
1489 1516
1490 1517 With the Western plug this works similar. 4 lines are used:
1491 1518 <verb>
1492   -| | | |
  1519 +| | | |
1493 1520 | | | |
1494 1521 1 2 3 4
1495 1522 </verb>
@@ -1556,9 +1583,9 @@ Your MSN is usually the extension at the end of your telefon number.
1556 1583
1557 1584 If your PBX is the <tt/Ackermann Euracom</tt>, then you may also check out
1558 1585 this German site for the configuration software maKs:
1559   -<url url="http://www.ganzfix.de">
  1586 +<url url="http://www.ganzfix.de">
1560 1587
1561   -<sect1> hardware_telestrouble: The PNP tools done work with my Teles 16.3 PNP
  1588 +<sect1> hardware_telestrouble: The PNP tools done work with my Teles 16.3 PNP
1562 1589 card!
1563 1590 <label id="hardware_telestrouble">
1564 1591 <p>
@@ -1597,7 +1624,7 @@ hardware to get rid of it. Check with Karsten Keil for this:
1597 1624 <p>
1598 1625 See section <ref id="msn" name="msn">.
1599 1626
1600   -<sect1> config_hardware: How should I configure my hardware? Is there
  1627 +<sect1> config_hardware: How should I configure my hardware? Is there
1601 1628 something special I should know about my ISDN card?
1602 1629 <label id="config_hardware">
1603 1630 <p>
@@ -1669,7 +1696,7 @@ only work if you configure i4l using modules.
1669 1696 <item> Manual: Unload the modules used by i4l with rmmod, then reload them with
1670 1697 modprobe.
1671 1698 <item> Runlevel: use telinit to switch to a runlevel which does not contain
1672   -ISDN, then switch back to the original runlevel.
  1699 +ISDN, then switch back to the original runlevel.
1673 1700 <item> Scripts: most distributions come with start/stop scripts.
1674 1701 For example, on a Suse 7.0 distribution, this will stop ISDN:
1675 1702 <code>
@@ -1717,6 +1744,12 @@ load HiSax for two Sedlbauer cards with the following command:
1717 1744 <code>
1718 1745 modprobe -v hisax protocol=2,2 type=28,28
1719 1746 </code>
  1747 +<item>Driver ID: the HiSax driver uses 'HiSax' as the default for a driver
  1748 +id if you have only one card. For more cards you have to set the id
  1749 +explicitely, e.g. for two cards in the form of
  1750 +<code>
  1751 +id="contr0%contr1"
  1752 +</code>
1720 1753 <item>Dialin of many people at the same time: have a look at question
1721 1754 <ref id="dialin_manyparallel" name="dialin_manyparallel">.
1722 1755 <item>Dialout through several cards: have a look at question
@@ -1778,7 +1811,7 @@ A higher bandwidth of 19.2kbit (HSCSD) could be requested with the command
1778 1811 AT+CBST=81,0,1+CHSN=3,0,0,0
1779 1812 </code>
1780 1813 but you can not be sure that your GSM provider will really use this rate.
1781   -Configure your dialin server accordingly.
  1814 +Configure your dialin server accordingly.
1782 1815
1783 1816 For a mini-howto see:
1784 1817 <url url="http://www.oltom.com/Linux/Docs/GSM%20over%20V.110%20Mini-HOWTO.txt">
@@ -1854,14 +1887,14 @@ howto (isdn.html) and a ISDN quick-install guide (isdnquick.html).
1854 1887 <tt><url url="http://www-ti.informatik.uni-tuebingen.de/~hippm/isdn.html"></tt>
1855 1888 <item>Chargeint tips:
1856 1889 <tt><url url="http://www.auf-der-er.de/chargeint.html"></tt>
1857   -<item>Homepage of kisdn (only works with Qt/KDE):
1858   -<tt><url url="http://www.millenniumx.de/kisdn.html"></tt>
1859 1890 <item>Homepage of linecontrol (manage isdn dialing similar to kisdn):
1860 1891 <tt><url url="http://linecontrol.sourceforge.net"></tt>
1861 1892 <item>(German) Homepage of ISDN Sniffer (read ISDN bus, e.g. via reversed
1862   -card): <tt><url url="http://krypt.cs.uni-sb.de/~osk/isdnosk.html"></tt>
  1893 +card): <tt><url url="http://krypt.cs.uni-sb.de/projects/isdnsniffer/"></tt>
1863 1894 <item>Homepage of Asterisk (Open Source Linux PBX):
1864 1895 <tt><url url="http://www.asterisk.org"></tt>
  1896 +<item>Homepage of ivcall (send and receive fax/voice calls):
  1897 +<tt><url url="http://0pointer.de/lennart/projects/ivcall/"></tt>
1865 1898 <item>Configuration software maKs for Ackermann Euracom (not isdn4linux related):
1866 1899 <tt><url url="http://www.ganzfix.de"></tt>
1867 1900 </itemize>
@@ -1904,6 +1937,21 @@ mISDN may work differently than described in this FAQ.
1904 1937 Please let me know about any amendmends for this FAQ.
1905 1938
1906 1939
  1940 +<sect1> config_kernel26: What has changed with the kernels 2.6.x?
  1941 +<label id="config_kernel26">
  1942 +<p>
  1943 +With the kernels 2.6.x the mISDN driver has been introduced (see question
  1944 +<ref id="config_misdn" name="config_misdn">). It is planned that the mISDN drivers will replace
  1945 +the old isdn4linux drivers like HiSax, which have been ported to 2.6.x only
  1946 +since mISDN was not ready yet.
  1947 +
  1948 +Please note that the ported drivers have not been upgraded to make use of the
  1949 +new kernel features like devfs. You still have to create all the devices you
  1950 +need, either with makedev.sh (part of isdn4k-utils), or by hand. Some
  1951 +distributions will do that for you (e.g. Suse), for others you have to do
  1952 +this yourself (e.g. Mandrake 10).
  1953 +
  1954 +
1907 1955 <!-- Troubleshooting
1908 1956 -->
1909 1957
@@ -2002,19 +2050,19 @@ should now see &dquot;CALLER NUMBER: xxxxxxx&dquot; and
2002 2050 &dquot;ATA&dquot;, and you should then see the message &dquot;CONNECT
2003 2051 64000/X.75&dquot; on both consoles. You can then send characters to the other
2004 2052 console by typing (to see the characters on your own console, turn on local echo).
2005   -<item>Next, try calling a known ISDN BBS. If you don't know of any, try
  2053 +<item>Next, try calling a known ISDN BBS. If you don't know of any, try
2006 2054 Gernot (see &dquot;Are there sites that offer guest access where I can test my
2007 2055 isdn4linux setup?&dquot;). If you have problems with the modem emulation, see
2008 2056 &dquot;Troubleshooting Modem Emulation&dquot;
2009   -<item>Fifth, try configuring the network interface or ipppd. Experience shows
  2057 +<item>Fifth, try configuring the network interface or ipppd. Experience shows
2010 2058 that they cause beginners (and not only beginners!) the most problems.
2011   -To make things easier and you're happy with asyncPPP (to see what
2012   -asyncPPP means, see the question &dquot;pppd, ipppd, syncPPP, asyncPPP -
  2059 +To make things easier and you're happy with asyncPPP (to see what
  2060 +asyncPPP means, see the question &dquot;pppd, ipppd, syncPPP, asyncPPP -
2013 2061 what is that? What should I use?&dquot;), you can use the normal pppd with
2014   -modem emulation (i.e. /dev/ttyI*).
  2062 +modem emulation (i.e. /dev/ttyI*).
2015 2063 <item>Ensure that you set up your authentication configuration properly (see
2016 2064 questions in section <ref id="pap" name="pap">.
2017   -</enum>
  2065 +</enum>
2018 2066 Otherwise, it is highly recommended that use an example script form
2019 2067 the HowTo (see the question &dquot;Where can I find scripts and other
2020 2068 information on configuring i4l?&dquot;). For testing you can try your own
@@ -2115,7 +2163,7 @@ fix your connection parameters with:
2115 2163 isdnctrl l2_prot &lt;interface&gt; &lt;protocol&gt;
2116 2164 </code>
2117 2165
2118   -<sect1> trouble_notelrings: Neither my telephone nor my fax machine ring
  2166 +<sect1> trouble_notelrings: Neither my telephone nor my fax machine ring
2119 2167 when I call them with isdn4linux?
2120 2168 <label id="trouble_notelrings">
2121 2169 <p>
@@ -2144,7 +2192,7 @@ because sometimes my &dquot;default&dquot; route is not your way.
2144 2192 You can login as &dquot;guest&dquot; without password.
2145 2193 FTP as &dquot;gast&dquot; with password &dquot;gast&dquot; avoids the
2146 2194 restricted shell.
2147   -<item>Under ++49-551-7704102, a 28800 bps modem and a Creatix ISDN
  2195 +<item>Under ++49-551-7704102, a 28800 bps modem and a Creatix ISDN
2148 2196 card (HDLC only, not X.75) are listening for logins.
2149 2197 <item>With the net setup from
2150 2198 <tt><url url="ftp://ftp.gwdg.de/pub/linux/isdn/isdn4linux-gwdg/rc.isdn-Beispiel"></tt>
@@ -2155,7 +2203,7 @@ from outside Germany you just have to change the number).
2155 2203 <item>Gernot Zander <tt><htmlurl url="mailto:hifi@scorpio.in-berlin.de"
2156 2204 name="hifi@scorpio.in-berlin.de"></tt>:
2157 2205 <quote>
2158   -There's a &dquot;gast&dquot; at +49 30 67 19 81 01 (X.75, mgetty). There's the
  2206 +There's a &dquot;gast&dquot; at +49 30 67 19 81 01 (X.75, mgetty). There's the
2159 2207 stones-html-page with pics in postscript to test downloading. Whoever
2160 2208 needs a target to call can use it. At ...81 03 there's a getty with
2161 2209 HDLC. As guest you enter a kind of BBS and can read some news.
@@ -2214,7 +2262,7 @@ and the rest is at:
2214 2262 /pub/linux/mirrors/funet/PEOPLE/Linus/net-source/tools/tcpdump-3.0.4-1.tar.gz
2215 2263
2216 2264 You might need to hack some, depending on the name of your ISDN interface
2217   -(mine is bri0). By default, it recognizes only isdn* and isdnY* as
  2265 +(mine is bri0). By default, it recognizes only isdn* and isdnY* as
2218 2266 interface names.
2219 2267
2220 2268 Henning Schmiedehausen <tt><htmlurl url="mailto:henning@pong.iconsult.com"
@@ -2226,12 +2274,12 @@ dump cisco HDLC, I made my own patch for tcpdump-3.0.4 that asks the
2226 2274 interface which encapsulation it used and sets itself accordingly. The
2227 2275 patch is against a tcpdump-3.0.4-1.tar.gz distribution, for example at
2228 2276 </quote>
2229   -<tt><url url="ftp://ftp.funet.fi/pub/Linux/PEOPLE/Linus/tools"></tt>
  2277 +<tt><url url="ftp://ftp.funet.fi/pub/Linux/PEOPLE/Linus/tools"></tt>
2230 2278 <quote>
2231 2279 This patch recognizes rawIP, ISDN-IP and CISCO-HDLC and can
2232 2280 dump these packets.
2233 2281 </quote>
2234   -(The patch was attached to the message - it should be easy to find in the
  2282 +(The patch was attached to the message - it should be easy to find in the
2235 2283 mailing list archive - Ed.)
2236 2284
2237 2285 Sascha Ottolski <tt><htmlurl url="mailto:sascha@alzhimer.isdn.cs.tu-berlin.de"
@@ -2260,7 +2308,7 @@ has to be transformed somewhat to be a form similar to System.map. You can do
2260 2308 it like this:
2261 2309 <code>
2262 2310 insmod -m isdn.o | sort | sed -e 's/ / T /g' |
2263   - egrep '.* T (a-z,A-Z,_)+' /etc/isdn/isdn.map
  2311 + egrep '.* T (a-z,A-Z,_)+' /etc/isdn/isdn.map
2264 2312 cat /System.map /etc/isdn/isdn.map /iSystem.map
2265 2313 </code>
2266 2314 (The line ending with &dquot;|&dquot; has to have the following text on
@@ -2302,9 +2350,9 @@ they disable the interrupts too long! It may also happen on old hardware
2302 2350 only 4MB RAM). You may be able to work around it by increasing the number and
2303 2351 size of the buffers. Check the source code header files for definitions like:
2304 2352 <code>
2305   -&num;define HSCX_RBUF_ORDER 1
2306   -&num;define HSCX_RBUF_BPPS 2
2307   -&num;define HSCX_RBUF_MAXPAGES 3
  2353 +&num;define HSCX_RBUF_ORDER 1
  2354 +&num;define HSCX_RBUF_BPPS 2
  2355 +&num;define HSCX_RBUF_MAXPAGES 3
2308 2356 </code>
2309 2357 The first two influence the size, the last one the maximum number of buffers.
2310 2358
@@ -2349,7 +2397,7 @@ Peter Hettkamp <tt><htmlurl url="mailto:Peter.Hettkamp@kassel.netsurf.de"
2349 2397 name="Peter.Hettkamp@kassel.netsurf.de"></tt> wrote:
2350 2398 <quote>
2351 2399 xosview reacts, at least for me with version 1.4, to the IP accounting
2352   -in the kernel. So, configure, if necessary build a new kernel, then
  2400 +in the kernel. So, configure, if necessary build a new kernel, then
2353 2401 couple with:
2354 2402 ipfwadm -A -a -S your-ip-address-here -D 0.0.0.0/0
2355 2403 ipfwadm -A -a -D your-ip-address-here -S 0.0.0.0/0
@@ -2361,8 +2409,8 @@ address.)
2361 2409 with Netscape, I only get the answer &dquot;unknown host&dquot;.
2362 2410 <label id="trouble_unknownhost">
2363 2411 <p>
2364   -What is entered on the &dquot;Win95 box&dquot; for the name server? As long as the
2365   -router has no name server of its own, then the provider's name server
  2412 +What is entered on the &dquot;Win95 box&dquot; for the name server? As long as the
  2413 +router has no name server of its own, then the provider's name server
2366 2414 of course has to be entered on all computers on the LAN.
2367 2415
2368 2416 <sect1> trouble_noroute: Addresses are now found, but now I get &dquot;no route
@@ -2376,7 +2424,7 @@ have to be restarted before changes to the networking take effect)?
2376 2424 <item>Does the router have a default route to the prepared interface to the
2377 2425 provide (e.g. ippp0 with syncPPP or sl0 for diald (even when the real
2378 2426 connection is over ppp0, diald uses a slip interface as a &dquot;doorknob&dquot;)
2379   -<item>Does the provider require the use of proxies? Then the addresses
  2427 +<item>Does the provider require the use of proxies? Then the addresses
2380 2428 of the proxies have to the entered in the appropriate clients on the LAN
2381 2429 computers
2382 2430 <item>Maybe your route was removed when using syncppp? Check the questions
@@ -2394,11 +2442,11 @@ Wolfgang Barth wrote on 5 Jan 1997:
2394 2442 I've noticed that after the first connection via ippp0 that the local
2395 2443 network can again be reached. Then the address 0.0.0.0 is no longer
2396 2444 listed in ifconfig for ippp0, but instead the address assigned from
2397   -the pool by the PPP partner.
  2445 +the pool by the PPP partner.
2398 2446 This was already discussed in de.comp.os.linux.networking, along
2399   -this possible solution:
2400   -Simply set ippp0 to a dummy IP number from the pool. Then the
2401   -local network will have problems after booting, even with the
  2447 +this possible solution:
  2448 +Simply set ippp0 to a dummy IP number from the pool. Then the
  2449 +local network will have problems after booting, even with the
2402 2450 default route, and the IP number in ifconfig will be overwritten
2403 2451 anyway.
2404 2452 </quote>
@@ -2412,7 +2460,7 @@ Since the certification of the HiSax driver is only valid for unchanged
2412 2460 source code, the source code is protected by a checksum. When you get this
2413 2461 message, then either you have changed the source code yourself, or the
2414 2462 author did not update the checksum when changing the source code (reason
2415   -could be that the complete certification tests have not yet been run on
  2463 +could be that the complete certification tests have not yet been run on
2416 2464 the changed code).
2417 2465
2418 2466
@@ -2499,7 +2547,7 @@ If your telephone number were 56789, then it would be configured as follows:
2499 2547 </code>
2500 2548 </itemize>
2501 2549 You may find national differences here (check section <ref id="countries"
2502   - name="countries">).
  2550 + name="countries">).
2503 2551
2504 2552
2505 2553 <sect1> msn_max: How many MSNs as a maximum can I use for an isdn card?
@@ -2774,7 +2822,7 @@ chmod o-rw /dev/ttyI* /dev/cui*
2774 2822 </code>
2775 2823 It has been reported that you also may have to change group and
2776 2824 permissions on the programs <tt/ipppd/ and <tt/isdnctrl/ to 'isdn'.
2777   -Then all users not in the group 'isdn' have no reading or writing
  2825 +Then all users not in the group 'isdn' have no reading or writing
2778 2826 privileges for the ISDN ttys. Those allowed to use ISDN have to be
2779 2827 explicitly added to the group 'isdn'.
2780 2828 <item>You can allow only root to log out, but set up exceptions for other users
@@ -2802,7 +2850,7 @@ Now the users XXXX and YYYY can dial out by typing <tt/dial/, and hangup with
2802 2850 make him owner of the ISDN interface.
2803 2851 </enum>
2804 2852
2805   -<sect1> dialout_manycards: How do I configure dialout with more than 1 ISDN
  2853 +<sect1> dialout_manycards: How do I configure dialout with more than 1 ISDN
2806 2854 card?
2807 2855 <label id="dialout_manycards">
2808 2856 <p>
@@ -2812,7 +2860,7 @@ There are several possibilities to configure dialout.
2812 2860 on one MSN):
2813 2861 just configure your cards in the order in which you want them to be dialed out.
2814 2862 First all channels on the first card are used, then all on the second card,
2815   -and so on. Please note that the net interface or ttyI device will try to
  2863 +and so on. Please note that the net interface or ttyI device will try to
2816 2864 dial out using the MSN it was configured for - on all cards. Even on those
2817 2865 that do not have this MSN! In such a case, the telco will replace that
2818 2866 invalid MSN with the correct one. Use <tt/isdnctrl mapping/ to configure the
@@ -2837,7 +2885,7 @@ want to use only MSN 333 on &lt;carddriver1&gt; (&lt;carddriver2&gt; will
2837 2885 use the default MSN when used). Configure to use telephone number 3 when you
2838 2886 really want to use only MSN 777 on &lt;carddriver2&gt; (&lt;carddriver1&gt;
2839 2887 will use the default MSN when used).
2840   -<item>Dialout on one specific card:
  2888 +<item>Dialout on one specific card:
2841 2889 After installing a patch that was posted by Karsten Keil on the mailing
2842 2890 list against 2.2.12, you can disallow calls on some cards by using the
2843 2891 <tt/isdnctrl mapping/ functionality.
@@ -2897,7 +2945,7 @@ The same principle applies to two or more forwarders.
2897 2945 Another option are the programs <tt/ip_resend/ and <tt/ip_resend_wakeup/
2898 2946 which you can find on:
2899 2947 <url url="http://www.baty.hanse.de/ip_resend/">
2900   -
  2948 +
2901 2949
2902 2950 <!-- Authenticate properly
2903 2951 -->
@@ -2926,7 +2974,7 @@ other side. In the log file I find a message that's something like:
2926 2974 &dquot;sent (0) (LCP ConfRej id=0x1 auth pap&dquot;
2927 2975 <label id="pap_rejectauth">
2928 2976 <p>
2929   -Your computer is refusing to identify itself with user name (e.g. XXX)
  2977 +Your computer is refusing to identify itself with user name (e.g. XXX)
2930 2978 and password (e.g. YYY). That only works with the authorization options
2931 2979 &dquot;user XXX&dquot; and &dquot;remotename YYY&dquot; for ipppd or pppd
2932 2980 together with a correct (!) /etc/ppp/pap-secrets. With a password of ZZZ it
@@ -2982,7 +3030,7 @@ the password in quotes!
2982 3030 <sect> syncppp: Sync PPP
2983 3031 <label id="syncppp">
2984 3032
2985   -<sect1> syncppp_whichppp: pppd, ipppd, syncPPP, asyncPPP .. what is they?
  3033 +<sect1> syncppp_whichppp: pppd, ipppd, syncPPP, asyncPPP .. what is they?
2986 3034 Which should I use?
2987 3035 <label id="syncppp_whichppp">
2988 3036 <p>
@@ -3079,29 +3127,29 @@ You can write out a login session with (&dquot;Debug-Log&dquot;), and see which
3079 3127 options the other computer is refusing. Next time, configure ipppd
3080 3128 without these unused options. A further side effect is that such
3081 3129 unused options increase the redundance (e.g. when the other computer
3082   -has bugs and refuses the options incorrectly). To create a log file,
  3130 +has bugs and refuses the options incorrectly). To create a log file,
3083 3131 see &dquot;How to I create a log for ipppd&dquot;.
3084 3132
3085 3133 <sect1> syncppp_2configs: I want to talk to remote machines which needs different
3086 3134 configurations. The only way I found to do this is to kill the ipppd and start
3087   -a new one with another config to connect to the second machine.
  3135 +a new one with another config to connect to the second machine.
3088 3136 <label id="syncppp_2configs">
3089 3137 <p>
3090   -You must bind a network interface explicitly to an ippp device, where you
3091   -can connect a (for this interface) individually configured ipppd. With the
  3138 +You must bind a network interface explicitly to an ippp device, where you
  3139 +can connect a (for this interface) individually configured ipppd. With the
3092 3140 (unfortunately poorly documented) command
3093 3141 <code>
3094 3142 isdnctrl pppbind interface Number
3095 3143 </code>
3096   -you can link the interface interface to the device ipppNummer. You can
3097   -release the link with &dquot;pppunbind&dquot;.
  3144 +you can link the interface interface to the device ipppNummer. You can
  3145 +release the link with &dquot;pppunbind&dquot;.
3098 3146
3099 3147 <sect1> syncppp_pppbind: How does the (little-documented) &dquot;pppbind&dquot;
3100 3148 command in isdnctrl work?
3101 3149 <label id="syncppp_pppbind">
3102 3150 <p>
3103 3151 You have to first know how ipppd gets its data. All data that come in
3104   -over the ISDN line is received by the network devices (these are
  3152 +over the ISDN line is received by the network devices (these are
3105 3153 set up with isdnctrl). Then the data given to one of the /dev/ippp*
3106 3154 devices - to one where a ipppd daemon is waiting for data.
3107 3155
@@ -3109,8 +3157,8 @@ To the network interfaces, all ipppd's appear to be able to handle the
3109 3157 just-received data - therefore it is normally impossible to predict
3110 3158 which ipppd will receive data from which network interface.
3111 3159
3112   -In practice, you usually install several ipppd's with differing
3113   -configurations. Each of these should receive data <em>exclusively</em>
  3160 +In practice, you usually install several ipppd's with differing
  3161 +configurations. Each of these should receive data <em>exclusively</em>
3114 3162 from a certain network interface (that has also be specially configured).
3115 3163 The &dquot;pppdbind&dquot; command serves just this purpose. With:
3116 3164 <code>
@@ -3129,29 +3177,29 @@ Similarly, the command &dquot;pppunbind&dquot; will undo this attachment.
3129 3177 configure the network device?
3130 3178 <label id="syncppp_dynip">
3131 3179 <p>
3132   -At least you must have a route, which forwards a packet to the ippp
3133   -network interface to trigger dialing. A default route to the ippp interface
  3180 +At least you must have a route, which forwards a packet to the ippp
  3181 +network interface to trigger dialing. A default route to the ippp interface
3134 3182 will work. Now you must choose a dummy IP address for your interface. If for
3135   -some reason you can't set the default route to the ippp interface, you may
3136   -take any address of the subnet from which you expect your dynamic IP number
3137   -and set a 'network route' for this subnet to the ippp interface. To allow
  3183 +some reason you can't set the default route to the ippp interface, you may
  3184 +take any address of the subnet from which you expect your dynamic IP number
  3185 +and set a 'network route' for this subnet to the ippp interface. To allow
3138 3186 overriding of the dummy address you must call the ipppd with
3139 3187 the 'ipcp-accept-local' option. You must know how the ipppd gets the
3140 3188 addresses it has to configure. If you don't give any option, the ipppd
3141 3189 tries to negotiate the local host address! With the option 'noipdefault'
3142   -it requests an address from the remote machine. With 'useifip' it gets the
3143   -addresses from the net interface. You also can set the addresses in the
3144   -option line with the a.b.c.d:e.f.g.h option. Note: the IP address of the
3145   -remote machine must be configured locally, or the remote machine must send
3146   -it in an IPCP request. If your side doesn't know the IP address after
3147   -negotiation, it will close the connection! You must allow overriding of
3148   -addresses with the 'ipcp-accept-*' options, if you have set your own or the
  3190 +it requests an address from the remote machine. With 'useifip' it gets the
  3191 +addresses from the net interface. You also can set the addresses in the
  3192 +option line with the a.b.c.d:e.f.g.h option. Note: the IP address of the
  3193 +remote machine must be configured locally, or the remote machine must send
  3194 +it in an IPCP request. If your side doesn't know the IP address after
  3195 +negotiation, it will close the connection! You must allow overriding of
  3196 +addresses with the 'ipcp-accept-*' options, if you have set your own or the
3149 3197 remote address explicitly. Try these options, e.g.:
3150 3198 <code>
3151 3199 /sbin/ipppd :&dollar;REMOTE noipdefault /dev/ippp0
3152 3200 </code>
3153   -where REMOTE must be the address of the remote machine (the machine giving
3154   -your address to you)
  3201 +where REMOTE must be the address of the remote machine (the machine giving
  3202 +your address to you)
3155 3203
3156 3204 <sect1> syncppp_msgetdns: How do I configure ipppd to obtain or provide the
3157 3205 nameserver address at dial in?
@@ -3281,7 +3329,7 @@ packet (e.g. gethostbyname()). Without ipppd (since at this time, ipppd
3281 3329 it has not been fully started), this network access cannot be processed,
3282 3330 You should try to put the needed hostnames in the local /etc/hosts or
3283 3331 in some way define the name so that it can be resolved without having
3284   -the access the ISDN/ippp interface.
  3332 +the access the ISDN/ippp interface.
3285 3333
3286 3334 <sect1> syncppp_framesdelayed: I get the message <tt>IP frames delayed</tt> -
3287 3335 but no connection.
@@ -3399,13 +3447,13 @@ AT&amp;B512
3399 3447 that limits the sent packets to 512 bytes.
3400 3448 </quote>
3401 3449
3402   -<sect1> syncppp_mtu: My ipppd works, but I keep getting the message pppd(104):
  3450 +<sect1> syncppp_mtu: My ipppd works, but I keep getting the message pppd(104):
3403 3451 ioctl(SIOCSIFMTU): Invalid argument&dquot;?
3404 3452 <label id="syncppp_mtu">
3405 3453 <p>
3406 3454 If mtu is not set, then a default value is assumed - possibly &dquot;0&dquot;
3407 3455 (which of course cannot be correct). Add <tt>&dquot;mtu 1024&dquot;</tt> to
3408   -your ipppd options (1500 could also be ok).
  3456 +your ipppd options (1500 could also be ok).
3409 3457
3410 3458 <sect1> syncppp_1stpacket: The first IP packet gets lost on automatic dialout
3411 3459 with dynamic IP address allocation.
@@ -3435,7 +3483,7 @@ up the connection. Change the registry entry
3435 3483 from 3 to a larger value (e.g. 5 or 7).
3436 3484 </itemize>
3437 3485
3438   -<sect1> syncppp_droppacket: What does the message &dquot;No phone number,
  3486 +<sect1> syncppp_droppacket: What does the message &dquot;No phone number,
3439 3487 packet dropped&dquot; mean?
3440 3488 <label id="syncppp_droppacket">
3441 3489 <p>
@@ -3444,7 +3492,7 @@ name="michi@bello.wor.de"></tt> wrote in Nov/Dec 1996:
3444 3492
3445 3493 That means that your computer has an IP packet from somewhat who was
3446 3494 logged on a few seconds before, but has since broken the connection.
3447   -Your computer tries to send this packet on and finds an appropriate
  3495 +Your computer tries to send this packet on and finds an appropriate
3448 3496 route. But the interface isdn(0|1|...) can't reach the other computer,
3449 3497 since it has no telephone number to dial.
3450 3498
@@ -3523,7 +3571,7 @@ You can write out a login session with (&dquot;Debug-Log&dquot;), and see which
3523 3571 options the other computer is refusing. Next time, configure ipppd
3524 3572 without these unused options. A further side effect is that such
3525 3573 unused options increase the redundance (e.g. when the other computer
3526   -has bugs and refuses the options incorrectly). To create a log file,
  3574 +has bugs and refuses the options incorrectly). To create a log file,
3527 3575 see &dquot;How to I create a log for ipppd&dquot;.
3528 3576
3529 3577 <sect1> asyncppp_fast: How can I increase my transfer rates with PPP?
@@ -3533,7 +3581,7 @@ You can add more channels with MPPP (see question
3533 3581 <ref id="2channel_mppp" name="2channel_mppp">).
3534 3582 For everyone for whom that's to expensive and who use <em>async PPP</em>,
3535 3583 there's a little trick. With the option &dquot;asyncmap 0&dquot; you can avoid
3536   -escaping all control characters (ASCII32). If the other side goes
  3584 +escaping all control characters (ASCII32). If the other side goes
3537 3585 along with this, you can increase the transfer rate by about 12&percnt;.
3538 3586
3539 3587 <sect1> asyncppp_log: How can I get a log for pppd?
@@ -3541,8 +3589,8 @@ along with this, you can increase the transfer rate by about 12&percnt;.
3541 3589 <p>
3542 3590 See this question for Sync PPP, it works the same way for pppd.
3543 3591
3544   -<sect1> asyncppp_suddendeath: Establishing the connection works fine,
3545   -but pppd crashes just after that (i.e. the first bytes gets through,
  3592 +<sect1> asyncppp_suddendeath: Establishing the connection works fine,
  3593 +but pppd crashes just after that (i.e. the first bytes gets through,
3546 3594 but then everything stops)
3547 3595 <label id="asyncppp_suddendeath">
3548 3596 <p>
@@ -3573,9 +3621,9 @@ Advantages:
3573 3621 </itemize>
3574 3622 Disadvantages:
3575 3623 <itemize>
3576   -<item> No handshaking
  3624 +<item> No handshaking
3577 3625 =&gt; Configuration must occur beforehand (IP addresses,...)
3578   -=&gt; sensible to use for only for one provider at a time
  3626 +=&gt; sensible to use for only for one provider at a time
3579 3627 <item> Authorization only by Caller ID
3580 3628 =&gt; Dialin only possible from one's own number
3581 3629 <item> Fixed IP address
@@ -3585,6 +3633,16 @@ assignment of addresses possible.
3585 3633 From this summary it should be clear under what conditions it makes sense
3586 3634 to use raw IP.
3587 3635
  3636 +<sect1> rawip_capi: How can I use Raw IP with the new CAPI 2.0 interface?
  3637 +<label id="rawip_capi">
  3638 +<p>
  3639 +Raw IP can still be used with the new CAPI interface and drivers by using
  3640 +<tt>ItunD</tt>, the ISDN tunnel Daemon. <tt>ItunD</tt> (ISDN tunnel Daemon)
  3641 +provides a network tunnel over ISDN lines using the CAPI interface. The
  3642 +ISDN4Linux isdn-net (raw IP) devices are supported.
  3643 +
  3644 +You can find <tt>ItunD</tt> at:
  3645 +<url url="http://sourceforge.net/projects/itund/">
3588 3646
3589 3647 <!-- ttyI* devices
3590 3648 -->
@@ -3596,7 +3654,7 @@ to use raw IP.
3596 3654 <label id="ttyI_nomodem">
3597 3655 <p>
3598 3656 No! The ttyI* devices just offer a similar communication interface, where
3599   -all commands are started with <em/AT/. This makes it easy to reuse software
  3657 +all commands are started with <em>AT</em>. This makes it easy to reuse software
3600 3658 that was written to communicate with a modem. <bf>Communication with a remote
3601 3659 analog modem is not possible via the ttyI* devices!</bf> The real communication
3602 3660 happens in digital, not analog form.
@@ -3604,7 +3662,7 @@ happens in digital, not analog form.
3604 3662 <sect1> ttyI_dev: Which devices should I use for calls out or calls in?
3605 3663 <label id="ttyI_dev">
3606 3664 <p>
3607   -Only the ttyI* devices should be used. The cui* devices are created
  3665 +Only the ttyI* devices should be used. The cui* devices are created
3608 3666 only for reasons of compatibility. Now that there is mgetty, there is not
3609 3667 reason to use the cui* devices any longer. If they are used, locking will
3610 3668 not work correctly (several programs could simultaneously attempt to use
@@ -3705,8 +3763,8 @@ Can happen when the partner cannot handle the large frames from i4l and simply
3705 3763 closes the B channel during the transfer. Try making the frames smaller with
3706 3764 AT&amp;B512.
3707 3765
3708   -<sect1> ttyI_uucp: When I use UUCP with X.75, I always get transfer errors!
3709   -<label id="ttyI_uucp">
  3766 +<sect1> ttyI_x75uucp: When I use UUCP with X.75, I always get transfer errors!
  3767 +<label id="ttyI_x75uucp">
3710 3768 <p>
3711 3769 Andreas Gutzwiller <tt><htmlurl url="mailto:andy@hippo.proxyon.imp.com"
3712 3770 name="andy@hippo.proxyon.imp.com"></tt> wrote on 5 Dec 1996:
@@ -3882,11 +3940,11 @@ For example, to disable any automatic dialouts:
3882 3940 To get things running again:
3883 3941 <code>
3884 3942 /sbin/isdnctrl system on
3885   -/sbin/ifconfig ippp0 up
  3943 +/sbin/ifconfig ippp0 up
3886 3944 /sbin/route add &dollar;GATE-IP dev ippp0
3887 3945 /sbin/route add default ippp0
3888 3946 </code>
3889   -The latter method has the disadvantage that dialin is then no longer
  3947 +The latter method has the disadvantage that dialin is then no longer
3890 3948 possible.
3891 3949 </enum>
3892 3950
@@ -3916,11 +3974,11 @@ syncPPP encapsulation (this may require a patch - see question
3916 3974 quieted down. named, sendmail, and also smbd (Samba) are likely candidates to
3917 3975 open connections (see questions <ref id="dod_localdns" name="dod_localdns">,
3918 3976 <ref id="dod_sendmail" name="dod_sendmail">, <ref id="dod_samba" name="dod_samba">).
3919   -<item> If broadcasts are your problem, you can also redirect the
  3977 +<item> If broadcasts are your problem, you can also redirect the
3920 3978 broadcast address to the dummy0 interface. It's not clean, but it works.
3921 3979 </itemize>
3922 3980
3923   -<sect1> dod_winclient: Can it be that the Win95 machine on my LAN is causing
  3981 +<sect1> dod_winclient: Can it be that the Win95 machine on my LAN is causing
3924 3982 automatic dialouts?
3925 3983 <label id="dod_winclient">
3926 3984 <p>
@@ -3930,11 +3988,11 @@ server of your provider (if known), trying to look up some domains
3930 3988 <itemize>
3931 3989 <item> Switch off the feature <tt>Use DNS for Windows Names Resolution</tt>
3932 3990 on all Windows computers on your LAN.
3933   -<item> Set up a local DNS name server such that it will answer all requests.
  3991 +<item> Set up a local DNS name server such that it will answer all requests.
3934 3992 See question <ref id="dod_localdns" name="dod_localdns">.
3935 3993 </itemize>
3936 3994
3937   -<sect1> dod_localdns: I have set up a local DNS name server. Why does it cause
  3995 +<sect1> dod_localdns: I have set up a local DNS name server. Why does it cause
3938 3996 unwanted dialouts? How can I find the cause?
3939 3997 <label id="dod_localdns">
3940 3998 <p>
@@ -4016,7 +4074,7 @@ nmdb -S -B 192.168.99.255 -I 192.168.99.99
4016 4074 if your Linux computer has 192.168.99.99 as ip address, and all users
4017 4075 are in the same subnet (192.168.99.255).
4018 4076
4019   -See also the above question: set -broadcast and possibly -arp
  4077 +See also the above question: set -broadcast and possibly -arp
4020 4078 when defining the interfaces!
4021 4079
4022 4080 Check out the help pages for the Samba configuration file for further
@@ -4057,7 +4115,7 @@ To prevent this problem the RST-provoking mode has been invented.
4057 4115 If on the closing attempt a new dialout is opened and the ip address changes,
4058 4116 then the kernel will send a ip packet with the reset flag on. This will close
4059 4117 down the open connection, preventing the dial on demand disaster.
4060   -To activate the RST-provoking mode use the command
  4118 +To activate the RST-provoking mode use the command
4061 4119 <code>
4062 4120 echo 7 > /proc/sys/net/ipv4/ip_dynaddr
4063 4121 </code>
@@ -4068,8 +4126,8 @@ cat /proc/sys/net/ipv4/ip_dynaddr
4068 4126 Your distribution may or may not have the patch for this rst-provoking mode
4069 4127 included, it was not liked in the kernel code for kernels newer than 2.0.x.
4070 4128
4071   -<sect1> dod_closeipconnect: After closing the line, I discover with
4072   -<tt>netstat -nt</tt> that IP connections are still open. How can I close
  4129 +<sect1> dod_closeipconnect: After closing the line, I discover with
  4130 +<tt>netstat -nt</tt> that IP connections are still open. How can I close
4073 4131 these manually?
4074 4132 <label id="dod_closeipconnect">
4075 4133 <p>
@@ -4111,8 +4169,8 @@ your machine is crashed, while interrupts are still processed normally, this
4111 4169 could happen.
4112 4170
4113 4171
4114   -<!-- Chargeint
4115   --->
  4172 +<!-- Chargeint
  4173 +-->
4116 4174 <sect> chargeint: Chargeint
4117 4175 <label id="chargeint">
4118 4176
@@ -4181,7 +4239,7 @@ Cisco's keep alive packages has been corrected, so you can either use it,
4181 4239 or tell the provider not to use keep alive packets
4182 4240 (<tt>&dquot;no keepalive&dquot;</tt> in the Cisco configuration).
4183 4241
4184   -It could also be that it's not the keep alive packets that are keeping the
  4242 +It could also be that it's not the keep alive packets that are keeping the
4185 4243 connection open, but rather OSPF routing updates. The sending of these
4186 4244 updates can only be switched off on the Cisco. You can configure
4187 4245 &dquot;snapshot server&dquot; on the BRI interface. That means it will
@@ -4219,21 +4277,21 @@ details.
4219 4277 <label id="2channel_raw">
4220 4278 <p>
4221 4279 Raw bundling works similarly to raw IP, only with several channels.
4222   -Therefore, it has the theoretical advantages and disadvantages of
4223   -raw IP. Raw bundling requires a network interface for each channel
  4280 +Therefore, it has the theoretical advantages and disadvantages of
  4281 +raw IP. Raw bundling requires a network interface for each channel
4224 4282 that is used. One network interface, the so-called master interface,
4225   -controls the establishment and breaking of connections. For each
4226   -further channel, an additional so-called slave interface is configured,
  4283 +controls the establishment and breaking of connections. For each
  4284 +further channel, an additional so-called slave interface is configured,
4227 4285 that is automatically switched on by the master interface.
4228 4286
4229 4287 <sect1> 2channel_rawconfig: How do I configure raw bundling?
4230 4288 <label id="2channel_rawconfig">
4231 4289 <p>
4232   -The master interface is created as usual with
  4290 +The master interface is created as usual with
4233 4291 <code>
4234 4292 isdnctrl addif master interface
4235 4293 </code>
4236   -and configured. For all required slave channels, slave interfaces
  4294 +and configured. For all required slave channels, slave interfaces
4237 4295 are created with the command:
4238 4296 <code>
4239 4297 isdnctrl addslave master interface slave interface
@@ -4271,9 +4329,9 @@ cover ISDN channels.
4271 4329 MPPP?
4272 4330 <label id="2channel_mpppgoodbad">
4273 4331 <p>
4274   -A disadvantage is that the slave channel has to be activated
  4332 +A disadvantage is that the slave channel has to be activated
4275 4333 &dquot;manually&dquot;. ipppd cannot by itself turn the slave channel on and
4276   -off as it needs to. The normal automatic functions of ipppd are
  4334 +off as it needs to. The normal automatic functions of ipppd are
4277 4335 either unreliable (auto hangup) don't work at all (auto dial).
4278 4336 This is not true for the other encapsulations. The transfers
4279 4337 rates are very good (ca. 30 KB/s with 4 channels).
@@ -4389,7 +4447,7 @@ making use of isdn4linux. Possibly ant-phone could be used for such a purpose:
4389 4447 <!-- Pecularities of your counterpart (remote device)
4390 4448 -->
4391 4449
4392   -<sect> remote: Pecularities of the remote ISDN device
  4450 +<sect> remote: Pecularities of the remote ISDN device
4393 4451 <label id="remote">
4394 4452
4395 4453 <sect1> remote_win95: How do I configure Windows95 to dial successfully into
@@ -4465,16 +4523,16 @@ isdnctrl encap isdn0 rawip /
4465 4523 isdnctrl l2_prot isdn0 x75i \
4466 4524 isdnctrl l3_prot isdn0 trans -l1
4467 4525 isdnctrl encap isdn0 uihdlc /
4468   -----------------------------------------------------
  4526 +----------------------------------------------------
4469 4527 </verb>
4470 4528 The parameter with the least problems is -h0.
4471 4529
4472 4530
4473   -<sect> leased: Leased lines
  4531 +<sect> leased: Leased lines
4474 4532 <label id="leased">
4475 4533
4476 4534 <!-- Config Leased line/D64S
4477   --->
  4535 +-->
4478 4536
4479 4537 <sect1> leased_flatrate: What's the difference between a leased line and
4480 4538 a flat rate?
@@ -4599,21 +4657,21 @@ The most elegant way is to use iprofd. This daemon takes advantage of
4599 4657 the <tt>AT&amp;W0</tt> command in the i4l modem emulation. You start iprofd
4600 4658 with a path as parameter, e.g. <tt>&dquot;iprofd /etc/i4lprofile&dquot;</tt>
4601 4659 Then with minicom or another terminal program, open an ISDN tty
4602   -device and enter the necessary AT command by hand.
  4660 +device and enter the necessary AT command by hand.
4603 4661 When finished, enter the command <tt>AT&amp;W0</tt>, then the kernel notifies
4604 4662 iprofd to write the current configuration to the file. From now on it is enough
4605 4663 to start iprofd in you isdn init script, and to initialize the appropriate
4606 4664 ISDN tty devices with <tt>ATZ</tt>.
4607 4665
4608   -<sect1> dialin_manyparallel: How can I allow several people to call in
  4666 +<sect1> dialin_manyparallel: How can I allow several people to call in
4609 4667 to me at the same time?
4610 4668 <label id="dialin_manyparallel">
4611 4669 <p>
4612 4670 You have to configure exactly as many gettys or network interfaces as the
4613 4671 number of people allowed to call in at one time. These gettys or network
4614   -interfaces can be set to the same MSN, since several people can be
  4672 +interfaces can be set to the same MSN, since several people can be
4615 4673 connected to a MSN at the same time (as long as there are B channels free).
4616   -However, not more than one getty can be assigned to a single ttyI* device.
  4674 +However, not more than one getty can be assigned to a single ttyI* device.
4617 4675
4618 4676 <sect1> dialin_manycards: When using several ISDN cards, how can I react
4619 4677 upon on a call received via a specific ISDN card?
@@ -4648,7 +4706,7 @@ ttyI1 correct, or do I have to start with ttyI0?
4648 4706 <label id="dialin_hdlc">
4649 4707