pillsdrugs
New Member
I've ordered for a new ip from my hosting company: 173.23.4.32 (not real ip)
I added ifcfg-venet0:2 with this config:
DEVICE=venet0:2
ONBOOT=yes
STARTMODE=onboot
GATEWAY=173.23.4.10
IPADDR=173.23.4.32
NETMASK=255.255.255.0
Did an ifup, network restart and added it to the container using vzctl with a working nameserver.
But the thing is, the container can't even ping the gateway that they sent me. The container cant access the internet. When I accessed the new ip on a browser, it goes to my dedicated server ip and not on the container itself. But when I tried doing an ssh on the new ip, it can't connect to my dedicated server. I did traceroute and its not going through my dedi's ip, and even has a different site's reverse dns name.
I've added ip addresses before and I can't seem to solve this one. Is this a network problem on my host's end?
Contact your host with a traceroute and they will surely fix it for you.
I added ifcfg-venet0:2 with this config:
DEVICE=venet0:2
ONBOOT=yes
STARTMODE=onboot
GATEWAY=173.23.4.10
IPADDR=173.23.4.32
NETMASK=255.255.255.0
Did an ifup, network restart and added it to the container using vzctl with a working nameserver.
But the thing is, the container can't even ping the gateway that they sent me. The container cant access the internet. When I accessed the new ip on a browser, it goes to my dedicated server ip and not on the container itself. But when I tried doing an ssh on the new ip, it can't connect to my dedicated server. I did traceroute and its not going through my dedi's ip, and even has a different site's reverse dns name.
I've added ip addresses before and I can't seem to solve this one. Is this a network problem on my host's end?