CDRouter Support

CDRouter Security Test Summaries (Full)

test-summary version 13.3

Test Case Descriptions

  • Modules: 6
  • Test Cases: 78

Below is a full description of the testcases in each module


internet-schedule.tcl

Internet schedule parental controls tests

Test Module Name Synopsis
Verify internet access schedule for Sunday internet-schedule.tcl internet_schedule_sunday Verify internet access schedule for Sunday


    step 1. Set NTP start time to the start of the next Sunday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Sunday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Sunday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Sunday internet access schedule is defined
    by the testvars internetScheduleSundayMode and
    internetScheduleSundayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Monday internet-schedule.tcl internet_schedule_monday Verify internet access schedule for Monday


    step 1. Set NTP start time to the start of the next Monday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Monday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Monday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Monday internet access schedule is defined
    by the testvars internetScheduleMondayMode and
    internetScheduleMondayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Tuesday internet-schedule.tcl internet_schedule_tuesday Verify internet access schedule for Tuesday


    step 1. Set NTP start time to the start of the next Tuesday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Tuesday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Tuesday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Tuesday internet access schedule is defined
    by the testvars internetScheduleTuesdayMode and
    internetScheduleTuesdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Wednesday internet-schedule.tcl internet_schedule_wednesday Verify internet access schedule for Wednesday


    step 1. Set NTP start time to the start of the next Wednesday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Wednesday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Wednesday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Wednesday internet access schedule is defined
    by the testvars internetScheduleWednesdayMode and
    internetScheduleWednesdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Thursday internet-schedule.tcl internet_schedule_thursday Verify internet access schedule for Thursday


    step 1. Set NTP start time to the start of the next Thursday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Thursday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Thursday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Thursday internet access schedule is defined
    by the testvars internetScheduleThursdayMode and
    internetScheduleThursdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Friday internet-schedule.tcl internet_schedule_friday Verify internet access schedule for Friday


    step 1. Set NTP start time to the start of the next Friday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Friday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Friday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Friday internet access schedule is defined
    by the testvars internetScheduleFridayMode and
    internetScheduleFridayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Saturday internet-schedule.tcl internet_schedule_saturday Verify internet access schedule for Saturday


    step 1. Set NTP start time to the start of the next Saturday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Saturday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Saturday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Saturday internet access schedule is defined
    by the testvars internetScheduleSaturdayMode and
    internetScheduleSaturdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.



internet-schedule-v6.tcl

Internet schedule parental controls tests (IPv6)

Test Module Name Synopsis
Verify internet access schedule for Sunday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_sunday Verify internet access schedule for Sunday (IPv6)


    step 1. Set NTP start time to the start of the next Sunday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Sunday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Sunday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Sunday internet access schedule is defined
    by the testvars internetScheduleSundayMode and
    internetScheduleSundayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Monday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_monday Verify internet access schedule for Monday (IPv6)


    step 1. Set NTP start time to the start of the next Monday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Monday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Monday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Monday internet access schedule is defined
    by the testvars internetScheduleMondayMode and
    internetScheduleMondayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Tuesday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_tuesday Verify internet access schedule for Tuesday (IPv6)


    step 1. Set NTP start time to the start of the next Tuesday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Tuesday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Tuesday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Tuesday internet access schedule is defined
    by the testvars internetScheduleTuesdayMode and
    internetScheduleTuesdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Wednesday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_wednesday Verify internet access schedule for Wednesday (IPv6)


    step 1. Set NTP start time to the start of the next Wednesday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Wednesday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Wednesday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Wednesday internet access schedule is defined
    by the testvars internetScheduleWednesdayMode and
    internetScheduleWednesdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Thursday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_thursday Verify internet access schedule for Thursday (IPv6)


    step 1. Set NTP start time to the start of the next Thursday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Thursday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Thursday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Thursday internet access schedule is defined
    by the testvars internetScheduleThursdayMode and
    internetScheduleThursdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Friday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_friday Verify internet access schedule for Friday (IPv6)


    step 1. Set NTP start time to the start of the next Friday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Friday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Friday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Friday internet access schedule is defined
    by the testvars internetScheduleFridayMode and
    internetScheduleFridayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.


Test Module Name Synopsis
Verify internet access schedule for Saturday (IPv6) internet-schedule-v6.tcl ipv6_internet_schedule_saturday Verify internet access schedule for Saturday (IPv6)


    step 1. Set NTP start time to the start of the next Saturday

    step 2. Restart DUT to force NTP request

    step 3. Send an HTTP GET request over IPv6 from the LAN client to
            a remote host on the internet

    step 4. Verify that the HTTP request succeeds or fails as expected
            based on the LAN client's Saturday internet access schedule

    step 5. Repeat steps 3 and 4 using HTTPS over IPv6

    step 6. Repeat steps 1 through 5, advancing the NTP start time set
            in step 1 to test the LAN client's internet access at
            various points throughout the day

    NOTE: The base time used to calculate the next Saturday in the first
    iteration of step 1 is defined by the testvar
    internetScheduleBase.  The time zone configured on the DUT must
    match that defined by the testvar internetScheduleTimeZone.

    NOTE: The LAN client's Saturday internet access schedule is defined
    by the testvars internetScheduleSaturdayMode and
    internetScheduleSaturdayTimes.

    NOTE: This test allows the DUT to prevent a LAN client's internet
    access by filtering the DNS query for the remote host, by
    preventing establishment of the TCP connection, by using a proxy
    to return a non-200 HTTP status code or by using a proxy to return
    a 200 HTTP status code with alternate web page text indicating
    that the page was administratively blocked.  The testvar
    internetScheduleBlockedText should be configured with a portion of
    the expected text returned when a page is blocked by the DUT.

    NOTE: If the testvar cpeRebootMode is set to "skip", this test
    will not be run.  If the testvar cpeRebootMode is set to "reboot",
    the CPE will be restarted during the test, either using the
    testvar RestartDut or by prompting the user.



nmap.tcl

Nmap based IPv4 portscan tests from the LAN side of the device

Test Module Name Synopsis
Nmap IPv4 TCP Connect scan nmap.tcl v4_lan_tcp_connect_info Nmap IPv4 TCP Connect scan


    step 1. Initiate a Nmap IPv4 TCP Connect scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Syn scan nmap.tcl v4_lan_tcp_syn_info Nmap IPv4 TCP Syn scan


    step 1. Initiate a Nmap IPv4 TCP Syn scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Fin scan nmap.tcl v4_lan_tcp_fin_info Nmap IPv4 TCP Fin scan


    step 1. Initiate a Nmap IPv4 TCP Fin scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Null scan nmap.tcl v4_lan_tcp_null_info Nmap IPv4 TCP Null scan


    step 1. Initiate a Nmap IPv4 TCP Null scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP XMAS scan nmap.tcl v4_lan_tcp_xmas_info Nmap IPv4 TCP XMAS scan


    step 1. Initiate a Nmap IPv4 TCP XMAS scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP PSH scan nmap.tcl v4_lan_tcp_psh_info Nmap IPv4 TCP PSH scan


    step 1. Initiate a Nmap IPv4 TCP PSH scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP URG scan nmap.tcl v4_lan_tcp_urg_info Nmap IPv4 TCP URG scan


    step 1. Initiate a Nmap IPv4 TCP URG scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP FIN+URG scan nmap.tcl v4_lan_tcp_finurg_info Nmap IPv4 TCP FIN+URG scan


    step 1. Initiate a Nmap IPv4 TCP FIN+URG scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP FIN+PSH scan nmap.tcl v4_lan_tcp_finpsh_info Nmap IPv4 TCP FIN+PSH scan


    step 1. Initiate a Nmap IPv4 TCP FIN+PSH scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Maimon scan nmap.tcl v4_lan_tcp_maimon_info Nmap IPv4 TCP Maimon scan


    step 1. Initiate a Nmap IPv4 TCP Maimon scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP ACK scan nmap.tcl v4_lan_tcp_ack_info Nmap IPv4 TCP ACK scan


    step 1. Initiate a Nmap IPv4 TCP ACK scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 UDP scan nmap.tcl v4_lan_udp_info Nmap IPv4 UDP scan


    step 1. Initiate a Nmap IPv4 UDP scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 SCTP Init scan nmap.tcl v4_lan_sctp_init_info Nmap IPv4 SCTP Init scan


    step 1. Initiate a Nmap IPv4 SCTP Init scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 SCTP Cookie scan nmap.tcl v4_lan_sctp_cookie_info Nmap IPv4 SCTP Cookie scan


    step 1. Initiate a Nmap IPv4 SCTP Cookie scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 OS Detection from LAN side of device nmap.tcl v4_lan_os_detection Nmap IPv4 OS Detection from LAN side of device


    step 1. Initiate a Nmap IPv4 scan for OS detection from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 OS Detection with version detection from LAN side of device nmap.tcl v4_lan_os_detection_version Nmap IPv4 OS Detection with version detection from LAN side of device


    step 1. Initiate a Nmap IPv4 scan for OS detection with version detection from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html


nmap-wan.tcl

Nmap based IPv4 portscan tests from the WAN side of the device

Test Module Name Synopsis
Nmap IPv4 TCP Connect scan nmap-wan.tcl v4_wan_tcp_connect_info Nmap IPv4 TCP Connect scan


    step 1. Initiate a Nmap IPv4 TCP Connect scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Syn scan nmap-wan.tcl v4_wan_tcp_syn_info Nmap IPv4 TCP Syn scan


    step 1. Initiate a Nmap IPv4 TCP Syn scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Fin scan nmap-wan.tcl v4_wan_tcp_fin_info Nmap IPv4 TCP Fin scan


    step 1. Initiate a Nmap IPv4 TCP Fin scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Null scan nmap-wan.tcl v4_wan_tcp_null_info Nmap IPv4 TCP Null scan


    step 1. Initiate a Nmap IPv4 TCP Null scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP XMAS scan nmap-wan.tcl v4_wan_tcp_xmas_info Nmap IPv4 TCP XMAS scan


    step 1. Initiate a Nmap IPv4 TCP XMAS scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP PSH scan nmap-wan.tcl v4_wan_tcp_psh_info Nmap IPv4 TCP PSH scan


    step 1. Initiate a Nmap IPv4 TCP PSH scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP URG scan nmap-wan.tcl v4_wan_tcp_urg_info Nmap IPv4 TCP URG scan


    step 1. Initiate a Nmap IPv4 TCP URG scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP FIN+URG scan nmap-wan.tcl v4_wan_tcp_finurg_info Nmap IPv4 TCP FIN+URG scan


    step 1. Initiate a Nmap IPv4 TCP FIN+URG scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP FIN+PSH scan nmap-wan.tcl v4_wan_tcp_finpsh_info Nmap IPv4 TCP FIN+PSH scan


    step 1. Initiate a Nmap IPv4 TCP FIN+PSH scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP Maimon scan nmap-wan.tcl v4_wan_tcp_maimon_info Nmap IPv4 TCP Maimon scan


    step 1. Initiate a Nmap IPv4 TCP Maimon scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 TCP ACK scan nmap-wan.tcl v4_wan_tcp_ack_info Nmap IPv4 TCP ACK scan


    step 1. Initiate a Nmap IPv4 TCP ACK scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 UDP scan nmap-wan.tcl v4_wan_udp_info Nmap IPv4 UDP scan


    step 1. Initiate a Nmap IPv4 UDP scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 SCTP Init scan nmap-wan.tcl v4_wan_sctp_init_info Nmap IPv4 SCTP Init scan


    step 1. Initiate a Nmap IPv4 SCTP Init scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 SCTP Cookie scan nmap-wan.tcl v4_wan_sctp_cookie_info Nmap IPv4 SCTP Cookie scan


    step 1. Initiate a Nmap IPv4 SCTP Cookie scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 OS Detection from WAN side of device nmap-wan.tcl v4_wan_os_detection Nmap IPv4 OS Detection from WAN side of device


    step 1. Initiate a Nmap IPv4 scan for OS detection from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv4 OS Detection with version detection from WAN side of device nmap-wan.tcl v4_wan_os_detection_version Nmap IPv4 OS Detection with version detection from WAN side of device


    step 1. Initiate a Nmap IPv4 scan for OS detection with version detection from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html


nmap-v6.tcl

Nmap based IPv6 portscan tests from the LAN side of the device

Test Module Name Synopsis
Nmap IPv6 TCP Connect scan nmap-v6.tcl v6_lan_tcp_connect_info Nmap IPv6 TCP Connect scan


    step 1. Initiate a Nmap IPv6 TCP Connect scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Syn scan nmap-v6.tcl v6_lan_tcp_syn_info Nmap IPv6 TCP Syn scan


    step 1. Initiate a Nmap IPv6 TCP Syn scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Fin scan nmap-v6.tcl v6_lan_tcp_fin_info Nmap IPv6 TCP Fin scan


    step 1. Initiate a Nmap IPv6 TCP Fin scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Null scan nmap-v6.tcl v6_lan_tcp_null_info Nmap IPv6 TCP Null scan


    step 1. Initiate a Nmap IPv6 TCP Null scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP XMAS scan nmap-v6.tcl v6_lan_tcp_xmas_info Nmap IPv6 TCP XMAS scan


    step 1. Initiate a Nmap IPv6 TCP XMAS scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP PSH scan nmap-v6.tcl v6_lan_tcp_psh_info Nmap IPv6 TCP PSH scan


    step 1. Initiate a Nmap IPv6 TCP PSH scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP URG scan nmap-v6.tcl v6_lan_tcp_urg_info Nmap IPv6 TCP URG scan


    step 1. Initiate a Nmap IPv6 TCP URG scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP FIN+URG scan nmap-v6.tcl v6_lan_tcp_finurg_info Nmap IPv6 TCP FIN+URG scan


    step 1. Initiate a Nmap IPv6 TCP FIN+URG scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP FIN+PSH scan nmap-v6.tcl v6_lan_tcp_finpsh_info Nmap IPv6 TCP FIN+PSH scan


    step 1. Initiate a Nmap IPv6 TCP FIN+PSH scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Maimon scan nmap-v6.tcl v6_lan_tcp_maimon_info Nmap IPv6 TCP Maimon scan


    step 1. Initiate a Nmap IPv6 TCP Maimon scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP ACK scan nmap-v6.tcl v6_lan_tcp_ack_info Nmap IPv6 TCP ACK scan


    step 1. Initiate a Nmap IPv6 TCP ACK scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 UDP scan nmap-v6.tcl v6_lan_udp_info Nmap IPv6 UDP scan


    step 1. Initiate a Nmap IPv6 UDP scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 SCTP Init scan nmap-v6.tcl v6_lan_sctp_init_info Nmap IPv6 SCTP Init scan


    step 1. Initiate a Nmap IPv6 SCTP Init scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 SCTP Cookie scan nmap-v6.tcl v6_lan_sctp_cookie_info Nmap IPv6 SCTP Cookie scan


    step 1. Initiate a Nmap IPv6 SCTP Cookie scan from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 OS Detection from LAN side of device nmap-v6.tcl v6_lan_os_detection Nmap IPv6 OS Detection from LAN side of device


    step 1. Initiate a Nmap IPv6 scan for OS detection from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 OS Detection with version detection from LAN side of device nmap-v6.tcl v6_lan_os_detection_version Nmap IPv6 OS Detection with version detection from LAN side of device


    step 1. Initiate a Nmap IPv6 scan for OS detection with version detection from the LAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html


nmap-wan-v6.tcl

Nmap based IPv6 portscan tests from the WAN side of the device

Test Module Name Synopsis
Nmap IPv6 TCP Connect scan nmap-wan-v6.tcl v6_wan_tcp_connect_info Nmap IPv6 TCP Connect scan


    step 1. Initiate a Nmap IPv6 TCP Connect scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Syn scan nmap-wan-v6.tcl v6_wan_tcp_syn_info Nmap IPv6 TCP Syn scan


    step 1. Initiate a Nmap IPv6 TCP Syn scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Fin scan nmap-wan-v6.tcl v6_wan_tcp_fin_info Nmap IPv6 TCP Fin scan


    step 1. Initiate a Nmap IPv6 TCP Fin scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Null scan nmap-wan-v6.tcl v6_wan_tcp_null_info Nmap IPv6 TCP Null scan


    step 1. Initiate a Nmap IPv6 TCP Null scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP XMAS scan nmap-wan-v6.tcl v6_wan_tcp_xmas_info Nmap IPv6 TCP XMAS scan


    step 1. Initiate a Nmap IPv6 TCP XMAS scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP PSH scan nmap-wan-v6.tcl v6_wan_tcp_psh_info Nmap IPv6 TCP PSH scan


    step 1. Initiate a Nmap IPv6 TCP PSH scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP URG scan nmap-wan-v6.tcl v6_wan_tcp_urg_info Nmap IPv6 TCP URG scan


    step 1. Initiate a Nmap IPv6 TCP URG scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP FIN+URG scan nmap-wan-v6.tcl v6_wan_tcp_finurg_info Nmap IPv6 TCP FIN+URG scan


    step 1. Initiate a Nmap IPv6 TCP FIN+URG scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP FIN+PSH scan nmap-wan-v6.tcl v6_wan_tcp_finpsh_info Nmap IPv6 TCP FIN+PSH scan


    step 1. Initiate a Nmap IPv6 TCP FIN+PSH scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP Maimon scan nmap-wan-v6.tcl v6_wan_tcp_maimon_info Nmap IPv6 TCP Maimon scan


    step 1. Initiate a Nmap IPv6 TCP Maimon scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 TCP ACK scan nmap-wan-v6.tcl v6_wan_tcp_ack_info Nmap IPv6 TCP ACK scan


    step 1. Initiate a Nmap IPv6 TCP ACK scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 UDP scan nmap-wan-v6.tcl v6_wan_udp_info Nmap IPv6 UDP scan


    step 1. Initiate a Nmap IPv6 UDP scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 SCTP Init scan nmap-wan-v6.tcl v6_wan_sctp_init_info Nmap IPv6 SCTP Init scan


    step 1. Initiate a Nmap IPv6 SCTP Init scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 SCTP Cookie scan nmap-wan-v6.tcl v6_wan_sctp_cookie_info Nmap IPv6 SCTP Cookie scan


    step 1. Initiate a Nmap IPv6 SCTP Cookie scan from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 OS Detection from WAN side of device nmap-wan-v6.tcl v6_wan_os_detection Nmap IPv6 OS Detection from WAN side of device


    step 1. Initiate a Nmap IPv6 scan for OS detection from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Test Module Name Synopsis
Nmap IPv6 OS Detection with version detection from WAN side of device nmap-wan-v6.tcl v6_wan_os_detection_version Nmap IPv6 OS Detection with version detection from WAN side of device


    step 1. Initiate a Nmap IPv6 scan for OS detection with version detection from the WAN
    step 2. Display the final Nmap report

    References:

    Nmap Network Scanning "The Official Nmap Project Guide to Network Discovery and Security Scanning"

    https://nmap.org/book/toc.html

Contents

×

About CDRouter

QA Cafe CDRouter is a comprehensive and powerful test automation solution focused on feature, security, and performance testing for broadband and enterprise edge gateways, Wi-Fi and mesh systems, and other CPE.

Get in touch via our Contact page or by following us on your favorite service: