# Router as Wireguard client blocks LAN reachability to same Wireguard server the router is connected to

**URL:** <https://forum.gl-inet.com/t/router-as-wireguard-client-blocks-lan-reachability-to-same-wireguard-server-the-router-is-connected-to/22529>\
**Category:** Router\
**Created:** [June 28, 2022, 11:01am UTC](https://forum.gl-inet.com/t/router-as-wireguard-client-blocks-lan-reachability-to-same-wireguard-server-the-router-is-connected-to/22529 "2022-06-28T11:01:53Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![hilll](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/4bbf92/32.png) [@hilll](https://forum.gl-inet.com/u/hilll)\
**Post date:** [August 2, 2022, 9:08am UTC](https://forum.gl-inet.com/t/router-as-wireguard-client-blocks-lan-reachability-to-same-wireguard-server-the-router-is-connected-to/22529/11 "2022-08-02T09:08:48Z")

</div>

when start wg client connect, the glinet-router agent all the LAN ip pkg to wg server([anydomain.com](http://anydomain.com)).  
not special route to [anydomain.com](http://anydomain.com).

the sample way to resolve is: in [anydomain.com](http://anydomain.com) set firewall, all accept pkg from wg network interface to [anydomain.com](http://anydomain.com).

if want to operate special in wg client routing, can reference as command:

ip rule del from all fwmark 0x60000/0x60000 lookup 31  
iptables -t mangle -D WG\_DDNS -s 192.168.8.0/24 -d 192.168.113.122/32 -i br-lan -j MARK --set-xmark 0x60000/0xffffffff

-s 192.168.8.0/24 — is the lan subnet  
-d 192.168.113.122/32 — is the [anydomain.com](http://anydomain.com) static ip

---

_[View the full topic](https://forum.gl-inet.com/t/router-as-wireguard-client-blocks-lan-reachability-to-same-wireguard-server-the-router-is-connected-to/22529)._