Bugzilla – Bug 141101
ippp0 doesn't come up at boot time
Last modified: 2006-01-04 13:49:51 UTC
I can't use my ISDN FRITZ Card PCI v. 2.0 Capi drivers are installed. But if I try to start network manually I get this message /etc/init.d/network start Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) eth0 configuration: eth-id-00:e0:18:da:65:49 eth0 (DHCP) . . . . . no IP address yet... backgrounding. waiting ippp0 error in /sbin/isdnctrl addif ippp0 failed Setting up service network . . . . . . . . . . . . . . done. entering /sbin/isdnctrl addif ippp0 shows Can't open /dev/isdnctrl or /dev/isdn/isdnctrl: No such device but /dev/isdnctrl is present did I make something wrong or is it a bug?
Seems the drivers are not loaded successfully. Does it work after rcisdn start ?
(In reply to comment #1) > Seems the drivers are not loaded successfully. > Does it work after rcisdn start ? > OK ippp0 is loaded now but I still can't use kinternet because there is no interface even though I configured ISDN everything with Yast. Where should rcisdn be started automaticly?
Is smpppd running ? What is in /etc/sysconfig/isdn/cfg* ?
(In reply to comment #3) > Is smpppd running ? > What is in /etc/sysconfig/isdn/cfg* ? > smppd is running content of cfg-contr0 AREACODE="+49 30" DIALPREFIX="" DRIVER="fcpci" ISDNLOG_START="yes" NAME="AVM FRITZ!Card PCI v2.0" PARA_SUBTYPE="2" PARA_TYPE="8002" PROTOCOL="euro" STARTMODE="auto" UNIQUE="gZD2.GGXqL9GEYV1" content of cfg-net0 CALLBACK="off" CBDELAY="2" CHARGEHUP="on" DEFAULTROUTE="no" DYNAMICIP="yes" FIREWALL="yes" IPADDR="192.168.99.1" IPPPD_OPTIONS="" MSN="43604508" MULTILINK="yes" PROTOCOL="syncppp" PROVIDER="provider0" PTPADDR="192.168.99.2" REMOTE_IN="" SECURE="on" STARTMODE="auto" USERCONTROL="no" NAME="ISDN-Verbindung"
I found that USERCONTROL="no" has to be set to "yes" now it works I think the german explanation is not quite clear how to use this option
Yes USERCONTROL=yes have to be set, if kinternet should have control over the device.