1 -------------------------------------------------------------------------------
3 ISDN4BSD Frequently Asked Questions
4 ===================================
6 last edit-date: [Wed Nov 1 15:08:03 2000]
8 $FreeBSD: src/share/examples/isdn/FAQ,v 1.6.2.2 2002/08/07 10:47:48 blackend Exp $
10 --------------------------------------------------------------------------------
15 1. How do I get started with synchronous PPP (sPPP) ?
16 2. does anyone know a software that can receive/send fax over ISDN ?
17 3. does i4b callback only work with setups where the remote end
19 4. trouble with kernel options IPFIREWALL and IPDIVERT and natd
20 5. I want to use -r with isdnd but it does not work
21 6. How do I configure and run the answering machine ?
22 7. Teles S0/16.3 ... unknown ?
23 8. How do i integrate a new lowlevel driver into i4b ?
24 9. Why it always says "no Space in TX FIFO - State F4 awaiting" ?
25 10. Incoming alert - what does it mean ?
26 11. How do i change irq's on my teles 16.3 card ?
27 12. NL: i'm getting CAUSE 100 or CAUSE 101 when dialling out
28 14. I'm using sPPP. I can connect to my ISP but no TCP/IP services work. HELP!
29 15. i4b 0.80.00: problems with AVM Fritz PCI
30 16. How do i setup logfile rotation for isdnd ?
31 17. How do i setup dialin from Windows NT RAS to i4b ?
32 18. How can I convert my old .g711a files to the new format?
33 19. I have lots of old .g711a files to convert what can I do?
34 20. How can I convert the .al files to Sun/NeXT .au/.snd/.vox files?
35 21. Help, isdn4bsd 0.82 fails to probe my Elsa PCC-16!
36 22. How do i enable and configure userland PPP with i4b ?
37 23. What is the procedure to install a new i4b on FreeBSD 3.x ?
38 24. Why do i get "ifconfig: ioctl (SIOCAIFADDR): file exists" ?
39 25. How to properly operate isdnd's fullscreen output in a 132x60 vty
40 26. NetBSD: i see isic0 while booting but I cannot access my Fritz!Card
41 27. i4b_pci_attach: pci_map_port 1 failed! What does this mean ?
42 28. What is: i4b-L2 i4b_rxd_ack: ((N(R)-1)=35) != (UA=36) !!!
43 29. Why does isdnd take up 95% CPU time ?
46 1. How do I get started with synchronous PPP (sPPP) ?
47 ================================================================================
49 Of course you first have to have sPPP interfaces in your kernel. If
50 you installed everything using FreeBSD/install.sh then the correct
51 entries should have been automatically made in /sys/conf/files for you.
52 For NetBSD it isn't quite as simple since NetBSD/install-netbsd.sh does
55 Then all you need to do is put an entry like this:
59 into your kernel configuration file (if it's not already there) and
60 generate and boot the new kernel. The above line will give you 4
61 sPPP interfaces - isp0 to isp3.
63 Then just modify /etc/isdn/isdnd.rc (see the example in etc-isdn/isdnd.rc)
64 to suit your needs (telephone numbers, etc).
66 The next step is to read the ispppcontrol man page and then to look at
67 etc/rc.isdn-PPP. ispppcontrol is a very important component in getting
68 sPPP working correctly and the ispppcontrol lines in your /etc/rc.isdn
71 In my experience there are two things which can cause problems:
73 1) the authproto line has to agree with what your ISP desires. In
74 general I've found that it's best to have something like this -
76 ispppcontrol <interface> myauthproto={pap,chap} myauthname=<AuthName>
77 myauthsecret=<AuthSecret> hisauthproto=none callin
79 The "hisauthproto=none" is usually needed because the ISP does not want
80 to authorise himself to you; he expects you to authorize yourself to him !
81 I once forgot to set hisauthproto and it took me quite a while to figure
82 out why I couldn't connect.
84 2) the IP address at your ISP's end must be correct.
86 How can I find out (1) whether my ISP wants pap or chap and (2) what his
87 IP address is ? you might ask. Generally, your ISP should have provide
88 this information to you. But, if he didn't, or you've mislayed the
89 documentation (as I did), there's still hope.
91 Fortunately, J"org Wunsch implemented the sPPP kernel code so that it
92 provides all the information required if the interface is configured
93 with the debug flag set (e.g. ``ifconfig isp0 debug''). It's just a
96 By the way, I suggest turning the debug flag on until you have things
97 working and then turning it off. The debug output is rather voluminous
98 and could fill up your /var partition, otherwise.
100 The debug output will appear on the console and also be logged to
101 /var/log/messages (under FreeBSD) unless you changed /etc/syslog.conf.
103 A. How to figure out the authproto
104 ----------------------------------
106 Here is an example where I configured isp0 with myauthproto=pap, my
107 ISP wanted chap, but was willing to accept pap:
109 /kernel: isp0: lcp up(starting)
110 /kernel: isp0: lcp output <conf-req id=0x7 len=10 5-6-34-e4-30-5a>
111 /kernel: isp0: lcp input(req-sent): <conf-req id=0x1 len=30 0-4-0-0-1-4-5-
112 f4-3-5-c2-23-5-11-4-5-f4-13-9-3-0-c0-7b-6e-fe-b5>
114 |___ c223 is chap, it's what the ISP wants to use
116 /kernel: isp0: lcp parse opts: 0x0 [rej] mru auth-proto 0x11 [rej]
117 x13 [rej] send conf-rej (I didn't agree)
118 /kernel: isp0: lcp output <conf-rej id=0x1 len=21 0-4-0-0-11-4-5-f4-13-9-3-
120 /kernel: isp0: lcp input(req-sent): <conf-ack id=0x7 len=10 5-6-34-e4-30-5a>
121 /kernel: isp0: lcp input(ack-rcvd): <conf-req id=0x2 len=13 1-4-5-f4-3-5-
123 /kernel: isp0: lcp parse opts: mru auth-proto
124 /kernel: isp0: lcp parse opt values: mru 1524 auth-proto [mine 0x0 !=
125 his chap] send conf-nak (we want to use pap, not chap)
126 /kernel: isp0: lcp output <conf-nak id=0x2 len=9 3-5-c0-23-5>
130 /kernel: isp0: lcp input(ack-rcvd): <conf-req id=0x3 len=12 1-4-5-f4-3-4-
131 c0-23> (he agrees to use pap)
132 /kernel: isp0: lcp parse opts: mru auth-proto
133 /kernel: isp0: lcp parse opt values: mru 1524 auth-proto send conf-ack
134 /kernel: isp0: lcp output <conf-ack id=0x3 len=12 1-4-5-f4-3-4-c0-23>
135 he agrees to use pap ___|^^^^^
137 so, if you have problems in the lcp phase, check which authentication method
138 your ISP wants to use. Usually chap is prefered, but pap will be accepted.
140 B. How to figure out the ISP's IP address
141 -----------------------------------------
143 ======================================================================
145 UPDATE NOTE (February 8, 1999):
147 Jan Riedinger writes:
148 ---------------------
149 >I further think Gary should mention
150 >in the FAQ in the section "B. How to figure out the ISP's IP address
151 >that it isn't normaly necessary to do it because of the auto
152 >address negotiation.
156 I think you're right. I wrote that stuff before the support for
157 negotiation of the IPS's address was added to if_spppsubr.c.
159 ======================================================================
162 I also intentionally configured the interface with the wrong address for
165 ifconfig isp0 0.0.0.0 10.0.0.1 debug link1
167 this means that I want the ISP to assign me an address (the 0.0.0.0) and
168 that I expect him to use 10.0.0.1 (which is wrong). Here's the result:
169 (note that these addresses have been changed by me)
171 /kernel: isp0: phase network
172 /kernel: isp0: ipcp open(initial)
173 /kernel: isp0: ipcp up(starting)
174 /kernel: isp0: ipcp output <conf-req id=0x9 len=10 3-6-0-0-0-0>
175 /kernel: isp0: ipcp input(req-sent): <conf-req id=0x1 len=16 2-6-0-2d-f-1-
177 /kernel: isp0: ipcp parse opts: compression [rej] address send conf-rej
178 /kernel: isp0: ipcp output <conf-rej id=0x1 len=10 2-6-0-2d-f-1>
179 /kernel: isp0: ipcp input(req-sent): <conf-nak id=0x9 len=10 3-6-c-22-38-4e>
180 /kernel: isp0: ipcp nak opts: address [wantaddr 12.34.56.78] [agree]
182 |___ he assigns me this
184 /kernel: isp0: ipcp output <conf-req id=0xa len=10 3-6-c3-b4-eb-63>
185 /kernel: isp0: ipcp input(req-sent): <conf-req id=0x2 len=10 3-6-62-4c-36-20>
186 /kernel: isp0: ipcp parse opts: address
187 /kernel: isp0: ipcp parse opt values: address 98.76.54.32 [not agreed]
189 |_this is *his* address
191 /kernel: isp0: ipcp output <conf-nak id=0x2 len=10 3-6-a-0-0-1>
192 I expect a different address and (incorrectly) reject what he wants.
193 I tell him that I expect 10.0.0.1. After this the connection fails.
195 Anyway, I now know that his address is really 98.76.54.32 and can use
196 it to correctly configure the interface.
198 With the correct IP address I shoulkd now be able to connect with no
199 problems. As stated above, the authorization protocol is normally not
200 so important since most ISPs are willing to use pap, although chap is
201 more secure. Generally, I'd try chap first and only switch to pap if
202 the ISP doesn't accept it.
204 (by Gary Jennejohn, Home - garyj@muc.de, Work - garyj@fkr.dec.com)
208 2. does anyone know a software that can receive/send fax over ISDN ?
209 ================================================================================
213 > does anyone know a software that can receive/send fax over ISDN? I am
214 > using a Fritz!Card, which can handle group 3 (analogous) fax, but I
215 > can't find any hint in the i4b software that this is supported in any
218 This is probably not implemented.
220 Implementing G3 fax in ISDN would mean simulating an analog modem
221 on the digital link. This means having to generate the right waveforms
222 for the modulated data, and receive analog data from the other end
223 which you had to run FFT analysis on and then interpret.
225 In addition you have to do this in realtime, to be able to deal with
226 the timing involved in the fax protocol, something neither
227 FreeBSD or Linux is good at in their native form..
229 A third point is that a software simulated faxmodem usually does not
230 work well. I tested Teles software faxmodem in Win-95 towards an Ericsson V34
231 HE modem, and was able to send faxes from the ISDN card at 4800 baud
232 only, and receive faxes ad 9600 baud only(!) (And it is not the
233 Ericsson modems fault, it works flawlessly towards other fax machines.)
235 My point is that the best thing to do is to use an ordinary faxmodem
236 to handle faxes with Hylafax of mgetty+sendfax or efax, or you may use
237 a combined ISDN card with an analog part.
239 Of course, if you are crazy enough, you may try to implement a
240 software simulated modem in e.g. RT-linux, or a similar realtime
241 extension for FreeBSD.
244 Nils Ulltveit-Moe (etonumo@eto.ericsson.se)
248 3. does i4b callback only work with setups where the remote end returns a busy ?
249 ================================================================================
251 > Is my assumption correct, does i4b callback only work with setups where
252 > the remote end returns a busy on the dialin?
254 Yes - otherwise you'll pay for the connection, at least here in Germany.
256 Most routers support two kind of callbacks - the one that i4b supports
257 means: the called system rejects (so no charge for this connection), waits
258 a configurable time and the calls back. Information on who has called and
259 who is to be called back relies on the ISDN calling party number information
260 and stuff statically configured in the routers (or isnd's) configuration.
262 The other type of callback (not supported by i4b right now) means: the
263 called system accepts the connection and starts ppp negotiation. During this
264 the ppp's aggree to do a callback. Information on who called in and who is
265 going to be called back is subject to the authentication/negotiation already
266 done by the two ppp's. Then ppp closes down, the connection is disconnected
267 and the called system calls back.
269 I've never seen someone actually use the second type due to its obvious
270 disadvantages. It may be usefull if you travel, call in from an unknown
271 number and want to be called back at that number.
273 Martin Husemann <martin@rumolt.teuto.de>
276 4. trouble with kernel options IPFIREWALL and IPDIVERT and natd
277 ================================================================================
279 NOTICE: section obsolete since IP address changes are handled properly now!
280 ===========================================================================
283 > Trying to build a router/gateway between my privat Ethernet and
284 > the Internet (via my ISP), I have problems with I4B or NAT (I think:).
286 > The 2.2.5-R kernel with options IPFIREWALL and IPDIVERT works fine
287 > with ISDN4BSD 0.50-alpha and firewall rule 'pass all from any to any'.
288 > However, when I add 'divert natd all from any to any via isp0'
289 > and start natd, name server lookups to the ISP's NS don't work.
291 > Also, ping and nslookup fails from any other internal host.
293 I had exactly the same problems. natd doesn't seem to get a message if
294 the IP address of the interface changes (after successful dialout).
295 I have to manually send a HUP signal to natd. I do this via the following
298 I added the following two lines to the system section of isdnd.rc:
299 regexpr = "call active" # look for matches in log messages
300 regprog = hup_natd # execute program whan match is found
302 The small script "hup_natd", located in /etc/isdn, looks like:
304 pid=`cat /var/run/natd.pid`
311 It looks ugly, but at least for me it works. The two sleeps are necessary
312 since I have to wait for ppp negotiation to complete (I don't get a message
313 from isdnd for that). If I'm lucky I have my connection after 3 seconds,
314 but 8 seconds should suffice for worst case (the first HUP without a sleep
315 sometimes even succeeded on an slow 486/33 with 8MB RAM, more HUPs don't hurt).
317 I'm really interested in some more elegant method.
319 Daniel (rock@cs.uni-sb.de)
322 Arve Ronning replied:
323 =====================
325 > I had exactly the same problems. natd doesn't seem to get a message if
326 > the IP address of the interface changes (after successful dialout).
328 Well, it (natd) _does_ pick up the dynamic address supplied for isp0.
329 Try 'natd -verbose ...' and you'll see it. Otherwise I agree, there is
330 certainly something missing in natd's functionality, or maybe sppp
332 supply what it's supposed to ??
334 > I have to manually send a HUP signal to natd. I do this via the following
337 YES...super; strange but correct. It works when I send natd a -HUP after
338 sppp is up. Thanx for the tip. However, natd must be -HUPed _every_ time
339 sppp has been down (idle timeout) and comes back up!
341 > I'm really interested in some more elegant method.
343 So am I, let's see what may come out of the discussion on the list.
347 5. I want to use -r with isdnd but it does not work
348 ================================================================================
350 > > Use isdnd in fullscreen mode.
352 > I tried that already, but got an error when I start isdnd that way:
354 > /usr/local/bin/isdnd -d 0xf9 -f -r /dev/ttyv1 -t cons25
356 > root is logged in on device /dev/ttyv1, the message in /var/log/messages looks like:
358 > "May 22 11:52:28 asterix isdnd[4160]: ERR ERROR, cannot setup tty as controlling terminal: Operation not permitted"
360 > How can I give this device permission ?
363 In case you want to use switch "-r" noone else _must_ use the tty you redirect
364 to, you have to remove the getty from the virtual terminal in /etc/ttys and
365 restart the init process.
368 6. How do I configure and run the answering machine (under FreeBSD 2.2.x) ?
369 ================================================================================
371 The answering machine will be activated, when isdnd executes the program
372 that has been named in "/etc/isdn/isdnd.rc" in the section "telephone
373 answering" at entry "answerprog = ". If the program is executed
374 without a pathname, the answer program is expected in "/etc/isdn".
375 Examples of such programs can be found in "/etc/isdn/samples". They
378 "answer" answers only, no recording
379 "record" answers, and records messages
380 "tell" the number of the calling person is told,
382 "tell-record" calling number as answer, message is recorded
383 "isdntel.sh" answers and records messages; by using the
384 program "isdntel", one has the control over
385 the recorded messages in the directory
386 "/var/isdn". Look at "man isdntel" and
389 These programs have to be altered to suit your needs. Unfortunately there
390 is no program with which you can record your answer message. This is not
391 really bad, because you only have to alter the above mentioned program
392 "record" a bit (comment out the "if ... fi" statements for the beep
393 and msg messages). You have to create the directory "/var/isdn" first in
394 order to record messages. They will be stored in this location then.
396 Stefan Herrmann <stefan@asterix.webaffairs.net>
399 7. Teles S0/16.3 ... unknown ?
400 ================================================================================
403 I have just purchased a Teles S0/16.3 card.
404 But it's not what i4b is looking for .... I mean, it's a different card.
406 The docs (and sources)of i4b talks about a Telws S0/16.3 card with 3
409 This one (is not PnP) has jumpers for 0x180 0x280 0x380.
411 It has the SIemens Chips numbered PSB 21525 N (HSCX TE V2.1) and PSB
412 2186N V1.1 (ISAC-S TE).
414 I undestand that the 16.3c is not supported, but over this board is
415 written "TELES.S0/16.3 Revision 1.3"
417 Can anybody tell me what is this card ???
422 It's not a different card. The jumpers are documented to select
423 IO-address 0x180, 0x280 or 0x380 in some TELES manuals.
424 But in fact they select the addresses 0xd80, 0xe80 or 0xf80.
429 And an additional note from Poul-Henning Kamp:
430 ----------------------------------------------
431 There is an intricate story behind this, in short some ISA cards
432 only decode the first 10 address bits (0x3ff), which over the years
433 has resulted in a mutation the "de-facto-spec" such that addressbits
434 10-15 can be used by the card for selecting various stuff. This
435 is extensively used on obscure cards with massive IO needs, sound,
436 IEEE488 and ISDN cards often belong in this category.
440 8. How do i integrate a new lowlevel driver into i4b ?
441 ================================================================================
443 1) Request a flag value from me
444 2) add an entry for the card into FreeBSD/CONFIG
445 3) add driver filename to FreeBSD/files.i386.cat
446 4) add entry for the card to FreeBSD/options.i386.cat
447 5) add support to print type of card to diehl/diehlctl/main.c
448 6) add support to print type of card to isdnd/support.c, name_of_controller()
449 7) place your file as named in 3) into directory layer1
450 8) add the flag value and function prototypes to layer1/i4b_l1.h
451 9) add support for NetBSD to layer1/isa_isic.c
452 10) add support for attach/probe to layer1/i4b_isic.c
453 11) add card type to machine/i4b_ioctl.h and update CARD_TYPEP_MAX
454 12) add an entry to the man page man/isic.4
456 Produce diffs (please use context diffs, flag "-c" for diff) and send them in.
459 9. Why it always says "no Space in TX FIFO - State F4 awaiting" ?
460 ================================================================================
462 as I wrote about two weeks ago I had massive problems concerning this
463 "no space in TX FIFO"-thing,
465 /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal
467 Even though I used a correctly recognized Teles S0/16.3 nonpnp isdncard,
468 nothing worked, errormsgs were flooding the console until I rebooted the box.
470 I decided to play around in the BIOS-settings, I first just set them all
471 to default, which didn't work, and then changed lots of things - unfortunately
472 I can't remember them. After about hundreds of trial 'n errors I gave up.
474 A few days ago I just made another attempt, booted the box and to my surprise
475 it all worked without the smallest problem, great data rates :)
477 I tried hard to found what the something special was I changed in the BIOS
478 settings, but I just couldnt get isdnd back to its stupid behaviour it
479 showed all the time before, but I would recommend everybody who has this
480 kind of problem to look into his BIOS.
482 (from Meike Aulbach, strange@stoned.rhein-main.de)
485 i4b now works for me, I had a USB-device interfering on IRQ 9,
486 which was supposed to be only for my Creatix Card.
487 (NetBSD 1.3, Creatix)
489 Strange enough, my DOS s0-test worked, are they just polling the card?
491 Even when the testsoftware under DOS is working, don't be shure, that
492 your hw-setup is correct for xxx(x)BSD. Triplecheck all your IRQ and
493 enable and disable PNP to triple-verify. Even unconfigured devices can
494 block your card. .....
496 And that took me more than 2 months to discover :-((((
498 (from Andreas Lohrum, andreas.lohrum@consol.de)
501 when i changed the mainboard of a box that ran i4b alright, i forgot to
502 set 'used by isa' in the pnp-bios-settings for the irq of my teles
503 isdn-card. because of that some pci-card got the interrupt that the
504 isdn-card should have gotten.
505 i then also got this error: 'No space in TX FIFO'.
507 The reason occurred to my rather quick, but i would think, that this would
508 be a nice hint in a FAQ :)
510 (from Heiko Schaefer, hschaefer@fto.de)
513 after my huge amount of problems, Meike's hint (changing the
514 ISA/PNP-settings in the BIOS) finally fixed things.
515 I have only tried out this stuff with my Creatix-card, I'll check
516 out the PNP-stuff with my Sedlbauer-card soon too though.
518 (from Harold Gutch, logix@foobar.franken.de)
521 10. Incoming alert - what does it mean ?
522 ================================================================================
524 In the log on vty6 (isdnd full screen log) I'm seeing
526 16.07.98 11:42:35 CHD 00001 rwth rate 90 sec/unit (rate)
527 16.07.98 11:42:35 CHD 00001 rwth dialing from 4191236 to 441291234
528 16.07.98 11:42:35 CHD 00001 rwth outgoing call proceeding (ctl 0, ch 0)
529 16.07.98 11:42:35 CHD 00001 rwth incoming alert <<<<<<<<<<<<<<<
530 16.07.98 11:42:35 CHD 00001 rwth outgoing call active (ctl 0, ch 0)
532 What does this 'incoming alert' mean?
535 It means that it is "ringing" at the remote end.
538 11. How do i change irq's on my teles 16.3 card ?
539 ================================================================================
543 So how do you change irq's on your teles 16.3 card (under FBSD or DOS,
544 I don't have and don't want to have Windows running on that computer) ?
548 The irq is configured into the card each time the driver under whatever
549 OS you currently boot initializes the card. Thus, change the irq for the
550 isic driver in your kernel config file to one of the supported (!) irqs
551 for this card (hint: read "man isic") which is currently unused in your
552 machine and generate a new kernel.
555 12. NL: i'm getting CAUSE 100 or CAUSE 101 when dialling out
556 ================================================================================
558 This one seems to be specific for the Netherlands. (-hm)
562 I'm trying to get i4b running on my new FreeBSD 2.2.8 system. The kernel
563 compiles smootly and everything is looking fine until it's time to dial.
564 I get the following error:
566 Feb 10 20:31:00 goofy isdnd[498]: CHD 00018 I4BPPP outgoing call disconnected (remote)
567 Feb 10 20:31:00 goofy isdnd[498]: CHD 00018 I4BPPP cause 101: Message not compatible with call state (Q.850)
568 Feb 10 20:31:00 goofy isdnd[498]: ERR set_channel_idle: controller [0], invalid channel [-1]!
569 Feb 10 20:31:00 goofy isdnd[498]: ERR msg_disconnect_ind: set_channel_idle failed!
571 The remote site is a Cisco 4000 type router. I used debug to take a view at
572 the ISDN events on the router but according to that the call doesn't arrive
575 Same hardware has worked fine with FreeBSD 2.2.6/i4b 0.63.
577 Who knows what's wrong?
582 This sounds very much like your local phone number or remote phone number
583 is configured wrongly... in the Netherlands you need to specify the number
584 EXCLUDING the city code... so if you live in Utrecht and your number is
585 0301234567 you specify 1234567.
587 I have seen this in several locations in the Netherlands for years, not
588 just with i4b, but also with differentt isdn equipment.. why? guess it
589 simply depends on which operator defines your line or what exchange it
590 is connected to... :P
591 What I found is that what solved this with other isdn hardware/software,
592 also solves it for i4b.. ie.. make sure the local phone number is
593 specified, and is specified without the city code.
594 The numbering plan should be 'unknown'
596 Anyway, it would be nice if the Dutch ptt (they are called KPN btw)
597 would tell us why this happens... they havent been able to tell me in the
598 past so I guess I give up on that, but if everyone finds out whats exactly
599 happening here I'd be interested to know... :)
601 List of number configurations that I have found to almost always work in
604 1. Local phone number:
605 usually your prefered msn without city code works here.
606 (ie, 1234567 if you would like to use 0201234567 for outgoing calls)
607 on some locations leaving it blank or defining it with the city code,
608 but without the leading 0 works as well here.
610 2. remote phone number:
611 When this is a 'local' call, don't specify city code.
612 For calling parties in other cities you of cource have to use the city
613 code... in general you can say that KPN only accepts the shortest
614 possible notation where it would still be clear who you want to call.
616 3. numbers for incomming call recognition:
617 KPN always specifies incoming caller ids with city code, but without
618 leading 0. so 0201234567 will be displayed as 201234567
624 (from Bart van Leeuwen bart@ixori.demon.nl)
627 14. I'm using sPPP. I can connect to my ISP but no TCP/IP services work. HELP!
628 ==============================================================================
630 This is probably because you have the RFC1323 - TCP Extensions for High
631 Performance - support turned on and your ISP (or some router in the loop)
632 is discarding the extensions.
634 This can easily be checked by doing ``sysctl net.inet.tcp.rfc1323''. If the
635 result is 1, then the RFC1323 support is turned on.
637 Turn this off by doing ``sysctl net.inet.tcp.rfc1323=0'' (This is
638 called "net.inet.tcp.do_rfc1323" under BSD/OS).
640 For FreeBSD make sure that tcp_extension="NO" is in your /etc/rc.conf
641 (/etc/defaults/rc.conf with more recent versions of FreeBSD) and
642 /etc/rc.conf.local (in -STABLE and upcoming 3.2)
644 This may be different for NetBSD, OpenBSD and BSD/OS.
646 Martin Husemann writes:
647 -----------------------
648 This does apply for NetBSD too (and probably OpenBSD, since it's been
649 in NetBSD for a long time). The sysctl name is even compatible ;-) We don't
650 have a coresponding rc.conf entry, I do it in /etc/netstart.local.
652 I would suggest to set this to 0 on all machines routed over ISDN (not only
653 the router), as this "high speed options" in fact do slow down an ISDN link
654 by making VJ "compression" impossible - as far as I understood it. So there
655 should be a more general advice in the FAQ, not only "turn it off if it
656 doesn't work for you".
658 I've only seen the problems against old linux kernels (about two years ago),
659 are there still machines out there that have such a broken TCP/IP stack? We
660 should start to blame the vendors...
662 (by Gary Jennejohn, garyj@muc.de, with additions from
663 Harold Gutch <logix@foobar.franken.de> and
664 Martin Husemann <martin@rumolt.teuto.de>).
667 15. i4b 0.80.00: problems with AVM Fritz PCI
668 ==============================================================================
673 The system is FreeBSD 3.1-RELEASE with i4b-00.80.00-beta-070599 [...]
675 I'm trying to compile a Kernel with support for my AVM Fritz!PCI card,
676 however, when compiling, it fails with the following error
678 sh ../../conf/newvers.sh GENERIC -DAVM_A1_PCI
679 cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-
681 -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -
683 ed -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../..
685 r/include -DAVM_A1_PCI -DKERNEL -DVM_STACK -include opt_global.h -elf
688 i4b_isic_pci.o: In function `i4b_pci_attach':
689 i4b_isic_pci.o(.text+0x141): undefined reference to `avma1pp_map_int'
690 i4b_isic_pci.o: In function `isic_pciattach':
691 i4b_isic_pci.o(.text+0x196): undefined reference to `isic_attach_avma1pp'
700 > i4b/layer1/i4b_avm_fritz_pci.c optional isic device-driver
702 > and am recomiling at the moment, but given that it's a 486, it could take
705 The problem appears to be that overinstall.sh does not update files.i386
706 and options.i386, and that AVM_A1_PCI was added after 3.1-RELEASE and
707 hence is not defined.
709 Manually editing these files (using install.sh as a guide) allows the
710 kernel to compile cleanly.
713 (from Rich Wood, rich@dynamite.org)
716 16. How do i setup logfile rotation for isdnd ?
717 ==============================================================================
719 For syslog-based logging:
720 -------------------------
722 man newsyslog (on FreeBSD)
724 You just add a line to /etc/newsyslog.conf:
725 /var/log/isdnd.log 664 7 100 * Z
726 and you are all done...
728 (From: Andreas Haakh <ah@alvman.RoBIN.de>)
731 For logfile-based logging:
732 --------------------------
734 I suggest using newsyslog(8). Adding a line like:
736 /var/log/isdn.log 664 100 * 168 Z /var/run/isdnd.pid
738 to /etc/newsyslog.conf will do the job (here: once a week, for the next
739 100 weeks) with compression of the old log.
741 This is the standard method for other daemons (apache, etc.).
743 (From: Udo Schweigert <ust@cert.siemens.de>)
746 17. How do i setup dialin from Windows NT RAS to i4b ?
747 ==============================================================================
749 > > I need to be able to dial in from a WNT box, equipped with TELES h/w and
750 > > s/w, to a FreeBSD machine. I don't have a clue what RAS is using.
752 > > ipr and isp. The latter seems to work but is hanging on authentication. Is
753 > > there somebody who has done this before and is able to give me some hints?
755 > RAS is using PPP, so you should be able to get the isp interface working. I
756 > haven't done it so I can't give you concrete hints, but setting the isp
757 > interface to debug mode and posting the log (with passwords cut out or with
758 > test passwords) could help us to debug your setup.
760 I have several customers using sPPP do dial in from their W95/W98/WNT.
762 If You use FreeBSD_3.2-BETA with i4b-071 or older then you have to apply
763 the attached patch to /sys/net/if_spppsubr.c (patch -p0 <patchfile).
765 You need to configure isp0. See the manpages or the supplied templates in
766 the i4b-distribution. I would suggest to supply an ip-number for the
767 isp0-interface and force the clients to accept this value.
768 Don't forget to supply the relevant parameters to sppconfig_isp0 in
771 On WNT you have to install the CAPI-2.0-drivers and Dialin-network.
773 Create a new entry and check the following box:
774 * Connection to internet
775 select the appropriate ISDN-device for dialout, insert a phone-number
777 You are asked for username & password. Supply the values You did define in
778 spppconfig_isp0 and dial...
780 Patch for i4b version 0.71 or older:
781 ------------------------------------
783 *** /sys/net/if_spppsubr.c Sun Dec 27 22:30:44 1998
784 --- /sys/net/if_spppsubr.c.orig Sat May 8 10:54:14 1999
788 addlog("[non-empty] ");
789 /* suggest a zero one */
790 ! p[2] = p[3] = p[4] = p[5] = 0;
796 addlog("[non-empty] ");
797 /* suggest a zero one */
798 ! /* p[2] = p[3] = p[4] = p[5] = 0; */
804 addlog("%s [not agreed] ",
805 sppp_dotted_quad(desiredaddr));
807 - p[2] = hisaddr >> 24;
808 - p[3] = hisaddr >> 16;
809 - p[4] = hisaddr >> 8;
814 /* Add the option to nak'ed list. */
816 addlog("%s [not agreed] ",
817 sppp_dotted_quad(desiredaddr));
820 + p[2] = hisaddr >> 24;
821 + p[3] = hisaddr >> 16;
822 + p[4] = hisaddr >> 8;
826 /* Add the option to nak'ed list. */
828 (From: Andreas Haakh <ah@alvman.RoBIN.de>)
831 18. How can I convert my old .g711a files to the new format?
832 ================================================================================
833 I got the best results with:
834 cat /some/path/dwhello.g711a | alaw2ulaw | g711conv -u > /tmp/newhello.al
836 (From: David Wetzel <dave@turbocat.de>)
839 19. I have lots of old .g711a files to convert what can I do?
840 ================================================================================
842 Create a shell script (/tmp/csnd.sh) with this contents:
845 OLDFILES=`ls *.g711a`
848 for THEFILE in $OLDFILES
851 echo -n "converting $THEFILE..."
852 BASENAME=`basename $THEFILE .g711a`
854 /bin/cat $THEFILE | alaw2ulaw | g711conv -u > $BASENAME.al
861 then type "chmod a+x /tmp/csnd.sh" in you shell.
862 cd /usr/local/lib/isdn (or where your old sounds live)
865 rm *.g711a (you should know what you do here :-)
867 (From: David Wetzel <dave@turbocat.de>)
870 20. How can I convert the .al files to Sun/NeXT .au/.snd/.vox files?
871 ================================================================================
873 /bin/cat /some/path/old.al | sox -t raw -A -b -r 8000 - -t .au /some/path/new.snd
876 (From: David Wetzel <dave@turbocat.de>)
879 21. Help, isdn4bsd 0.82 fails to probe my Elsa PCC-16!
880 ================================================================================
882 >Isdn4bsd 0.82 fails to probe my Elsa PCC-16. It just can't find isic0.
884 flags have changed from 19 to 20.
887 (From: "Frank J. Beckmann" <frank@vogon.agala.harz.de>)
890 22. How do i enable and configure userland PPP with i4b ?
891 ================================================================================
893 NOTE: this is the procedure used as of end of July 1999, it may change in
896 Get the current ppp sources from
898 http://www.freebsd.org/~brian
900 unpack them and apply the patch
902 ftp://ftp6.uk.freebsd.org/pub/PPPoISDN/pppcommit.patch
904 to the ppp directory (where you just unpacked the above mentioned ppp source).
905 Make and install the result.
907 Have a look at the user-ppp directory and the end of etc-isdn/isdnd.rc.sample
908 for ppp and i4b sample configurations to get things up and running.
910 More information to ppp setup can be found at
912 http://www.Awfulhak.org/ppp.html
913 http://www.freebsd.org/doc/handbook/ppp-and-slip.html
914 http://www.freebsd.org/doc/faq/ppp.html
916 and in the directory "user-ppp" of the isdn4bsd distribution.
919 23. What is the procedure to install a new i4b on FreeBSD 3.x ?
920 ================================================================================
925 tar xvzf i4b-00.82.00-beta-140799.tar.gz
936 cd ../../compile/<YOURKERNEL>
944 (From: Luke Roberts <luke@roberts.nl>)
947 24. Why do i get "ifconfig: ioctl (SIOCAIFADDR): file exists" ?
948 ================================================================================
950 Ich ?berlege gerade, aber ich glaube, ich bekomme sie auch. Das
951 Problem existiert schon seit geraumer Zeit immer beim Konfigurieren
952 eines point-to-point Interfaces (SLIP, PPP).
954 Das `file exists' ist ein Misnomer, es r?hrt daher, da? der
955 Routingcode die errno's in einer leicht ver?nderten Weise benutzt, so
956 da? nicht neue errno's daf?r erfunden werden mu?ten. Lies es als
957 `route exists'. (Und falls Du im Zusammenhang mit Routing mal ein `no
958 such process' siehst, lies es als `no such route'.)
960 Die Meldung ist harmlos. Sonst h?tte ich mir schon l?ngst mal die
961 M?he gemacht, mich durch den ganzen Routing-Code zu hangeln und zu
962 sehen, warum das passiert.
964 (From Joerg Wunsch <j@uriah.heep.sax.de>)
967 25. How to properly operate isdnd's fullscreen output in a 132x60 vty
968 ================================================================================
970 Q: I'm using allscreens_flags="132x60" in /etc/rc.conf but the vty gets
971 switched after isdnd is started, so isdnd didn't know about the new
972 dimensions of the screen.
975 In /etc/rc.isdn change
978 isdn_ttype=cons60l1wide
979 /usr/sbin/vidcontrol VESA_132x60 < ${isdn_fsdev}
981 The new VESA modes don't have termcap entries yet, so you'll
982 have to add one yourself to define 132x60:
984 cons60l1wide|cons60-iso8859-1:\
988 (From: "H. Eckert" <ripley@nostromo.in-berlin.de>)
991 26. NetBSD: i see isic0 while booting but I cannot access my Fritz!Card
992 ================================================================================
995 isic0 at pci0 dev 8 function 0: Fritz!Card
996 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
997 isic0: interrupting at irq 11
999 i4b: ISDN call control device attached
1000 i4btrc: 2 ISDN trace device(s) attached
1001 i4bctl: ISDN system control port attached
1002 i4brbch: 4 raw B channel access device(s) attached
1003 i4btel: 2 ISDN telephony interface device(s) attached
1004 i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression)
1005 i4bisppp: 2 ISDN SyncPPP device(s) attached
1007 But I could not use the card, because I forgot
1008 "options __I4B_IS_INTEGRATED" in the kernal config file.
1009 [Jan Sparud helped me to find that]
1011 (From: David Wetzel <dave@turbocat.de>)
1014 27. i4b_pci_attach: pci_map_port 1 failed! What does this mean ?
1015 ================================================================================
1019 I am trying to set up a ELSA QuickStep 1000pro PCI ISDN adaptor in a FreeBSD
1020 3.3 box. I configured the kernel according to the i4b.ps documentation. At
1021 boottime, these messages are displayed:
1023 isic0: <ELSA QuickStep 1000pro PCI ISDN adaptor> rev 0x01 int a irq 11 on
1025 i4b_pci_attach: pci_map_port 1 failed!
1027 What does this mean ?, should I be worried ?, will the device function
1030 A: Problem is solved.
1032 In the BIOS, the PCI slot containing the ISDN card was set to IRQ 14 (having
1033 no IDE devices). The isic driver finds the card using irq 11 and then says
1034 "pci_port_map_port failed". The slot is set to IRQ 11 (which was free also)
1035 and everything works fine here ..
1037 From: Joost Mulders <dhcp@j-mulders.demon.nl>
1040 28. What is: i4b-L2 i4b_rxd_ack: ((N(R)-1)=35) != (UA=36) !!!
1041 ================================================================================
1043 > Some time I get follow message at console:
1045 > i4b-L2 i4b_rxd_ack: ((N(R)-1)=35) != (UA=36) !!!
1047 A layer 2 error occured. These types of errors are automatically
1048 corrected by the layer 2 protocol.
1051 29. Why does isdnd take up 95% CPU time ?
1052 ================================================================================
1054 Q: i just set up my isdn w/ user ppp, it works nice, but my isdn daemon takes
1055 up 95% of my CPU time.
1059 Mem: 42M Active, 4616K Inact, 11M Wired, 2896K Cache, 14M Buf, 408K Free
1060 Swap: 132M Total, 5128K Used, 127M Free, 3% Inuse
1062 PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
1063 63 root 58 0 1372K 752K RUN 38:05 93.75% 93.75% isdnd
1064 207 gboehm 2 0 25196K 22044K select 1:15 2.20% 2.20% XF86_Mach64
1067 A: i just found out what i did wrong ...
1068 i forgot to set these both lines in my /etc/rc.conf:
1073 had to do that if i want to run isdnd as an daemon service, 'cause the
1074 defaults in /etc/defaults/rc.conf are:
1076 isdn_fsdev="/dev/ttyv4" # Output device for fullscreen mode (or NO for daemon mode).
1077 isdn_flags="-dn -d0x1f9" # Flags for isdnd
1079 From: Guido Boehm <g.boehm@web.de>