Yahoo Answers is shutting down on May 4th, 2021 (Eastern Time) and beginning April 20th, 2021 (Eastern Time) the Yahoo Answers website will be in read-only mode. There will be no changes to other Yahoo properties or services, or your Yahoo account. You can find more information about the Yahoo Answers shutdown and how to download your data on this help page.
Trending News
Possible DOS attack - Please help!?
My internet has been down now for 4 days and I only see this in my routers log. Is this a DOS attack and how can I prevent it?
Mon, 2013-02-25 15:35:00 - UDP Packet - Source:1.172.195.209,26601 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:35:02 - UDP Packet - Source:81.226.7.9,29982 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:02 - UDP Packet - Source:78.179.58.0,31283 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:09 - TCP Packet - Source:50.72.82.135,63837 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:09 - TCP Packet - Source:101.0.34.140,52317 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:09 - TCP Packet - Source:76.116.182.70,59898 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:09 - TCP Packet - Source:94.173.18.113,62502 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:10 - TCP Packet - Source:68.5.1.164,56170 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:10 - TCP Packet - Source:24.87.59.183,49981 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:10 - TCP Packet - Source:101.160.60.113,50269 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:35:10 - TCP Packet - Source:50.53.2.161,52200 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:11 - TCP Packet - Source:64.229.109.13,54857 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:35:11 - TCP Packet - Source:24.207.108.116,52492 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:35:12 - TCP Packet - Source:79.84.187.108,62571 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:12 - TCP Packet - Source:60.230.231.180,63007 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:12 - TCP Packet - Source:94.173.18.113,62502 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:12 - TCP Packet - Source:108.44.0.59,60063 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:12 - TCP Packet - Source:96.242.71.70,65451 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:13 - TCP Packet - Source:96.240.26.110,60291 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:35:13 - TCP Packet - Source:96.242.71.70,65455 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:13 - TCP Packet - Source:24.87.59.183,49981 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:35:13 - TCP Packet - Source:108.44.0.59,60072 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:58.33.14.93,44528 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:190.92.44.106,18844 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:76.20.32.76,61197 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:80.6.247.106,43821 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:81.205.219.225,62223 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:72.178.219.77,45814 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:67.193.152.131,57727 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:86.156.34.232,1237 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:09 - TCP Packet - Source:76.20.32.76,61200 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:10 - TCP Packet - Source:60.242.73.214,52046 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:10 - TCP Packet - Source:72.178.219.77,33409 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:10 - TCP Packet - Source:174.100.83.238,55877 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:10 - TCP Packet - Source:75.72.137.12,60470 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:10 - TCP Packet - Source:68.5.1.164,48349 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:11 - TCP Packet - Source:174.0.217.147,62455 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:38:11 - TCP Packet - Source:101.98.134.252,49016 Destination:41.132.229.89,56849 - [DOS]
Mon, 2013-02-25 15:38:12 - TCP Packet - Source:77.100.166.67,52178 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:38:12 - TCP Packet - Source:76.174.247.238,51961 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:39:10 - TCP Packet - Source:62.194.1.99,60577 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:39:11 - TCP Packet - Source:207.216.170.188,62965 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:39:11 - TCP Packet - Source:137.147.155.50,59976 Destination:41.132.229.89,26452 - [DOS]
Mon, 2013-02-25 15:39:11 - TCP Packet - Source:121.222.51.49,55939 Destination:41.132.229.89,24670 - [DOS]
Mon, 2013-02-25 15:39:11 - TCP Packet - Source:46.99.12.3,48427 Destination:41.132.229.89,26452 - [DOS]
Thanks but I have restarted my router many times like that before and obtained new IP's every time but internet was still down. Do you know of any software that I can use to protect me from this?
1 Answer
- Anonymous8 years agoFavorite Answer
Change your iP.
Find your current Public iP> http://www.findmyip.org/
Disconnect the power to the modem for 30 minutes> re-power it, and let it 'resolve' the iP with the upstream (iSP) server (that may take a few minutes)> re-check the iP.
If during the power-down your iSP issued the original iP to another customer, you will be given a fresh iP.
If that iP re-issue doesn't happen, you will likely get the original one back (it's called 'sticky').
Repeat the power-down/power-up if necessary.
Note a good firewall (preferably hardware i.e. a NAT router) is mandatory for everyone these days.
Focused or target-specific DoS is rare against home Networks, but not unheard of.
The 'Net is deluged with these probes into the porosity of everyone's iP, from the entire globe. Turn off any notifications/alerts about them or you'll go nuts.