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 have a friend who's having a very strange problem. he has his linux box (debian sarge) configured with a static ip and everything in its proper place in /etc/network/interfaces. it's been working well for more than a year. all of a sudden though, resolvconf won't properly regenerate /etc/resolv.conf after a reboot. normally resolvconf takes the input and generates /etc/resolv.conf as a symlink to another file which is /etc/resolvconf/run/resolv.conf or something like that. in this case, when he reboots his machine /etc/resolv.conf is empty. (everything else works ok, he can ping hosts from his /etc/hosts.conf file alright, but outside name lookups time out).
here's where it gets very strange - if he manually brings the interface down and back up, everything works fine: /etc/resolv.conf is properly generated and name resolution works. so this is only a problem when the computer has to reboot. strange huh?
we're figuring there must be some problem with resolvconf, but does anyone have any thoughts?
well see resolvconf is automatically used (by debian i guess) as you can see from the /etc/network/interfaces file:
# The primary network interface
iface eth0 inet static
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 184.108.40.206 220.127.116.11
and i've seen similar contents from google searches. so i guess resolvconf is supposed to handle everything automatically. i'm inclined to believe the permissions are ok, since it was working well in the past. he brings the network interface up using ifdown and ifup. and since doing that solves the problem, again, i'm inclined to believe the permissions are ok.