Thanks for the heads up - anyone can fix it (it's a wiki), but I will also take a look at it today.
On Apr 6, 2013, at 12:17 PM, Eric Chou <eric.cho...@gmail.com> wrote: > Hi, anybody know who to contact to update the OpenFlow Tutorial page? > http://www.openflow.org/wk/index.php/OpenFlow_Tutorial. From history it seems > the Feb 2013 the link for the new VM image was added (with mininet 2.0). But > the new mininet topology is when comes to host links: > > Old: > openflow@openflowtutorial:~$ sudo mn --topo single,3 --mac --switch ovsk > --controller remote > *** Adding links: > (s1, h2) (s1, h3) (s1, h4) > *** > mininet> net > s1 <-> h2-eth0 h3-eth0 h4-eth0 > mininet> > > New: > mininet@mininet-vm:~$ sudo mn --topo single,3 --mac --switch ovsk > --controller remote > *** Adding links: > (h1, s1) (h2, s1) (h3, s1) > *** > mininet> net > c0 > s1 lo: s1-eth1:h1-eth0 s1-eth2:h2-eth0 s1-eth3:h3-eth0 > h1 h1-eth0:s1-eth1 > h2 h2-eth0:s1-eth2 > h3 h3-eth0:s1-eth3 > mininet> > > So in new VM s1 port1 and port2 connects to h1 and h2 instead of h2 and h3. > The dpctl and Ping test section should be updated reflect that if the dpctl > commands stay the same, same applies to xterm for tcpdump. > > I spent about 20 minutes trying to figure out why it was working before and > now it is not, imagine this might be a blocker especially when someone is > just trying to learn the technology. > > Thanks, > > Eric > > > _______________________________________________ > 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
