Hi Andrea, In flow.cc, the flow struct is defined and that is used to parse the packet-in content. You can get the seq number for tcp_header which is described in packets.h. It should not be hard to parse this, since the packet is parsed for the various headers already.
Regards KK On 11 October 2011 12:07, andrea simeoni <andreasimeon...@gmail.com> wrote: > Hi Murphy, > > thank you for answering. I' ve already checked in /inet++, and I found the > tcp.hh file. > At first hand it seems being not useful for my task. Or maybe it is, by I > don't know how to make it useful :) > I'm right? The file is only few lines of code, so if you have suggestions it > would not take too much time. > > Thank you very much > > > 2011/10/11 Murphy McCauley <jam...@nau.edu> >> >> It's not quite as developed as the Python packet library, but take a look >> in include/netinet++. >> >> -- Murphy >> >> > Hi guys, >> > >> > I'm writing a C++ component that needs to access the TCP sequence number >> > of a packet upon packet-in-event notification. >> > Is there an high level function that simplifies such task? Or I have to >> > take an offset after calling the get_buffer() function from the event? >> > >> > Thank you. >> > -- >> > Andrea Simeoni >> > _______________________________________________ >> > nox-dev mailing list >> > nox-dev@noxrepo.org >> > http://noxrepo.org/mailman/listinfo/nox-dev >> > > > > -- > Andrea Simeoni > > _______________________________________________ > 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
