Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'wget is not good' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
wget is not good
Authored by: fotoun on May 06, '01 05:03:27AM
I tried the proposed wget -q -O /dev/stdout | grep '' | sed 's|||g'. This is not good for me because it returns the address of the proxy ! To get the same information directly, I prefer to use ifconfig -a | grep inet | grep -v "" | awk '{print $2}'.

[ Reply to This | # ]
Authored by: robg on May 06, '01 09:21:19AM

On my machine, behind the firewall, that still returns the value of the local box (192.x) not the public IP. Are you on a proxy, but NOT behind a firewall?


[ Reply to This | # ]
Authored by: fotoun on May 07, '01 05:43:56PM

I use a transparent proxy and my IP is not translated. That means that I am not 'behind' a Firewall but behind a simple HTTP proxy.

[ Reply to This | # ]
wget does not work for me
Authored by: James Bond on May 13, '01 11:31:05AM

What do I need to do to get it to work?

I am behind port 8080 operated by my ISP/Cable supplier.

I have set http_proxy and use_proxy as per the GNU documentation but I get the following:

[localhost:~] roger% set | grep proxy
use_proxy on
[localhost:~] roger% wget
=> `index.html.3'
Connecting to
connect: Operation timed out

(try: 2) => `index.html.3'
Connecting to ^C

[ Reply to This | # ]