No idea how this has existed in NOX for so long. In coreapps/pyrt/pyglue.cc lines 187 and 204 call htons(). They should be htonl().
-- Murphy On Sep 16, 2011, at 5:36 AM, Partti, Tapio (NSN - FI/Espoo) wrote: > It’s destiny and I tested with the latest updates. I’m on 64 bit machine. > > -Tapio > > From: ext Murphy McCauley [mailto:jam...@nau.edu] > Sent: Friday, September 16, 2011 11:21 AM > To: Partti, Tapio (NSN - FI/Espoo) > Cc: nox-dev@noxrepo.org > Subject: Re: [nox-dev] python flow fetcher request with network address > fields specified > > Which NOX branch are you using? If the answer isn't destiny, please try > again with destiny. > > If you ARE using destiny, are you on a 32 or a 64 bit machine? > > -- Murphy > > On Sep 16, 2011, at 1:11 AM, Partti, Tapio (NSN - FI/Espoo) wrote: > > > Hi, > > I have trouble using the python flow fetcher. I can successfully fetch flows > as long as the request doesn’t contain uint32_t types on fields, i.e. nw_src > or nw_dst. No matter what values I use, only the first two bytes will be > non-zero. For example, if I construct the request like this: > > > Flow_stats_request = {“dpid”: dpid_int, “match”: {“in_port”: inport, > “nw_dst”: ipstr_to_int(“192.168.1.2”), “dl_type”: 0x800}} > > with wireshark I can see flow fetcher sending Stats Request with nw_dst > 1.2.0.0. It would seem that some bit shifting is going on, although I’m not > sure if I’m using the flow fetcher correctly. > > Can someone please tell me how to get it working properly or suggest how I > can fix it if it’s a bug? Thanks. > > -Tapio > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
