OpenVZ Forum


Home » General » Support » communicating between virtual machines
Re: communicating between virtual machines [message #35249 is a reply to message #35243] Thu, 12 March 2009 04:40 Go to previous messageGo to previous message
arulP is currently offline  arulP
Messages: 18
Registered: March 2009
Location: india
Junior Member

I cannot ping from one VE to the other and the sshd service is running in both the VEs.Do i need another ethernet card for communicating between two VEs?


here are the details:
[root@yahoo2 ~]# ip rule list ---------------------------routing rules
0: from all lookup local
32766: from all lookup main
32767: from all lookup default


[root@yahoo2 ~]# ip route list table all
192.168.4.171 dev venet0 scope link
192.168.4.170 dev venet0 scope link
192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.102
192.168.4.0/24 dev venet0 proto kernel scope link src 192.168.4.173
169.254.0.0/16 dev venet0 scope link
default via 192.168.4.1 dev eth0
local 192.168.4.173 dev venet0 table local proto kernel scope host src 192.168.4.173
broadcast 192.168.4.255 dev eth0 table local proto kernel scope link src 192.168.4.102
broadcast 192.168.4.255 dev venet0 table local proto kernel scope link src 192.168.4.173
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 192.168.4.0 dev eth0 table local proto kernel scope link src 192.168.4.102
broadcast 192.168.4.0 dev venet0 table local proto kernel scope link src 192.168.4.173
local 192.168.4.102 dev eth0 table local proto kernel scope host src 192.168.4.102
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
unreachable ::/96 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo metric 1024 expires 21333833sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21333836sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev veth170.0 metric 256 expires 21333929sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev veth171.0 metric 256 expires 21334117sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255
local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:fe38:6a4a via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:fe56:c259 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::223:54ff:fe17:a95e via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 expires 21333836sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev veth170.0 table local metric 256 expires 21333929sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev veth171.0 table local metric 256 expires 21334117sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255


------in virtual machine
[root@op /]# ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default

------------------------------netfilter configuration


[root@yahoo2 ~]# iptables -t nat -L && iptables -t filter -L && iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination




-----------------------packet paths
[root@yahoo2 ~]# tcpdump ----------------------------------------------------in HN
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
09:58:13.112700 IP 192.168.4.6.netbios-ns > 192.168.4.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
09:58:13.113430 IP 192.168.4.102.34670 > 192.168.4.1.domain: 1328+ PTR? 255.4.168.192.in-addr.arpa. (44)
09:58:13.121168 IP 192.168.4.1.domain > 192.168.4.102.34670: 1328 NXDomain* 0/1/0 (91)
09:58:13.121269 IP 192.168.4.102.54181 > 192.168.4.1.domain: 31018+ PTR? 6.4.168.192.in-addr.arpa. (42)
09:58:13.121577 IP 192.168.4.1.domain > 192.168.4.102.54181: 31018 NXDomain* 0/1/0 (89)
09:58:13.121680 IP 192.168.4.102.59213 > 192.168.4.1.domain: 56387+ PTR? 1.4.168.192.in-addr.arpa. (42)
09:58:13.121987 IP 192.168.4.1.domain > 192.168.4.102.59213: 56387 NXDomain* 0/1/0 (89)
09:58:13.122038 IP 192.168.4.102.58371 > 192.168.4.1.domain: 27962+ PTR? 102.4.168.192.in-addr.arpa. (44)
09:58:13.122396 IP 192.168.4.1.domain > 192.168.4.102.58371: 27962 NXDomain* 0/1/0 (91)
09:58:13.219456 IP 192.168.4.7.netbios-ns > 192.168.4.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
09:58:13.219595 IP 192.168.4.102.35445 > 192.168.4.1.domain: 58836+ PTR? 7.4.168.192.in-addr.arpa. (42)
09:58:13.219879 IP 192.168.4.1.domain > 192.168.4.102.35445: 58836 NXDomain* 0/1/0 (89)
09:58:13.227269 arp who-has 192.168.3.200 tell 192.168.3.84
09:58:13.227330 IP 192.168.4.102.49192 > 192.168.4.1.domain: 24555+ PTR? 200.3.168.192.in-addr.arpa. (44)
09:58:13.227678 IP 192.168.4.1.domain > 192.168.4.102.49192: 24555 NXDomain* 0/1/0 (91)
09:58:13.227786 IP 192.168.4.102.37992 > 192.168.4.1.domain: 47504+ PTR? 84.3.168.192.in-addr.arpa. (43)
09:58:13.228088 IP 192.168.4.1.domain > 192.168.4.102.37992: 47504 NXDomain* 0/1/0 (90)
09:58:13.286779 arp who-has 192.168.3.34 tell 192.168.3.31
09:58:13.286875 IP 192.168.4.102.44656 > 192.168.4.1.domain: 45284+ PTR? 34.3.168.192.in-addr.arpa. (43)
09:58:13.287188 IP 192.168.4.1.domain > 192.168.4.102.44656: 45284 NXDomain* 0/1/0 (90)
09:58:13.287245 IP 192.168.4.102.60931 > 192.168.4.1.domain: 15132+ PTR? 31.3.168.192.in-addr.arpa. (43)
09:58:13.287597 IP 192.168.4.1.domain > 192.168.4.102.60931: 15132 NXDomain* 0/1/0 (90)
09:58:13.312632 arp who-has 192.168.3.138 tell 192.168.3.105
09:58:13.312711 IP 192.168.4.102.39256 > 192.168.4.1.domain: 44893+ PTR? 138.3.168.192.in-addr.arpa. (44)
09:58:13.313041 IP 192.168.4.1.domain > 192.168.4.102.39256: 44893 NXDomain* 0/1/0 (91)
09:58:13.313097 IP 192.168.4.102.38241 > 192.168.4.1.domain: 755+ PTR? 105.3.168.192.in-addr.arpa. (44)
09:58:13.313450 IP 192.168.4.1.domain > 192.168.4.102.38241: 755 NXDomain* 0/1/0 (91)
09:58:13.400946 arp who-has 192.168.3.76 tell 192.168.3.11
09:58:13.401028 IP 192.168.4.102.52068 > 192.168.4.1.domain: 3891+ PTR? 76.3.168.192.in-addr.arpa. (43)
09:58:13.401354 IP 192.168.4.1.domain > 192.168.4.102.52068: 3891 NXDomain* 0/1/0 (90)
09:58:13.401410 IP 192.168.4.102.46938 > 192.168.4.1.domain: 52643+ PTR? 11.3.168.192.in-addr.arpa. (43)
09:58:13.401764 IP 192.168.4.1.domain > 192.168.4.102.46938: 52643 NXDomain* 0/1/0 (90)
09:58:13.419504 IP 192.168.4.12.netbios-ns > 192.168.4.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
09:58:13.419589 IP 192.168.4.102.57456 > 192.168.4.1.domain: 54390+ PTR? 12.4.168.192.in-addr.arpa. (43)
09:58:13.419913 IP 192.168.4.1.domain > 192.168.4.102.57456: 54390 NXDomain* 0/1/0 (90)
09:58:13.472443 arp who-has 192.168.3.169 tell 192.168.3.99
09:58:13.472518 IP 192.168.4.102.56024 > 192.168.4.1.domain: 53334+ PTR? 169.3.168.192.in-addr.arpa. (44)
09:58:13.472852 IP 192.168.4.1.domain > 192.168.4.102.56024: 53334 NXDomain* 0/1/0 (91)
09:58:13.472907 IP 192.168.4.102.51156 > 192.168.4.1.domain: 54159+ PTR? 99.3.168.192.in-addr.arpa. (43)
09:58:13.473262 IP 192.168.4.1.domain > 192.168.4.102.51156: 54159 NXDomain* 0/1/0 (90)
09:58:13.560280 IP 192.168.4.15.netbios-ns > 192.168.4.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
09:58:13.560374 IP 192.168.4.102.50605 > 192.168.4.1.domain: 15489+ PTR? 15.4.168.192.in-addr.arpa. (43)
09:58:13.560690 IP 192.168.4.1.domain > 192.168.4.102.50605: 15489 NXDomain* 0/1/0 (90)
09:58:13.613198 arp who-has 192.168.3.47 tell 192.168.3.64
09:58:13.613277 IP 192.168.4.102.42911 > 192.168.4.1.domain: 50
...

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: set alternative router for VE through dhcp
Next Topic: Kernel Panic with Server Dual Quad Xeon E54xx
Goto Forum:
  


Current Time: Thu Aug 08 03:19:16 GMT 2024

Total time taken to generate the page: 0.02705 seconds