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.
flakey wireless LAN seems to prevent dial-up internet access
I'm in the process of getting my broadcom wireless card on my Acer laptop running in fc5. Right now, I'm in the middle of using the the bcm43xx driver and NetworkManager. It's turning the light on and, most recently, on boot up, supposedly given me an ip address.
However, once everythign is actually up and running, it won't connect, although NetworkManager shows the AP in its menu. That wouldn't be a big deal except that the wireless is only set-up as a local LAN--I use dial-up to connect to the internet and now, when I dial in with wvdial, while it says I've got an ip, my web browser won't connect and I can't ping a www server.
It's somewhat reminsicent of when I first got the modem working--for reasons I still don't understand, I had to specify particular DNS servers to use, which allowed me to actually get on the web, despite wvdial claiming I had an ip.
I'm GUESSING what's happening is that Linux is looking for the internet on the (unconnected, and not quite working) wireless connection, and not via the dial-up. But I'm totally clueless about what to do about it....Any suggestions?
Last edited by crazybilly; 10-29-2006 at 09:41 PM.
You need your service providers DNS address/addresses in the file /etc/resolv.conf.
Even if you are using dhcp and having difficulties browsing etc, it is a good idea to have them setup.
With ipforward, computers on your lan, I am presuming with fixed ip address's, will also need DNS entries in their /etc/resolv.conf. If you have a windows computer on the lan set up the ip manually with DNS entries.
There are good tutorials on DNS on the web, but first of course you need to be browsing.
If the installation of your wireless card overrides the DNS eentries in resolv.conf, set the card up manually with a static IP. This is the most convenient way if you are having problems connecting.
Hope this helps.