search for: tcp_open

...); > tsopt->tsopt.kind = TCP_OPTION_TS; > tsopt->tsopt.length = sizeof ( tsopt->tsopt ); > tsopt->tsopt.tsval = ntohl ( currticks() ); > tsopt->tsopt.tsecr = ntohl ( tcp->ts_recent ); > } > > (When opening the connection, the TCP_SYN flag is set (from tcp_open() I > guess?).) > > So, the two builds use different TCP stacks on the client side. OK, so I've changed the test with BIOS to use gpxelinux.0 instead (hoping that will match the syslinux.efi case better, did not check details in the source yet) and that does not work either but in a...

Hello, I'm trying to find out how to pxe boot with syslinux.efi on QEMU with OVMF. After getting through the initial hurdle caused by the iPXE based option ROM included with QEMU having a problem as described in these threads: http://www.syslinux.org/archives/2014-November/022804.html http://sourceforge.net/p/edk2/mailman/message/33236100/ I'm now getting further to almost being able

...ION_NOP, sizeof ( tsopt->nop ) ); tsopt->tsopt.kind = TCP_OPTION_TS; tsopt->tsopt.length = sizeof ( tsopt->tsopt ); tsopt->tsopt.tsval = ntohl ( currticks() ); tsopt->tsopt.tsecr = ntohl ( tcp->ts_recent ); } (When opening the connection, the TCP_SYN flag is set (from tcp_open() I guess?).) So, the two builds use different TCP stacks on the client side. (Obviously I have no clue, but this is what I could gather in five minutes.) Laszlo

i''m using the following probe to calculate how many bytes are being written by tcp write calls, by process and total: fbt:ip:tcp_output:entry { this->tcpout_size = msgdsize(args[1]); @tcpout_size[execname] = sum(this->tcpout_size); @tcpout_size["TOTAL_TCP_OUT"] = sum(this->tcpout_size); } I run this probe for N seconds. I suppose that if i get the