Yannis it worked! Thank you a lot! My mistake was that I activated the LANs on the device and I was putting the controller on one of the LANs. Using the WAN works, I have the same behavior as in Mininet when I run the pyswitch from NOX for example. I am very happy now I can start working :)
Best, Diana On Tue, Jun 5, 2012 at 6:46 PM, Yiannis Yiakoumis <yiann...@stanford.edu>wrote: > Hi Diana, > > On Tue, Jun 5, 2012 at 1:20 AM, Diana Marosin <marosin.di...@gmail.com> > wrote: > > Dear all, > > > > I am trying for a while to configure properly a network created by > Linksys > > and TP-Link routers on which I have OpenWrt 0.8 (I believe) and OpenFlow > > 1.0. Can you please go throw my fairly long configuration steps and > clarify > > some issues? > > > > My file /etc/config/openflow looks like this > > > > config 'ofswitch' > > > > option 'dp' 'dp0' > > > > option 'ofports' 'eth0.0 eth0.1 eth0.2 eth0.3' > > > > option 'ofctl' 'tcp:10.92.0.100:6633' > > > > option 'mode' 'inband' > > > > > > > Now, can you explain fairly what is inband and outofband controll and > > suggest which is better for NOX controller? > > > I suggest you start with out-of-band. inband creates some flow entries > to handle control traffic, and that would probably cause more > confusion. I suggest you have outofband, connect your controller to > the wan port, and then two hosts on the local ports. You don't your > own script. OpenFlow will start on its own, and you can > start/stop/restart using /etc/init.d/openflow start/stop/restart etc. > > You can use wireshark in the controller and capture the control > traffic. packet-ins, flow-mods etc would be helpful to understand > what's going on. In case you haven't done already, I encourage you to > walk through the OpenFlow tutorial using Mininet before you start > playing with the AP, it will clarify a lot of things ( > http://www.openflow.org/wk/index.php/OpenFlow_Tutorial ). > > Hope this helps, > Yiannis > > > > > In order to start the openflow protocol I created a separtated script for > > startup in /etc/init.d/ that is bellow > > > > #!/bin/sh /etc/rc.common > > > > START=90 > > > > STOP=90 > > > > boot() { > > > > ofdatapath --detach punix:/var/run/dp0 -d 586D8762F8B1 -i br-lan > > > > ofprotocol unix:/var/run/dp0 tcp:10.92.0.100:6633 --fail=closed > > > > } > > > > > > > > start() { > > > > ofdatapath --detach punix:/var/run/dp0 -d 586D8762F8B1 -i br-lan > > > > ofprotocol unix:/var/run/dp0 tcp:10.92.0.100:6633 --fail=closed > > > > } > > > > > > > > restart() { > > > > stop > > > > start > > > > } > > > > > > I mention that the fail=closed dosen't work, I can still ping my host > even > > if I don't start a controller. > > > > > > I can verify flows installed using wireshark and filtering for FlowMod > or I > > use > > > > dpctl dump-flows unix:/var/run/dp0 > > > > > > Next question that is very important for me is how do I see in whireshark > > the traffic that is by *default* on the switches and the one that passes > by > > the flows I installed. Is there any way to actually see that things go as > > expected? > > > > > > Hope you will reply to me :) Also, maybe I missed some tutorials or > someone > > actually uses real devices and can give me more pointers on how this > works. > > > > > > Thanks a lot!!! > > > > > > Best, > > > > Diana > > > > > > _______________________________________________ > > 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
