I'm working with a dreadfully old version of nox but just found a problem in how it makes aggregate stats requests. I'm posting it here in case anyone else is working with nox 0.4 with the of1.0 patch OR in case it still exists in more current versions.
Srini, Masa: I found this bug because it really messed up framing with the flowvisor. Shot in the dark, but it might be the culprit that's also been causing CPU issues with our network. Short story: nox was sending a stats request that was well-formed in an openflow sense (the number of bytes sent is the same as the header.length) but the stats request was 4 bytes short: [from wireshark] 0000 01 10 00 34 00 00 00 1a 00 02 00 00 00 0f ff ff 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 ff 00 00 03 This is a 52 byte packet, but a stats request is 12 bytes and an aggregate body is 44, so it should be a 56 byte packet. I'm not brave enough (or have enough free time) to delve into the actual cause... especially since it's such old code, but I thought I would mention it because I know a lot of others are using the same old code. Given that the embedded ofp_match grew by 4 bytes since 0.89, it seems likely some constant didn't get updated with the of1.0 patch. FYI, - Rob . _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
