Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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've got a computer running WinXP, with a USB ADSL modem. I want to share this connection with a Linux box (currently Suse 8.2).
I've got them connected via a crossover cable, run the network wizard on XP which has set up IP 192.168.0.1 & netmask 255.255.255.0. On the linux box I've set IP/proxy options as 192.168.0.2 everywhere this is an option in Yast.
I can ping the linux box from XP, but not vice versa. I presume I'm missing something, but don't know what to do now. Any suggestions?
OK, so I half solved the problem - I couldn't ping the linux box because it was going onto standby
Anyway, I can ping both ways - but I can't access the internet from the linux box. Everything seems to be set up OK on the XP one, and the static IP on linux is set to 192.168.0.2, with 192.168.0.1 as the proxy and defailt gateway. I've manually entered my ISP's DNS servers.
I've now removed all proxy entries (guess I was trying too many things )....I can ping any IP from the linux box, but neither Konqueror nor Mozilla download any page - in both cases they halt with the status bar reading "waiting for reply", or similar.
Originally posted by kbcnetau Weird. How about if you try connecting to an IP address rather than a URI?
Try: <http://18.104.22.168> - this is the IP address of one of the Google servers. If you try this and get Google, you may have a name resolution (DNS) problem.
That worked - but at a glacial pace. So now I wonder if the problem isn't a physical one with the equipment I've got. How can I test that the network between the two boxes is running cleanly, beyond pinging, before I think of buying new kit? And if that's not the problem, what should I do with the DNS issue (at the moment, the XP box is getting the DNS address automatically, and I've set the Linux DNS as 192.168.0.1 - is this correct?)
Changing to the external DNS doesn't help. And the thread that PEACEDOG linked to isn't dealing with the same problem - there it was getting the crossover working to ping both ways.
However, I've run pings for half an hour each way across my crossover, and I'm getting a packet loss of 40-50%, which I'm guessing could be my problem - if so, is there any possible explanation for this, other than hardware?
Um, what's the brand of network card on the Linux box? I had a similar problem a couple of years ago with DLink cards using the via-rhine.o driver. Under heavy traffic, packets started vanishing. Put the NIC in a Windoze machine, no problems. Then I just started using cards with Realtek chipsets and have never had a NIC problem since (touch wood!).