In /etc/conf.d/isdn you specify the number of channels. /etc/init.d/isdn then creates devices based on than number. If you specify 2 (for ISDN BRI), the devices are: /dev/isdnctrl[01] /dev/isdn[01] /dev/ippp[01] /dev/ttyI[01] BUT: - There should be only isdnctrl0, since there is only one controller (and one D-channel). - The number of ttyI devices is independent of the number of controllers (in Germany for instance, you get three MSNs per BRI, so you could start 3 vboxgettys on /dev/ttyI[012]) - The number of ippp devices is independent of the number of controllers, too. You could configure 64 ippps to dial in to 64 different providers using just one controller. Although you can actively use only two ttyI / ippp at a time, you should be able to *configure* more than that.
Which ebuild and version are you talking about?
Sorry, I forgot to mention the ebuild: net-dialup/isdn4k-utils-3.9_pre20060124 Seems to be the most recent one.
OK, if you don't reopen next time, changes are noone will ever notice again.
first of all: isdn4k is legay stuff and udev-support will be never implemented anymore. So the device-create-stuff is an ugly hack, but it works for those who still needs it. The option in conf.d is there to limit the number of device-nodes. If you just have 1 or 2 controllers, you don't need all 64 slots. 2nd: you are right what you say about BRI = 2 channels. But if you read the docs, isdn4k uses logical channels. You can indeed map only 1 channel and then you can have something like this: ctrl 0 = isdn card 0 channel 0 crtl 1 = isdn card 1 channel 0/1 ctrl 2 = isdn card 1 channel 0/1 you will see such strange mappings when you use AVM DSL/ISDN-Combi-Controllers, where the DSL part is connected via CAPI but implements only 1 logical channel (mapped to isdn4k via 'capidrv'). So you *really* need to create all isdnctrlX nodes, even if most of the time 2 ctrl-nodes accesses the same controller. isdn4k is strange, long live CAPI! :-D btw: if you are not locked with a legacy ISDN-card w/o CAPI/mISDN-support, move to CAPI. I4L will die! Then you can use ordinary PPP with pppcapiplugin and can have as many provider-configs as you like. well, after this explaination: it's a WONTFIX
