OVH Community, your new community space.

Allocating IP block - how to add it


DennisMidjord
18-07-2014, 23:30
I don't think that's possible in Debian, edan. :-/

edan
18-07-2014, 04:59
If you need is just to point the IP block to the server than using range will fix the problems and no need to write those many config, just creating ifcfg-eth0-range0 than fill like below:

IPADDR_START=92.222.204.176
IPADDR_END=92.222.204.191
NETMASK=255.255.255.255
CLONENUM_START=1

Restart the network.

Update: on CentOS.

DennisMidjord
18-07-2014, 03:33
I'm not sure I get this. Next to 'auto eth0' I added eth0:0 eth0:1 eth0:2 and so on, all the way up to eth0:32.
When I did /etc/init.d/networking restart, it suddenly worked, but I got a long error.
root@ns318686:~# /etc/init.d/networking restart
[warn] Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
[....] Reconfiguring network interfaces...RTNETLINK answers: No such process
RTNETLINK answers: File exists
Failed to bring up eth0:0.
RTNETLINK answers: File exists
Failed to bring up eth0:1.
RTNETLINK answers: File exists
Failed to bring up eth0:2.
RTNETLINK answers: File exists
Failed to bring up eth0:3.
RTNETLINK answers: File exists
Failed to bring up eth0:4.
RTNETLINK answers: File exists
Failed to bring up eth0:5.
RTNETLINK answers: File exists
Failed to bring up eth0:6.
RTNETLINK answers: File exists
Failed to bring up eth0:7.
RTNETLINK answers: File exists
Failed to bring up eth0:8.
RTNETLINK answers: File exists
Failed to bring up eth0:9.
RTNETLINK answers: File exists
Failed to bring up eth0:10.
RTNETLINK answers: File exists
Failed to bring up eth0:11.
RTNETLINK answers: File exists
Failed to bring up eth0:12.
RTNETLINK answers: File exists
Failed to bring up eth0:13.
RTNETLINK answers: File exists
Failed to bring up eth0:14.
RTNETLINK answers: File exists
Failed to bring up eth0:15.
RTNETLINK answers: File exists
Failed to bring up eth0:18.
RTNETLINK answers: File exists
Failed to bring up eth0:19.
RTNETLINK answers: File exists
Failed to bring up eth0:20.
RTNETLINK answers: File exists
Failed to bring up eth0:21.
RTNETLINK answers: File exists
Failed to bring up eth0:22.
RTNETLINK answers: File exists
Failed to bring up eth0:23.
RTNETLINK answers: File exists
Failed to bring up eth0:24.
RTNETLINK answers: File exists
Failed to bring up eth0:25.
RTNETLINK answers: File exists
Failed to bring up eth0:26.
RTNETLINK answers: File exists
Failed to bring up eth0:27.
RTNETLINK answers: File exists
Failed to bring up eth0:28.
RTNETLINK answers: File exists
Failed to bring up eth0:29.
RTNETLINK answers: File exists
Failed to bring up eth0:30.
RTNETLINK answers: File exists
Failed to bring up eth0:31.
RTNETLINK answers: File exists
Failed to bring up eth0:32.
done.

DennisMidjord
18-07-2014, 02:57
heise, that's the only way we can get eth0:16 working - with auto and broadcast. I removed gateway from eth0:17 on purpose because Neil said it wasn't necessary. It didn't change anything.

I also tried your corrections. That didn't do anything unfortunately.

heise
17-07-2014, 22:28
iface eth0:15 inet static
address 188.165.155.15
netmask 255.255.255.255
gateway 37.187.24.254
auto eth0:16
iface eth0:16 inet static
address 178.33.38.79
netmask 255.255.255.255
broadcast 178.33.38.79
gateway????
iface eth0:17 inet static
address 92.222.204.176
netmask 255.255.255.255
gateway????
iface eth0:18 inet static
address 92.222.204.177
netmask 255.255.255.255
gateway 37.187.24.254

DennisMidjord
17-07-2014, 20:25
This is the entire interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 37.187.24.178
netmask 255.255.255.0
network 37.187.24.0
broadcast 37.187.24.255
gateway 37.187.24.254

iface eth0 inet6 static
address 2001:41D0:A:18b2::
netmask 64
post-up /sbin/ip -f inet6 route add 2001:41D0:A:18ff:ff:ff:ff:ff dev eth0
post-up /sbin/ip -f inet6 route add default via 2001:41D0:A:18ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del default via 2001:41D0:A:18ff:ff:ff:ff:ff
pre-down /sbin/ip -f inet6 route del 2001:41D0:A:18ff:ff:ff:ff:ff dev eth0

iface eth0:0 inet static
address 188.165.155.0
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:1 inet static
address 188.165.155.1
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:2 inet static
address 188.165.155.2
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:3 inet static
address 188.165.155.3
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:4 inet static
address 188.165.155.4
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:5 inet static
address 188.165.155.5
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:6 inet static
address 188.165.155.6
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:7 inet static
address 188.165.155.7
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:8 inet static
address 188.165.155.8
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:9 inet static
address 188.165.155.9
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:10 inet static
address 188.165.155.10
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:11 inet static
address 188.165.155.11
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:12 inet static
address 188.165.155.12
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:13 inet static
address 188.165.155.13
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:14 inet static
address 188.165.155.14
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:15 inet static
address 188.165.155.15
netmask 255.255.255.255
gateway 37.187.24.254
auto eth0:16
iface eth0:16 inet static
address 178.33.38.79
netmask 255.255.255.255
broadcast 178.33.38.79
iface eth0:17 inet static
address 92.222.204.176
netmask 255.255.255.255
iface eth0:18 inet static
address 92.222.204.177
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:19 inet static
address 92.222.204.178
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:20 inet static
address 92.222.204.179
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:21 inet static
address 92.222.204.180
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:22 inet static
address 92.222.204.181
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:23 inet static
address 92.222.204.182
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:24 inet static
address 92.222.204.183
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:25 inet static
address 92.222.204.184
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:26 inet static
address 92.222.204.185
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:27 inet static
address 92.222.204.186
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:28 inet static
address 92.222.204.187
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:29 inet static
address 92.222.204.188
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:30 inet static
address 92.222.204.189
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:31 inet static
address 92.222.204.190
netmask 255.255.255.255
gateway 37.187.24.254
iface eth0:32 inet static
address 92.222.204.191
netmask 255.255.255.255
gateway 37.187.24.254
Can anybody see anything wrong?

Razakel
17-07-2014, 20:21
Quote Originally Posted by DennisMidjord
The problem with support tickets is that it sometimes takes a very long time to get a reply. I know I can't expect anything else since they offer really cheap servers, but I actually prefer to use the forums since I can get a faster reply.

I'll try to mess around with it a bit.
To be honest, there's not too much the UK and Irish support can do regarding technical issues. All of that is dealt with by the French datacentre staff.

DennisMidjord
17-07-2014, 20:19
The problem with support tickets is that it sometimes takes a very long time to get a reply. I know I can't expect anything else since they offer really cheap servers, but I actually prefer to use the forums since I can get a faster reply.

I'll try to mess around with it a bit.

Razakel
17-07-2014, 20:16
Did you do anything differently when you set them up? Try removing and re-adding them.

IP blocks not being routed correctly does occasionally happen. Open a support ticket if you're still having trouble.

DennisMidjord
17-07-2014, 20:02
This was what it said in the email we received - we have been using gateway for all the other IP's:
OVH 2 rue Kellermann 59100 Roubaix
Technical support: 08.99.49.87.65 (€1.349/call + €0.337/min) Commercial support: 08.20.69.87.65 (€0.118/min)
Fax: 03.20.20.09.58
support@ovh.com



Dear Customer,

Further to your request, we have just assigned a block of 16 IP addresses that will be routed via 37.187.24.178:

92.222.204.176/28

You can use the IP addresses of this block in 2 ways:


1 - Configuration within a dedicated server


In this case, all IPs of your block 92.222.204.176/28 are usable.

Please use of one of the following guides for the configuration:

- If used in virtual machines: http://guide.ovh.com/BridgeClient.

- If used on the same interface network of your server: http://guide.ovh.com/AjouterAliasIp.

In general, all IPs must have the following netmask:
255.255.255.255, and the gateway is composed of the main IP of the server ending in .254


2 - Configuration within a virtual rack (vRack) or on a Dedicated Cloud offer


If you use this block in a virtual rack or a Dedicated Cloud, the following addresses must be freed up:

Network IP : 92.222.204.176
IP for router n1 : 92.222.204.188
IP for router n1 : 92.222.204.189
Gateway IP : 92.222.204.190 (not usable)
Broadcast IP: : 92.222.204.191

Then use the sub-netmask 255.255.255.240.


For your information, your block has the following characteristics:

92.222.204.176/28
Network IP :92.222.204.176
Broadcast IP :92.222.204.191
Gateway IP :92.222.204.190
Netmask :255.255.255.240


Kind regards,

OVH Ltd
3 Southwark street
London
SE1 1RQ
Tel: 020 7357 6616
Fax: 0330 684 0028
Registered company 5519821
E-mail: customersupport@ovh.co.uk

OVH Customer Support
Mon-Fri 9am to 6pm

Join the OVH Community at forum.ovh.co.uk

Check our service status at http://status.ovh.co.uk/

Neil
16-07-2014, 10:27
Hi, no need for the gateway if you are just aliases see http://help.ovh.co.uk/IpAlias

DennisMidjord
15-07-2014, 21:23
Hi!

We've just bought another IP block containing 16 IP's.

This is what we've added to /etc/network/interfaces:
Code:
iface eth0:17 inet static
	address 92.222.204.176
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:18 inet static
	address 92.222.204.177
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:19 inet static
	address 92.222.204.178
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:20 inet static
	address 92.222.204.179
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:21 inet static
	address 92.222.204.180
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:22 inet static
	address 92.222.204.181
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:23 inet static
	address 92.222.204.182
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:24 inet static
	address 92.222.204.183
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:25 inet static
	address 92.222.204.184
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:26 inet static
	address 92.222.204.185
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:27 inet static
	address 92.222.204.186
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:28 inet static
	address 92.222.204.187
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:29 inet static
	address 92.222.204.188
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:30 inet static
	address 92.222.204.189
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:31 inet static
	address 92.222.204.190
	netmask 255.255.255.255
	gateway 37.187.24.254
iface eth0:32 inet static
	address 92.222.204.191
	netmask 255.255.255.255
	gateway 37.187.24.254
We already have added from eth0:0 to eth0:16. We're not able to ping any of the newly added IP's, but we can still ping our old ones.

Have we done anything wrong?