[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    [kde] kppp and interface does not come up
From:       Dani Belz <kde () dan-b ! net>
Date:       2004-10-14 10:43:38
Message-ID: 200410141243.38607.kde () dan-b ! net
[Download RAW message or body]

Hi,

some time ago (3 months), I posted a question because kppp always aborted 
while dialing in with a modem connected via USB-Serial-Adapter to my computer 
(as I don't have a serial port).

I now have KDE 3.3.0 built from source and it still doesn't work. So I give it 
a second try. Maybe someone has any idea. I started kppp from a console, 
configured it and pressed the "connect button". The messages written to the 
console while dialing in are the followin:

kppp: AcctEnabled: false
kppp: End of script
kppp: QSocketNotifier stopped!
kppp: started if timeout timer with 30000
kppp: sendRequest: trying to send msg type 9
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received ExecPPPDaemon
Kernel supports ppp alright.
In parent: pppd pid 7249
kppp: recvResponse(): received message
kppp: response.status: 1
kppp: execppp() returned with return-code 1
Couldn't find interface ppp0: Kein passendes Gerät gefunden
Couldn't find interface ppp0: Kein passendes Gerät gefunden
Couldn't find interface ppp0: Kein passendes Gerät gefunden
Couldn't find interface ppp0: Kein passendes Gerät gefunden
Couldn't find interface ppp0: Kein passendes Gerät gefunden
kppp: Interface is down
[ repeated a thousend times... approximately :) ]
kppp: if_waiting_timed_out()
kppp: sendRequest: trying to send msg type 10
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received KillPPPDaemon
In killpppd(): Sending SIGTERM to 7249
kppp: recvResponse(): received message
kppp: response.status: 1
It was pppd that died
pppd exited with return value 5
Sending 6726 a SIGUSR1
kppp: Received a SIGUSR1
kppp: It was pppd that died
kppp: sendRequest: trying to send msg type 7
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received RemoveSecret
kppp: recvResponse(): received message
kppp: response.status: 1
kppp: sendRequest: trying to send msg type 7
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received RemoveSecret
kppp: recvResponse(): received message
kppp: response.status: 1
kppp: Executing command on disconnect since pppd has died.
kppp: sendRequest: trying to send msg type 4
kppp: sendRequest: sent message
Opener: received OpenResolv
kppp: response.status: 0
kppp: sendRequest: trying to send msg type 4
kppp: sendRequest: sent message
Opener: received OpenResolv
error opening resolv.conf!
kppp: response.status: -13
kppp: UnLocking Modem Device
kppp: sendRequest: trying to send msg type 3
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received RemoveLock
kppp: recvResponse(): received message
kppp: response.status: 0
kppp: sendRequest: trying to send msg type 11
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
Opener: received PPPDExitStatus
kppp: recvResponse(): received message
kppp: response.status: 5
kppp: sendRequest: trying to send msg type 5
kppp: sendRequest: sent message
Opener: received OpenSysLog
kppp: response.status: 0

Someone who can analyse these messages and who can tell me what I did wrong? 
Is there a special pppd argument I have to set for USB-Serial-Adapters?

Thanks
- Dani
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic