@Clive_A 

Clive_A wrote

Hi @MR.S 

Thanks for posting in our business forum.

MR.S wrote

  @Clive_A 

 

Do you have any tips? I have connetction to the wireguard server but I don't get any traffic in the tunnel until I enter 0.0.0.0/0 but I don't want to route all traffic through the tunnel only some networks, I have only tested on an ER706W so I don't know if it is the same on ER8411 or ER707-M2

 

All tips are gratefully received 

0.0.0.0/0 as allowed-ips? Is there a firewall/ACL? I cannot think of anything why would it be like that. Anything like the routing table on the peer??

 

On the Omada, it does not matter. When you set it up on the Omada system, without any config, it would work and if you put the allowed-ips(those LAN subnets from the Omada) on the other peer, it would work and allow access. At least I knew this was true about the Omada when I wrote the config guide.

 

No firewall/ACL and when I try to route a network is visible in routing tabel but dont work, The strange this is that wireguard site to site between a ER706w and ER707-M2 rout work but on a wireguard server on a linux computer I have to use 0.0.0.0/0 to get trafic but then all go tru wireguard server and that is nothing I want..

it would have been cool if you could create another tab in the configuration called wireguard client, that would probably have solved many problems :-)

Anyway, now I've at least tried and learned a bit more about wireguard :-)

  @Clive_A 

I don't think there is a routing problem on the wireguard server that runs on linux, then it wouldn't help to set 0.0.0.0/0 on the TP-Link router. moreover, the wireguard server works for all other clients.

but there is not much more to spend time on, I was most interested in using TP-Link wireguard as a pure client on the router, it turns out to be difficult right now, I hope there will be an improved version of wireguard in a later update :-)

so thanks for the help so far