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.
ok what i have setup is a small home lan using verizon dsl, westell external modem, pppoe, tyring to set it up so this machine, running redhat 7.1 can share internet with 2 win machiens (1 95 and one 98)
on the 95 machine, (have not touched the 98 machine) i have its ip address set to 192.168.1.2 (98 will be 1.3, ip for linux machine is 1.1), its subnet mask to 255.255.255.0, its dns to my isp's dns, and i made up some things for domain and host.
all this is in tcp/ip options for the network adapter on the 95 machine
on the 95 machine i can ping 192.168.1.1 and it works ok, but when i load internet explorer and try to go to a site it is EXTREMELY slow, and aim just stays at 'connecting' for minutes upon end, never loading up.
any clues to whats causing htis massive slowdown?
maybe some win settings or another line i'm missing in rc.local ???
any help would be much appreciated
nick (quoting his roomate ray, who posted the same thing on dslreports)
yeah, we did that already. I had to go to bed last night while my roommate carried the torch and worked on it so i am not 100% sure on the details. In a text message he left on my screen (which i only gave a cursory glance because i had to leave for work, where i am now) he had said that the internet DOES work only incredibly slow. I tried it real quick on the win95 machine and nothing came up in about 20-30 seconds so i left for work. I would assume though that he was able to get something to come up in the browser after a while, or at least ping a website, or something.
i forget where i got those dns servers from. it was some text file... conf.dns or dns.conf or something, perhaps in /etc/bin or just /etc or i dont know. Try going to network configuration (kde menu --> system --> network configuration or something similar) and looking in there. I believe they may be listed in there.
Does the linux box connect to the web fine on its own, say using Lynx or are things slow there too? I'd advise you check your DNS settings (as previously mentioned), and I've only ever tried setting the policy for ipchains before setting up any rules on the chain, you may want to look at that. I've never had to use ip_dynaddr before either.
Originally posted by jharris Does the linux box connect to the web fine on its own, say using Lynx or are things slow there too? I'd advise you check your DNS settings (as previously mentioned), and I've only ever tried setting the policy for ipchains before setting up any rules on the chain, you may want to look at that. I've never had to use ip_dynaddr before either.
HTH - good luck
yeah, the linux box is fine on the internet itself, dsl and all (i was on it when i posted that last message)
what do you mean by setting the policy for ipchains before setting the rules? we're basically going off of what someone i talked to on aim told us to do, not fully awayre of *what* it is that we were doing
Originally posted by Lardofutardo what do you mean by setting the policy for ipchains before setting the rules? we're basically going off of what someone i talked to on aim told us to do, not fully awayre of *what* it is that we were doing
ray: all the ip masq lines are in that /etc/rc.d/rc.firewall file that we commented out when working on it the other day. i'd say to try deleting (or just commenting out) those other lines and re-enabling the rc.firewall and follow the instructions at http://www.linuxdoc.org/HOWTO/IP-Mas...O-3.html#ss3.3 to make it an executable and execute it and such, than doe the tests in that page to try to test it. Whatever, you're probably at work now anyway, and i will be home in a few hours. we will get this working tonight by crikey.