Is the version of POX you're using more than two years old? I think more recent versions are unlikely to have this happen.
If your POX is old, you could update it (in which case, you'd probably want to run my fork of ripl/riplpox), or you could make the relevant change in your local POX (I think it was a change to HELLO message processing in of_01.py in early 2013). Another way to fix this would be to configure OVS to use OpenFlow 1.0 only. This should be something like... ovs-vsctl set bridge br0 protocols=openflow10 Except instead of br0, you'll want to do it for every switch that Mininet creates. There may be an easy way to get Mininet to do this, but I don't know it off the top of my head; you might try the Mininet list. Or maybe there's a way to make it the default for OVS; I don't know a way to do that off the top of my head either; you might try the OVS list. -- Murphy On Apr 16, 2015, at 12:32 AM, david jhon <djhon9...@gmail.com> wrote: > Hi everyone, > > I am working with openvswitch 2.3.90 and made some changes in vswitch code. I > am trying to use ripl and riplpox along with the pox controller but pox > throws this error: > > WARNING:openflow.of_01:Bad OpenFlow version (4) on connection [Con 19/None] > INFO:openflow.of_01:[Con 19/None] closing connection > > and does not process any packets. I am building and running ovs by compiling > from its source available at its git repository. > > P.S. I am using following command to start the topology: sudo mn --custom > ~/ripl/ripl/mn.py --topo ft,4 --controller=remote --mac > > and ~/pox/pox.py riplpox.riplpox --topo=ft,4 --routing=hashed --mode=reactive > to start the controller. > > It seems POX does not support 2.3.90 version of openvswitch or what else? Pls > let me know if there exist a work around for this. Many thanks! > > Regards, > Jhon > >
