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'm sorry, debian uses a different layout than slackware, so i don't know where your config file is to add the gateway automatically. try looking around /etc/rc.d/netconfig or something like that. mine is in /etc/rc.d/rc.inet1.conf, as i said before.
as for DNS...two things come to mind. first, are you sure you didn't change any firewall settings? port 53 needs to be open to outbound traffic in order for name resolution to take place. that's worth verifying. second, my dns servers are listed in /etc/resolv.conf. i obtain them automatically from dhcp like you're supposed to. can you check that file and see what, if anything, is inside? if all else fails i believe you can edit the file manually to put them in.
if you've checked both those things and verified that port 53 is open and that resolv.conf has a couple good ip addresses for dns servers, then i don't know. perhaps have tcpdump running in a terminal while you attempt various pings and dns lookups to see if you can learn anything from watching the packet traffic.
Originally posted by TroelsSmit
the command: "sudo route add default gw 192.168.1.1" was tried - where should this be added so I don't have to run it after every boot ?
You don't have to add this. The reason for an DHCP server is, that this happens automatically.
I can then move through the router - but DNS still doesnt work.
The DHCP server might not know the IP address of the DNS server. On the other hand, it did work under Knoppix. So, all necessary information should be available.
Doesn't a tool to setup these things exist ? I mean, I have all the information Im just not sure where to put it ??
It usually runs out of the box. All information you were given is only necessary under special circumstances.
If all else fails, boot up the Knoppix CD and check the content of /etc/dhclient.conf there. As you mentioned earlier, DHCP runs fine under Knoppix. So, the contents of the config files should be somewhat usable...
Another file you might want to look at is /etc/resolv.conf. This file tells the system how names should be resolved (among others: which name server to use). AFAIK, dhclient will modify this file, when executed successfully.
I then ran "sudo ifconfig eth0 down" and then up.
I'm not sure if ifconfig eth0 up/down is sufficient. You might want to try ifup eth0 and ifdown eth0. The difference: ifup/down execute additional scripts if such scripts have been defined in /etc/networks/interfaces.
and you're sure your firewall isn't blocking outbound traffic on port 53?
also, find out what your ISP's namesever's are either through windows, or knoppix, or whatever, and put those in /etc/resolv.conf. try that too, cause your router might not be configured to act as a nameserver.
If Window$, open a command prompt, and type in "ipconfig /all" without the quotes. Then look for the DNS servers in the output.
Of course, the DNS servers listed there will be what your router is giving out, which may be its own address. You would have to log into the router itself to hunt down the IP address of your ISP's DNS servers. If you're on high speed internet, you could also plug the cable modem/DSL directly into any computer, then check the files I listed above and you'll know the ISP DNS IP address.