Hi Ruchika, On 2015年03月04日 18:46, Ruchika Luthra wrote: > Hello, > > I am trying to understand the working of ARP in the earlier mentioned topology > s1 --------- s2 > l l l l > h1 h2 h3 h4 > > Switch running : Ofsoftswitch13 > Controller Running ./bin/ryu-manager ryu.app.simple_switch_13 > > Now say h1 ping -c2 h4 > At the controller side, I see these logs > > /packet in 1 22:66:d9:ea:c0:25 ff:ff:ff:ff:ff:ff 1/ > /packet in 2 22:66:d9:ea:c0:25 ff:ff:ff:ff:ff:ff 3/ > /packet in 2 5a:1c:4e:38:7b:f5 22:66:d9:ea:c0:25 2/ > /packet in 1 5a:1c:4e:38:7b:f5 22:66:d9:ea:c0:25 3/ > /packet in 1 22:66:d9:ea:c0:25 5a:1c:4e:38:7b:f5 1/ > /packet in 2 22:66:d9:ea:c0:25 5a:1c:4e:38:7b:f5 3/ > /packet in 2 4e:a9:9d:a0:bc:17 33:33:00:00:00:fb 1/ > /packet in 1 4e:a9:9d:a0:bc:17 33:33:00:00:00:fb 3/ > /packet in 2 2a:b6:c4:15:e7:a2 33:33:00:00:00:fb 3/ > /packet in 1 2a:b6:c4:15:e7:a2 33:33:00:00:00:fb 3/ > > FYI: > IP MAC > h1 10.0.0.1 22:66:d9:ea:c0:25 > h2 10.0.0.2 2e:1e:81:dd:65:e8 > h3 10.0.0.3 32:46:9c:bc:0e:c3 > h4 10.0.04 5a:1c:4e:38:7b:f5 > s1-eth1 56:86:fa:2e:28:9e > s1-eth2 7e:99:5e:7a:09:8c > s1-eth3 02:da:16:5c:31:18 > > s2-eth1 4e:a0:9d:a0:bc:17 > s2-eth2 ae:3f:ff:2e:c4:df > s2-eth3 2a:b6:c4:15:e7::a2 > The first line shows that it is ARP request with broadcast MAC received at > the controller. > > My main point of doubt is that: > > 1. Where is the ARP Reply Constructed? > > *CASE 1*: When the MAC Interface binding is already at the control plane? > > *CASE 2:* When the Controller asks the switch to flood the ARP request > through its interface? say the destination host replies, that hey I am the > destination IP and my MAC is this. But the Reply also leads to PACKET_IN to > the controller and it learns the binding. > > Doubt : In case 1, the ARP Reply is constructed at the controller? > In case 2: The ARP Reply is constructed by the destination host? > > Help me know if my understanding is Right in case of Ryu controller?
If you use simple_switch_13.py, the ARP Reply is constructed by the destination host, because simple_switch_13.py acts as a L2 switch. For more infomations about simple_switch_13.py behavior, please refer to the Ryu-Book page. (http://osrg.github.io/ryu-book/en/html/switching_hub.html) Thanks > > > Thank you > -- > Ruchika Luthra > M.E (CS) 4th Sem > BITS Pilani > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
