FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
194 views 2 comments
by anonymous

Win 10.0.19045

RUT950 RUT9_R_00.07.03.3 (Host on 192.168.0.0 network / 4G WAN)

WireGuard 0.5.3 (Client on 192.168.1.0 network)

I thought I had followed the guides correctly. Can establish a tunnel which remains connected. Tiny traffic exchanged. Can't ping devices on host network.

Outside of the wrong blend of sleep / caffeine what did I miss?

Thanks!

1 Answer

0 votes
by anonymous

Hello,

Your Allowed IPs fields are incomplete:

  1. on the server add 192.168.1.0/24
  2. on the client add 192.168.0.0/24

Regards,

Best answer
by anonymous
Of course - thank you.

Given the client is a laptop for field work is using 0.0.0.0/24 an acceptable solution given the client site network will typically be unknown?
by anonymous

is using 0.0.0.0/24 an acceptable solution

I don't think so. If you want to reach any 192.168.0.0/16 except 192.168.0.0/24 from the server you need to build the Allowed IPs in reverse there is no direct formulae to mask one network.

Then it will be: 192.168.128.0/17 + 192.168.64.0/18 + 192.168..32.0/19 + 192.168.16.0/20 + 192.168.8.0/21 + 192.168.4.0/22 + 192.168.2.0/23 + 192.168.1.0/24.

The Allowed IPs on the client will stay the same: 192.168.0.0./24