<div>The 169.254 addresses are not just a Windows thing. That is a scope that is allocated by IANA called the Automatic Private IP Addressing scope. Many things are starting to implement it, windows was just one of the first. It allows someone without networking knowledge to setup a small private network amongst computers and still have them be able to talk without setting up anything in networking (just DHCP.)
</div>
<div> </div>
<div>It can be a pain, especially if you have a slower DHCP server and it ends up triggering APIP before it receives the offer back from the DHCP server. I know that in BSD that is a kernel tunable. I'm pretty sure that Linux would allow the same kind of tuning.
<br><br> </div>
<div><span class="gmail_quote">On 8/23/05, <b class="gmail_sendername">n.d</b> <<a href="mailto:admin@c0wzftp.com">admin@c0wzftp.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">i got that crazy 169 stuff to. (fedora core 4)<br><br><br>[root@datastor ~]# route -n<br>Kernel IP routing table
<br>Destination Gateway Genmask Flags Metric Ref Use<br>Iface<br><a href="http://192.168.0.0">192.168.0.0</a> <a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.255.0">255.255.255.0
</a> U 0 0 0 eth0<br><a href="http://169.254.0.0">169.254.0.0</a> <a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.0.0">255.255.0.0</a> U 0 0 0 eth0<br><a href="http://0.0.0.0">
0.0.0.0</a> <a href="http://192.168.0.1">192.168.0.1</a> <a href="http://0.0.0.0">0.0.0.0</a> UG 0 0 0 eth0<br><br><a href="mailto:ajeffri@loopysite.org">ajeffri@loopysite.org</a> wrote:<br>
<br>>On Tue, Aug 23, 2005 at 07:04:30PM -0500, Stuart Thiessen wrote:<br>><br>><br>>>I do not have any network on <a href="http://169.254.0.0">169.254.0.0</a>. Could it be that all of my<br>>>traffic is going to
<a href="http://169.254.0.0">169.254.0.0</a>? Would that be able to find the<br>>>gateway? If <a href="http://169.254.0.0">169.254.0.0</a> is representing my alias address, then I am<br>>>confused because I did set the alias address with an address local to
<br>>>the <a href="http://192.168.0.0">192.168.0.0</a> network. I can ping it and such with the designated<br>>>192.168.0.xxx address.<br>>><br>>><br>><br>><a href="http://169.254.0.0/16">169.254.0.0/16
</a> is the address range that Windows uses when it can't find an address<br>>via DHCP. I don't know what it's doing in your Linux routing table, however.<br>>Maybe it's a case of the distro trying to be helpful.<br>
><br>>I just ran route -n on a box of mine that has aliases, and they don't show<br>>up there. They will always show up in the output of ifconfig -a as something<br>>like eth0:0 for the first alias, eth0:1 for the second, etc. and the real
<br>>interface as eth0.<br>><br>><br>><br><br><br><br>_______________________________________________<br>Cialug mailing list<br><a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br><a href="http://cialug.org/mailman/listinfo/cialug">
http://cialug.org/mailman/listinfo/cialug</a><br></blockquote></div><br>