I'm using newly installed 13.04 on my lap. I've connected to wifi connection in our university and configured the proxy settings in network settings. I can access web and even software updater work nicely, but using the terminal I even can't ping into a website. "ping google.com" gives 100% packet loss
|
for me the following worked in our company network with proxy:
this is to force the system to use the new file we create now.
create new file "95proxies" and add there the content of the apt.conf file Example:
now the system use the 95proxies file Try
this should work now |
|||
|
|
|
If you use a proxy server, and want to access the Web through Terminal, you need to export the proxy variables. To do that, just press Ctrl+Alt+T on your keyboard to open Terminal. When it opens, run the command(s) below:
Make sure you replace proxy_username, and password, with your information. Another way is to: (from terminal)
This will open an empty document, just add the lines below, and save it
|
|||||||||||||||||||||
|
|
I had the same issues with the network at my university as well. I believe that there is nothing wrong with your machine or the proxy server. The problem is that the network admins block certain protocols and ports and only allow you to perform specific operations. In your example, 'ping' doesn't work but lets say if you try 'ssh', you may have no issues at all. |
|||
pingcommand? There should be aReply from (<IP Address>): Destination network unreachablekind of message. Also, let's trytraceroute -n google.comand tell us what the output is (I think you'll first need tosudo apt-get install tracerouteto installtraceroute). – Alaa Ali Jun 18 '13 at 9:20traceroute to google.com (74.125.236.97), 30 hops max, 60 byte packets 1 10.8.108.254 2.687 ms 20.577 ms 20.742 ms 2 192.248.8.62 6.150 ms 7.613 ms 9.987 ms 3 192.168.100.1 10.132 ms 18.938 ms 19.579 ms 4 192.168.100.6 19.812 ms 20.852 ms 21.386 ms 5 192.248.8.125 21.666 ms 22.230 ms 23.575 ms 6 * * * 7 * * *– Sudheera Jun 19 '13 at 7:07