BUG - SSL VPN Default Gateway Broke

This sounds eerily similar to what you describe...

community.sophos.com/.../remote-access-ssl-vpn-and-same-192-168-1-x-network-on-both-ends-xg-125

that is only needed for site-site tunnels not a VPN software client on a PC it works fine on version 17.5 not 18

client already creates a separate ip range so that is not an issue. the issue is the vpn server is not pushing the route add to the client.

I assumed your clients have done something like that - numbers serves as example.

DHCP inside company: 192.168.1.0/24
Range: 192.168.1.10 - 50

DHCP VPN: 192.168.1.0/24
Range: 192.168.1.51 - 70

Have you created a rule to indicate the this traffic coming from your VPN interface is allowed to go inside your network?

inside company: 192.168.1.0/24

End Users house IP network (netgear Example)

192.168.1.0/24

DHCP VPN for SSL VPN Client : 10.1.1.0/24
Range: 10.1.1.51 - 70

yes there are rules if i manually add a route into the Users PC it works fine and routes how it should (Tunnel All Mode) This is the problem the SSL VPN Client does not add this route even though you add it in the SSL VPN configuration under SSL Remote Access NOT SSL site-site

route add 192.168.1.0 255.255.255.0 GW 10.1.1.51

inside company: 192.168.1.0/24

End Users house IP network (netgear Example)

192.168.1.0/24

DHCP VPN for SSL VPN Client : 10.1.1.0/24
Range: 10.1.1.51 - 70

yes there are rules if i manually add a route into the Users PC it works fine and routes how it should (Tunnel All Mode) This is the problem the SSL VPN Client does not add this route even though you add it in the SSL VPN configuration under SSL Remote Access NOT SSL site-site

route add 192.168.1.0 255.255.255.0 GW 10.1.1.51

Have you enabled to use this as default gateway?

yes and that is what does not seem to be working in V18 latest release