On Fri, Oct 13, 2000 at 15:30 +0000, Geordon VanTassle wrote:
Oct 12 22:44:05 moat kernel: martian source 8e3ffea9 for fffffea9, dev eth1 Oct 12 22:44:05 moat kernel: ll header: ff ff ff ff ff ff 00 10 a4 aa da e2 08 00 Oct 12 22:44:05 moat kernel: Packet log: input REJECT eth1 PROTO=17 169.254.63.142:137 169.254.255.255:137 L=96 S=0x00 I=11008 F=0x0000 T=128 (#69)
This is some braindead MS system with a failed DHCP attempt or some other "auto config" (i.e. not knowingly configured) network stuff. Somebody at MS had the bright idea to say "if we don't have / don't get an address, we simply dice us one." That's when they use the IPs you can see above. Watch the "wide" netmask and the broadcast for "the other unconfigured machines"! Seems MS wants to cope with ignorant environments and even run when not setup correctly ... Sadly I couldn't find any reference to where those IPs come from. RFC1918 addresses are explicitely reserved at the registrars. Those MS fallbacks seem not to be. Do they collide in some future time with some other "customer"? Or are they registered and reserved and I'm just too blind to see? And - most important to solve the problem - is there a chance to teach those WinDoze machines the expected behaviour of "when you don't get an address, you don't have one"? I'm sick of seeing those things happen and realizing it's quite difficult to tell which machine has the problem (to go there and fix it) -- since the IP is so strange and out of the local subnet there won't be ARP entries pointing to the MAC of the NIC involved. One has to wait for the Doze user to call and whine "my computer can't see the net" (unless they're used to it and don't complain but boot again, instead). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.