| 1 |
On Fri, Jun 8, 2018 at 2:19 PM Hilco Wijbenga <hilco.wijbenga@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Fri, Jun 8, 2018 at 1:59 PM Grant Taylor |
| 4 |
> <gtaylor@×××××××××××××××××××××.net> wrote: |
| 5 |
> > > Any ideas? |
| 6 |
> > |
| 7 |
> > My bet is routing. Specifically the default gateway probably gets |
| 8 |
> > changed to route through the VPN when connected. |
| 9 |
> > |
| 10 |
> > You may want to reconfigure the VPN client to only route work prefixes |
| 11 |
> > through the VPN and let everything else go through your local default |
| 12 |
> > gateway. |
| 13 |
> > |
| 14 |
> > Note: What I'm suggesting is typically called "Split Horizon" routing / |
| 15 |
> > VPN. |
| 16 |
> |
| 17 |
> Yup, "Use only for resources on this connection" seems to have done |
| 18 |
> the trick. Thanks! |
| 19 |
|
| 20 |
Sigh, I take it back. That causes the internal sites to no longer work. |
Archives