local network static ip (ubuntu server)

[AlexGoesHigh]

alright i just set up an old pc with ubuntu server, now to make it easier to connect to it via my local network i want to give it a static ip, an ip that is always going to use when connected to my local network, now i have no idea if i have to do this via the router or directly with that pc, right now i have ssh connection to it with the dhcp ip given by the router but since that ip is going to change every time it has to be turned off or rebooted.

 

I want a way i know for sure its going to connect whenever is ssh or in the future different stuff (like a torrent server) via my local network.

[Oshino Shinobu]

Typically changing the IP address is done through the server directly, rather than doing it via remote connection (at least, from my experience). If the server has a command line for changing some base settings, you'll likely do it through there. 

 

Also, DHCP doesn't necessarily change the IP address each time the server is rebooted. My FreeNAS server uses DHCP with 192.168.1.224 and I haven't bothered to set it to static because it's never changed on me when I shut down or reboot the server. Unless your network is very active, with new devices coming and going all the time, DHCP addresses shouldn't need to be reassigned that often. 

 

That said, It's a good idea to free up a space of IP addresses by setting the router's DHCP pool to something like 192.168.1.21 - 192.168.1.220. That way you get 192.168.1.2 (assuming router is on 1.1) to 192.168.1.20 and 192.168.1.21 to 192.168.1.254 as static address space. Would leave 192.168.1.254 free though as it's often a default address for new devices. 

[manikyath]

most routers (even bottom of the barrel crap ones) allow you to reserve specific IP's in DHCP for specific devices (or rather, mac addresses).

[Night_]

Like @manikyath said, there shoud be an option in your router's DHCP server to lease an IP address based on your server's MAC address. Look around in your router administration panel, there should be a menu option for it somewhere.

Otherwise you could always configure your server with a static IP that has the same subnet as the one used by your router. However doing so with a DHCP server on the network might eventually cause an address collision, so such a configuration might not always be a good option.

 

[fjdhdhcyfhf]

When it comes to ubuntu server; if you can get a decent result from google then it is much faster to get to what you want by searching the debian wiki.

use ifconfig to get name of your NIC

Modify the /etc/network/interfaces file to give it a static IP.

https://wiki.debian.org/NetworkConfiguration#Configuring_the_interface_manually

 

[manikyath]

6 hours ago, Night_ said:

 

Otherwise you could always configure your server with a static IP that has the same subnet as the one used by your router. However doing so with a DHCP server on the network might eventually cause an address collision, so such a configuration might not always be a good option.

you'd have to choose one outside dhcp range (most routers' stock settings only lease ~100 IP addresses out of 253 available)

[Night_]

@manikyath

Some can issue address outside the range even if configured not to. Regardless though, system-wise it's still a better idea to let the DCHP handle this kind of thing if it already exists on the same network.

[manikyath]

4 hours ago, Night_ said:

@manikyath

Some can issue address outside the range even if configured not to. Regardless though, system-wise it's still a better idea to let the DCHP handle this kind of thing if it already exists on the same network.

if dhcp is configured to only give a specific range, and it gives IPs outside of that range, you should throw your router in the garbage.

[Night_]

@manikyath

And waste what otherwise could be a well-manifactured piece of hardware? Please, that's part of the reason why there's alternative open-source Linux or BSD based firmwares out there.

[manikyath]

15 minutes ago, Night_ said:

@manikyath

And waste what otherwise could be a well-manifactured piece of hardware? Please, that's part of the reason why there's alternative open-source Linux or BSD based firmwares out there.

if a DHCP server gets allocated a range, it should use that, and only that range. i dont even wanna know what other idiotic crap they did beyond that.

[Night_]

@manikyath

DHCP is only a piece of software. If it doesn't work out of the box, it can be reconfigured manually or swapped for another. There's no need to always strictly relay on what some company does with it.