You just want to check the TOS field value of a packet you got from a Python packet_in handler? In that case, all that matters is ipv4.py (from the Python packet parsing library), and I'm pretty sure the TOS field works fine in it.
So if you're seeing packet.next.tos is 0, then... I suspect it is actually 0 on the wire (which is true most of the time...). I'd suggest you use wireshark or tcpdump or something to analyze the traffic. If you can find packets with those that have a nonzero TOS, but they're showing up in NOX as 0, please send a packet trace and your NOX code. -- Murphy On Monday, May 02, 2011 07:46:23 AM false wrote: > Hi, > > My NOX controller version is zaku. > > I recently wanted to know the tos field value, so I print > openflow.OFPFW_NW_TOS and packet.next.tos, but these results were so > strange like the following: openflow.OFPFW_NW_TOS = 2097152 > packet.next.tos=0 > Not only ping, but also ftp service, they were always the same results. > I surveyed nox-dev and tried to fix the problem according this post: > http://www.mail-archive.com/nox-dev@noxrepo.org/msg01708.html > but it's no use, and I found this post: > http://www.mail-archive.com/nox-dev@noxrepo.org/msg01396.html > > So, NW_TOS can not work now? > > Can anybody tell me how to solve this problem? > Any suggest will be helpful. Thank you! > > Yi-Shou _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
