Summary: I cannot ping between hosts using Opendaylight and Mininet, and would appreciate some advice on what might be the problem.
The setup and what I have done so far: I am stuck on this for two days and cannot find anything about it. I have a Win7 laptop with a VMware 10.0.3 workstation. I installed Ubuntu 12.04 with Opendaylight, and I have Mininet 2.0 running. All network adapters are bridges. I can ping between them. Running Firefox, Putty, and Xming on Win7. I can enter Opendaylight.
Opening the confusion and starting Mininet with: sudo mn --mac --controller = remote, ip = 192.168.0.118, port = 6633 I get a normal network creation response, etc. Ping fails. In Wireshark, I see ARP requests, but no answers. Now the controller shows the switch. Adding a 10.0.0.254/8 gateway causes the controller to see hosts, but still not ping. I still see ARP requests, but no answers. I removed the gateway and installed the threads according to the instructions. No ping.
I tried to do all this from the virtual machines themselves, skipping Putty and the laptop, with the same result. I also tried using Ubuntu 14.04 and Mininet 2.10. The same result. I read the Opendaylight wiki and apparently someone else did not have this problem. This means that I have to miss something basic. I just can’t understand what it is.
EDIT, MININET OUTPUT: (As indicated below)
mininet> s1 ovs-ofctl dump-flows s1
ovs-ofctl: 127.0.0.1 is not a bridge or a socket
mininet> s1 ovs-ofctl dump-flows "s1"
NXST_FLOW reply (xid=0x4):
mininet>
So, the threads created on the controller did not reach Mininet?
Hi, and thanks for your input. I tried to follow your example in the letter, and below is what I get:
Last login: Thu Jul 10 13:56:17 2014
mininet@mininet-vm:~$ sudo mn --mac --controller=remote,ip=192.168.0.115,port=6633
*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2
*** Adding switches:
s1
*** Adding links:
(h1, s1) (h2, s1)
*** Configuring hosts
h1 h2
*** Starting controller
*** Starting 1 switches
s1
*** Starting CLI:
mininet> pingall
*** Ping: testing ping reachability
h1 -> X
h2 -> X
*** Results: 100% dropped (0/2 received)
mininet> s1 ovs-ofctl show "s1"
OFPT_FEATURES_REPLY (xid=0x1): dpid:0000000000000001
n_tables:255, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: OUTPUT SET_VLAN_VID SET_VLAN_PCP STRIP_VLAN SET_DL_SRC SET_DL_DST SET_NW_SRC SET_NW_DST SET_NW_TOS SET_TP_SRC SET_TP_DST ENQUEUE
1(s1-eth1): addr:a6:fc:ac:e6:ab:2a
config: 0
state: 0
current: 10GB-FD COPPER
speed: 10000 Mbps now, 100 Mbps max
2(s1-eth2): addr:2e:8a:70:b0:48:82
config: 0
state: 0
current: 10GB-FD COPPER
speed: 10000 Mbps now, 100 Mbps max
LOCAL(s1): addr:1a:74:aa:bb:5a:49
config: PORT_DOWN
state: LINK_DOWN
speed: 100 Mbps now, 100 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0
mininet>
mininet>
mininet> s1 ovs-ofctl add-flow "s1" priority=1,ip,nw_dst=10.0.0.2,actions=mod_dl_dst:00:00:00:00:00:02,output=2
mininet> s1 ovs-ofctl add-flow "s1" priority=1,ip,nw_dst=10.0.0.1,actions=mod_dl_dst:00:00:00:00:00:01,output=1
mininet>
mininet>
mininet> s1 ovs-ofctl dump-flows "s1"
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=44.765s, table=0, n_packets=0, n_bytes=0, idle_age=44, priority=1,ip,nw_dst=10.0.0.1 actions=mod_dl_dst:00:00:00:00:00:01,output:1
cookie=0x0, duration=71.05s, table=0, n_packets=0, n_bytes=0, idle_age=71, priority=1,ip,nw_dst=10.0.0.2 actions=mod_dl_dst:00:00:00:00:00:02,output:2
mininet>
mininet>
mininet> pingall
*** Ping: testing ping reachability
h1 -> X
h2 -> X
*** Results: 100% dropped (0/2 received)
mininet> h1 ping -c2 h2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable
From 10.0.0.1 icmp_seq=2 Destination Host Unreachable
--- 10.0.0.2 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 999ms
pipe 2
mininet>
I executed the same command as in the above list, I got the same result. Then I ran the command below and here is the output. I did not know that there are two controllers on the output, but the connected one is correct with the correct IP address.
mininet>
mininet> s1 ovs-vsctl list controller
_uuid : 5c50bc34-725b-497c-86f2-e0b8eafc34f9
connection_mode : []
controller_burst_limit: []
controller_rate_limit: []
enable_async_messages: []
external_ids : {}
inactivity_probe : []
is_connected : true
local_gateway : []
local_ip : []
local_netmask : []
max_backoff : 1000
other_config : {}
role : other
status : {sec_since_connect="395", state=ACTIVE}
target : "tcp:192.168.0.115:6633"
_uuid : e5ba6cf2-dd48-4c2b-88b7-4546e90f98d0
connection_mode : []
controller_burst_limit: []
controller_rate_limit: []
enable_async_messages: []
external_ids : {}
inactivity_probe : []
is_connected : false
local_gateway : []
local_ip : []
local_netmask : []
max_backoff : 1000
other_config : {}
role : []
status : {}
target : "ptcp:6634"
mininet>
And I ran the ss command on the controller, and everything showed either "Active" or "Resolved".