summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
-rw-r--r--dpibreak.1.in14
-rw-r--r--dpibreak.1.md17
2 files changed, 21 insertions, 10 deletions
diff --git a/dpibreak.1.in b/dpibreak.1.in
index 460c56e..b194f43 100644
--- a/dpibreak.1.in
+++ b/dpibreak.1.in
@@ -201,15 +201,21 @@ file if another instance is already running on the system.
Only for daemon. log goes here.
.SH BUGS
-There are two types of bugs:
+There are three types of bugs:
.RS 4
a. DPIBreak does not work as described in the manual.
.br
b. It works as described but fails to bypass the DPI.
+.br
+c. A site becomes unreachable or misbehaves with DPIBreak running, but
+works when it is stopped.
.RE
-Reporting both cases to the bug tracker helps improve the program.
-For case (b), it would be helpful if you could include information
-such as your region and ISP.
+Reporting all cases to the bug tracker helps improve the program. (a)
+indicates an implementation bug. (b) may motivate new circumvention
+techniques. (c) may be resolved with a site-specific workaround or a
+narrowing flag. For (b) and (c), please include your region, ISP,
+flags in use, and any other network software running (VPN, custom DNS,
+ad-blocker, firewall).
Any other minor improvements or suggestions are also welcome.
.PP
diff --git a/dpibreak.1.md b/dpibreak.1.md
index 7700ee9..a9b2439 100644
--- a/dpibreak.1.md
+++ b/dpibreak.1.md
@@ -158,14 +158,19 @@ Only for daemon. log goes here.
## BUGS
-There are two types of bugs:
+There are three types of bugs:
> a\. DPIBreak does not work as described in the manual.\
-> b. It works as described but fails to bypass the DPI.
-
-Reporting both cases to the bug tracker helps improve the program. For
-case (b), it would be helpful if you could include information such as
-your region and ISP.
+> b. It works as described but fails to bypass the DPI.\
+> c. A site becomes unreachable or misbehaves with DPIBreak running, but
+> works when it is stopped.
+
+Reporting all cases to the bug tracker helps improve the program. (a)
+indicates an implementation bug. (b) may motivate new circumvention
+techniques. (c) may be resolved with a site-specific workaround or a
+narrowing flag. For (b) and (c), please include your region, ISP, flags
+in use, and any other network software running (VPN, custom DNS,
+ad-blocker, firewall).
Any other minor improvements or suggestions are also welcome.