From: Darryl Yeoh <drl@bsd.my>
To: wireguard@lists.zx2c4.com
Subject: AllowedIPs
Date: Sat, 21 Oct 2023 09:29:56 +0800 [thread overview]
Message-ID: <df215452-cc26-4f1b-9e5a-690632b00ac0@bsd.my> (raw)
Hi lists,
I've a Debian 11 box in my LAN set up as a WG client. When I set:
AllowedIPs 0.0.0.0/0, ::/0
everything works.
However when I set:
AllowedIPs 0.0.0.0/1, 128.0.0.0/1, ::/1, 8000::/1
nothing works. Like ping/dig/curl just hangs until I hit Ctrl+c to
return to prompt.
When I test this config on my Android phone, it works with both of the
AllowedIPs.
Seems odd. Any ideas ?
Regards,
-Darryl
next reply other threads:[~2023-12-20 5:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 1:29 Darryl Yeoh [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-29 16:07 AllowedIPs Aaron Bolton
2020-08-29 23:16 ` AllowedIPs Eric Light
2020-08-30 8:56 ` AllowedIPs Aaron Bolton
2020-08-30 9:00 ` AllowedIPs Eric Light
2020-08-30 9:55 ` AllowedIPs Aaron Bolton
2020-08-30 10:04 ` AllowedIPs Eric Light
2020-08-30 10:34 ` AllowedIPs Aaron Bolton
2020-08-30 11:01 ` AllowedIPs Tomcsanyi, Domonkos
2020-08-30 19:08 ` AllowedIPs Eddie
2020-08-30 19:52 ` AllowedIPs Aaron Bolton
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=df215452-cc26-4f1b-9e5a-690632b00ac0@bsd.my \
--to=drl@bsd.my \
--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).