wireguard-apple VS wireguard-tools

I am trying to integrate WireGuard for iOS and macOS in Xcode, the build process is success, but the integration shows error which is attached below,although I had followed the procedures said in Github(https://github.com/WireGuard/wireguard-apple/blob/master/README.md)... I am facing issue while integrating WireGuardKit in Xcode project. Help me to solve this, if anyone had done with it, share your ideas/thoughts as soon as possible... Anyhelp will be appreciated!

The [github repo](https://github.com/WireGuard/wireguard-apple) is a readonly mirror. The [official git repo](https://git.zx2c4.com/wireguard-apple) has no discussion/wiki area that I can see.

I thought so too, but I saw posts like this that made me wonder. I haven't had a chance to look at the source code yet.

I have an MDM and for iOS devices I am able to send configurations (profiles) with Wireguard client data and it is configured automatically. I have followed this: https://github.com/WireGuard/wireguard-apple/blob/master/MOBILECONFIG.md

Okay, I just dove into wireguard‘s source code and it looks like I made wrong assumptions. When I used mullvad or wireguard, it always showed „127.0.0.1“ as the server, however, according to wireguard‘s source, this is just set as a placeholder. I assume that mullvad used this code to implement their app too.

https://github.com/WireGuard/wireguard-apple/blob/13b720442d...

https://ibb.co/x5kwxZW

The most hopeful discussion was this Github project... but., I can't get iOS to accept the .mobileconfig as a legitimate profile. Hoping some of the smart folks here had a solution.

The Apple Wireguard project on Github currently supports both iOS and MacOS natively.

So, I found this guide to create a mobileconfig for WireGuard (https://github.com/WireGuard/wireguard-apple/blob/master/MOBILECONFIG.md) , and I’ve heard a mobileconfig with a managed device can force the phone to make ALL traffic go through vpn (I run a pihole accessible via WireGuard and want to use with that) and my question is how do I setup a managed device for myself for the purpose of total network traffic control?

I'm trying to build the official Wireguard Xcode for iOS, but I get this build error with WireGuardGoBridgeiOS

Oh, this is cool. I'm a huge proponent of CLI tools supporting sensible JSON output, and things like https://github.com/WireGuard/wireguard-tools/blob/master/con... and PowerShell's |ConvertTo-Json are a huge part of my management/monitoring automation efforts.

But, unfortunately, sensible is doing some heavy lifting here and reality is... well, reality. While the output of things like the LSI/Broadcom StorCLI 'suffix the command with J' approach and some of PowerShell's COM-hiding wrappers (which are depressingly common) is technically JSON, the end result is so mindbogglingly complex-slash-useless, that you're quickly forced to revert to 'OK, just run some regexes on the plain-text output' kludges anyway.

Having said that, I'll definitely check this out. If the first example given, parsing dig output, is indeed representative of what this can reliably do, it should be interesting...

> Possible? Maybe. Easy? No. Especially the “testable” part.

a testable shell script? Never seen one.

Thinking about scirpts I've read in the past, I remember seeing Jason Donenfeld's bash script for wireguard-wg and thinking how productive and readable it was,

https://github.com/WireGuard/wireguard-tools/blob/master/src...

I see this when my equipment roams back into my private network and the wireguard server is inside that LAN. It can be solved by NAT'ing packets arriving on your edge router's inside interface, destinated to your outside IP, back to the inside wireguard server IP.

Alternatively if your client is Linux, there is:

https://github.com/WireGuard/wireguard-tools/tree/master/con...

you have a copy here that you can edit: https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-dns/reresolve-dns.sh

You could adapt this script for it. What this one does is re-resolve the domain of the endpoint for when it's a dynamic dns. You run it on a timer from cron, and when your dynamic dns changes it will update the endpoint IP with wg set. You could adapt this script to update your AllowedIPs instead of the endpoint.

I found the GitHub Repository to wireguard-tools however, I cannot read the exact commands required to connect to a certain VPN! I've created a .conf file and was wondering how you could use that with WireGuard-tools to establish a VPN tunnel to my network?