OVH Community, your new community space.

IP misconfig email


LawsHosting
16-09-2010, 18:05
The issue has been fixed, and I've fixed the rest of my servers.

As I use Webmin for half of my sysdmin routines, it screwed up the broadcast ip settings......

LawsHosting
16-09-2010, 14:28
I dont want to seem I'm spamming the forum but I would like to bring up
OVH's phone support.

I tried calling a few hours ago for assistance with this issue and this is what my operator said

"When I press 2, nothing happens, it just repeats the options over & over"

I would suggest this to be looked into, as I'm sure I'm not OVH's only disabled customer.

LawsHosting
16-09-2010, 14:12
Seems to be ok, IP/sites are pingable, however:

server1:~# /etc/init.d/networking restart
Reconfiguring network interfaces...
SIOCDELRT: No such process
SIOCDELRT: No such process
done.
If its not broke, dont worry eh

YouWhat
16-09-2010, 14:04
Im not sure as to why it isnt in there, but I have put it in there so as that way there is no confusion on the servers part as to its gateway paths etc.

If you have a virtual mac setup for the IP the above will not respond to the ping requests as it uses mac address of eth0, you will then have to set the hardware address for the virtual port up using hwaddress xx:xx:xx:xx:xx:xx (I am not 100% certain of

eg

iface eth0:2 inet static
address 94.23.152.xxx
netmask 255.255.255.255
gateway 94.23.238.254
hwaddr 00:11:22:33:aa:bb

LawsHosting
16-09-2010, 13:52
Ok, if we need to add gateways to failovers, why isn't it stated on http://help.ovh.net/IpAlias under Debian.

YouWhat
16-09-2010, 13:38
If server IP address is 123.123.123.123 then the server gateway is 123.123.123.254

For your Failover IP the /etc/network/interfaces file should have the Failover ips set like following

auto eth0:0
iface eth0:0 inet static
address Failover IP address here
netmask 255.255.255.255
gateway 123.123.123.254

eg My /etc/network/interfaces file is as follows to use the Failover IPs

# 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 eth0:0 eth0:1 eth0:2
iface eth0 inet static
address 94.23.238.xxx
netmask 255.255.255.0
network 94.23.238.0
broadcast 94.23.238.255
gateway 94.23.238.254

iface eth0:0 inet static
address 94.23.152.xxx
netmask 255.255.255.255
gateway 94.23.238.254

iface eth0:1 inet static
address 94.23.152.xxx
netmask 255.255.255.255
gateway 94.23.238.254

iface eth0:2 inet static
address 94.23.152.xxx
netmask 255.255.255.255
gateway 94.23.238.254
As you can then test and see after restarting the network that the IPs then are configured. (Using ifconfig)

eth0 Link encap:Ethernet HWaddr 00:1c:c0:73:e3:44
inet addr:94.23.238.xxx Bcast:94.23.238.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:64038428 errors:0 dropped:0 overruns:0 frame:0
TX packets:96613595 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:34940881280 (34.9 GB) TX bytes:124140790882 (124.1 GB)
Memory:e0200000-e0220000

eth0:0 Link encap:Ethernet HWaddr 00:1c:c0:73:e3:44
inet addr:94.23.152.xxx Bcast:94.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:e0200000-e0220000

eth0:1 Link encap:Ethernet HWaddr 00:1c:c0:73:e3:44
inet addr:94.23.152.xxx Bcast:94.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:e0200000-e0220000

eth0:2 Link encap:Ethernet HWaddr 00:1c:c0:73:e3:44
inet addr:94.23.152.xxx Bcast:94.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:e0200000-e0220000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4875 errors:0 dropped:0 overruns:0 frame:0
TX packets:4875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:548668 (548.6 KB) TX bytes:548668 (548.6 KB)

LawsHosting
16-09-2010, 13:19
Ok, maybe a new thread will be useful.

I've just received one of these emails for a 3yr old server but I'm a bit confused.

I dont use any BridgeClent/VM/etc

What I did find is that I've no gateways for my failover ip's, but on http://help.ovh.co.uk/IpAlias I see no instructions to add gateways or broadcasts to these IPs.

My /etc/network/interfaces has
auto eth0:0
iface eth0:0 inet static
address 87.98.xxx.xxx
netmask 255.255.255.255
etc

My broadcast seems to be automatically set as 87.255.255.255 for all failovers starting 87, 94.255.255.255 for all failovers starting 94, .255 for all failovers starting 178...

TIA