I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.

What's the issue?
Overwritten test scenario, can be summarized and link to payload lists from other repos

How do we solve it?
Chop down the content to the required and needed information, link to payload lists instead of enumerating all possible usernames and passwords, provide further guidance on how to test.

If no one is up to handle it, I can take care of it

So I took a shot at trying to get this to work with IP V6 addresses with no luck. If I disable the ufw service i'm able to access my site using the V6 address, but when I enable ufw the connection times out. I found /etc/ufw/after6.rules and tried to modify it to work, but I must be doing something wrong. My guess is it's something with the V6 subnet.

# BEGIN UFW AND DOCKER
*filter
:ufw6-u

There are lots of other common development ports that we should check for, including (but not limited to):

• 5000 (Flask and Kestrel's default port)
• 9200 (Elasticsearch's REST API)