Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest.
By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,.
Having a problem logging in? Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. To receive this Complete Guide absolutely free.
I entered this command in a shell: googleearth HTTPPROXY='10.1.1.2:8080' but it didn't set the proxy (I Think) because it didn't connected to the server. I can see it didn't. If you would have read the replies a bit more carefully you would have seen there's a few options and none of those match what you did.
So here's three examples. Use these steps if you are the only human using this machine, and you want.all. applications (that adhere to the PROXY environment variables) used by unprivileged users to use the same proxy all of the time: 0. Find out which shell you use (in a terminal window type 'echo $SHELL', without the quotes). If it is not Bash or if it does not source /etc/profile, then find out which central resource files your shell sources. Become root and see if you have the '/etc/profile.d' directory.
If you do, create a file there called '/etc/profile.d/proxy.sh' and fill it with these contents. Code: export HTTPPROXY=export HTTPSPROXY=changes then close the file. Open a terminal window and type 'env grep PROX' to verify the variables got set. Use these steps if you are just one of the users on this machine, and you want.only. applications (that adhere to the PROXY environment variables) to use a proxy when you select it: 0. Open a terminal window or use your Desktop Environments 'run' command, type 'env HTTPPROXY=/path/to/googleearth'. In your XFCE, KDE, GNOME or other Desktop Environment you might have GUI tools to help you set a proxy for other applications.
But i dont have a /etc/profile.d directory (only have a profile text file in my /etc directory) and my shell is bash. Now how i can use a global proxy for all the applications as you told? If you want.all. applications (that adhere to the PROXY environment variables) used by unprivileged users to use the same proxy all of the time you can add the code under 'A' to /etc/profile.
If you want.all. applications (that adhere to the PROXY environment variables) of.all. users (inclluding root) to use the same proxy all of the time you can add the code under 'B' to /etc/profile.
Apr 8, 2018 - 7 We are all aware that Google Earth is able to provide us with some of the most spectacular satellite images on the Internet. A new application. But when i installed it on an other system with a LAN Network Connection, google earth could not connect to the server (system connects to the internet by a LAN Network with a proxy) i dont know where i have to configure google earth network proxy settings.
Question How do I get Google Earth to work with the Cisco Web Security Appliance? Environment Google Earth 4.2 Symptoms The application Google Earth does not work when the client is connected to the Cisco Web Security appliance (WSA). This can be a result of proxy settings on the client or authentication requirements of the WSA. Case 1 When you are using Google Earth through the WSA, error code 26 or a message indicating that servers can't be reached is seen. If WSA is set up in explicit mode in the network, you will need to configure Google Earth to use the proxy. This can be done by making some changes in Internet Explorer:.
Click 'Start' and select 'Control Panel.' . Double-click 'Internet Options.' . Select the 'Connections' tab. Click 'LAN Settings.'
. Under 'Proxy server,' select 'Use a proxy server for your LAN' and enter the proxy information.
Once this has been completed, select 'OK' to save these changes. Case 2 Google Earth is not working through the WSA with a message indicating failed authentication/credentials required.
In cases where authentication is required to process a request, Google Earth will need a way to authenticate. To work around this issue, we will need to exempt authentication for the Google Earth servers. To exempt Google Earth from Authentication Exemption: For AsyncOS versions below 6.x:. On WSA GUI, browse to ' Web Security Manager'. Select Destination Authentication Exemptions Destinations.
Add the addresses - kh.google.com, geo.keyhole.com and auth.keyhole.com,.pack.google.com, pack.google.com, mw1.google.com, clients1.google.com, earth.google.com, maps.google.com, maps.gstatic.com, csi.gstatic.com and.gstatic.com. Commit the changes.
For AsyncOS 6.x and later:. Create a new custom URL policy called ' Destination Authentication Exemption Destinations' and add kh.google.com, geo.keyhole.com, auth.keyhole.com,.pack.google.com, pack.google.com, mw1.google.com, clients1.google.com, earth.google.com, maps.google.com and maps.gstatic.com to the list. Create an identity called 'application bypass identity' and set it to no authentication required. In the advanced section, select the URL category named ' Destination Authentication Exemption Destinations'. Create an access policy called 'application bypass policy' and assign the 'application bypass identity' to it. You will now be bypassing Google Earth requests for authentication.
Case 3 If network traffic is being transparently being redirected to WSA, the Google Earth client is unable to respond to transparent authentication requests and failure occurs. In these scenarios, WSA can be configured to cache user credentials based on the client's IP address. In this case, as long as there has been prior web traffic from the client, the Google Earth client would not need to be re-authenticated. For AsyncOS 6.x and later, this can be configured under: Network Authentication Surrogate Type: IP Address.