Kyriakos Zarifis <kyr.zarifis <at> gmail.com> writes: > > > 1. You probably get the first error because your topology is a loop and the switch is getting a packet for a host H and sees that the port that it thinks it's supposed to send the packet to (learned port) is the same port where it received the packet (inport). > The learned port is the same as the inport because at some point before this error happened, the switch received a packet from host H on that port, and registered the host on that port. > > 2. What kind of data traffic are you sending? > > 3. Associating a flow to a VLAN is just another action, like sending a flow out a port. For the latter, you'd use action OFPAT_OUTPUT. For setting a VLAN to a flow, you use the action OFPAT_SET_VLAN_VID. This is described in section 5.2.4. of the spec > On Mon, Oct 31, 2011 at 7:11 AM, dongxia pan <bartley.pan <at> gmail.com> wrote: > hi, when I execute nox_core with the form: sudo ./nox_core -v -i ptcp:6633 pyswitch monitoring. > > two openvswitches directly link to two physical switches separatly, which don't support openflow protocol. > > controller brings about error and info information,as follows: > > 1. pyswitch | ERR:' ** warning** learned port = inport' > 2.00043 | packet | INFO: (udp parse) warning UDP packet data shorter than UDP len: 94 < 147 > > what causes these results ? is there any one who can give me some hints or reasons? > > another question: how to configure a VLAN using NOX ? > > > _______________________________________________ > nox-dev mailing listnox-dev <at> noxrepo.orghttp://noxrepo.org/mailman/listinfo/nox-dev > > > >
I also met this problem that it reports udp length mismatch. Actually I have not run any traffic between my two VMs. Thanks, Liang _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
