Security Incidents mailing list archives
Re: UDP port 137 packets sent to 70.255.224.194 (and to other hosts/nets as well)
From: Pavel Lozhkin <pauel () BALAKOVO RU>
Date: Wed, 30 Aug 2000 09:07:56 +0400
169.254.0.0/16 is reserved for auto-configuration of local addresses in networks where no DHCP server is found[1]. That block is not (or at least should not) be routed over the internet backbones[2]. Any traffic from 169.254.0.0/16 is either from your local network, or forged--and either way, complaining to IANA or ISI is a waste of their time.
Thanks.I did not know it Seems,i have read this in the RFC for the DHCPD and already forget But this traffic is external for me and income from other nets,not mine - it is exactly.This traffic was denied by EXTERNAL firewall with my router. Any ideas ? is it fake UDP source ? -- ** The hedgehog is a proud bird, he does not fly without kick ** Pauel System administrator ICQ UIN 39596913 8990192 Phone (7-84570)-52525 (7-84570)-40658 Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Current thread:
- UDP port 137 packets sent to 70.255.224.194 Felipe Alfaro (Aug 29)
- Re: UDP port 137 packets sent to 70.255.224.194 Paul L Schmehl (Aug 30)
- Re: UDP port 137 packets sent to 70.255.224.194 (and to other hosts/nets as well) Pavel Lozhkin (Aug 30)
- Re: UDP port 137 packets sent to 70.255.224.194 (and to other hosts/nets as well) Daniel S. Riley (Aug 31)
- Re: UDP port 137 packets sent to 70.255.224.194 (and to other hosts/nets as well) Pavel Lozhkin (Aug 31)
- Re: UDP port 137 packets sent to 70.255.224.194 (and to other hosts/nets as well) Daniel S. Riley (Aug 31)
- Re: UDP port 137 packets sent to 70.255.224.194 Jens Hektor (Aug 30)