From: Morten Christensen <mc-mail@g.mc.cx>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard works for 10.0.0.x/24, but not for 10.10.10.x/24
Date: Sat, 25 Aug 2018 11:47:11 +0200 [thread overview]
Message-ID: <a21f27c3-9398-4d0e-fb88-51d69c3de873@g.mc.cx> (raw)
In-Reply-To: <20180825021224.GA30319@sita-lt.atc.tcs.com>
Den 25-08-2018 04:12, skrev Sitaram Chamarty:
> Hi
>
> I have a very peculiar problem.
>
> My wireguard server serves up for my laptop and phone using
> 10.0.0.1 as its own IP, and .2 and .3 respectively as my laptop
> and phone's IPs.
>
> But if I switch it to any other subnet, like 192.168.25.x/24, or
> even 10.10.10.x/24, it does not work.
>
> (Before someone asks, yes I did remember to change the wg0.conf
> on both sides before flipping the switch.)
>
> I can provide more details, I can run any debugging commands you
> ask me to, but there is literally no other difference except a
> `:%s/10.0.0/10.10.10/g` in /etc/wireguard/wg0.conf, on both
> sides.
>
> I am using the wg-quick command, if it matters.
>
> I can ping from the laptop to the server (10.10.10.2 ->
> 10.10.10.1). I can access services running locally on the
> server (such as tcp/80 or udp/53). "traceroute" will show the
> first hop as 10.10.10.1, but after that -- silence. It just
> won't go beyond that.
>
> So whatever it is, it seems to be on the server side. Packets
> make it to the remote endpoint, but don't get routed out to the
> internet after that.
Most times vpn-packets get a step further. The remote endpoint do not
know how to return them to the vpn-server.
Is your wireguard-server the router/gateway on your system ?
--
Morten Christensen
next prev parent reply other threads:[~2018-08-25 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 2:12 wireguard works for 10.0.0.x/24, but not for 10.10.10.x/24 Sitaram Chamarty
2018-08-25 9:47 ` Morten Christensen [this message]
2018-08-25 13:16 ` Sitaram Chamarty
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=a21f27c3-9398-4d0e-fb88-51d69c3de873@g.mc.cx \
--to=mc-mail@g.mc.cx \
--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).