Traffic wrotemaikcat wrote2)the NAT rule for vz based servers is different,
with that in mind please issue:
Code:
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o venet0:0 -j SNAT --to-source 92.222.5.180
Gyoo wrote14:54:57.029032 IP 10.8.0.6 > 8.8.8.8: ICMP echo request, id 1, seq 9, length 40
Your NAT rule is not working ..
Apparently it has been removed, probably after I restarted my server a few days ago. Whoops.
I just installed iptables-permanent to solve this issue for next times.
Anyway, I retried a ping after putting the rules again, the result is the same :
17:50:16.852915 IP 10.8.0.6 > 8.8.8.8: ICMP echo request, id 1, seq 111, length 40
17:50:21.853165 IP 10.8.0.6 > 8.8.8.8: ICMP echo request, id 1, seq 112, length 40
I noticed that you're specifying port 24 for this rule... can't the problem come from that ?
Gyoo wrote14:55:06.168047 IP 5.39.111.9 > 92.222.5.180: ICMP echo request, id 30068, seq 156, length 64
14:55:06.168361 IP 92.222.5.180 > 5.39.111.9: ICMP echo reply, id 30068, seq 156, length 64
This is very confused .. are you pinging your server from somewhere else ?
Who is:
5.39.111.9
Gyoo wrotevenet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:92.222.5.180 P-t-P:92.222.5.180 Bcast:92.222.5.255 Mask:255.255.255.0
Has this IP address changed ?
5.39.111.9 seems to be located in a datacenter of OVH. This ping must come from them to track the uptime of the server, or something like that.
And the adress for venet0:0 has not changed.