# GLiNet wireguard server with RPi4 OpenWrt as client using site to site connection **URL:** \ **Category:** Router\ **Created:** [July 22, 2023, 1:19pm UTC](https://forum.gl-inet.com/t/glinet-wireguard-server-with-rpi4-openwrt-as-client-using-site-to-site-connection/31668 "2023-07-22T13:19:56Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\ **Post date:** [July 23, 2023, 10:46pm UTC](https://forum.gl-inet.com/t/glinet-wireguard-server-with-rpi4-openwrt-as-client-using-site-to-site-connection/31668/2 "2023-07-23T22:46:30Z")
> [@mr.nobody](#): > > I have noticed that accessing luci on my Slate Ax shows Unsupported protocol type at the WGSERVER interface. Don't worry about that; that's how it looks by default. Further, you shouldn't need LuCI to set this up. It can all be done via the GL GUI. > [@mr.nobody](#): > > My office Slate AX router (192.168.0.10 WAN) [...] That's an unrouteable IP behind a NAT for any WG Client. There's no public IP as it's behind your company network. Unless you get get some port forwarding set up on the upstream router, you'd have to switch from a WG Server at your office to a WG Client to your RPi as a WG Server. Setting that up for the `allowed ip` directives & such would require some finagling though. I know that may sound counter intuitive but here's the thing: WG, in reality, is all peer to peer. I agree w/ GL that it's easier to grasp the concept of a Server/Client paradigm though. Here's a 'known good' WG Server -\> WG Client on the same subnet. It may/may not be helpful. I'm sure you can adapt the IPs, confs to your needs: > [@No TCP for connected VPN clients (just ICMP)](https://forum.gl-inet.com/t/no-tcp-for-connected-vpn-clients-just-icmp/30871/22): > > Well there certainly was a hurdle to overcome: after enabling the VPN WG Server GL GUI’s defaults for generating WG Client confs automatically set the endpoint to the public IP. I wanted the WG Client device to connect to the WG Server directly within the LAN, not over the WAN/Internet, so of course I changed that to the WG Server’s IP 192.168.10.1 from the perspective of the Client device. My Client device, the Certa, is known to preform with VPN providers using a MTU of 1320. YMMV. Server … Though this would appear to be more related: > [@Building a Site-2-Site network manually using two GL.iNet routers(SDK 4.X)](https://forum.gl-inet.com/t/building-a-site-2-site-network-manually-using-two-gl-inet-routers-sdk-4-x/31479): > > This post is to introduce the guide to config WireGuard LAN to LAN VPN (Site-2-Site) based on GL-iNet SDK 4.X fimrware. Supported Models Router Model Stable Beta GL-MT3000 (Beryl AX) √ - GL-AXT1800 (Slate AX) √ - GL-A1300 (Slate Plus) √ - GL-X3000 (Spitx AX) √ - GL-AX1800 (Flint) √ - GL-MT2500 (Brume 2) √ - GL-AR300M (shadow) - √ GL-MT300N-V2 (Mango) - √ GL-E750 (Mudi) - √ GL-SFT1200 (Opal) - √ GL-MT1300 (Beryl) - √ GL-X750 (Spitz) - √ GL-XE300 (Pul… (This is all WG so any confs generated by the GL GUI should easily work with your RPi.) --- _[View the full topic](https://forum.gl-inet.com/t/glinet-wireguard-server-with-rpi4-openwrt-as-client-using-site-to-site-connection/31668)._