Kacheong Poon writes: > But this is only half the question. Can a machine with only > routable address talk to a machine with only LLA if they happen > to be on the same link? How can this happen? Maybe because of > a mis-configuration?
Yes, or a failing DHCP server, or a server that refuses to provide addresses to certain kinds of clients. I suspect that talking to such machines on your local network (when you have a routable address yourself) requires special work. Otherwise, you'll misidentify the peer as off-link and send your replies to a router. (Perhaps it'll still work if there's a matching route and the router knows what to do with LLA ... and allows one-armed forwarding. More likely, it'll fail.) Thus, doing nothing means that windows/mac machines stuck with LLAs (for whatever reason) will be accessible only by 'cheating.' The user will have to explicitly (manually) configure an address in the LLA range on one of the interfaces, and treat it as a regular subnet. That might be "good enough" for most debugging purposes. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
