Forum Discussion
jone14_166962
Altocumulus
AltocumulusBig-IP Edge Client / Windows 10 1809 - No internet connection with connected VPN
Hi everybody
I've updated my computer to Windows 10 Build 1809:
After a successfull connection with Big-IP Edge Client VPN the internet connection is broken. Ping to Google DNS servers with connected VPN:
We have configured Network Access with "split tunneling". The very same VPN worked perfectly with the previous build of Windows 10 (1803).
Version of VPN client: 7160,2018,417,2013
Does anyone run into the same problem?
Thank you, John
The latest windows update for Windows 10 1809 January 22, 2019—KB4476976 (OS Build 17763.292) seems to fix the issue!
Portallion_1480Nimbostratus
NasimMalik, did you say you have found a workaround for this? Your comment suggests as much, but there is no info on what you did.
Toby_Garcia_146Altostratus
Looks like a known issue article has been published. Per the article, the workaround is to force all traffic through the tunnel (i.e. disable split tunnel).
https://support.f5.com/csp/article/K18448121
Chris_T_373828I encountered a similar issue today after receiving the 1809 update yesterday. I have no Internet access when the VPN is connected. I haven't found a workaround.
Any workaround is appreciated.
- Toby_Garcia_146
If you're an administrator on the device, you may be able to update add a static route to force traffic through the tunnel. But that won't work if the access policy is setup to drop the connection if the routing table changes.
In that case, your APM admin must update the policy with the workaround.
- Chris_T_373828
There's a Knowledge Center article describing this issue and a workaround. As an end user I don't have the configuration utility that is mentioned.
https://support.f5.com/csp/article/K18448121
NasimMalik_3304Yes, SSL F5 VPN doesn't work on Window 10 1809 machine.Logged a call with F5 support and they advised below '' At the moment the reported issue is escalated to our Product Development team. New software defect ID745498 with a title "[Windows RS5]OS doesn't using default route 0.0.0.0/0.0.0.0 if config with split tunnel" was created to track that issue. ''
Tested on one of window machine 1809 and it seems working.
Route print -p 0.0.0.0 netmask 128.0.0.0 default gateway Route print -p 128.0.0.0 netmask 128.0.0.0 default gateway
But ,This is not the fix, but the workaround while the issue is being analyzed by F5 product developers.
jone14_166962Thank you for the useful information! I hope, we will get a fix soon..
- jone14_166962
I just tested with the latest version of the Big IP Edge client (7171.2018.808.2011). Same behavior, it doesn't work either.