Add a couple of tests for sequential ifconfig(8) options, incl. PR kern/41912.

Add also a test that writes random garbage to every ifconfig(8) option that
takes parameters. Based on quick testing, iwn(4) and wm(4) pass, but
urtwn(4) panics. Use at your own risk; in some cases, it may be possible
that horrors are written directly to the hardware.

Add a basic test for enabling/disabling network interface capabilities.

Add test cases for different 802.11 options. These include cases for
PR kern/35045, PR kern/45745, and PR kern/55424.

Test creating thousands of bridge(4)'s. Unlike with tap(4) (PR kern/55417),
this test succeeeds. It is even possible to have the ultimate ifconfig(8)
output with more than 65,000 devices.

Add a test case for kern/52771.

Add test cases for PR kern/53546 and PR kern/55417. Both are skipped as
both reproduce panics.

Add a test case for PR bin/55389.

Add a test for non-critical/low PR bin/43141.

Test creating thousands of bridge(4)'s. Unlike with tap(4) (PR kern/55417),
this test succeeeds. It is even possible to have the ultimate ifconfig(8)
output with more than 65,000 devices.

ifconfig/t_capabilities: s/if_capabilities/if_capenable/ in message

ifconfig/t_capabilities: Skip unless run_unsafe is configured to yes

The test modifies if_capabilities for all available interfaces.
This is not a behavior we expect for normal ATF runs.

Similar tests modifying living network configurations are already
skipped by default. This is the last one remained for ifconfig(8).

Also, I'm not sure whether this is a test for ifconfig(8).

XXX
Pullup to netbsd-10 ASAP. No other branches are affected.

branches: 1.1.6;
Add a basic test for enabling/disabling network interface capabilities.

Move more PR references from comments to ATF's "descr".

Add '-e ignore" to atf-check(1) and remove xfail. Pointed by njoly@.

branches: 1.2.4;
Remove shebang lines from test-script sources; avoids duplicate with
the build process which adds one too.

Add a test for non-critical/low PR bin/43141.

Use the new "run_unsafe" atf_config_get() option also with a couple of other
tests that are known to be unsafe.

Skip these also for Qemu runs as they cause panics. Point to PR kern/55451.

Ups. Fix shell parameter.

Add also a test that writes random garbage to every ifconfig(8) option that
takes parameters. Based on quick testing, iwn(4) and wm(4) pass, but
urtwn(4) panics. Use at your own risk; in some cases, it may be possible
that horrors are written directly to the hardware.

Skip the repeated_link_addr test by default as it causes the
evbarm-aarch64 testbed to hang (PR port-evbarm/55521), and will not be
safe to run by default even after that bug is fixed, for similar
reasons as t_repeated_updown.

Remove the expected timeout; there is something more sinister behind the
timeouts seen on the Qemu/evbarm-aarch64 runs.

Expect a timeout for evbarm-aarch64, as seen in the recent Qemu runs.

Add a couple of tests for sequential ifconfig(8) options, incl. PR kern/41912.

apply this change to a a couple more tests:
---
date: 2020-07-27 09:57:44 -0700; author: gson; state: Exp; lines: +6 -1; commitid: m3HouRBlhyJQVJhC;
Skip the repeated_link_addr test by default as it causes the
evbarm-aarch64 testbed to hang (PR port-evbarm/55521), and will not be
safe to run by default even after that bug is fixed, for similar
reasons as t_repeated_updown.
---

t_repeated_mtu.sh changes the MTU, which may cause NFS to fail.
if you have NFS root, this is system killing.

t_repeated_scan.sh kills and restarts both hostapd and
wpa_supplicant.

Add a couple of tests for sequential ifconfig(8) options, incl. PR kern/41912.

apply this change to a a couple more tests:
---
date: 2020-07-27 09:57:44 -0700; author: gson; state: Exp; lines: +6 -1; commitid: m3HouRBlhyJQVJhC;
Skip the repeated_link_addr test by default as it causes the
evbarm-aarch64 testbed to hang (PR port-evbarm/55521), and will not be
safe to run by default even after that bug is fixed, for similar
reasons as t_repeated_updown.
---

t_repeated_mtu.sh changes the MTU, which may cause NFS to fail.
if you have NFS root, this is system killing.

t_repeated_scan.sh kills and restarts both hostapd and
wpa_supplicant.

Use atf_pass to avoid test failure in case there are no suitable interfaces.

Reference also PR kern/53860.

Require root privileges.

Fix references in comments.

Add a test case for PR bin/55389.

Instead of just skipping interfaces that are "up", skip the whole
repeated_updown test case unless explicitly enabled with "atf-run -v
run_unsafe=yes". Gratuitously configuring interfaces "up" is no more
safe than gratuitously configuring them "down"; for example, it could
lead to accidentally connecting to an insecure network or diverting
traffic from the desired route.

Skip interfaces that are already UP before the test starts. We can
not change state of the test host this way, it breaks e.g. test systems
with the root filesystem on NFS.

Use atf_pass to avoid test failure in case there are no suitable interfaces.

Reference also PR kern/52526.

Add a test case for kern/52771.

Test creating thousands of bridge(4)'s. Unlike with tap(4) (PR kern/55417),
this test succeeeds. It is even possible to have the ultimate ifconfig(8)
output with more than 65,000 devices.

Instead of UINT_MAX + 2, test what is claimed.

Actually create the tap(4) with a negative device number. Doh.

Fix pastos.

Add test cases for PR kern/53546 and PR kern/55417. Both are skipped as
both reproduce panics.

disable these tests unless ATF_SBIN_IFCONFIG_WIFI_ENABLE=yes is
in the environment. they change wifi configuration, restart
wpa_supplicant and hostapd, and, on broken wifi chipsets, may
hang the test run.

Add test cases for different 802.11 options. These include cases for
PR kern/35045, PR kern/45745, and PR kern/55424.