OVH Community, your new community space.

need help with an ip problem

spid3r1987

28-04-2011, 17:03

well tech support sorted this
according to tech
"A double incoming IP route has been detected in the router, it is fixed now."

spid3r1987

19-04-2011, 08:55

Originally Posted by spid3r1987

nope, now i can only see

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
94.23.15.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         94.23.15.254    0.0.0.0         UG    0      0        0 eth0

but now all 3 failover ip's are working properly.
weird lol!

WAS WORKING!!!
not changed anything and now my .110 ip wont work again :S

spid3r1987

18-04-2011, 08:44

Originally Posted by Myatu

When looking at your output in this post: http://forum.ovh.co.uk/showpost.php?p=38429&postcount=8, I see this:

Code:

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 178.32.50.16 0.0.0.0 255.255.255.248 U 0 0 0 eth0 178.32.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 94.23.15.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 94.23.15.254 0.0.0.0 UG 0 0 0 eth0

Now, disregarding the mask being incorrect (which you seem to have corrected since then, following the previous discussion), I can only see the main IP (94.xx), and two of the failover IPs. So the exception here is that 178.32.50.110 is not listed in the route, which is also the one causing the issues. Is this still the case?

nope, now i can only see

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
94.23.15.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         94.23.15.254    0.0.0.0         UG    0      0        0 eth0

but now all 3 failover ip's are working properly.
weird lol!

Myatu

15-04-2011, 17:56

When looking at your output in this post: http://forum.ovh.co.uk/showpost.php?p=38429&postcount=8, I see this:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
178.32.50.16    0.0.0.0         255.255.255.248 U     0      0        0 eth0
178.32.50.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
94.23.15.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         94.23.15.254    0.0.0.0         UG    0      0        0 eth0

Now, disregarding the mask being incorrect (which you seem to have corrected since then, following the previous discussion), I can only see the main IP (94.xx), and two of the failover IPs. So the exception here is that 178.32.50.110 is not listed in the route, which is also the one causing the issues. Is this still the case?

spid3r1987

14-04-2011, 15:25

hey
contacted support and got this

Code:

However, the IP address 178.32.50.110 I still can not ping,
but the IP address is not blocked and I can not see any issues with it within our system.
I believe it still could be an issue with configuration.
I can only suggest that you investigate this yourself as far as I can see there is no issues with IP address.

how else can i investigate whats wrong with my IP
my ifconfig shows

Code:

eth0:3    Link encap:Ethernet  HWaddr 00:1C:C0:73:1D:7D
          inet addr:178.32.50.110  Bcast:178.32.50.110  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:27 Base address:0xc000

iv even wiped the OS and re-installed and still getting this problem

would greatly appreciate some help on WTF to do lol