Skip to content

Commit

Permalink
rlm_radius: Formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
arr2036 committed Mar 5, 2020
1 parent f95596b commit b701d27
Showing 1 changed file with 17 additions and 17 deletions.
34 changes: 17 additions & 17 deletions src/modules/rlm_radius/test_plan.adoc
Expand Up @@ -126,7 +126,7 @@ Restart the `NAS + Proxy` instance after each test.

Set `replicate = yes` to enable replicate mode.

=== 1.1 Spurious ICMP responses
=== 1.1. Spurious ICMP responses

Platforms:: MacOS, Linux, FreeBSD

Expand All @@ -139,7 +139,7 @@ incoming RADIUS packets.
* Send 50 <<PAP Access-Request>>s
** Verify that no ICMP messages are generated by the operating system when responses are received.

=== 1.2 Base TX packet rate
=== 1.2. Base TX packet rate

Platforms:: MacOS, Linux, FreeBSD

Expand All @@ -165,7 +165,7 @@ When sending datagrams on macOS no native `sendmmsg` function exists, so we expe
** Use the PAP test packet. Verify a packet rate of at least 25,000PPS on MacOS, and 50,000PPS on Linux and FreeBSD.

== 2. Proxy mode
=== 2.1 Entering and exiting zombie state (no status checks)
=== 2.1. Entering and exiting zombie state (no status checks)

Platforms:: Any

Expand Down Expand Up @@ -215,7 +215,7 @@ to it.
** Verify this request is sent on the freshly revived connection
_(active connections, last event was connection connected)_.

=== 2.2 Entering and exiting zombie state (status check - full failure)
=== 2.2. Entering and exiting zombie state (status check - full failure)

Platforms:: Any

Expand Down Expand Up @@ -280,7 +280,7 @@ Immediate entry into zombie state is likely incorrect and will probably change.
* Send a <<PAP Access-Request>>
** Verify this request is sent immediately.

=== 2.3 Entering and exiting zombie state (status check - partial failure and revival)
=== 2.3. Entering and exiting zombie state (status check - partial failure and revival)

Platforms:: Any

Expand Down Expand Up @@ -316,7 +316,7 @@ Immediate entry into zombie state is likely incorrect and will probably change.
* Send a <<PAP Access-Request>>
** Verify this request is sent immediately.

=== 2.4 Synchronous retransmissions
=== 2.4. Synchronous retransmissions

Platforms:: Any

Expand Down Expand Up @@ -360,7 +360,7 @@ i.e. repeat these tests with:
* `replicate = yes`.
* `replicate = no`.

=== 3.1 Well formedness
=== 3.1. Well formedness

Platforms:: Any

Expand All @@ -386,7 +386,7 @@ You will need to use different subrequest types to produce the different packet
** Verify packet is well formed.
** Verify Message-Authenticator attribue is present.

=== 3.2 Outbound packet buffer overrun
=== 3.2. Outbound packet buffer overrun

Platforms:: Any

Expand All @@ -401,7 +401,7 @@ Rationale:: Verify that internal logic deals correctly with packet buffer overru
** Verify the connection is *NOT* reconnected and stays in the `ACTIVE` state.
** Verify the request is not re-queued and rlm_radius returns `fail`.

=== 3.3 SNDBUF exhaustion - single packet
=== 3.3. SNDBUF exhaustion - single packet

Platforms:: MacOS, Linux, FreeBSD

Expand All @@ -420,7 +420,7 @@ outbound requests immediately fail,
_(this is a temporary condition, not a fatal one)_.
** The request is not re-queued and rlm_radius returns `fail`.

=== 3.4 SNDBUF exhaustion - multiple packets
=== 3.4. SNDBUF exhaustion - multiple packets

Platforms:: MacOS, Linux, FreeBSD

Expand All @@ -441,13 +441,13 @@ fail.
** The connection is *NOT* re-established. This is a temporary condition, not a fatal one.
** Requests do not explicitly fail (absence of trunk request `PENDING -> FAILED` transitions).

=== 3.5 EHOSTUNREACH - Unreachable host
=== 3.5. EHOSTUNREACH - Unreachable host

Platforms:: MacOS, Linux, FreeBSD

---

* Configure a destination host on the same subnet as one of the DUT's interfaces.
* Configure a destination host on the same subnet as one of the NAS + Proxy's interfaces.
This host should not exist.
* Send 50 <<PAP Access-Request>>s 0.5 seconds apart (set parallel = 1 and use the delay module).
* ARP resolution failures should result in sendmmsg returning an error code `EHOSTUNREACH`
Expand All @@ -456,13 +456,13 @@ Platforms:: MacOS, Linux, FreeBSD
** Verify that this error results in the connection being re-established.
** Verify that requests are re-queued onto another connection or immediately fail.

=== 3.6 ENETUNREACH - Unreachable network
=== 3.6. ENETUNREACH - Unreachable network

Platforms:: MacOS, Linux, FreeBSD

---

* Configure a destination host on the a different, unreachable subnet as one of the DUT's
* Configure a destination host on the a different, unreachable subnet as one of the NAS + Proxy's
interfaces. You may need to remove the default route for this host, or ensure that the
upstream router sends ICMP Unreachable messages.
* Send 50 <<PAP Access-Request>>s 0.5 seconds apart (set parallel = 1 and use the delay module).
Expand All @@ -471,21 +471,21 @@ Platforms:: MacOS, Linux, FreeBSD
** Verify that this error results in the connection being re-established.
** Verify that requests are re-queued onto another connection or immediately fail.

=== 3.7 ENETDOWN - Network interface down
=== 3.7. ENETDOWN - Network interface down

Platforms:: MacOS, Linux, FreeBSD

---

* Configure a destination host on the same subnet as one of the DUT's interfaces. You may
* Configure a destination host on the same subnet as one of the NAS + Proxy's interfaces. You may
need to remove the default route if there are multiple interfaces.
* Send 50 <<PAP Access-Request>>s 0.5 seconds apart (set parallel = 1 and use the delay module).
* As messages are being sent disable the interface the packets are being set out of.
** Verify that writing fails with `ENETDOWN` or other appropriate error code.
** Verify that this error results in the connection being re-established.
** Verify that requests are re-queued onto another connection or immediately fail.

=== 3.8 Memory usage
=== 3.8. Memory usage

Platforms:: Any

Expand Down

0 comments on commit b701d27

Please sign in to comment.