FedoraThis forum is for the discussion of the Fedora Project.
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 a Dell D600m laptop dual-booting WinXP and FC3. The box has a built in NIC and a Centrino-based wireless connection. I use the box at work with the wired connection active, and at home (under WinXP, to this point) with the wireless connection to talk to my home network. I recently got the wireless connection configured and ALMOST working under FC3 using the IPW2200 packages. I don't think I will typically need both connections active at the same time.
Like I said, "almost"...
Last night, when I fired up FC3 here at home and tried to connect to my WAN for the first time, I succeeded in connecting (I had a strong signal, etc.) and my WAP showed a connection from the appropriate MAC address. I had an IP assigned by the WAP (using DHCP) there. Problem was I could not seem to get to the outside world via my connection. It seems like when I start up a Web browser, it doesn't know to use eth1 (the wireless connection) and/or it is still trying to use the DNS settings, etc., that are configured for use when I am connected to my work LAN via eth0 (the wired NIC).
I am obviously missing something fairly simple in getting the network configuration set up to fully use the wireless connection. Can someone point me toward the needed steps to be able to easily switch between the wired and wireless connections, depending on where I am (wired at work, wireless at home and possibly when travelling)?
Thanks! I will give the "route" command a shot later this morning. It makes sense to me that this should be part of the solution. The remaining question (at least in my mind, until I get a chance to play with this) will be how DNS will work, given that on my eth0 connection I have two DNS entries specified that correspond to work servers. On my other systems with wireless connections at home, the DNS is dynamically handled...
I will give it a shot and see what happens, and then post a follow-up.
just a hint if all other stuff doesn't work
i have a centrino based notebook as well XP & FC3 dual booted the networking is better in FC3 than XP. I use NetworkManager. it auto detects which network device is the best and tries to connect.
Thanks for the tip. I will give this a shot this evening. I tried the "ip route" command above and it failed. I don't have my laptop with me at the moment, so I don't have the specific error message in front of me, but it seemed like it was failing to get the wireless connection established as the default connection.
I had the two packages already installed that were mentioned in the article at the URL you supplied, so it was just a matter of turning on the NetworkManager service, and then starting the NetworkManagerInfo thingy (what do you call those, anyway? an applet?). The first time that I booted after setting the NetworkManager to start, I couldn't get it to connect. It saw my home WAN, and prompted me for the WEP key, but I couldn't get it to connect. I'm not sure what the difference is, but I rebooted and this time it connected.
I haven't played much with it, but at least I know it worked one time!