Thread: Link-local IP address, I think it is a software bug...
View Single Post
AdamWu is offline AdamWu
2007-08-10 , 08:04
Posts: 8 | Thanked: 1 time | Joined on Aug 2007
#8
Originally Posted by iball View Post
No one should run a local subnet on that range as it's super-easy for an attacker to get in on it and is usually a sign of a lazy network admin.
Hmm, I thought hackers would assume everyone uses 192.168.x.x ... Maybe that is why I picked this werido net range at the very beginning ... but that was a couple of years ago, can't remember exactly why...

Originally Posted by iball View Post
Hosts files? It's a lot easier to run a fairly secure mini-DNS system on your local subnet that would make things a lot easier.
The thing is, I am hosting some service for my personal daily use (internet radio, web, etc) and I have a domain name associated to my cable modem's IP, so I can always refer service by name instead of IP address. This is great, but the problem is when I am actually within the subnet, the name resolution would not work... what I can see are two solutions: 1. Host file; 2. Set up a small internal DNS.

I chose 1 becuase it is quick and dirty, for using method 2, I would also have to turn off the DHCP on my router, and set up a customizable DHCP server to push the internal DNS to the client, so that any machines connected to this net knows to first try the internal DNS. I admit #2 is the right thing to do, but #1 is a big time saver...

BTW, if you don't know what I'm talking about, there is my problem in detail with "pictures":

Code:
Internet
 \--> (public IP) cable modem (192.168.1.x)
                           \---> Router (169.254.1.x)
                                      \---> Machine 1 (169.254.1.11)
                                      \---> Machine 2 (169.254.1.12)
                                      \---> Machine 3 (169.254.1.13)
Suppose I am running music cast service on machine 3, and I have set up proper port forwarding in the router and cable modem. My blog has a link refering to this service using name http://music.name.com:1234

* When I am outside of this network, I click on the link, everything works;

* But when I am inside, on machine 1, I click on the link, it would not work, becuase the name resolves to the modem's public IP, but it really should be Machine 3's internal IP. So the packet got lost wondering around... >_<

----------

Maybe this weekend I would spend some time to apply solution #2 when I make the change to net range...

One thing you are absolutely right: I am a lazy admin... :P
Last edited by AdamWu; 2007-08-10 at 08:19.