How to access to LAN via OpenWrt Wireguard

[psherman]

@RobertH

sudo nano /etc/wireguard/wg0.conf

This is not where WireGuard is defined in OpenWrt.

@RobertH

adding the local LAN subnet to the AllowedIPs entry should instruct Wireguard to allow the Peer to route to the LAN subnet / allow you access.

For this specific thread, The peer configuration on the OpenWrt (“server”) side should have a single /32 address within the 10.14.0.1/24 subnet. Nothing more, nothing less.
The remote peer (“client”) must include 192.168.1.0/24 (0.0.0.0/0 would work, of course).

[vanadium]

i was loking for wireguard in etc but could not find it as Robert said. Where is it defined in OpenWrt?

[psherman]

It is part of /etc/config/network

You had it in your very first post:

@vanadium

config interface 'WG_Server'
	option proto 'wireguard'
	option private_key '<privatkey>'
	option listen_port '12345'
	list addresses '10.14.0.1/24'

config wireguard_WG_Server
	option public_key '<public key>'
	option description 'RN9S'
	option persistent_keepalive '25'
	list allowed_ips '10.14.0.3/32'
	option route_allowed_ips '1'
	option endpoint_port '12345'

config wireguard_WG_Server
	option public_key '<public key>'
	option description 'Mojca_Latitude'
	option persistent_keepalive '25'
	list allowed_ips '10.14.0.4/32'
	option route_allowed_ips '1'
	option endpoint_port '12345'

And all of this looks okay except for the fact that the endpoint_port should be remoed from the peer configs.

I'm pretty sure that we already validated that everything is correct in your OpenWrt side of the configuration.

[vanadium]

I have tried everything but without sucess. But for kicks i installed a ping tool on my phone that is conected to wireguard. And i can ping my NAS with no problem. So i think that there is some problem in wireguard client on my windows 10 laptop

[psherman]

@vanadium

So i think that there is some problem in wireguard client on my windows 10 laptop

So let’s see the wg config from the win10 machine.

[vanadium]

Config on win10 client

[Interface]
PrivateKey = <key>
Address = 10.14.0.4/32
DNS = 1.1.1.1

[Peer]
PublicKey = <key>
AllowedIPs = 0.0.0.0/0
Endpoint = Public IP on my router:12345

[psherman]

and what happens when you try to ping 192.168.1.235 from the windows machine with the WG tunnel up?

[gabrielo]

in your windows 10 open a command prompt as administrator and type:

route add 192.168.1.0 mask 255.255.255.0 10.14.0.1
ping 192.168.1.235

succeeds or not?

[vanadium]

@psherman:

@gabrielo:

What does that now mean?

[psherman]

@vanadium

What does that now mean?

It means that @gabrielo was correct that the route was not being added into Windows properly. Now that you've added the route, your windows machine should have access to the NAS.

[vanadium]

Ok i can log in into my router when on 4G, i can acess open media vault control panel on my nas, but cant acess the files on it in windows explorer. In my eyes this is a huge sucess and i am wery grateful for help, now i must only figure out why i cant acess the folders. This must now be only a windows thing...

[vanadium]

Left one is working only on wifi, right one is working when on wireguard, must see how autocad will acept this kind of paths

amazing tnx for help, need only to find out how to set up that mapped drives work

[gabrielo]

@vanadium

What does that now mean?

you need to investigate how your wireguard client in windows can add the above route automatically

[psherman]

Yes. We have now established that Wireguard on OpenWrt is working as expected. The remaining issues are windows related.

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.