Hi @Navas1 

Thanks for posting in our business forum.

Navas1 wrote

I am trying to achieve the following

 

a) I have a dedicated wireguard server in a remote datacenter ( configured as 192.168.4.0/24 )

b) I have PC's from multiple locations connecting that wireguard server as clients (peers) 

c) I have an office ROUTER (ER7206) with LAN subnet of 192.168.0.0/24 and I want to access all the peers connected to the wireguard server ( 192.168.4.0/24 )

 

when I set Allowed address as 0.0.0.0/0 then I can access those 192.168.4.0/24 subnets but the issue is all of my internet traffic is routed through wireguard tunnel. I don't want that I only want to access my wireguard peers and not the whole internet. Internet should be routed through my local gateway WAN

 

Please let me know if you need any more info.

I hold a grain of salt about your statement.

First, you whole remote subnet is 192.168.4.0/24. Yep, no problem with that.

Allowed IP address is supposed to be 192.168.4.0/24 and you should be able to ping the remote peer WG int IP. Will you be able to do that? Paste a screenshot here.

Second, your config on the 7206, seems to be good.

But what are the devices WG IP addresses?

If you can ping the WG int IP, you are accessible and available in the WG subnet which means you should be able to ping other clients that get a WG IP.

Have you considered that if there is a problem with your clients' firewall?

So, here's the thing, our troubleshoot and walkthrough stops when you can access the remote peer WG int IP which reflects that the WG tunnel is up and you are actually connected to the remote peer network. 

Get a computer connected to that if possible. That's the most efficient way to test this if there is a problem with WG or not.

But if you cannot ping other devices, that should be a problem you troubleshoot yourself as it's beyond our ability as the WG works and we cannot determine any problems with your remote devices.

From the Omada router to the remote peer, this WG tunnel as long as it is good, the rest of the issues you experience should not result from the Omada router because the tunnel is up and there is nothing we can configure to work around it. The routing tables are created and working already.

 

Navas1 wrote

OK, thanks for the clarifications.

 

It seems I have wasted around ~200 bucks

 

I should have gone with openwrt with cheaper router. big mistake.

 

What a disappointment

 

Hi @Navas1 

Thanks for posting in our business forum.

Navas1 wrote

ping from my LAN

 

 

ping within ER7206 router ( I logged in through SSH )

 

 

routing table

 

 

SSH and ER7206 can ping it which means it is working.

What's the IP of the macOS? The routing table of the macOS?

Do you have any static routing? Can you screenshot and paste it here directly?

Hi @Navas1 

Thanks for posting in our business forum.

Navas1 wrote

Routing table

 

navas@Navass-MacBook-Pro ~ % netstat -rn           

Routing tables

 

Internet:

Destination        Gateway            Flags           Netif Expire

default            192.168.0.1        UGScg             en5       

13.201.205.86      192.168.8.1        UGHS              en0       

35.186.199.111     192.168.8.1        UGHS              en0       

43.204.135.234     192.168.8.1        UGHS              en0       

100.108/16         utun100            USc           utun100       

100.108.51.9       100.108.51.9       UH            utun100       

127                127.0.0.1          UCS               lo0       

127.0.0.1          127.0.0.1          UH                lo0       

169.254            link#28            UCS               en5      !

192.168.0          link#28            UCS               en5      !

192.168.0.1/32     link#28            UCS               en5      !

192.168.0.1        50:91:e3:80:5f:e8  UHLWIir           en5   1192

192.168.0.100/32   link#28            UCS               en5      !

192.168.0.255      ff:ff:ff:ff:ff:ff  UHLWbI            en5      !

224.0.0/4          link#28            UmCS              en5      !

224.0.0.251        1:0:5e:0:0:fb      UHmLWI            en5       

239.255.255.250    1:0:5e:7f:ff:fa    UHmLWI            en5       

255.255.255.255/32 link#28            UCS               en5      !

There is no 192.168.4.0/24 route on your PC.

Try:

sudo route -n add -net 192.168.4.0/24 192.168.0.1