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.
My server local ip keeps changing --- one day it is 192.168.1.104 and a week later I need to change the port forwarding on my router to 192.168.1.103. My desktop retains the same ip. Is there something on the server that might be releasing the ip and requesting a new one??
I know that in the lan ip setup section of my net gear rp614v3s browser based set up program thaer is asection in which I can reserve Ip addresses for each machine on my Lan.
So Id suggest that you go to your routers web browser based configuration utility and reserve an ip addrees for the spacific hardware mac address of the servers nick card.
Are you using the -k switch when shutting down dhcpcd? This will send a SIGHUP to the dhcpcd process which will cause a DHCP_RELEASE to be sent to the server. If you don't want that to happen, try removing the -k from your shutdown script.
Are you using the -k switch when shutting down dhcpcd? This will send a SIGHUP to the dhcpcd process which will cause a DHCP_RELEASE to be sent to the server. If you don't want that to happen, try removing the -k from your shutdown script.
I second this solution. Windows doesn't release the IP back the the DHCP server on shutdown, so the DCHP server still has it set as assigned. Your Linux box is probably releasing the IP back to the DHCP Server on shutdown, so it will get a random free one on the next boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.