How to configure the additional IPs on a dedicated server?

ashl3y_ · 05-04-2013, 12:03 AM

I'm running debian and am looking for help on how to do this. (I don't have any cpanel installed or anything like that..)

http://www.nish.com/2007/12/how-to-s...ips-on-debian/

I found this article but I still haven't much of an idea on what to do..

Quote:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 6*.*.*.27
netmask 255.255.255.0
gateway 6*.*.*.1

Would I just add

Quote:

address 6*.*.*.25

to the bottom of that?

druuna · 05-04-2013, 02:25 AM

You need to create an entry for every individual network interface. It doesn't matter if it is real or virtual:

Code:

# The loopback network interface
auto lo
  iface lo inet loopback

# The primary network interface (eth0)
auto eth0
  iface eth0 inet static
  address 6*.*.*.27
  netmask 255.255.255.0
  gateway 6*.*.*.1

# The secondary network interface (eth0:1)
auto eth0:1
  iface eth0:1 inet static
  address 6*.*.*.25
  netmask 255.255.255.0

Don't forget to (re)start networking after making changes.

ashl3y_ · 05-04-2013, 03:22 AM

Quote:

Originally Posted by druuna

You need to create an entry for every individual network interface. It doesn't matter if it is real or virtual:

Code:

# The loopback network interface
auto lo
  iface lo inet loopback

# The primary network interface (eth0)
auto eth0
  iface eth0 inet static
  address 6*.*.*.27
  netmask 255.255.255.0
  gateway 6*.*.*.1

# The secondary network interface (eth0:1)
auto eth0:1
  iface eth0:1 inet static
  address 6*.*.*.25
  netmask 255.255.255.0

Don't forget to (re)start networking after making changes.

Sorry if I may sound foolish, but, what I'm doing is defining the network devices correct? So if I setup apache to listen to lets say the IP address 1.1.1.1 and I added

Quote:

auto eth0:1
iface eth0:1 inet static
address 1.1.1.1
netmask 255.255.255.0

It would start accepting connections? I don't have to add a gateway do I even if some IP addresses are completely different?
Thanks for the help!

Edit: seems like Apache is not configured correctly.. I can ssh into that IP address now! (Which is progress)
Here is what it is telling me.. Any ideas??

Quote:

Restarting web server: apache2(98)Address already in use: make_sock: could not bind to address 1.1.1.1
no listening sockets available, shutting down

druuna · 05-04-2013, 04:01 AM

Quote:

Originally Posted by ashl3y_

but, what I'm doing is defining the network devices correct?

Correct.

Quote:

So if I setup apache to listen to lets say the IP address 1.1.1.1 and I added

Code:

auto eth0:1
 iface eth0:1 inet static
 address 1.1.1.1
 netmask 255.255.255.0

It would start accepting connections?

That is basically correct. You first set up the network devices/interfaces and then you point your service to it if needed (which is apache in your case, but can be any service).

Out of the box apache will listen on port 80 on all available interfaces. This is true for many services (but the port that the service listens on is different).

As root user try the following command:

Code:

netstat -planA inet

The above command shows ip's, ports and service (local and remote) used by your box.

Quote:

I don't have to add a gateway do I even if some IP addresses are completely different?

That depends on who needs to contact this IP and from where. If this is local testing using a private network range then you probably do not need one.

This might explain it better: Default gateway

Quote:

Edit: seems like Apache is not configured correctly.. I can ssh into that IP address now! (Which is progress)

If you can ssh using the newly created IP address then the network part seems to be ok.

Quote:

Restarting web server: apache2(98)Address already in use: make_sock: could not bind to address 1.1.1.1

1.1.1.1 isn't a private IP range.

I do wonder why you are trying to set it up this way.

ashl3y_ · 05-04-2013, 05:52 AM

Quote:

Originally Posted by druuna

Correct.

That is basically correct. You first set up the network devices/interfaces and then you point your service to it if needed (which is apache in your case, but can be any service).

Out of the box apache will listen on port 80 on all available interfaces. This is true for many services (but the port that the service listens on is different).

As root user try the following command:

Code:

netstat -planA inet

The above command shows ip's, ports and service (local and remote) used by your box.

That depends on who needs to contact this IP and from where. If this is local testing using a private network range then you probably do not need one.

This might explain it better: Default gateway

If you can ssh using the newly created IP address then the network part seems to be ok.

1.1.1.1 isn't a private IP range.

I do wonder why you are trying to set it up this way.

I just substituted 1.1.1.1 with an actual IP address. It's really along the lines of 87.*.*.238, but I'd rather not post that here. Thank you for your help also.

Still having issues with Apache. Any clue why this is happening?

Edit: Nevermind, the issue was that I had the "Listening" on that IP address twice in my ports.conf.

Thank you so much for your help!