TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 Some more output in case it helps: ifconfig -a What's the deal? Where would I look now? The problem must be related to the Ubuntu VE itself, I assume, since it works with newly created ones. Of course, /sys/devices/virtual/net/venet0/statistics/rx_bytes is updating, and none of the /sys/devices/virtual/net/venet0/statistics/rx_ error files make a peep. I can run tcpdump on the host and get the same output immediately. This output occasionally occurs with some delay, I believe because tcpdump tries to reverse-DNS the ips involved: 17:47:20.977819 IP dolores.40623 > 213.133.98.97.domain: 60247+ PTR? 8.8.8.8.in-addr.arpa. I've cleared all iptables rules both on host and inside the VE.It cannot ping the host, nor anything else.I can connect INTO the old instance perfectly well, but it cannot connect to the outside.It works just fine if a setup a new OpenVZ instance.I'm migrating an old Ubuntu OpenVZ instance (Jaunty) to a new CentOS 6.3 host (using vzdump/vzrestore).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |