Reply
Thread Tools
Posts: 9 | Thanked: 0 times | Joined on Jul 2007
#11
I've been having a similar problem with my 770. This problem always occurs in public wifi hot spots. If, when trying to connect, the 770 says that it has make a "local link" connection to the WiFi network in question, it will never allow access.

Yesterday evening we were at bar/restaurant in New Brunswick, NJ (Stuff Yer Face) and I attempted to get on line. On my first try, I connected thru the "local link" and, of course nothing worked. There was a question mark next to the WiFi symbol at the top of the screen. Then I tried it again, and it connected without indicating anything about local link. The connection worked fine. I was able to surf and get my email without any problem.

Does anybody know what's going on here?

Thanks
 
Posts: 8 | Thanked: 1 time | Joined on Aug 2007
#12
Originally Posted by sycohen View Post
Does anybody know what's going on here?
Yeah, even if I put my 770 next to my router, 1/4 of the chance it cannot acquire IP on the first try. I have to re-connect to get the IP / gateway / DNS by DHCP.
 
Posts: 8 | Thanked: 1 time | Joined on Aug 2007
#13
Originally Posted by Milhouse View Post
Even when you are inside your LAN, if the machine name resolves to a public IP address you should connect to you modem and from there connect to your internal machine. Granted it means you are going out onto the public internet and back into your own network which will involve a few miliseconds more latency (and add to your download limit if you have a capped connection) but in general it should work.

If it doesn't work, it's most likely because the loopback interface is not enabled on your router which is preventing internal connections from being routed back into your internal network via the WAN interface. If your router supports a loopback interface enable it and see if you can access your internal workstation via it's hostname (without using /etc/hosts).
I don't see "loopback" anywhere on the setting pages (on any routers I have ever used). Granted my cable modem is a cheap one... :P but still I don't think what you described is how it is suppose to work...
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#14
Originally Posted by AdamWu View Post
I don't see "loopback" anywhere on the setting pages (on any routers I have ever used). Granted my cable modem is a cheap one... :P
Well that's the option on Linksys routers, I don't know about your router - it's possible it doesn't support this feature. You may have to use your imagination though and try differently named options that achieve the same result - any option to do with NAT for instance, eg. "Internet NAT Redirection" is another way of describing the loopback interface.

Originally Posted by AdamWu View Post
but still I don't think what you described is how it is suppose to work...
Fair enough... but let's remember you are the guy using link-local IP addresses on his internal LAN!

Last edited by Milhouse; 2007-08-10 at 19:46.
 
Posts: 149 | Thanked: 134 times | Joined on Jul 2007 @ Florida
#15
Originally Posted by AdamWu View Post
...

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

Not sure where you came up with that configuration, but it may be part of the problem.

From RFC3330:
169.254.0.0/16 - This is the "link local" block. It is allocated for
communication between hosts on a single link. Hosts obtain these
addresses by auto-configuration, such as when a DHCP server may not
be found.
From RFC1918:
3. Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

It's not a bug in the Nokia, it's a bug in your router's configuration.
Please change your subnet to one of the standard "private address space" subnets and try again.
 
Posts: 8 | Thanked: 1 time | Joined on Aug 2007
#16
OK, this is clear to me that probably using "link-local" IP range in DHCP settings is non-standard.

But, hey come on, the definition says absolutely nothing about "link-local" IP address cannot communicate with other machines outside the subnet. So, the behavior of 770 still deviates from the norm, and I think my suggestion about the software bug is still valid. (The de facto proof: the four other machines I have, plus over 5 other machine I have used on this network with many different flavored OS all connects to Internet with zero problem)

And if you still think my DHCP assigning link-local IP is annoying to you, here you go: I can throw DHCP away, just manually assign a link-local IP address, a gateway, and a DNS. By doing this I am now completely compliant with the definition - "no DHCP", and guess what? Of course 770 still refuse to connect to the Internet...


BTW, yeah, I don't think my dirt-cheap cable modem has that advance thingy... and, for the sake of doing the right thing, I will go for the "dual interfaced nameserver" scheme... ^_^

Last edited by AdamWu; 2007-08-11 at 03:22.
 
Posts: 61 | Thanked: 2 times | Joined on Jan 2007 @ United Kingdom
#17
Originally Posted by AdamWu View Post
But, hey come on, the definition says absolutely nothing about "link-local" IP address cannot communicate with other machines outside the subnet.
Surely "It is allocated for communication between hosts on a single link." covers that - you are trying to connect to an onward link (via the router), which according to the RFC definition is not what that range is designed for.

Given everything else works, I agree that the Nokia is not as friendly as your other devices, but as it is working within the definitions of the RFC, I doubt it'll change.
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#18
Originally Posted by AdamWu View Post
So, the behavior of 770 still deviates from the norm, and I think my suggestion about the software bug is still valid.
So file a bug in Maemo Bugzilla.

Chances are, Nokia have anally stuck to the RFC whereas other vendors may be a little more flexible... that certainly seems to be the way Nokia operate (to wit hidden SSIDs which Nokia refuse to list in a network scan yet hidden SSIDs are listed no problem on a Windows machine - who has the "bug" that explains the difference? Windows, probably)

In the mean time, it might be a good idea to fix your whacked out network.
 
gogol's Avatar
Posts: 177 | Thanked: 57 times | Joined on Aug 2007 @ Washington State, USA
#19
Jesus, it doesn't seem that outrageous of a setup...

Seems what would fit nicely is to host a copy of privoxy (and maybe even Tor) on one of your local machines. Set it up to be available to all machines on your 169.254 subnet and set the 770 to proxy through it. Wahla, adblock (and even anonymity) without extra cpu cycles on the tablet

..although you'd probably need a separate proxy for voip / chat etc. Maybe it is a little whacked
 
Posts: 100 | Thanked: 6 times | Joined on Jul 2007
#20
so how do we avoid the link-local ip problem if travelling around the world and wanna connect to wi-fi networks???...is there some trick or settings which should be made to minimize or eliminate it?...and should we create some sort of link with our own home LAN network to do so??

Thanx!
 
Reply


 
Forum Jump


All times are GMT. The time now is 16:43.