Adam

I think being able to retrieve some basic host networking info (probably just assigned IPs and associated CIDRs for NICs) is reasonable given that that info could be directly relevant...

Got the nicknames stored in the E2EE config file instead; still need to actually test that it works with `status`, and probably still need more changes to make it work...

Got everything working client-side. Let me know if you have any other feedback now.

The provided output doesn't seem to match what you put in your `configure` command. Please retry with the latest release (we just pushed a new one today) and share a...

Wiretap uses the 172.16/16, 172.17/16, 172.18/16, and 172.19/16 subnets internally. Trying to use any IPs from those ranges within your `--routes` probably won't work. Try re-configuring your docker environment to...

Looks like the initial wireguard handshake still isn't completing. When that handshake succeeds you should see a line like "Last Handshake: X seconds ago" under the `interface: wiretap_relay` heading in...

ToC and some cleanup might be good enough. I'll get some additional internal feedback on user preferences before committing to the full Wiki idea. Agreed that would be a good...

@luker983 Can you review the new How it Works section in [this branch](https://github.com/sandialabs/wiretap/tree/readme-updates) and make sure I got it all right? In particular some clarification about how the API address...

Yeah the Details section is probably better off in a Wiki page, I'll move that. > I think we can do both, demonstrate the concepts without compromising accuracy Fair, that...

It's not part of the repo. It's generated when you run the `wiretap configure` command