Yes the problem was coming from that ^^ It is necessary to have the prosmicious mode activated on the Vmware virtual switches. Thank you very much for all your help.
2012/5/22 Julien <[email protected]> > No, no ping unfortunatly. I am using a Vmware EsXi server for created my > topology so for connected my hosts to my openflow switches I use a Vmware > virtual switches, you think the problem can come from that ? > > Because when I ping, I get a "Destination Host unreachable". > > -- > Julien > Envoyé avec Sparrow <http://www.sparrowmailapp.com/?sig> > > Le lundi 21 mai 2012 à 22:58, Murphy McCauley a écrit : > > This doesn't seem to be an error. Is the ping not going through? > > -- Murphy > > On May 21, 2012, at 1:52 AM, Julien Ratinaud wrote: > > Ok thank you. > > So here is the error I get when I use the pyswitch and spanning_tree > components and I try to ping two host : > http://hpics.li/d09742c > > Any idea ? > > 2012/5/20 Julien Ratinaud <[email protected]> > > Hello everybody, > > The problem , if I use only pyswitch I don't get any flows. But I will try > tomorow morning and I will send the error I get with pyswitch. > > Me too I have a loop in my network and like you see I have some problems. > When you tell "add static routing in nox" how are you doing that ? Which > file you are modifying ? Because I have two host and they are not able to > ping. So I don't know how to defined the route into NOX. > > Thank You > > Julien Ratinaud > > 2012/5/20 Qingyun Zuo <[email protected]> > > Hi, recently I used "routing" component in my mininet. I found that when > the topology contained a loop it would lead to routing storm and produce a > mass of packets. That is to say, "routing" don't solve the storm problem? > My real testbed has a loop, I used to add static routing in nox and > manually solve the arp reply packet. But I think that is not good when the > topology becomes large. So can anybody help to solve the routing problem? > > 2012/5/20 <[email protected]> > > > Date: Fri, 18 May 2012 15:07:44 -0700 > From: Murphy McCauley <[email protected]> > To: Julien Ratinaud <[email protected]> > Cc: [email protected] > Subject: Re: [nox-dev] Problem sp_routing > Message-ID: > <CAHC=y9rlbyk+hjm2_17-x+g0gr_cnds_uf0k9tlgcvtqp81...@mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > Can you try with just pyswitch? > > If you look up the error type and code in the spec, I believe it refers to > a buffer ID being wrong. If it happens with pyswitch, looking at the > control traffic in wireshark with the OpenFlow dissector may help to > understand why. > > -- Murphy > On May 18, 2012 2:48 PM, "Julien Ratinaud" <[email protected]> wrote: > > > Thanks for the reply but still same problem if I use only one. > > > > 2012/5/18 Murphy McCauley <[email protected]> > > > >> To start with, pyswitch and routing both do essentially the same job -- > >> forward packets. You only need one or the other. > >> > >> -- Murphy > >> > >> On May 18, 2012, at 7:32 AM, Julien Ratinaud wrote: > >> > >> Hello everybody, > >> > >> I am using NOX in my Openflow network composed of four Openflow switches > >> and four clients, when I ping between them, my ping is not succesfull. > When > >> I launch NOX, I use the component pyswitch, spanning_tree and routing. > On > >> my controller, I get this message : http://hpics.li/802cd61 > >> > >> Someone know where is the problem ? > >> > >> Thank you > >> > >> Best Regards, > >> > >> Julien Ratinaud > >> > >> > >> > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.noxrepo.org/private.cgi/nox-dev-noxrepo.org/attachments/20120518/6df4462b/attachment-0001.htm > > > > ------------------------------ > > _______________________________________________ > nox-dev mailing list > [email protected] > http://lists.noxrepo.org/listinfo.cgi/nox-dev-noxrepo.org > > > End of nox-dev Digest, Vol 3, Issue 18 > ************************************** > > > > > -- > Best Regards > Zuo Qingyun > > > > > >
