Description of problem:
pppd is packaged in version 2.4.2, capiplugin.so is of version 2.4.1. that does not
Version-Release number of selected component (if applicable):
just start a pppd with an option of "plugins capiplugin.so"
Steps to Reproduce:
no capi-based ppp-service (disappointing)
working capi-based ppp-service
volunteer(rhce) wanted? please contact me.
it's now fixed in isdn4k-utils-3.2-16.p1.1, which should be available
in rawhide. Thanks for your report
Does the capi-based ppp-service work for you with this version?
no, it does not work ;-(
first: /usr/lib/libcapi20.so is missing but a simple ln -s
libcapi20.so.2 libcapi20.so seems to be a workaround
next: starting a pppd with capiplugin.so results in this messages:
Jun 29 21:39:34 zabelthau pppd: Plugin capiplugin.so loaded.
Jun 29 21:39:34 zabelthau pppd: capiplugin: $Revision: 1.32 $
Jun 29 21:39:34 zabelthau pppd: capiconn: 1.7
Jun 29 21:39:34 zabelthau kernel: CSLIP: code copyright 1989 Regents
of the University of California
Jun 29 21:39:34 zabelthau kernel: PPP generic driver version 2.4.2
Jun 29 21:39:34 zabelthau pppd: pppd 2.4.2 started by root, uid 0
Jun 29 21:39:34 zabelthau pppd: capiplugin: phase serialconn.
Jun 29 21:39:34 zabelthau pppd: capiplugin: dialing 00191011 (hdlc)
Jun 29 21:39:36 zabelthau pppd: capiplugin: connected: "29" ->
"00191011" outgoing (pcli=0x301/ncci=0x10301)
Jun 29 21:39:36 zabelthau pppd: capiplugin: tty /dev/capi/0
doesn't exist - CAPI Filesystem Support not enabled in kernel or not
Jun 29 21:39:37 zabelthau pppd: capiplugin: disconnect(local):
"29" -> "00191011" outgoing (pcli=0x301/ncci=0x10301) 0x349f (0x0000)
- Normal, unspecified
Jun 29 21:39:37 zabelthau pppd: capiplugin: exit
Jun 29 21:39:37 zabelthau pppd: Exit.
the layer-2-hdlc-connection seems to be stablished (right?) but then
capiplugin looks for a device /dev/capi/0 i don' see it, there are
just a lot of /dev/capi20.##
it looks like the kernel does not support CAPI! in this case you have
to enable CAPI Support in kernel and rebuild again. Could you try it
no, the kernel supports capi. the problem was, that the module capifs was loaded but
the capi-filesystem was not mounted, which is usually done unter /dev/capi. I will
attach a gpl'ed patch for isdn4k-utils-3.2-16.p1.1 to this bug-report next weekend if
that is usefull for you. please reassign the bug-report as NEEDINFO to me if you want
Benedikt, it would be great if you could send the patch please. Thanks
the new isdn4k-utils in the rawhide included the fix for this problem. Thanks for