My 770 WLAN works fine at work where it is granted a public IP address upon connection. But at home where my router assigns private IP addresses, it always say the IP is "Link-local" and the browser or music player refuse to connect to the internet (even the connection manager always show both gateway and DNS servers addresses are acquired).

I went deeper into probing the problem by setting up a web server on a computer on the same "local" subnet. I used the 770 browser to visit the local web server, and it works fine. This confirms to me that it is not a hardware issue - neither the wifi signal is bad, nor the router being incompatible.

Then I noticed in advances settings on the 770, one can set up "proxy" for a connection. So, I think, becuase 770 seems to only talk to local machines, how about set up a local proxy?

I installed tinyproxy on a local machine, and set my 770 to use that proxy, and guess what... everything works again... the brower, music player are all able to connect to the internet via the local proxy...

My guess is that, there may be a bug in the connection managing software, when the ethernet interface is assigned a local ip address (even if by DHCP), it always thinks acquiring IP has failed, and did not set up proper default routing (even if a getway is provided).


Here is my configurations in detail:

A. No Proxy, refuse to connect to Internet:

Router / Gateway: 169.254.32.32
DNS: 169.254.32.32
770 IP: 169.254.32.15

(770 "sees" all above configurations, but cries "Link-local" and does even try to use the gateway...)



B. With proxy, Internet works:

Router / Gateway: 169.254.32.32
DNS: 169.254.32.32
770 IP: 169.254.32.15
Proxy Machine: 169.254.32.16