Introduce some regress tests against our routing table. At least that way
authorclaudio <claudio@openbsd.org>
Fri, 18 Apr 2014 16:38:28 +0000 (16:38 +0000)
committerclaudio <claudio@openbsd.org>
Fri, 18 Apr 2014 16:38:28 +0000 (16:38 +0000)
commitf42cad18709b8f08e7d0d21ef0c8fe4c4a21fda2
tree0b8b3c81b5156e6f55b9adbfa961f286aed144ce
parenta6f6f5a31d44f7988bc0a8e793c40488ffc9a1bb
Introduce some regress tests against our routing table. At least that way
there is a chance that we do not break the network stack even more.
These regress tests already found a few issues.
The framework is ugly and does not properly recover from failures. Somebody
more skilled can come up with a better solution.
mpi@, blambert@ and sthen@ support this
12 files changed:
regress/sbin/route/Makefile
regress/sbin/route/rttest1.ok [new file with mode: 0644]
regress/sbin/route/rttest10.ok [new file with mode: 0644]
regress/sbin/route/rttest11.ok [new file with mode: 0644]
regress/sbin/route/rttest2.ok [new file with mode: 0644]
regress/sbin/route/rttest3.ok [new file with mode: 0644]
regress/sbin/route/rttest4.ok [new file with mode: 0644]
regress/sbin/route/rttest5.ok [new file with mode: 0644]
regress/sbin/route/rttest6.ok [new file with mode: 0644]
regress/sbin/route/rttest7.ok [new file with mode: 0644]
regress/sbin/route/rttest8.ok [new file with mode: 0644]
regress/sbin/route/rttest9.ok [new file with mode: 0644]