> > Having said that, I took another look at the routing table on the Win10 > client and noticed something odd. The only /32 routes I could find are > 192.168.112.236 255.255.255.255 On-link 192.168.112.236 281 > 192.168.112.255 255.255.255.255 On-link 192.168.112.236 281 > > the .236 address is the client , so I presume that the .255 address is > the VPN server IP ? If so, then you've got a very peculiar network > issue, as you say your network range is 192.168.112.0/24 .
Windows always adds an onlink route to broadcast address --- that's what you are seeing with the route to 192.168.112.255, not a route to the "server". Nothing peculiar. One thing not clearly mentioned is whether the SMB "server" is on the VPN "server". If so, smb mount may be using a hostname that resolves as the VPN IP of the server. Or the VPN IP itself. Then SMB traffic will flow via the VPN. The bypass route is not relevant here: OpenVPN adds a bypass route only if redirect-gateway is in use. Which is not the case here. Also the relevant IP of the server for bypass depends on how is remote specified in the config -- remote could be made to resolve always to the public IP (via NAT) or to the LAN IP while on LAN. However, in both cases a bypass route is not required in this particular setup. Selva
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
