/freebsd/tests/sys/netinet6/frag6/ |
H A D | frag6_01.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_08.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_09.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_15.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_02.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_04.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_05.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_06.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_10.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_11.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_12.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_13.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_16.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_07.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_14.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_03.sh | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_07.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_08.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_10.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_14.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_05.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_13.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|
H A D | frag6_03.py | diff 4527b28baf0d6ca9e78eefd821b2c95181cd61e8 Thu Oct 24 22:08:33 CEST 2019 Bjoern A. Zeeb <bz@FreeBSD.org> frag6 test cases: check more counters, wait for expiry
When done with tests check that both the per-VNET and the global-fragmented- packets-in-system counters are zero to make sure we do not leak counters or queue entries.
This implies that for all test cases we either have to check for the ICMPv6 packet sent in case of TLL=0 expiry (if it is sent) or sleep at least long enough for the TTL to expire for all packets (e.g., fragments where we do not have the off=0 packet).
This also means that statistics are now updated to include all the expired packets.
There are cases when we do not check for counters to be zero and this is when testing VNET teardown to behave properly and not panic, when we are intentionally leaving fragments in the system.
MFC after: 3 weeks Sponsored by: Netflix
|