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

List:       kde-bugs-dist
Subject:    [Bug 78836] New: Connection Status plugin doesn't
From:       meldroc () frii ! com
Date:       2004-03-31 23:30:38
Message-ID: 20040331233038.30475.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=78836      
           Summary: Connection Status plugin doesn't
           Product: kopete
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kopete-devel kde org
        ReportedBy: meldroc frii com


Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc (GCC) 3.3.3 (Debian 20040321) 
OS:          Linux

For me, the Connection Status plugin doesn't.  From what I've googled, this plugin \
uses netstat -rn to see if a default gateway exists.

When I'm offline, netstat -rn gives me 

meldroc localhost:~$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

Online, I get

meldroc localhost:~$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
170.147.45.137  0.0.0.0         255.255.255.255 UH        0 0          0 ppp0
0.0.0.0         170.147.45.137  0.0.0.0         UG        0 0          0 ppp0

which theoretically should let Kopete know when I'm on or not.  Nevertheless, if I \
disconnect using kppp, kopete shows my status as still online, and if I start kopete \
while offline, then go online, kopete shows the pulsating connecting icons for each \
service forever (or until I manually disconnect all & connect all.)

The current method strikes me as being very brittle.  Maybe Kopete should use DCOP \
messaging to talk to kppp and fetch connection status.  I guess this is also a \
feature request for kppp - a DCOP interface that allows other apps to query it for \
connection status.


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