Portal Home > Knowledgebase > Articles Database > IP's don't work on my server
IP's don't work on my server
| Posted by Bluz, 03-14-2011, 09:42 PM |
| I recently just bought 10 extra IP's from my host for 100 euro, but the problem is only 8 work, I've tried complaining to them but they just say it's on my end only, It's a vps machine and even tried getting them to go there tests while the server was offline in which they told me the same bull crap that ssh works just fine on there end. Basically it works like this.
1.0.0.1
1.0.0.2
1.0.0.3
1.0.0.4
1.0.0.5
1.0.0.6
1.0.0.7 - doesn't work
1.0.0.8 - doesn't work
1.0.0.9
1.0.0.10
And it's just the two that don't work, anyone have any idea what I can do about this? I'm using solusVM if that matters. Any help on this would be awesome thanks alot guys.
Also a side question, with ipv6 addresses I've heard you can make 1 ipv6 into several IP addresses? so say I got 1.0.0.0.0.0 I could make it all the way to 1.0.0.0.10 ?blah this is confusing. I just heard from a friend a ipv6 allows you to get like 10 ipv4's would've been and you can visit them the same way. (I visit the site via IPort)
|
| Posted by JonFatino, 03-14-2011, 10:11 PM |
| type ifconfig and paste output please.
did open ticket with data center and make sure ips route was correct?
|
| Posted by Mr Terrence, 03-14-2011, 10:26 PM |
| Sound like a routing issue, open a ticket with your provider as stated above
|
| Posted by Bluz, 03-14-2011, 10:29 PM |
| Yeah I opened two support tickets with them cause the first one kept getting closed by them saying it's fine, it's just me. Here's the output.
eth0 Link encap:Ethernet HWaddr 00:30:67:33:5C:8A
inet addr:212.117.175.91 Bcast:212.117.175.255 Mask:255.255.255.0
inet6 addr: fe80::230:67ff:fe33:5c8a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2299170545 errors:0 dropped:0 overruns:0 frame:0
TX packets:3035491351 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:286597031886 (266.9 GiB) TX bytes:4229721575677 (3.8 TiB)
Interrupt:233 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:353 errors:0 dropped:0 overruns:0 frame:0
TX packets:353 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18678 (18.2 KiB) TX bytes:18678 (18.2 KiB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:3040146732 errors:0 dropped:0 overruns:0 frame:0
TX packets:1612165083 errors:0 dropped:236 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4197258030216 (3.8 TiB) TX bytes:210854964834 (196.3 GiB)
If it's just me then why does it not work for a friend of mine in the states :-/
Edit: So if it's a routing issue it's my fault and cannot be fixed? That sucks...I was really planning on using these guys for alot of servers cause there costs are so good, all be it expensive at 10 bucks a IP address. But overtime you save money that way I suppose...this just really sucks that I'm loosing two IP's over this.
|
| Posted by JonFatino, 03-15-2011, 04:39 AM |
| is this a dedicated server or a vps?
I dont see 10 ips bound there.
and if its a "routing issue" its not your fault.
Since your renting a dedi
and not colo / run your own hardware...
Its the data centers job to provide you with all hardware...
99.9% of all routing issues just have a messed up config.
if your machine is a vps (which above that is stated)
If its a vmware/xen/ect dedicated vps it has eth0 and eth0:1 and eth0:2
But if its a linux vps then its probably a openvz vps.
which uses venet0
when command ifconfig runs it should look like this.
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:69341 errors:0 dropped:0 overruns:0 frame:0
TX packets:35113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:101728236 (97.0 MiB) TX bytes:1961682 (1.8 MiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:XXX.XXX.XXX.XXX P-t-P:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
and normally when its a openvz vps.
They have control panels like solusvm/veportal
and the host has to go into admin panel and bind the ips for you.
From the output you listed above.
it does not look like the ips are bound to the server.
|
| Posted by Bluz, 03-15-2011, 02:56 PM |
| The above is a dedicated server running vpses, I did the command in the master directory as well not in any virtual machines.
|
| Posted by dima23, 03-15-2011, 04:18 PM |
| you need to contact them for fix it
|
| Posted by Emyhost, 03-18-2011, 04:51 AM |
| You try to ping the IP having problem in the server, to make sure they do really added the IP. If it reachable means high possibility is due to routing issue, or else, is the provider issue.
However, you can't do much work on it, just contact your provider and wait for their reply.
|
Add to Favourites 
Print this Article
Also Read
