Roaring Penguin PPPoE Kontrol

Network

Score 73%

Description:

Roaring Penguin PPPoE Kontrol is a little tool that docks to the KDE3 system tray.

It provides you with a simple contextmenu, including entries to connect to your provider, disconnect again and get your current dynamic IP address, assigned to you by your provider. The IP can also be copied to the clipboard.

Active traffic is visualized by a glowing animation of the tray icon.

Last changelog:

11 years ago

Version 0.40 features an animated tray icon that glows mysteriously when data is running through your internet connection. Furthermore RPPPPoEK will now recognize when your internet connection is brought up from external, i. e. by manually running pppoe-start in a shell.

This version needs Roaring Penguin PPPoE Version 3.6 or higher. Previous versions will (probably) also work, but you need to change the utility script, rppppoek.sh. Please see the README file for details.

migsy
11 years ago

Would it be possible to show more verbose errors instead of just 'Could not connect.' etc? Like, could not connect because the server is not reachable or because the authentication failed? Or maybe even because the user doesn't have proper permissions to execute the pppoe-* commands...

Thanks, great app.

Report

derMosher
11 years ago

I cannot show errors when you don't have permission to execute pppoe-*. Those are started via sudo, and sudo would prompt you for a password, but you don't see that dialog.

Wrong credentials will be logged in /var/log/messages, for example:

Apr 24 19:24:25 mosher sudo: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/pppoe-start
Apr 24 19:24:25 mosher pppd[2804]: pppd 2.4.3 started by root, uid 0
Apr 24 19:24:25 mosher pppd[2804]: Using interface ppp0
Apr 24 19:24:25 mosher pppd[2804]: Connect: ppp0 /dev/pts/4
Apr 24 19:24:25 mosher pppoe[2805]: PADS: Service-Name: ''
Apr 24 19:24:25 mosher pppoe[2805]: PPP session is 1227 (0x4cb)
Apr 24 19:24:27 mosher pppd[2804]: PAP authentication failed
Apr 24 19:24:27 mosher pppd[2804]: Connection terminated.
Apr 24 19:24:27 mosher pppoe[2805]: Session 1227 terminated -- received PADT from peer
Apr 24 19:24:27 mosher pppoe[2805]: Sent PADT
Apr 24 19:24:27 mosher pppd[2804]: Exit.
Apr 24 19:24:27 mosher pppoe-connect: PPPoE connection lost; attempting re-connection.

The interesting line is this one:

Apr 24 19:24:27 mosher pppd[2804]: PAP authentication failed

This is what a timeout looks like:

Apr 24 19:27:31 mosher sudo: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/pppoe-start
Apr 24 19:27:31 mosher pppd[3704]: pppd 2.4.3 started by root, uid 0
Apr 24 19:27:31 mosher pppd[3704]: Using interface ppp0
Apr 24 19:27:31 mosher pppd[3704]: Connect: ppp0 /dev/pts/4
Apr 24 19:28:02 mosher pppd[3704]: LCP: timeout sending Config-Requests
Apr 24 19:28:02 mosher pppd[3704]: Connection terminated.
Apr 24 19:28:02 mosher pppd[3704]: Modem hangup
Apr 24 19:28:06 mosher pppoe[3705]: Timeout waiting for PADO packets
Apr 24 19:28:06 mosher pppd[3704]: Exit.
Apr 24 19:28:06 mosher pppoe-connect: PPPoE connection lost; attempting re-connection.

Again this is the interesting one:

Apr 24 19:28:02 mosher pppd[3704]: LCP: timeout sending Config-Requests

I don't know another way to get error codes, the script pppoe-start only gives 0 or 1, meaning success or failure. The problem with /var/log/messages is, that file is not world readable, so I cannot easily extract the error information from pppoe-start.

Report