Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I have successfully figured out how to release an IP in Linux finally, dhclient.
I was SSH'd into my server (192.168.0.1) from me (192.168.0.19) and decided to run dhclient to see help, commands etc..
bad idea.
dhclient came up with the stuff and tried to process something which it seemed to get stuck on.
Instantaneously I lost my IRC, ICQ, MSN, the SSH client cut me off, webpages wouldn't load. I lost internet AND lan.
I went to the server and it said:
host 192.168.0.19/if3 ignores redirects from 192.168.0.1 to 192.168.0.1
I didn't know how to fix it so I logged in, shut down the server into maintenance mode, then let it boot back up so the services restarted and I got my net back on my .19 PC, excellent..
But then I woke up the next morning - no net on .19, same message on the server, so I did it again, worked for the whole day till night time where the same thing happened.
I seem to now periodically lose internet and lan on the .19 machine and that night, another machine .18 and I don't know why. So i'm not sure if it's all machines, or just the .19, but for sure atleast the .19. All I did was run dhclient with no parameters when I was ssh'd into the server and I seem to have opened a can of UGLY worms.
It looks your dhclients starts from time to time, it couldn't find DHCP server and you have no network access. When you get the same problem, look if dhclinent is running on the server (ps aux|grep dhclinet). If it is, you need to trace the script it's starting from ('cd /etc/rc.d/init.d;fgrep dhclient *' - it will show you places where 'dhclient' is run in the scripts, check every of them).
Note: dhclient doesn't show help. It starts looking for DHCP server...To look into the options, use rather 'man dhclinet'.
Very unclear story. My doubts are:
-what is the server? is it a gateway to internet for LAN clients?
-how many NICs it has got?
-what for you are using dhclient at server box? which NIC(s) it should setup?
-what way the clients IP are setup?
Be more specific....
Fine. I understand eth0 IP is constant although get via dhclient. You need to setup it to work with eth0 only.
So /etc/dhclient.conf should be for instance:
interface "eth0"{
request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, host-name;
require subnet-mask, domain-name-servers;
}
The most important is to use dhclient on eth0 only.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.