Connected to Internet w/wvdial but ppp fails to 'negotiate'
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Connected to Internet w/wvdial but ppp fails to 'negotiate'
I am making connection to my ISP using wvdial but ppp says: "unable to negotiate" and exits with code (10)
after ppp gets a prompt it says "Dont know what to do, starting ppp and hoping for the best"
I am told that ppp should make a file named: /etc/resolv.conf and that I can edit that file. However, I do not have a file named resolv.conf in the /etc/ directory
Is it that I haven't configured ppp correctly??
If not, what do I do to configure it in order for it to produce the file: /etc/resolv.conf?
'after ppp gets a prompt it says "Dont know what to do, starting ppp and hoping for the best"'
wvdial has two methods of negotiating with the ISP. You should try both methods. You set the method by specifying Stupid Mode in /etc/wvdial.conf
Stupid Mode = 1
Stupid Mode = 0
"Dont know what to do, starting ppp and hoping for the best"
This is probably the last in a series of error messages. If playing with Stupid Mode has no effect on the problem then please also post the several error messages ahead of this one.
"I am told that ppp should make a file named: /etc/resolv.conf and that I can edit that file. However, I do not have a file named resolv.conf in the /etc/ directory"
You have not got far enough in the signon protocol to have run into problems with /etc/resolv.conf yet.
--> Don't know what to do! Starting pppd and hoping for the best.
--> Starting ppd at Wed date/time
--> pid of ppd: number
--> Disconnecting at Wed date/time + 30 seconds
--> The PPP daemon has died. PPP negotiation has failed (exit code = 10)
--> man ppp explains error codes in more detail
--> I guess that's it for now, exiting
--> The PPP daemon has died. (exit code = 10)
I assume those are error codes in hex (after the 'Carrier detected' line)
I think that wvdial does not understand what it is receiveing and is printing what it received in hex. They are not necessarily error codes. The next thing to lok at are your Hays command strings (Init strings). Could you post your /etc/wvdial.conf with your password xxxx out.
The modem init command, I noticed linux users ATZ. This is suppose to reset it to factory defaults. However there is also AT&F which supposedly does the same thing. There is some difference between the two but I dont know what it is.
However, on my internal USR Performance Pro if I leave ATZ it will try to negotiate all day long, but if I use AT&F I connect every time.
Causes ppp to initate without saying "I don't what to do etc"
However, the ppp daemon still exits 30 seconds later with a code 10
When I call my ISP, there is no record of my connection at the time I make the attempt.
I was told that there is a file: resolv.conf in the /etc/ directory which contained all the DNS info - I do not have this file, the "man resolv" also says I should have this file.
How do I generate the <resolv.conf> file in the /etc/ directory????
BTW - thanks for all the inputs I've received so far
So, it looks to me that ppp is communcating with the outside world but nowhere have I been required to give the domain-name of my ISP or the TCP/IP numbers
I suspect this is the stuff that goes in the <resolv.conf> file - of which there ain't
I am suffering the same exact negotiation failure on a debian system "knoppmyth". The root of the problem for me seems to be that the wvdial negotion never sees the "login:" prompt to complete the negotiation. If I use minicom to dial my ISP I discovered that the ISP does not send the login prompt immediatly after the "CONNECT" message. If I enter a <CR> right after the modem gives the CONNECT message then the ISP sends the login prompt immediatly. If I make no response after the CONNECT message then the ISP waits for about 15 seconds or so and then sends the login prompt.
What appears to be happening in my case is that after wvdial gets the CONNECT message it times out waiting for the login prompt and trys ppp, but of course it then never gets the login prompt and the ppp link can never complete!
Does anyone know how to resolve this? It seems to me either of two things could resolve this:
1) somehow get wvdial to send a <CR> following the connect message so that the login prompt will be sent earlier.
or
2) increase the timeout value used by wvdial to wait for the login prompt before giving up and going to ppp
I don't know how to do either of these. Can anybody out there help?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.