Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eddie <stunnel@attglobal.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Still No Connection from iPhone
Date: Fri, 18 Oct 2019 14:16:47 -0700	[thread overview]
Message-ID: <ddf59e13-effa-9001-d5dd-0cae17261970@attglobal.net> (raw)
In-Reply-To: <63b32dcd-ec67-6a71-8780-c7893d1b7cab@attglobal.net>

On 10/14/2019 2:53 PM, Eddie wrote:
> Title says it all.  I'm still unable to connect to my home CentOS 
> server from my iPhone.  A check of the IP shows I'm still routed via 
> AT&T.
>
> On the server, wg shows no connectivity from the client at all and if 
> I temporarily block the port in my firewall it doesn't show any 
> attempt to connect.
>
> I'm running the latest version of wg for iOS (0.0.20191012 (14)) on 
> the latest iPhone iOS (13.1.2).  Logs from iPhone attached.
>

Answering my own post, as I can now connect.

For the Peer section, Allowed IPs is listed as Optional.  A value of 
0.0.0.0/0 enabled the connection, leaving it as Optional doesn't.

After connecting, I couldn't browse the internet.  Entering a value into 
another Optional field appears to fix that:  the Interface DNS servers.

Guess Optional isn't really optional.  :-)

As an aside, for the DNS servers, before you enter a value it shows 
Optional.  If you put in a value and then erase that, the underlying 
text now says:  Strongly recommended.

Cheers.


_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-10-18 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 21:53 Eddie
2019-10-18 21:16 ` Eddie [this message]

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=ddf59e13-effa-9001-d5dd-0cae17261970@attglobal.net \
    --to=stunnel@attglobal.net \
    --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).