Bug 41591 - never redials when connection lost
never redials when connection lost
Status: CLOSED DUPLICATE of bug 39646
Product: Red Hat Linux
Classification: Retired
Component: wvdial (Show other bugs)
7.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-05-21 10:34 EDT by Tommy Watt
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-25 17:20:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tommy Watt 2001-05-21 10:34:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; compaq)

Description of problem:
whenever a dialup connection is lost, red hat does not redial to 
reconnect, even though the option to do so is set.

Wether I disconnect manually, or a connection is lost by the ISP 
disconnecting me, the same thing still happens, the "Restore connection 
when lost" option in the Dialup Configuration screen from the Gnome 
desktop, is unselected.  No matter how many times I select this option, 
and how many times I get disconnected, for any reason, it turns this 
option off and does not redial.

I even tried reformatting my system from scratch, and it made no 
difference.  

This is extremely important for me, since I need to be connected to the 
internet 24/7.


How reproducible:
Always

Steps to Reproduce:
1. Dial into internet via RH PPP.
2. Get disconnected for ANY reason.
3. It won't redial even though option is set to do so, option is then 
turned off, even though I didn't turn it off.
	

Additional info:
Comment 1 Tommy Watt 2001-05-25 17:20:32 EDT
hello???
Comment 2 Trond Eivind Glomsrxd 2001-05-30 11:12:46 EDT

*** This bug has been marked as a duplicate of 39646 ***

Note You need to log in before you can comment on or make changes to this bug.