FYI: bug logged as https://openflow.stanford.edu/bugs/browse/FLOWVISOR-95
- Rob . On Thu, Jun 23, 2011 at 1:23 PM, Aaron Rosen <aro...@clemson.edu> wrote: > Thanks Rob, > > Your 100% right here. I had the wrong port to output the packet on. > > Thanks, > > Aaron > > On Thu, Jun 23, 2011 at 4:18 PM, Rob Sherwood <rob.sherw...@stanford.edu> > wrote: >> Hi Aaron, >> >> The error message is a little obscure, but my guess is that port 39 >> that you're sending to is not in your slice. The common mistake that >> people make (if they are using HP hardware) is that their controller >> doesn't track ofp_port_status messages that say when a port is no >> longer available and then send to that port anyway. Is this by chance >> your problem? >> >> I'll look into the flowvisor making the error message a little less dumb. >> >> - Rob >> . >> >> >> >> On Thu, Jun 23, 2011 at 10:59 AM, Aaron Rosen <aro...@clemson.edu> wrote: >>> Hello, >>> >>> I'm sending out UDP packets from my controller though I'm getting a >>> packet back from flowvisor saying: >>> >>> Type: request was not understood (1) >>> Code: Permission error (5) >>> >>> The packets source IP address and destination IP address are also in >>> my flowspace so I'm curious why this is occurring. >>> >>> Thanks, >>> >>> Aaron >>> >>> P.S: I've attached the packet with the error message. >>> >>> -- >>> Aaron O. Rosen >>> Masters Student - Network Communication >>> 306B Fluor Daniel >>> >>> _______________________________________________ >>> openflow-discuss mailing list >>> openflow-discuss@lists.stanford.edu >>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >>> >>> >> > > > > -- > Aaron O. Rosen > Masters Student - Network Communication > 306B Fluor Daniel > _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss