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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have been attempting to go online with linux, im using fedora core 1, i am trying to dial using the redhat network config, and i have so far managed to get my modem worked, connet and all that(heres a copy of my logs)
Aug 31 01:04:27 localhost ifup-ppp: pppd started for NetPTC on /dev/modem at 115200
Aug 31 01:04:27 localhost pppd: pppd 2.4.1 started by root, uid 0
Aug 31 01:04:28 localhost wvdial: WvDial: Internet dialer version 1.53
Aug 31 01:04:28 localhost wvdial: Initializing modem.
Aug 31 01:04:28 localhost wvdial: Sending: ATZ
Aug 31 01:04:28 localhost wvdial: ATZ
Aug 31 01:04:28 localhost wvdial: OK
Aug 31 01:04:28 localhost wvdial: Sending: ATM1L1
Aug 31 01:04:28 localhost wvdial: ATM1L1
Aug 31 01:04:28 localhost wvdial: OK
Aug 31 01:04:28 localhost wvdial: Modem initialized.
Aug 31 01:04:28 localhost wvdial: Sending: ATDT8684000
Aug 31 01:04:28 localhost wvdial: Waiting for carrier.
Aug 31 01:04:28 localhost wvdial: ATDT8684000
Aug 31 01:05:26 localhost wvdial: CONNECT 45333 NoEC
Aug 31 01:05:26 localhost wvdial: Carrier detected. Chatmode finished.
Aug 31 01:05:26 localhost pppd: Serial connection established.
Aug 31 01:05:26 localhost pppd: Using interface ppp0
Aug 31 01:05:26 localhost pppd: Connect: ppp0 <--> /dev/modem
Aug 31 01:05:58 localhost pppd: LCP: timeout sending Config-Requests
Aug 31 01:05:58 localhost pppd: Connection terminated.
Aug 31 01:05:58 localhost pppd: Hangup (SIGHUP)
Aug 31 01:05:58 localhost pppd: Exit.
unfortunately i cannot figure out why it times out, i have checked up on many ppp howto's, im beyond the scope of a few of them, ive looked into pap and chap authentication(i know for a fact i use PAP authentication and no compression) the problem is the guides tell me of a debug command to which typing "debug" or "./debug" does nothing nor do anywhere in the those tutorials do they really explain what to do even if the debug command worked.
if anyone has any idea where i should go or what i should do i'd appreciate the help.
For some reason, wvdial flaked out on me as well. Although the crazy thing was that I had it working for like 3 or 4 months just fine. Then one day I went to connect via wvdial and it did exactly what you describe. And it's done that ever since. I used kppp for a while, but then decided to figure out how to use pppd directly, since both wvdial and kppp use pppd.
Honestly, I don't have any advice on how to correct wvdial since I never figured out what the problem was (or what had changed). If you'd like though, I can share with you how I set up something similar using pppd.
The things you'll want to customize are the 115200 (max baud rate), /dev/modem (you can also use the direct serial port such as /dev/ttyS0), and <username>, which is your login name.
Inside 'verizonchat' is the following:
'' AT OK ATZ OK AT$QCMDR=3 OK ATDTxxxyyyzzzz CONNECT ''
(where '' represents two singles quotes, not a double quote)
In this file, you'll want to supply your dialup number xxxyyyzzzz as well as any modem start-up commands you might have. One thing to note about this is that everything is in request-response pairs -- AT OK, ATZ OK, etc. The AT$QCMDR is specific to my modem, you probably won't need it.
Once you finished creating these two files for your ISP (and you can call these two whatever you want, BTW), you'll need to set up your CHAP/PAP authentication (which it sounds like you may have already done). In case you haven't, edit either the chap-secrets or pap-secrets file in /etc/ppp to include the following line
"<username>" * "<password>"
(where " is a double quote, not a single quote)
Obviously you'll need to replace <username> with your username and <password> with your password.
OK, now that you have all of that done, to connect it is very simple. As root, issue
pppd call verizon
Or, substitute whatever the name for your main file is that you created.
One other thing you may need to do (I had to do this) is to add at least one of your DNS servers to the /etc/resolv.conf file in order to get DNS resolution. You can do this simply by adding a line to your /etc/resolv.conf file such as