Getting error while running linux tests in packetdrill

138 views
Skip to first unread message

Ramana Reddy

unread,
Aug 6, 2015, 1:58:33 AM8/6/15
to packe...@googlegroups.com
Hi all,
I followed the following link https://code.google.com/p/packetdrill/wiki/README
and when I run all the linux tests ( sudo ./run_tests.sh), its throwing the following error:
./blocking/blocking-accept.pkt:11: error handling packet: bad outbound TCP options.
And the same error is throwing in all other cases too.


In addition to that I would like to know how to run our own packetdrill scripts.

Thanks,
Ramana
P.S  : I am using ubuntu 12.04 64-bit version.

Ramana Reddy

unread,
Aug 6, 2015, 4:51:08 AM8/6/15
to packe...@googlegroups.com
The tests are working fine. but one common error is coming for some test cases:

Running ./early_retransmit/er-delayed-2pkt-sack.pkt ...
error: "Invalid argument" setting key "net.ipv4.tcp_early_retrans"
./early_retransmit/er-delayed-2pkt-sack.pkt:27: error executing `sysctl -q net.ipv4.tcp_early_retrans=3` command: non-zero status 255

The tests are not displaying any output. How can I check or test in my system.
How to write our test suites using packetdrill.



Thanks,
Ramana

Neal Cardwell

unread,
Aug 6, 2015, 7:34:59 AM8/6/15
to Ramana Reddy, packe...@googlegroups.com
On Thu, Aug 6, 2015 at 4:51 AM, Ramana Reddy <gtvr...@gmail.com> wrote:
The tests are working fine. but one common error is coming for some test cases:

Running ./early_retransmit/er-delayed-2pkt-sack.pkt ...
error: "Invalid argument" setting key "net.ipv4.tcp_early_retrans"
./early_retransmit/er-delayed-2pkt-sack.pkt:27: error executing `sysctl -q net.ipv4.tcp_early_retrans=3` command: non-zero status 255

It sounds like perhaps your kernel is not recent enough to support the value of 3 for the net.ipv4.tcp_early_retrans sysctl. So I'd suggest trying net.ipv4.tcp_early_retrans=2 instead. 


The tests are not displaying any output. How can I check or test in my system.

You can use the -v option for verbose output. Or you can also run tcpdump to watch the packets, or strace to watch the system calls.
 
How to write our test suites using packetdrill.

Please consult the USENIX ATC and USENIX login papers linked off of the packetdrill home page at:


Hope that helps,
neal

Ramana Reddy

unread,
Aug 6, 2015, 12:16:05 PM8/6/15
to Neal Cardwell, packe...@googlegroups.com
Hi Neal
Thanks for your reply.  I upgraded the kernel version to 3.16 and run the test suites again, but few tests
are throwing the following error:

root@ramanar:~/packetdrill/gtests/net/packetdrill#./packetdrill tests/linux/fast_retransmit/fr-4pkt-sack-linux.pkt
tests/linux/fast_retransmit/fr-4pkt-sack-linux.pkt:25: error handling packet: live packet field ipv4_total_length: expected: 4040 (0xfc8) vs actual: 2040 (0x7f8)
script packet:  0.200761 P. 1001:5001(4000) ack 1
actual packet:  0.200751 . 1001:3001(2000) ack 1 win 457

Regards,
Ramana


Neal Cardwell

unread,
Aug 6, 2015, 12:44:19 PM8/6/15
to Ramana Reddy, packe...@googlegroups.com
On Thu, Aug 6, 2015 at 11:16 AM, Ramana Reddy <gtvr...@gmail.com> wrote:
Hi Neal
Thanks for your reply.  I upgraded the kernel version to 3.16 and run the test suites again, but few tests
are throwing the following error:

root@ramanar:~/packetdrill/gtests/net/packetdrill#./packetdrill tests/linux/fast_retransmit/fr-4pkt-sack-linux.pkt
tests/linux/fast_retransmit/fr-4pkt-sack-linux.pkt:25: error handling packet: live packet field ipv4_total_length: expected: 4040 (0xfc8) vs actual: 2040 (0x7f8)
script packet:  0.200761 P. 1001:5001(4000) ack 1
actual packet:  0.200751 . 1001:3001(2000) ack 1 win 457

Hi,

Please refer to this commit:

https://code.google.com/p/packetdrill/source/detail?r=ea8f2fec724dfc0342dd007eac1c69bc3a2f0067

The tests in the packetdrill distribution were verified to pass on Ubuntu using a Linux 3.11.0-rc4 kernel. Since the behavior of the kernel changes in subtle ways between each release, a single static set of tests will not pass on all versions of the Linux kernel. Unfortunately, our team does not have the cycles to maintain a branch of test cases to match the expected behavior for each Linux release.

neal

Reply all
Reply to author
Forward
0 new messages