Force Juniper-network client to use split routing
Posted
by
craibuc
on Server Fault
See other posts from Server Fault
or by craibuc
Published on 2011-03-14T13:12:45Z
Indexed on
2014/06/13
9:30 UTC
Read the original article
Hit count: 332
I'm using the Juniper client for OSX ('Network Connect') to access a client's VPN. It appears that the client is configured to not use split-routing. The client's VPN host is not willing to enable split-routing.
Is there a way for me to over-ride this configuration or do sometime on my workstation to get the non-client network traffic to by-pass the VPN? This wouldn't be a big deal, but none of my streaming radio stations (e.g. XM) work will connected to their VPN.
Apologies for any inaccuracies in the terminology.
** edit **
The Juniper client changes my system's resolve.conf file from:
nameserver 192.168.0.1
to:
search XXX.com [redacted]
nameserver 10.30.16.140
nameserver 10.30.8.140
I've attempted to restore my preferred DNS entry to the file
$ sudo echo "nameserver 192.168.0.1" >> /etc/resolv.conf
but this results in the following error:
-bash: /etc/resolv.conf: Permission denied
How does the super-user account not have access to this file? Is there a way to prevent the Juniper client from making changes to this file?
© Server Fault or respective owner