testing: Don't check for exact IKEv1 fragment size

Similar to 7a9c0d51, the exact packet size depends on many factors we don't
want to consider in this test case.
This commit is contained in:
Martin Willi 2015-03-10 10:21:16 +01:00
parent 58c3e09918
commit 2b0f34a2ef

View File

@ -1,7 +1,7 @@
moon::cat /var/log/daemon.log::received FRAGMENTATION vendor ID::YES moon::cat /var/log/daemon.log::received FRAGMENTATION vendor ID::YES
sun::cat /var/log/daemon.log::received FRAGMENTATION vendor ID::YES sun::cat /var/log/daemon.log::received FRAGMENTATION vendor ID::YES
moon::cat /var/log/daemon.log::splitting IKE message with length of 1484 bytes into 2 fragments::YES moon::cat /var/log/daemon.log::splitting IKE message with length of .*bytes into 2 fragments::YES
sun::cat /var/log/daemon.log::splitting IKE message with length of 1388 bytes into 2 fragments::YES sun::cat /var/log/daemon.log::splitting IKE message with length of .*bytes into 2 fragments::YES
moon::cat /var/log/daemon.log::received fragment #1, waiting for complete IKE message::YES moon::cat /var/log/daemon.log::received fragment #1, waiting for complete IKE message::YES
moon::cat /var/log/daemon.log::received fragment #2, reassembling fragmented IKE message::YES moon::cat /var/log/daemon.log::received fragment #2, reassembling fragmented IKE message::YES
sun::cat /var/log/daemon.log::received fragment #1, waiting for complete IKE message::YES sun::cat /var/log/daemon.log::received fragment #1, waiting for complete IKE message::YES