From: George Philippou <george-marie@hotmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Internet Sharing on macOS
Date: Sun, 6 Jan 2019 19:31:29 +0000 [thread overview]
Message-ID: <HE1P189MB032959BA22692C843131BB028D880@HE1P189MB0329.EURP189.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1446 bytes --]
Hello,
I am a user of the Internet Sharing option in macOS, however I cannot use this feature in conjunction with wireguard. I do not know if this is a known problem, or if it's easily circumvented by some basic knowledge of the way the system and wireguard handle network interfaces. I am sharing a description of my set-up for your consideration.
Since the area I want to cover is too big for just the ISP-provided access point, I connect my laptop (MacBook) to that access point via an ethernet connection through the wall, and I am then able to use my MacBook's WiFi adapter as a secondary access point (this is achieved through System Preferences > Sharing).
However, when I do that, none of the connected devices are able to connect to the internet, unless I disconnect from my VPN on the MacBook first. My intention is to have only one instance of wireguard running on my laptop so that any devices that connect to it as an access point will automatically be covered by the wireguard instance already running.
Note than I am still able to use wireguard on my iPhone in this case, when I connect to the MacBook access point, but this can only be done when I'm not using wireguard on the MacBook itself.
Some tinkering around with ifconfig using various combinations of wireguard and internet sharing can be found here, since it probably includes some hints I'm not seeing: http://ix.io/1xGj
Thanks for your time,
George
[-- Attachment #1.2: Type: text/html, Size: 3226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-01-08 2:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=HE1P189MB032959BA22692C843131BB028D880@HE1P189MB0329.EURP189.PROD.OUTLOOK.COM \
--to=george-marie@hotmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).