Ive recently started having a problem on my Windows 10 Sophos Connect client VPN connection to Sophos XG v18 GA-Build354 which had been running fine until recently so I'm unable to pin it down to the 354 update? Basically its a routing problem as im not tunnelling on this config only routing traffic to the remote LAN subnet, but for some reason im now seeing the traffic on my own XG logs as Spoofed traffic as its not being routed over the VPN connection. But my local routing table does show the routes been added but for some unknown reason the route for the relevant remote subnet is using an apipa address as the gateway address which doesnt seem right so i checked on a w10 vm with Connect client config to another XG instance but on an older v18 build and that routing table does also use the an apipa address as the local gateway for the remote subnet. This does tally with the TAP adapters unconnected ip address which is always an apipa address until a connection is made but on the working connection instance the TAP adapters not dropping the apipa ip address like the Tap adapter seems to be doing on my not working VPN connection, on the working connection the initial apipa IP address is still on the NIC as an additional IP address where as on the non working connection im only seeing the configured remote VPN subnet thats setup on the remote XG for the Connect clients VPN? The problem with the connection still doesnt seem to be routing traffic on the related VPN connection if i manually try to set the TAP NICs IP address statically to include the initial apipa IP aswell as the Remote VPN subnet IP in an attempt to fix the routing table manually but it still isnt sending traffic over the VPN for some reason??
So im posting here now in the hopes somebody might have some knowledge to enlighten me on how the Connect client should be working in regards to its Routing?
Thanks in advance and i look forward to reading replies!
This thread was automatically locked due to age.
