VE connectivity problems. OUT to IN not working IN to OUT working perfectly
Hi, I am experimenting hard problems with connectivity in only one container. All connectivity of this vps is down when atempt to connect from outside (and all static ips assigned to this container). In master node i can ping to ve ip without problems. And inside the problematic container i have all access to outside, appears be ok (i only can access, via vzctl enter $id in master). Also comment, my hardware node is in another subnet. And connect problems are random, sometimes goes online and get offline time ago. But only in one vps, the rest of vps are in the same subnet and working perfect at now. Here a tracert from a ve without problems and the problematic container: Damaged VPS: root@server [/]# tracert terra.es traceroute to terra.es (213.4.130.210), 30 hops max, 40 byte packets 1 x-x-x.XxX.com.com (x.x.99.21) 0.087 ms 0.054 ms 0.056 ms 2 hos-tr4.juniper3.rz4.hetzner.de (213.239.244.193) 0.658 ms 0.703 ms 0.766 ms 3 hos-bb2.juniper4.s04.hetzner.de (213.239.240.139) 0.774 ms 0.786 ms 0.591 ms 4 lambdanet-ffm-gw.hetzner.de (213.239.247.206) 4.013 ms 4.071 ms 3.922 ms 5 ffm-b3-link.telia.net (213.248.68.205) 4.009 ms 4.052 ms 4.071 ms 6 ffm-b2-link.telia.net (80.91.251.226) 3.961 ms 3.981 ms 3.967 ms 7 telefonica-ic-127710-ffm-b2.c.telia.net (213.248.89.90) 29.474 ms 28.370 ms 28.318 ms 8 xe3-0-0-0-grtfraix3.red.telefonica-wholesale.net (84.16.14.162) 3.857 ms 3.913 ms 3.884 ms 9 So-2-3-0-0-grtlont1.red.telefonica-wholesale.net (84.16.13.234) 19.434 ms 19.423 ms 19.510 ms 10 So2-1-0-0-grtmadde2.red.telefonica-wholesale.net (213.140.43.221) 38.165 ms 38.075 ms 38.143 ms 11 So4-1-0-0-grtmadrr1.red.telefonica-wholesale.net (213.140.36.189) 36.520 ms 36.479 ms So3-3-0-0-grtmadde2.red.telefonica-wholesale.net (213.140.37.9) 40.560 ms 12 158.Red-80-58-75.staticIP.rima-tde.net (80.58.75.158) 40.058 ms So-1-3-0-0-grtmadde2.red.telefonica-wholesale.net (213.140.38.249) 43.065 ms 43.077 ms 13 158.Red-80-58-75.staticIP.rima-tde.net (80.58.75.158) 44.266 ms 44.011 ms 43.577 ms 14 www.terra.es (213.4.130.210) 41.876 ms 38.841 ms 38.914 ms ---------------------------- VPS working [root@xx2 ~]# tracert terra.es traceroute to terra.es (213.4.130.210), 30 hops max, 40 byte packets 1 x-x-x-X.XxX.com (x.x.99.21) 0.074 ms 0.111 ms 0.039 ms 2 hos-tr4.juniper3.rz4.hetzner.de (213.239.244.193) 0.325 ms 0.380 ms 0.441 ms 3 hos-bb2.juniper4.s04.hetzner.de (213.239.240.139) 1.839 ms 1.872 ms 1.946 ms 4 lambdanet-ffm-gw.hetzner.de (213.239.247.206) 4.080 ms 4.148 ms 4.208 ms 5 ffm-b3-link.telia.net (213.248.68.205) 4.053 ms 4.120 ms 4.182 ms 6 ffm-b2-link.telia.net (80.91.251.226) 4.096 ms 4.106 ms 4.082 ms 7 telefonica-ic-127710-ffm-b2.c.telia.net (213.248.89.90) 3.779 ms 3.761 ms 3.782 ms 8 Xe11-1-0-0-grtpartv1.red.telefonica-wholesale.net (84.16.14.170) 14.282 ms 14.297 ms 14.254 ms 9 Xe4-0-0-0-grtparix1.red.telefonica-wholesale.net (84.16.13.230) 14.556 ms 14.589 ms 14.602 ms 10 So2-0-0-0-grtmadde2.red.telefonica-wholesale.net (84.16.12.5) 36.803 ms So0-0-0-0-grtmadde2.red.telefonica-wholesale.net (213.140.36.73) 32.502 ms So2-0-0-0-grtmadde2.red.telefonica-wholesale.net (84.16.12.5) 36.875 ms 11 www.terra.es (213.4.130.210) 31.936 ms 31.628 ms 37.530 ms I do not have special configurations. My config is: - Centos 5 x64 in master and VE (the ve managed with cPanel). - Linux kernel: 2.6.18-92.1.13.el5.028stab059.6 - vzctl 3.0.23 Thanks for help Regards, Amil
PARTIALLY SOLVED: VE connectivity problems. OUT to IN not working IN to OUT working perfectly
Well the problem was with iptables. Service iptables stopped solves (at this time) all networks problems OUT to IN. However, i need iptables on my container for manage iptables rules (via apf or csf in this case), so i mean that need enable some iptables rules or something to solve this hard routing issues. Any kind of help is higly appreciated. Thanks!
Re: VE connectivity problems. OUT to IN not working IN to OUT working perfectly
Uninstalling csf or disabling iptables service was not the definitive solution. Connectivity problems still appears random. I contact my provider to verify and discard routing issues.