wireguard works for 10.0.0.x/24, but not for 10.10.10.x/24

Sitaram Chamarty sitaramc at gmail.com
Sat Aug 25 04:12:24 CEST 2018


I have a very peculiar problem.

My wireguard server serves up for my laptop and phone using 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

I am using the wg-quick command, if it matters.

I can ping from the laptop to the server ( ->  I can access services running locally on the
server (such as tcp/80 or udp/53).  "traceroute" will show the
first hop as, 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.

Both sides are running the same version of wireguard (20180809).
Server is CentOS 7.4, client is Fedora 28.

Does anything in this ring a bell for anyone?


More information about the WireGuard mailing list