![]() |
2007-08-10
, 19:28
|
Posts: 8 |
Thanked: 1 time |
Joined on Aug 2007
|
#12
|
![]() |
2007-08-10
, 19:33
|
Posts: 8 |
Thanked: 1 time |
Joined on Aug 2007
|
#13
|
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).
![]() |
2007-08-10
, 19:43
|
Posts: 3,401 |
Thanked: 1,255 times |
Joined on Nov 2005
@ London, UK
|
#14
|
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...
![]() |
2007-08-10
, 19:55
|
Posts: 149 |
Thanked: 134 times |
Joined on Jul 2007
@ Florida
|
#15
|
...
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
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.
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)
![]() |
2007-08-11
, 03:14
|
Posts: 8 |
Thanked: 1 time |
Joined on Aug 2007
|
#16
|
![]() |
2007-08-11
, 08:17
|
Posts: 61 |
Thanked: 2 times |
Joined on Jan 2007
@ United Kingdom
|
#17
|
But, hey come on, the definition says absolutely nothing about "link-local" IP address cannot communicate with other machines outside the subnet.
![]() |
2007-08-12
, 12:33
|
Posts: 3,401 |
Thanked: 1,255 times |
Joined on Nov 2005
@ London, UK
|
#18
|
So, the behavior of 770 still deviates from the norm, and I think my suggestion about the software bug is still valid.
![]() |
2007-08-19
, 10:23
|
|
Posts: 177 |
Thanked: 57 times |
Joined on Aug 2007
@ Washington State, USA
|
#19
|
![]() |
2007-08-19
, 11:13
|
Posts: 100 |
Thanked: 6 times |
Joined on Jul 2007
|
#20
|
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