-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script generates invalid key? #497
Comments
That's pretty weird, as you're the first to report this kind of issue, I would assume an issue with your setup. What OS is running on the host you're running the script on? Could you post the generated config? |
So it doesn't appear to be complete. My guess is the script doesn't check if the installation succeeded and just blindly executes commands
|
I got the script to populate the config file correctly by uninstalling then reinstalling. I think the install failed and the script doesn't check for that. Anyway, the Mac client is now "Active" but there is no connection. The script prompted for a "public" interface and I entered the one I use to connect to the virtual network, i.e. the interface I use to ssh to the VM from the Mac guest: eth0. I presume that was correct |
This script blindly executes commands without checking for errors or even providing any output to debug issues. wg is executed blindly, for example. |
Hello. Short version: I ran your script, it generated a .conf file, but I cannot use this with my mac wireguard client:
I'm not sure how to proceed from here.
Long version: I'm attempting to use wireguard to get around a mysterious bug that disallows routing between my VM and host (Macbook M2 host, Linux arm guest as the router). With previous versions of everything I could do this via ip masquerade which was ideal as it was fast and hardly used any CPU (no encryption, no tunneling, etc.) Now, due to a bug that neither Apple nor Parallels want to admit exists let alone address, this nice solution no longer works. I can get other VMs to use the linux router, but not the host OS.
Anyway, my current hald-assed solution is to use ssh tunneling which hardly works and also has the side effect of bypassing my (mac-side) firewall. Not good even under ideal conditions. I tried wireguard as an alternative to see if it would work any better but got the above error.
The text was updated successfully, but these errors were encountered: