Bug 62064 - wvdial does not recognise NO ANSWER and never times out
Summary: wvdial does not recognise NO ANSWER and never times out
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: wvdial
Version: 7.2
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-27 05:49 UTC by Anthony Rumble
Modified: 2016-10-05 10:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-05-15 10:16:05 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 62064 0 master MERGED hostdev: properly set is_hostdevice 2016-10-05 10:41:45 UTC

Description Anthony Rumble 2002-03-27 05:49:02 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226

Description of problem:
wvdial does not recognise the modem responce NO ANSWER
and never times out to try redialling.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Setup WVDIAL
2.Dial a site that is temporarily not answring (This happens often)
3.Modem will respond with NO ANSWER.. wvdial sits there foreever
	

Actual Results:  wvdial just sat there forever, never timed out, never did anything.

Expected Results:  I can accept that it might not recognise NO ANSWER, but it should
at least timeout at some stage, and redial

Additional info:

This is a major problem, as customers with perminant links basically find that,
when their ISP has the system down for maintenance, they often just turn off the
modems, rather than busy their lines out.

When this happens.. their dialup connection just sits there forever in wvdial.
Comment 1 Anthony Rumble 2002-03-27 07:05:27 UTC 
Just to clarify this a little further.

If wvdial does not get ANY response it is expecting (ie CONNECT etc)..
it will hang there forever.
Comment 2 Harald Hoyer 2005-07-08 15:32:22 UTC 
is this still an issue?
Note You need to log in before you can comment on or make changes to this bug.