# Bug: Wireguard Client Split Tunnel not routing all allowed\_ips

**URL:** <https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514>\
**Category:** Router\
**Created:** [April 26, 2021, 12:56pm UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514 "2021-04-26T12:56:03Z")\
**Posts on this page:** 11\
**Page:** 2

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [June 20, 2022, 6:40am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/22 "2022-06-20T06:40:04Z")

</div>

> [@s.okamoto](#):
>
> Would there a problem writing it here?

No problem. Can you post?

---

<div class="post-metadata">

**Author:** ![s.okamoto](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/c5a1d2/32.png) [@s.okamoto](https://forum.gl-inet.com/u/s.okamoto)\
**Post date:** [June 20, 2022, 7:38am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/23 "2022-06-20T07:38:13Z")

</div>

thank you alzhao.

there is patch for /etc/init.d/wireguard.  
this will enable even if multiple prefixes are described in AllowedIPs.  
[wireguard.zip](https://forum.gl-inet.com/uploads/short-url/y0AJ4Bsp5wxlyGtPWW8JX2P3S9N.zip) (1.0 KB)

---

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [June 20, 2022, 8:24am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/24 "2022-06-20T08:24:32Z")

</div>

I asked developer to have a check and merge it in firmware 3.215.

---

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [September 16, 2022, 10:20am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/26 "2022-09-16T10:20:16Z")

</div>

I reopened the bug internally.

---

<div class="post-metadata">

**Author:** ![amarsaudon](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/b77776/32.png) [@amarsaudon](https://forum.gl-inet.com/u/amarsaudon)\
**Post date:** [October 17, 2022, 10:47pm UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/27 "2022-10-17T22:47:55Z")

</div>

Fighting this exact same issue on a GL-SFT1200 running 3.215. Is there a workaround available? Had to flip the link to full tunnel for the time being as a band-aid, but I’d prefer to avoid the overhead wherever possible.

---

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [October 18, 2022, 9:43am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/28 "2022-10-18T09:43:45Z")

</div>

Let’s confirm:

Firmware 3.x only support the first item in AllowedIPs settings. If you need to have multiple items in AllowedIPs, you may need to use vpn policy.

We solved this problem in Firmware 4.x. So if you use a router which there is Firmware 4.1 for it, pls try.  
If still not 4.x firmware (e.g. SFT1200) pls use vpn policy.

---

<div class="post-metadata">

**Author:** ![jtf](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/bbce88/32.png) [@jtf](https://forum.gl-inet.com/u/jtf)\
**Post date:** [January 12, 2023, 4:48am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/29 "2023-01-12T04:48:46Z")

</div>

I have a Beryl router that is updated to v4.1.0 beta3, and I still can’t get local routing to work. My goal is to have Wireguard provide a site to site tunnel of all traffic to my home router (a pfsense router) such that my remote systems can access the internet from the home router, and also access the sub-net of my home network. I can establish the Wireguard tunnel, and the internet access, but I can’t ping systems in the sub nets in either direction (home to remote or remote to home). I’ve followed some excellent tutorials on setting this up on the pfSense side, and I believe I have that set up properly, but I could be wrong. Is there a good tutorial on how to set up site to site with the Beryl, or how to debug it if it doesn’t work? With the 4.1.0 firmware, do I simply set 0.0.0.0/0, or do I also need to add the subnet route? (My pfsense network is 192.168.22.0/24, so do I also enter that in the ‘Allowed IP’s’?)

---

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [January 14, 2023, 1:56am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/31 "2023-01-14T01:56:54Z")

</div>

From what you described, you met an issue on Opla 4.x firmware. That may not related to this thread.

So pls just send your requrest via email with your wireguard config and we will help.

---

<div class="post-metadata">

**Author:** ![ceear](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@ceear](https://forum.gl-inet.com/u/ceear)\
**Post date:** [June 25, 2023, 8:00am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/32 "2023-06-25T08:00:06Z")

</div>

Just wanted to confirm that @s.okamoto patch is perfectly working. I’m on 3.216 (AR750S) and can reach all subnets defined in the wirguard config.

Thank you s.okamoto !

---

<div class="post-metadata">

**Author:** ![nullswitch](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/n/90ced4/32.png) [@nullswitch](https://forum.gl-inet.com/u/nullswitch)\
**Post date:** [September 9, 2023, 6:04pm UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/33 "2023-09-09T18:04:44Z")

</div>

Can you post your wireguard setup? And did you apply the patch or are you saying it looks fixed in 3.216?

I can’t remember the last time I tried but it’d be great to see a working example to make sure I’m not doing something stupid (like using ; instead of ,)

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [October 29, 2025, 4:24am UTC](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514/35 "2025-10-29T04:24:32Z")

</div>



[Previous page](https://forum.gl-inet.com/t/bug-wireguard-client-split-tunnel-not-routing-all-allowed-ips/15514.md?page=1)
