Bug 8801
Summary: | wvdial not working with ISP | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brad Johnston <brad> |
Component: | wvdial | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | abartlet, alane, seppo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-25 03:47:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brad Johnston
2000-01-24 16:13:59 UTC
This is an instance of wvdial not knowing how to respond to the prompt from the Cisco hardware. What is the remote server expecting at this point? this is the same problem that i have had with panix.com and have come to the conclusion that the resolution is manual configuration (wvDial is not configurable for specialized responses): the below assumes that the problem is on interface ppp0, and that we are doing a straight login with no PAP or CHAP authentication; change accordingly. 1. create a valid 'chat' script named chat-ppp0; this will look like: # chat-ppp0 for panix.com # # errors 'ABORT' 'BUSY' 'ABORT' 'ERROR' 'ABORT' 'NO CARRIER' 'ABORT' 'NO DIALTONE' 'ABORT' 'Invalid Login' 'ABORT' 'Login incorrect' # connect '' 'ATZ' 'OK' 'ATDT121200000000' 'CONNECT' '' # login to Annex 'please?' 'ppp' 'name:' 'my_username' # NOTE: the \q in the next line prevents the password from # being echoed to the log file if we are debugging the chat # script; removing it means that the plain-text password is # going to be in two places, not just one. 'word:' '\qmy_password' # #EOF ## 2. add some new lines to the ifcfg-ppp0 file; these look like: DEFABORT="yes" DEBUG="no" # "yes" to log everything INITSTRING="ATZ" HARDFLOWCTL="yes" ESCAPECHARS="no" PPPOPTIONS="my-ppp-options go-here" REMIP="" NETMASK="" IPADDR="123.123.123.123" # if you have a static IP MRU="" MTU="" DISCONNECTTIMEOUT=15 RETRYTIMEOUT=5 3. comment out the WVDIALSECT= line in ifcfg-ppp0; this will cause ppp-watch to attempt to use 'chat' instead. comment out the PAPNAME= line as well if you are not using CHAP/PAP. The interface should now come up w/o a problem, using 'chat' instead of 'wvDial'. Since netcfg and linuxconf have had ppp support removed from them in 7.0, this bug is critical in RH7. The only alternative is manual configuration. Evidence suggests front line support personnel completely clueless when faced with this problem; probability of them being able to talk a customer through manual ppp setup using an editor to edit/create the above files is nil. Remeber that wvdial has 'stupid mode' making it behave just like Win9X, just starting PPP and hoping for the best. Unless your ISP provides a script for Win95 this should work without hassle. wvdial still handles authentication and the like, just passing it to pppd as pap and chap instead of sending it down the line itself. Bug 8801 has been closed due to inactivity and the lack of other bugs similar to it being opened by customers. Looking at the bug currently, it would seem to be a specific ISP settings that is confusing the program. [And as always ppp configuration is outside what Red Hat support offers.] |