On Sat, 15 Jan 2022 03:48:36 -0500, Doug Lytle <supp...@drdos.info> wrote:
>On 1/15/22 3:27 AM, Bo Berglund wrote: >> But I want to include the*client* side LAN devices to be accessible to all >> of >> the devices on the*server* side LAN. >> Basically the two LANs should be routed together both ways... > >I'm using the pfSense version of OpenVPN to do just what you're asking. >I use: > >IPv4 Remote network(s) > >In the client config for OpenVPN; it provides the routes for the remote >client. > Thanks, could you be more precise, please? In the server.conf or client.ovpn? And what is the exact wording of the command line you mean (an example would be nice)? I guess in must be in the server.conf because it needs to do something to publish the route into the tunnel towards the client for the server side gateway. And then of course the client must supply its local network address too... BTW: What is "pfSense version of OpenVPN"? I have currently tested with the remote ASUS router connecting to my internal OpenVPN server on a Linux server (so *not* to the main ASUS router yet). So in my case the OpenVPN server is just another device on my local network which means it does not get involved in any routing from other devices in the main LAN. Question: Is there a way to add a route into the ASUS router directing calls for 192.168.117.0/24 to use gateway 192.168.119.216, which is my OpenVPN server? I.e. if the OpenVPN server can send a request to the main gateway (ASUS router) to add this route for other devices on the network to use? I am exploring the possibility to not mess too much with the ASUS router but instead use the existing infrastructure regarding OpenVPN that already works. -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
