# Router as Wireguard client blocks LAN reachability to same Wireguard server the router is connected to **URL:** \ **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:** 5
**Author:** ![Augustus\_Meyer](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/f14d63/32.png) [@Augustus\_Meyer](https://forum.gl-inet.com/u/Augustus_Meyer)\ **Post date:** [July 1, 2022, 8:25am UTC](https://forum.gl-inet.com/t/router-as-wireguard-client-blocks-lan-reachability-to-same-wireguard-server-the-router-is-connected-to/22529/5 "2022-07-01T08:25:52Z")
More details anout this bug to be found here: > [@Wrong iptables for wg, accessing servers IP](https://forum.gl-inet.com/t/wrong-iptables-for-wg-accessing-servers-ip/22570): > > Some additions to my last msgs here: Doing more research, I noticed a serious bug regarding the fw: Trying to access my email (POP) server, which is also on the wg-server, I noticed following wrong rules: First rule is already wrong: Thu Jun 30 15:52:27 2022 kern.warn kernel: [454382.914405] TRACE: mangle:FORWARD:rule:5 IN=br-lan OUT=wg0 MAC=xx:xx:xx:xx:xx:xx:xx:xx:37:0a:44:93:08:00 SRC=192.168.8.221 DST=my.wg.server.ip LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=6125 DF PROTO=TCP SPT=50866 DPT=11… --- _[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)._