<![CDATA[Client multi-subnet problems]]>Hi there,

I have a working OpenVPN tunnel between a satellite site and our datacentre. The datacentre is the server and the satellite site is the client.
Server subnet is 192.168.15.0/24 and Satellite subnet is 192.168.18.0/24.
Both ends are running latest pfsense.
The satellite site now has a second subnet (192.168.80.0/24) and i'd like to be able to route traffic from that subnet to the server subnet (and vice versa).
I've tried adding 192.168.80.0/24 as a second comma-separated subnet in the server (datacentre) pfsense, and I can see that appear in the routes
I've bounced both sides and still no connectivity on the 192.168.80.0/24 network
Both sides have * in their firewall rules for OpenVPN so that's not the problem.
Any ideas what i'm doing wrong?

]]>https://forum.netgate.com/topic/188694/client-multi-subnet-problemsRSS for NodeSat, 18 Apr 2026 00:40:57 GMTWed, 12 Jun 2024 15:38:29 GMT60<![CDATA[Reply to Client multi-subnet problems on Wed, 12 Jun 2024 17:31:04 GMT]]>@Pentangle
If it's a TLS OpenVPN with a wider tunnel subnet than a /30 you might have a CSO created for the client. So you also need add the additional subnet there.

]]>https://forum.netgate.com/post/1173279https://forum.netgate.com/post/1173279Wed, 12 Jun 2024 17:31:04 GMT