Hi,
Yes.I am using the same code which you have sent me. It is working fine.
But I don't know how to send messages from the console of one guest
operating system to another. The following is the output of xm list on
the Dom 0 on my Laptop command prompt:
root@roadrunner:/home/flow# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 6776 8 r-----
1954.8
vm2 3 500 1 -b----
5.0
vm3 4 500 1 -b----
4.3
root@roadrunner:/home/flow#
this is my output of brctl show;
root@roadrunner:/home/flow/LINC-Switch# brctl show
bridge name bridge id STP enabled interfaces
br-linc1 8000.feffffffffff no tap-linc-port1
vif3.0
br-linc2 8000.feffffffffff no tap-linc-port2
vif4.0
>From one terminal of Dom 0, the simpleswitch.py is running; In another
terminal LINC switch is running; Then If I try to ping from the terminal of
vm2 to vm3, it is saying unknown host or network unreachable.
the following is my output of ping from one of the terminal on Dom0:
root@roadrunner:/home/flow/LINC-Switch# tcpreplay -i tap-linc-port1
pcap.data/ping.pcap
sending out tap-linc-port1
processing file: pcap.data/ping.pcap
Actual: 1 packets (98 bytes) sent in 0.13 seconds
Rated: 753.8 bps, 0.01 Mbps, 7.69 pps
Statistics for network device: tap-linc-port1
Attempted packets: 1
Successful packets: 1
Failed packets: 0
Retried packets (ENOBUFS): 0
Retried packets (EAGAIN): 0
If I do tcpdump on one of the terminal on Dom0, it is giving the following
output:
root@roadrunner:/home/flow/LINC-Switch# tcpdump -v -i tap-linc-port2
tcpdump: WARNING: tap-linc-port2: no IPv4 address assigned
tcpdump: listening on tap-linc-port2, link-type EN10MB (Ethernet), capture
size 65535 bytes
13:55:54.895702 IP (tos 0xc0, ttl 1, id 0, offset 0, flags [DF], proto IGMP
(2), length 32, options (RA))
0.0.0.0 > all-systems.mcast.net: igmp query v2
13:55:54.895735 IP6 (hlim 1, next-header Options (0) payload length: 32)
fe80::985e:84ff:fec8:4b3e > ip6-allnodes: HBH (rtalert: 0x0000)
(pad1)(pad1)[icmp6 sum ok] ICMP6, multicast listener querymax resp delay:
1000 addr: ::
13:55:55.014927 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:55.014989 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 66)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:55.015057 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:56.016291 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:56.016364 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 66)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:56.016410 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:58.017839 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:58.017915 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 66)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:55:58.017967 IP6 (hlim 255, next-header UDP (17) payload length: 46)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
0.0.0.0.in-addr.arpa. (38)
13:56:00.076467 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:00.076560 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 70)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:00.076619 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:01.077943 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:01.078018 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 70)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:01.078072 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:03.079726 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:03.079809 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 70)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:03.079862 IP6 (hlim 255, next-header UDP (17) payload length: 50)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
251.0.0.224.in-addr.arpa. (42)
13:56:05.092555 IP6 (hlim 255, next-header UDP (17) payload length: 47)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
2.0.0.10.in-addr.arpa. (39)
13:56:05.092615 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 67)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
2.0.0.10.in-addr.arpa. (39)
13:56:05.092652 IP6 (hlim 255, next-header UDP (17) payload length: 47)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
2.0.0.10.in-addr.arpa. (39)
13:56:05.093132 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 91)
roadrunner.local.mdns > 224.0.0.251.mdns: 0*- [0q] 1/0/0
2.0.0.10.in-addr.arpa. (Cache flush) PTR roadrunner.local. (63)
13:56:24.782748 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
00:16:3e:ac:7d:2e (oui Unknown), length 300, xid 0x86d06251, Flags [none]
Client-Ethernet-Address 00:16:3e:ac:7d:2e (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 3: "vm3"
Parameter-Request Option 55, length 13:
Subnet-Mask, BR, Time-Zone, Default-Gateway
Domain-Name, Domain-Name-Server, Option 119, Hostname
Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
NTP
13:56:24.897105 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:24.897181 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 74)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:24.897270 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:25.897729 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:25.897784 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 74)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:25.897820 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:27.695031 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
00:16:3e:ac:7d:2e (oui Unknown), length 300, xid 0x86d06251, secs 3, Flags
[none]
Client-Ethernet-Address 00:16:3e:ac:7d:2e (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 3: "vm3"
Parameter-Request Option 55, length 13:
Subnet-Mask, BR, Time-Zone, Default-Gateway
Domain-Name, Domain-Name-Server, Option 119, Hostname
Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
NTP
13:56:27.897309 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::985e:84ff:fec8:4b3e.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:27.897365 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP
(17), length 74)
roadrunner.local.mdns > 224.0.0.251.mdns: 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:27.897402 IP6 (hlim 255, next-header UDP (17) payload length: 54)
fe80::fcff:ffff:feff:ffff.mdns > ff02::fb.mdns: [udp sum ok] 0 PTR (QM)?
255.255.255.255.in-addr.arpa. (46)
13:56:32.697262 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
00:16:3e:ac:7d:2e (oui Unknown), length 300, xid 0x86d06251, secs 8, Flags
[none]
Client-Ethernet-Address 00:16:3e:ac:7d:2e (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 3: "vm3"
Parameter-Request Option 55, length 13:
Subnet-Mask, BR, Time-Zone, Default-Gateway
Domain-Name, Domain-Name-Server, Option 119, Hostname
Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
NTP
13:56:41.701152 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
UDP (17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
00:16:3e:ac:7d:2e (oui Unknown), length 300, xid 0x86d06251, secs 17, Flags
[none]
Client-Ethernet-Address 00:16:3e:ac:7d:2e (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 3: "vm3"
Parameter-Request Option 55, length 13:
Subnet-Mask, BR, Time-Zone, Default-Gateway
Domain-Name, Domain-Name-Server, Option 119, Hostname
Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
NTP
^C
37 packets captured
37 packets received by filter
0 packets dropped by kernel
My question is how to make use of LINC switch to communic, ate between
virtual machines on the Xen-hypervisor. And how to identify a VM on the
network. If I see the ifconfig on the VM, it is giving IPV6 address, but if
I use it to ping fromanother VM, it is giving "unknown host error".
This is my output from the terminal of vm2 when I tried to ping VM3:
root@vm2:~# ping fe80::216:3eff:feac:7d2e
ping: unknown host fe80::216:3eff:feac:7d2e
root@vm2:~#
Can we able to communicate from the consoles of VMs on Xen or not?
Is communication possible only on the terminals on Dom 0 by using the tap
ports that used to connect with VMs?
Do I need to edit network connection on the dom0?
Sorry to bother you. Could you suggest me some materials to read.
Thanks
Gandhi
On 14 February 2013 03:51, FUJITA Tomonori <fujita.tomon...@lab.ntt.co.jp>wrote:
> On Thu, 14 Feb 2013 02:59:24 -0600
> Gandhimathi Velusamy <mathiy...@gmail.com> wrote:
>
> > It is not throwing any error but when ping from one of the VM to another,
> > How to give the ip address. My doubt is how to assign addresses to VMs
> and
> > use them. If i ping like from vm2 to vm3 by, ping 10.0.0.2 it throws
> error
> > saying ne"twork unreachable" .I made the Testbed setup as per the advise
> of
> > rpt from flowforwarding.org.
>
> I need more detailed info to figure out what's the problem but why not
> using his l2 learning switch code?
>
>
> https://github.com/FlowForwarding/LINC-Switch/blob/master/scripts/ryu/l2_switch_v1_3.py
>
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
