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

List:       kde-devel
Subject:    Re: Little Summary of "Daemon for managing dialup internetconnec
From:       Carsten Pfeiffer <carpdjih () cetus ! zrz ! TU-Berlin ! DE>
Date:       1999-07-01 22:00:26
[Download RAW message or body]

On Tue, Jun 29, 1999 at 01:01:30PM +0200, Matt Koss wrote:

Hi,

sorry for my bad responsiveness, I'm really short on time these days
(well, actually that's weeks already :-/ )
 
> >> BTW, is NetMgr suitable for ISDN connections ?
> >> I am writing kisdn everywhere, but I still don't know if it can be used
> >> here.

generally - yes. Currently, kisdn has no commandline options to
connect/disconnect. You just could send it a USR1 to connect or HUP to
disconnect. But we still have plans to make a commandline version of
kisdn.

> >  Both actions setup a timer. If timer expires, connecting (or
> >  disconnecting) is considered failed. Clients which have requested so,
> >  gets informed about failure (or success) via the NetMgr-notify-system.
> 
> That's nice, but how will it interfere with kppp / kisdn ?
> AFAIK kppp has it's own timer for failure detection. I don't know 'bout kisdn.

If a connection can't be established, kisdn notices this. However, there
is currently no way to find out, whether authentication failed or passed,
or if the handshake of the ipppd worked properly. kisdn just knows if the
(physical) connection is up or not. There is a timeout after which kisdn
'assumes' everything went ok, tho.
 
I'm all for this KNetManager, and we definitely want to help making
this stuff work properly.

Cheers,
Carsten Pfeiffer
-- 
http://www.geocities.com/SiliconValley/1632/

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