Hi, in the words of the tutorial: Most OpenFlow switches can start up with a passive listening port (in your current setup this is 6634)… so the switch actively registers to 6633 and passively listens on 6634. Doesn't need to be 6634.
In the case of multiple switches, such as: sudo mn --topo linear,3 --mac --switch ovsk --controller remote mininet> net c0 s1 lo: s1-eth1:h1-eth0 s1-eth2:s2-eth2 s2 lo: s2-eth1:h2-eth0 s2-eth2:s1-eth2 s2-eth3:s3-eth2 s3 lo: s3-eth1:h3-eth0 s3-eth2:s2-eth3 h1 h1-eth0:s1-eth1 h2 h2-eth0:s2-eth1 h3 h3-eth0:s3-eth1 mininet> The first switch listens on 6634, second on 6635, third on 6636 (I asked this a few days ago and answered by Bob Lantz): mininet> h1 ping -c3 h2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=14.6 ms 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.612 ms 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.049 ms --- 10.0.0.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.049/5.093/14.618/6.739 ms mininet> h1 ping -c3 h3 PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. 64 bytes from 10.0.0.3: icmp_req=1 ttl=64 time=23.3 ms 64 bytes from 10.0.0.3: icmp_req=2 ttl=64 time=0.484 ms 64 bytes from 10.0.0.3: icmp_req=3 ttl=64 time=0.062 ms --- 10.0.0.3 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.062/7.970/23.365/10.887 ms mininet> mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6634 stats_reply (xid=0x331cebd): flags=none type=1(flow) cookie=0, duration_sec=10s, duration_nsec=749000000s, table_id=0, priority=65535, n_packets=3, n_bytes=294, idle_timeout=10,hard_timeout=30,icmp,in_port=1,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.<skip> mininet@mininet-vm:~$ mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6635 stats_reply (xid=0xcf8ab798): flags=none type=1(flow) cookie=0, duration_sec=8s, duration_nsec=108000000s, table_id=0, priority=65535, n_packets=1, n_bytes=42, idle_timeout=10,hard_timeout=30,arp,in_port=2,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.3,nw_proto=2,actions=output:3 cookie=0, duration_sec=8s, duration_nsec=113000000s, table_id=0, priority=65535, n_packets=1, n_bytes=42, idle_timeout=10,hard_timeout=30,arp,in_port=3,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:03,dl_dst=00:00:00:00:00:01,nw_src=10.0.0.3,nw_dst=10.0.0.1,nw_proto=1,actions=output:2 mininet@mininet-vm:~$ mininet@mininet-vm:~$ dpctl dump-flows tcp:127.0.0.1:6636 stats_reply (xid=0x413119ba): flags=none type=1(flow) cookie=0, duration_sec=10s, duration_nsec=105000000s, table_id=0, priority=65535, n_packets=1, n_bytes=42, idle_timeout=10,hard_timeout=30,arp,in_port=2,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:03,nw_src=10.0.0.1,nw_dst=10.0.0.3,nw_proto=2,actions=output:1 cookie=0, duration_sec=10s, duration_nsec=116000000s, table_id=0, priority=65535, n_packets=1, n_bytes=42, idle_timeout=10,hard_timeout=30,arp,in_port=1,dl_vlan=0xffff,dl_vlan_pcp=0x00,dl_src=00:00:00:00:00:03,dl_dst=00:00:00:00:00:01,nw_src=10.0.0.3,nw_dst=10.0.0.1,nw_proto=1,actions=output:2 mininet@mininet-vm:~$ Eric On Apr 22, 2013, at 9:19 PM, Ben Pfaff <b...@nicira.com> wrote: > On Tue, Apr 23, 2013 at 03:37:40AM -0000, Varun Moruse wrote: >> what is significance of port numbers 6633 and 6634? >> what does they mean and do we use them interchangebly???? > > 6633 is generally used for OpenFlow. > I don't know what port 6634 is used for. > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
