🚀 go-pugleaf

Hal Burgiss wrote:
> 
> On Thu, 02 Dec 1999 10:31:13 -0500, James Silverton
> <jim.silverton@erols.com> wrote:
> >I recently installed SuSE 6.2 in a dual boot arrangement using
> >Bootmagic. For the immediate future, my connection with the Internet is
> >going to be over a 56K modem with an ISP (Erols) whose contract has
> >several months to run. Suggestions that I change ISPs would not be
> >helpful but I need some advice and information. The ISP quite honestly
> >says that it does not support Unix but has given me the only thing I
> >really needed, the IP of their news server, without any problems.  I
> >have found that wvdial works very well indeed to make a connection with
> >the ISP but two things are apparent.
> >
> >Once wvdial starts pppd, I have no easy indication that the connection
> >is still up other than hang-ups of, for example, Netscape or failures
> >of ping. Second, my ISP negotiates  password "verification" and failure
> >here is much more common than actual busy signals when dialing. Since
> >wvdial will have started pppd before the process is complete, I do no>>>>>>>>>>>>Deletions<<<<<<<<<<<<<<<
> One way to do this is to watch /var/log/messages. In an xterm you can
> run 'tail -f /var/log/messages'. Not pretty, but it works. There is also
> an app called root-tail (sp?), that does this but writes it directly to
> the root window (background). Kinda neat.
> 
> >In Windows dial-up networking, I can watch the process and immediately
> >redial if verification fails. I am impressed by wvdial and would like to
> >continue to use it but the verification failure and lack of a visual
> >indication of connection are a pain. Does anyone have any suggestions
> >for  a visual connection indicator since, AFAIK, such  a signal would
> >solve both my problems?
> >
> 
> Maybe there is some applet out there for this. In WindowMaker there is
> wmppp. This has on-off buttons, yellow light for connecting, red for
> dropped connection, and green for connected. It also has speed
> indicator. You have to set this up to invoke a script/command of your
> choosing.

Hi!

The best suggestion so far has been the Window Maker wmifs which is
essentially what you suggest. I down-loaded it from
http://www.mezaway.org/dockapps/wmifs.html

and it does work under KDE even if the display window is on the small
side. This was suggested by Joe Yardle on the ma-linux@tux.org
discussion group.

Jim.

On Thu, 02 Dec 1999 10:31:13 -0500, James Silverton
<jim.silverton@erols.com> wrote:
>I recently installed SuSE 6.2 in a dual boot arrangement using
>Bootmagic. For the immediate future, my connection with the Internet is
>going to be over a 56K modem with an ISP (Erols) whose contract has
>several months to run. Suggestions that I change ISPs would not be
>helpful but I need some advice and information. The ISP quite honestly
>says that it does not support Unix but has given me the only thing I
>really needed, the IP of their news server, without any problems.  I
>have found that wvdial works very well indeed to make a connection with
>the ISP but two things are apparent.
>
>Once wvdial starts pppd, I have no easy indication that the connection
>is still up other than hang-ups of, for example, Netscape or failures
>of ping. Second, my ISP negotiates  password "verification" and failure
>here is much more common than actual busy signals when dialing. Since
>wvdial will have started pppd before the process is complete, I do not
>have any indication of success or failure other than the hang-ups.
>Wvdial does not check password verification and pppd remains active
>even after a failure.

One way to do this is to watch /var/log/messages. In an xterm you can
run 'tail -f /var/log/messages'. Not pretty, but it works. There is also
an app called root-tail (sp?), that does this but writes it directly to
the root window (background). Kinda neat.

>In Windows dial-up networking, I can watch the process and immediately
>redial if verification fails. I am impressed by wvdial and would like to
>continue to use it but the verification failure and lack of a visual
>indication of connection are a pain. Does anyone have any suggestions
>for  a visual connection indicator since, AFAIK, such  a signal would
>solve both my problems?
>

Maybe there is some applet out there for this. In WindowMaker there is
wmppp. This has on-off buttons, yellow light for connecting, red for
dropped connection, and green for connected. It also has speed
indicator. You have to set this up to invoke a script/command of your
choosing. 

But I would think there should be a way to tweak pppd to solve the
problem. Maybe slow it down, to give it more time to authenticate. 

-- 
Hal B
hburgiss@bellsouth.net
--
            Linux helps those who help themselves

That's strange, On my SuSE 6.2 box pppd dies, and wvdial redials after a
connection loss. Even authentication failures show in the wvdial window as
"detected error ??? - password failure?".

Look in the SuSE help system for the entries to put into the pppd config
file. there should be only 2 entries there.

lock
debug

Link for this info:  http://sdb.suse.de/sdb/en/html/daniel_wvdial.html

I followed the article as I found it on my local box, and no problems with
the wvdial connection. I still can't get KPPP to work on 6.2 though, I
really miss the statistics box it has.


James Silverton wrote:

> I recently installed SuSE 6.2 in a dual boot arrangement using
> Bootmagic. For the immediate future, my connection with the Internet is
> going to be over a 56K modem with an ISP (Erols) whose contract has
> several months to run. Suggestions that I change ISPs would not be
> helpful but I need some advice and information. The ISP quite honestly
> says that it does not support Unix but has given me the only thing I
> really needed, the IP of their news server, without any problems.  I
> have found that wvdial works very well indeed to make a connection with
> the ISP but two things are apparent.
>
> Once wvdial starts pppd, I have no easy indication that the connection
> is still up other than hang-ups of, for example, Netscape or failures of
> ping. Second, my ISP negotiates  password "verification" and failure
> here is much more common than actual busy signals when dialing. Since
> wvdial will have started pppd before the process is complete, I do not
> have any indication of success or failure other than the hang-ups.
> Wvdial does not check password verification and pppd remains active even
> after a failure.
>
> In Windows dial-up networking, I can watch the process and immediately
> redial if verification fails. I am impressed by wvdial and would like to
> continue to use it but the verification failure and lack of a visual
> indication of connection are a pain. Does anyone have any suggestions
> for  a visual connection indicator since, AFAIK, such  a signal would
> solve both my problems?
>
> TIA,
>
> Jim.

Michael Hart wrote:
> 
> That's strange, On my SuSE 6.2 box pppd dies, and wvdial redials after a
> connection loss. Even authentication failures show in the wvdial window as
> "detected error ??? - password failure?".
>

This surely does not happen when Erols fails on password authentication.
Even dial-up networking in Windows just sits there and does nothing.
However, as I do have a display window there, I can cancel and try
again.
 
> Look in the SuSE help system for the entries to put into the pppd config
> file. there should be only 2 entries there.
> 
> lock
> debug
> 
> Link for this info:  http://sdb.suse.de/sdb/en/html/daniel_wvdial.html
> 
> I followed the article as I found it on my local box, and no problems with
> the wvdial connection. I still can't get KPPP to work on 6.2 though, I
> really miss the statistics box it has.
> 
> James Silverton wrote:
> 
> > I recently installed SuSE 6.2 in a dual boot arrangement using
> > Bootmagic. For the immediate future, my connection with the Internet is
> > going to be over a 56K modem with an ISP (Erols) whose contract has

>>>>>>>>>>>>>>Deletions>>>>>>>>>>>>>>>>>>>>>

As I posted earlier, wmifs does mostly solve the problem and I will keep
the suggestion of

lock
debug

for use later if necessary.

Thanks again,

Jim.

On Fri, 03 Dec 1999 01:16:27 GMT, Hal Burgiss blurted:
>On Thu, 02 Dec 1999 10:31:13 -0500, James Silverton
><jim.silverton@erols.com> wrote:
>Maybe there is some applet out there for this. In WindowMaker there is
>wmppp. This has on-off buttons, yellow light for connecting, red for
>dropped connection, and green for connected. It also has speed
>indicator. You have to set this up to invoke a script/command of your
>choosing. 
there is a applet called kmodem on the SuSE cdroms (kde alpha apps AFAIK)
I use it and it gives you the same little icon that you get in windopes

-- 
Charles Blackburn
Summerfield Technology Limited - Official SuSE Reseller
Sponser Of the Birmingham (UK) Linux User Group
E-MAIL: charlesb@summerfieldtechnology.co.uk
Birmingham LUG: BLUG@summerfieldtechnology.co.uk
WWW: http://www.summerfieldtechnology.co.uk

On Fri, 03 Dec 1999 14:33:36 -0500, James Silverton blurted:
>Michael Hart wrote:
>As I posted earlier, wmifs does mostly solve the problem and I will keep
>the suggestion of
>
>lock
>debug

if you want it to keep retrying when it gets disconnected, try the persist
option

-- 
Charles Blackburn
Summerfield Technology Limited - Official SuSE Reseller
Sponser Of the Birmingham (UK) Linux User Group
E-MAIL: charlesb@summerfieldtechnology.co.uk
Birmingham LUG: BLUG@summerfieldtechnology.co.uk
WWW: http://www.summerfieldtechnology.co.uk

James Silverton wrote:
> 

[snip]

> Does anyone have any suggestions
> for  a visual connection indicator since, AFAIK, such  a signal would
> solve both my problems?
> 
> TIA,
> 
> Jim.

I'm not sure if I entirely understood what you are lokking for, perhaps
the program tleds is. It indicates Network traffic by flashing NumLock
and ScrollLock Leds. AFAIK it cooperates with any kind of interface,
including modem.

Jan

Jan Rademacher wrote:
> 
> James Silverton wrote:
> >
> 
> [snip]
> 
> > Does anyone have any suggestions
> > for  a visual connection indicator since, AFAIK, such  a signal would
> > solve both my problems?
> >
> > TIA,
> >
> > Jim.
> 
> I'm not sure if I entirely understood what you are lokking for, perhaps
> the program tleds is. It indicates Network traffic by flashing NumLock
> and ScrollLock Leds. AFAIK it cooperates with any kind of interface,
> including modem.


Thanks Jan. IMHO, the best solution suggested has been wmifs. It works
remarkably well to solve my problem which was that wvdial starts pppd 
before password verification with my ISP is complete and does not kill
the daemon if verification fails. May I also say that I have enjoyed the
quick responses and discussions with Antoine at Window Maker (Sorry,
delated the e-mail with your last name Antoine!).

Jim.