• 是否试过最新的版本 (https://github.com/XX-net/XX-Net/releases )？

• 是否查看过 Wiki (https://github.com/XX-net/XX-Net/wiki )？

• 是否以相关关键词搜索过类似 issues？

• 描述遇到的问题，贴出所有能帮助分析问题的状态页和日志，如包含大量文本时，请上传为 txt 文件：

• 如果问题得到解决，请务必回复相关情况，谢谢。

XX-Net Status:

sys-platform: x86_64, Darwin-18.2.0-x86_64-i386-64bit
os-system: Darwin
os-version: Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018;

It would be a good idea to recommend the Wireguard MacOS app instead of the command line in the usage instructions.

The docs recommend using Azure Cloud Shell.

Azure Cloud Shell has Python 3.5 installed.

You also can't use apt to install packages.

Approximate steps to get around this:

1. Install pyenv
2. Install python 3.6.10: pyenv install 3.6.10
3. Clone algo
4. cd to `./a

How to let server in ubuntu print log?

suggest： Output specific logs when be scanned, record the scanner's IP，use fail2ban ban scanner ip.

Prerequisites

• Did you check the wiki?
• Did you search in issues?
• Are you running the latest version?
• I will write this according to

Right now in different places in the SE codebase there are references to /opt and then as well to /usr.

All SE code should reference one place only. Could someone please create a PR that fixes this.

This PR should also take PR #454 into consideration (no conflicts)

In the text in section 3.3 of the manual it says: Let’s give it tag ID 100

Then in the example, has switched to tag id 10:

  {
    "type": "MATCH_TAGS_DIFFERENCE",
    "not": false,
    "or": false,
    "id": 10,
    "value": 0
  }, 

And following paragraph: difference between tags with tag ID 10 is zero

Looks like a typo and all should either be 10 or 100.

The FAQ suggests https://dnsleaktest.com/ and https://ipleak.net/ to test dns leaks. Do they support IPv6 leaks? I don't have an IPv6 connection to test.

An alternative is https://browserleaks.com/dns that explicitly tests IPv6:

This test attempts to resolve 100 randomly generated domain names asynchronously, 50 with A record (IPv4-only) and 50 with both A and AAAA records (IPv4+IPv6).

I really don't understand why you didn't spend additional 30 min to create a good documentation for such a great project 🙂, some how-to with examples would be really appreciated? Thanks

Right now we emit a message like

T: Error: Unable to find cluster information
T: No current-context set. Please use the --context option to 
T: explicitly set the context.

This is all fine, but some higher-level explanation would be helpful as well, probably linking to documentation:

T: Telepresence uses kubectl/oc to access your Kubernetes/OpenShift
T: cluster. Ple

Following tokio-rs/mio#928.

Generally speaking when changing from level to edge trigger you need to put read/write in a loop, because it could that after a call to read/write another one is ready once the first one is done.

TcpConnection needs to basically call read in a loop here: https://github.com/Genymobile/gnirehtet/blob/2bf8a3cfbe2168031897b8f917c088fe6d4771

https://github.com/pirate/wireguard-docs/blob/master/README.md#dns-2

Currently it is described as if the setting will be somehow pushed/shared with peers. This is not the case. Instead, DNS servers listed in this key will just be populated on the local interface.

Should the Debian install docs mention:

sudo apt-get install apt-transport-https

?

Just hit that myself, and we also had a recent support request about it.

/cc @danderson

After playing around with N2N for quite a bit, I was at first a bit disappointed by the performance - 20 Mbit/s on a gigabit connection? Well, at first I didn't enable AES (after adding -A, I was able to go to 50 Mbit/s), then I checked the CPU, which was at 100% (a 1 CPU instance). Upgraded the node to 2 CPUs, 100 Mbit/s. We're getting there! Now, I used -v to get some more details; I did not

• in linux with xfce and dark background, the icon is barely visible
  
• the GUI should have an option to close and only appear notification icon
  

when ping ping 10.22.22.1 from client there is no ping
and see bellow lines at client
[WARN]recv return -1,errno=No route to host

[root@vosnow ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- a

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

Im scrolling and read i2pd.console and read stuff like:

[trust]
## Enable explicit trust options. false by default
# enabled = true
## Make direct I2P connections only to routers in specified Family.
# family = MyFamily
## Make direct I2P connections only to routers specified here. Comma separated list of base64 identities.
# routers = 
## Should we hide our router from other route