On Thu, 6 Feb 2003, Michael Sternberg wrote: > > ftp://ftp.isi.edu/internet-drafts/draft-ietf-zeroconf-ipv4-linklocal-07.txt > > In short: > > 0. Static IP configured - use it and announce neighbors with ARP > broadcast. > 1. DHCP configured - try to get IP. If successful - use and update > neighbors. > 2. If no answer - pick a random address from 169.254.0.0/16 range. > 3. Check if it's already used - with ARP probes. > 4. If address already used - wait a little and return to step 2. > 5. If free address was found - use it and update neighbors. > 6. Periodically check for DHCP server. > > It should be a matter of changing a few scripts. > Why he major distributions not using it ?
I hope the following is not total bullshit, please correct me if I'm wrong... Windows had this problem: when the network was not accissiblesuddenly all the network interfaces were down. this causes major headaches to many programs. Linux (and probably most unixes as well, but I never botherd checking) has this nice loopback interface. Even if you brutally cut the notwork cable, thje network won't be down: the loopbak interface will be live and well. So Windows had to keep this interface "alive" somehow. The result is this wierd configuration method. There are a number of problems: Just one that I can think of: a couple of machines in the range 169.254 can actually start talking to each other before the netwrk starts top get properly configured. This is probably a big loophole that can be used together with a DoS on the dhcp server (take a look at the default and the maximal lease time of the dhcp package). -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
