Fwiw, the lldp packets are "malformed" because flowvisor is sourcing them not 100% according to spec. It's not that the network is trashing them somehow.
I agree with Nick that the problem is elsewhere: if you can capture the of error message, it will have the openflow message that *caused* the problem embedded into it. - Rob . On Tue, Sep 6, 2011 at 1:00 PM, ibrahim mun <[email protected]> wrote: > Thanks Nick, I agree it doesn't seem a FV problem, but the lldp packets > are suspicious. However I updated to the last version but didn't see the > patch, I'll try it and if doesn't work I'll try to figure out the core > difference between pyswitch ans switch in the nox_dev maillist! > > ________________________________ > Date: Tue, 6 Sep 2011 15:47:02 -0400 > Subject: Re: [openflow-discuss] FlowVisor and pyswitch > From: [email protected] > To: [email protected] > CC: [email protected] > > On Tue, Sep 6, 2011 at 15:35, ibrahim mun <[email protected]> wrote: > > I'm using FlowVisor 8.1 and Nox zaku. > when I use nox with switch component every thing go perfect, but for the > same network, when I use pyswitch it doesn't work! > I receive error type=3, code=2 a (permission error) and on wireshark I see > malformed lldp packets. > > There are some malformed LLDP packets on the flowvisor side: > https://openflow.stanford.edu/bugs/browse/FLOWVISOR-131 > (There's a patch attached to that bug if you really need it today) > Although I'm not convinced they're the source of the problems you're having. > -- > Nick > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
