Forum Discussion
Below are workaround instructions that worked for me as an end user. This is not intended as central workaround a for a multi-user deployment.
-
Start cmd as administrator. One way to do this is
win+r cmd ctrl+shift+enter
-
Find the Gateway ip address for your Internet connection using the route print command in the administrator command prompt. You'll find it in the first entry in the IPv4 Route Table where Network Destination is 0.0.0.0 and the Netmask is 0.0.0.0. You will use the Gateway ip address in the next step. The following step assumes that the Gateway ip address is 192.168.1.1
route print
-
Enter the following commands to route Internet traffic through your Internet connection's gateway. Use your gateway's IP address for the last address in the following commands. The first two commands make certain that the appropriate entries exist and may generate a benign error message.
route add 0.0.0.0 mask 128.0.0.0 192.168.1.1 route add 128.0.0.0 mask 128.0.0.0 192.168.1.1 route change 0.0.0.0 mask 128.0.0.0 192.168.1.1 route change 128.0.0.0 mask 128.0.0.0 192.168.1.1 rem hit enter to make certain that the prior command is executed
Hi Chris,
Great, but could we apply this workaround to large scale (I mean to say a organisation who has more than 100 sites and each site has own default gateway) ?
- Secondly, if just BEACUASE OF THIS FEATURE UPDATE we force all traffic to tunnel( internet and Corporate ) then 1. we are not using F5 as split tunnel feature 2. before enable do we need to know which F5 model can able to handle all traffics ?