From: zhengmian hu <huzhengmian@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wrong route on macOS
Date: Thu, 8 Jul 2021 00:52:50 -0400 [thread overview]
Message-ID: <CAAntei-TBN5VUpnHLNExgg_4V80zU+PMAHcjVOqfmDbeJ3G1aA@mail.gmail.com> (raw)
I expect no data to be sent to the server when I only visit the local
address. However, this is not true for wireguard on macOS.
Detailed setup:
App:
Downloaded from app store. App version: 1.0.13 (24), Go backend
version: f9b48a96.
Server:
```
[Interface]
Address = 10.110.210.1/24
SaveConfig = true
ListenPort = 51820
PrivateKey = xxxxSERVER_PRIVATExxxx
[Peer]
PublicKey = xxxxCLIENT_PUBLICxxxx
AllowedIPs = 10.110.210.7/32
Endpoint = xxxx
```
Client:
```
[Interface]
PrivateKey = xxxxCLIENT_PRIVATExxxx
Address = 10.110.210.7/32
[Peer]
PublicKey = xxxxSERVER_PUBLICxxxx
AllowedIPs = 10.110.210.1/24
Endpoint = xxxSERVER_IPxxx:51820
PersistentKeepalive = 25
```
Test:
```
❯ traceroute 10.110.210.7
traceroute to 10.110.210.7 (10.110.210.7), 64 hops max, 52 byte packets
1 10.110.210.1 (10.110.210.1) 22.118 ms 19.846 ms 19.929 ms
2 10.110.210.7 (10.110.210.7) 40.627 ms 40.264 ms 43.752 ms
```
Route:
```
❯ netstat -rn -f inet
Routing tables
Internet:
Destination Gateway Flags Netif Expire
default 192.168.0.1 UGScg en0
default link#17 UCSIg utun2
10.110.210/24 link#17 UCS utun2
10.110.210.7 10.110.210.7 UH utun2
127 127.0.0.1 UCS lo0
127.0.0.1 127.0.0.1 UH lo0
...
255.255.255.255/32 link#17 UCSI utun2
```
Expected behaviour:
When using `traceroute 10.110.210.7`, the server `10.110.210.1` doesn't show up.
Other:
I have tried the same configuration on Windows, and it works fine.
next reply other threads:[~2021-07-08 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 4:52 zhengmian hu [this message]
2021-07-08 5:07 ` Wrong route on macOS zhengmian hu
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=CAAntei-TBN5VUpnHLNExgg_4V80zU+PMAHcjVOqfmDbeJ3G1aA@mail.gmail.com \
--to=huzhengmian@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.