OpenVZ Forum - RDF feed
type: channel
items: Containers Use Host IP and not configured IPs
items: Re: Containers Use Host IP and not configured IPs

Containers Use Host IP and not configured IPs
type: item
description: Hello, I am having a networking issue i cant seem to figure out. Here is what I did 1: took backups of all VPSs & did a clean OS install on the server ( CentOS 6.5 ) 2: reinstalled SolusVM control panel with openvz virtualization 3: restored VPSs with vzdump --restore ... The issue is that the VPSs are now using the Host IP address and not the IP configured # vzctl restart 115 Restarting container Stopping container ... Container was stopped Container is unmounted Starting container... Container is mounted Adding IP address(es): 7x.xx.139.109 7x.xx.138.128 Setting CPU limit: 200 Setting CPU units: 1000 Setting CPUs: 2 Container start in progress... # vzctl enter 115 entered into CT 115 [~]# lynx -dump http //www.cpanel.net/showip.cgi 7x.xx.138.86 I really need some help figuring this out. The cpanel installs running on the VPSs are throwing the invalid license screen due to this IP issue Scott
creator: scottcase
date: 2015-05-02T15:21:26-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: Hi, from the openvz view - add the correct ipv4 to your container via cli like: % vzctl set <CTID> --ipadd 7x.xx.138.86 --save Maybe an SolusVM control panel issue - please check forum at https://forum.solusvm.com/, too! Bye, Thorsten
creator: curx
date: 2015-05-02T16:09:11-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: Hello Curx 7x.xx.138.86 is the node ip address, the container should be using 7x.xx.139.109 as the main ip address. I tried your suggestion with no change [root@ ~]# vzctl set 115 --ipadd 7x.xx.139.109 --save Deleting IP address(es): 7x.xx.139.109 Adding IP address(es): 7x.xx.139.109 CT configuration saved to /etc/vz/conf/115.conf [root@ ~]# vzctl enter 115 entered into CT 115 root@ [~]# lynx -dump http //www.cpanel.net/showip.cgi 7x.xx.138.86 root@[~]# exit logout exited from CT 115 [root@ ~]# Scott
creator: scottcase
date: 2015-05-02T16:18:52-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: Hi, * any iptables rules used on hardwarenode & ct? * are you useing a proxy for your ct? * can you give ip a l && ip r l from hardwarenode and container (ip/r can be "obfuscated") Bye, Thorsten
creator: curx
date: 2015-05-02T17:09:18-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: Hello curx, Here is the requested information Host Node IPTables [root@ ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination SOLUSVM_TRAFFIC_IN all -- anywhere anywhere SOLUSVM_TRAFFIC_OUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain SOLUSVM_TRAFFIC_IN (1 references) target prot opt source destination all -- anywhere 7x.xx.139.101 all -- anywhere 7x.xx.139.102 all -- anywhere 7x.xx.139.103 all -- anywhere 7x.xx.139.104 all -- anywhere 7x.xx.139.105 all -- anywhere 7x.xx.139.106 all -- anywhere 7x.xx.139.107 all -- anywhere 7x.xx.139.109 all -- anywhere xxxxxxmail.com all -- anywhere xxxxxaseitnow.net all -- anywhere 7x.xx.138.6 all -- anywhere 7x.xx.137.254 all -- anywhere 7x.xx.137.253 all -- anywhere xxxxxxhosting.net all -- anywhere xxxxxxeutcart.com all -- anywhere xxxxxxasnline.com all -- anywhere xxxxxxxutions.com all -- anywhere 7x.xx.138.128 all -- anywhere xxxxxxxlobal2.com Chain SOLUSVM_TRAFFIC_OUT (1 references) target prot opt source destination all -- 7x.xx.139.101 anywhere all -- 7x.xx.139.102 anywhere all -- 7x.xx.139.103 anywhere all -- 7x.xx.139.104 anywhere all -- 7x.xx.139.105 anywhere all -- 7x.xx.139.106 anywhere all -- 7x.xx.139.107 anywhere all -- 7x.xx.139.109 anywhere all -- xxxxxxmail.com anywhere all -- xxxxxaseitnow.net anywhere all -- 7x.xx.138.6 anywhere all -- 7x.xx.137.254 anywhere all -- 7x.xx.137.253 anywhere all -- xxxxxxhosting.net anywhere all -- xxxxxxeutcart.com anywhere all -- xxxxxxasnline.com anywhere all -- xxxxxxxutions.com anywhere all -- 7x.xx.138.128 anywhere all -- xxxxxxxlobal2.com anywhere [root@ ~]# [root@ ~]# ip a l && ip r l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWE…
creator: scottcase
date: 2015-05-02T17:26:44-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: SolusVM support has resolved the issue for me.
creator: scottcase
date: 2015-05-02T19:59:37-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: Can you give us more info, about the solution!
creator: curx
date: 2015-05-03T09:27:27-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: It was something with iptables on the host, they completely reset iptables and all was good. something about the NAT table was messed up.
creator: scottcase
date: 2015-05-03T12:54:35-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: That's odd. If you have a chance, could you do a 'ip a l && ip r l' again? I expect to see a difference here, but I might be wrong. Could be helpful if it happens to you again, or to somebody else...
creator: Ales
date: 2015-05-04T23:46:31-00:00

Re: Containers Use Host IP and not configured IPs
type: item
description: This is the command they ran that fixed it iptables -F -t nat
creator: scottcase
date: 2015-05-04T23:53:58-00:00