04-16-2012 10:32 AM - edited 03-21-2019 05:39 AM
021609: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.245(35101) -> 169.254.1.255(5000), 20 packets
021610: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.220(21302) -> 255.255.255.255(21302), 29 packets
021611: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.220(54063) -> 169.254.1.255(5000), 20 packets
021612: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.220(7500) -> 169.254.1.255(7500), 30 packets
021613: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.48(63118) -> 169.254.1.255(5000), 20 packets
021614: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.141(58303) -> 169.254.1.255(5000), 20 packets
021615: Apr 16 17:25:34.071: %SEC-6-IPACCESSLOGP: list 104 denied udp 169.254.1.201(55422) -> 169.254.1.255(5000), 20 packets
UC_560#
can't figure out why I am getting this. Can someone help me in the right direction troubleshoot it. Thanks.
04-16-2012 10:57 AM
Have you ever worked with Cisco routers before ?
You have an access list with loggin enabled, and the system is reporting to you what is happening.
04-16-2012 11:09 AM
yes, I understand that. My question is what is the best way to troubleshoot where the request is coming from ? And what debug to use?
04-16-2012 11:52 AM
These are coming from other customers of your (likely cable) ISP, to the 'automatic IP' broadcast address.
Likely it's uPnP, in any case they can't damage you in any manner, and there is nothing to worry about.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide