|
Page 1 of 1
|
[ 9 posts ] |
|
| Author |
Message |
|
FriedSushi
Forum Maggott
Joined: Tue Sep 26, 2006 11:00 pm
Posts: 103
Location: Behind you with a gun.
|
 Noob with a Router I'm a noob, just installed my router a month ago, havn't monitered connections, thought it was secure, with a password on it ect... I looked at connected computers and I had four. I only have two computers. I got curious after turning off DHCP Servering of what activity was on my comp when I found this!
OMG was I being DOS'D??????? Like 20 different countries just tried to attack me! Or maybe I'm just a noob and needs to shut up.
Router wrote: 12/23/2006 14:12:31 **UDP Flood Stop** (from WAN Inbound)
12/23/2006 14:12:30 **UDP flood** 221.127.244.30, 19093->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:29 **UDP flood** 219.128.170.93, 14873->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:29 **UDP flood** 216.154.19.161, 16183->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:27 **UDP flood** 60.41.166.79, 19473->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:26 **UDP flood** 88.7.84.8, 26300->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:26 **UDP flood** 222.71.85.216, 62591->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:25 **UDP flood** 85.30.63.13, 800->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:25 **UDP flood** 218.106.94.2, 5246->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:24 **UDP flood** 60.17.55.83, 50904->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:23 **UDP flood** 124.187.185.249, 60586->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:23 **UDP flood** 82.241.163.228, 15874->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:23 **UDP flood** 70.254.118.132, 55097->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:23 **UDP flood** 222.137.126.176, 15999->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:22 **UDP flood** 12.219.81.14, 55459->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:21 **UDP flood** 200.125.125.190, 17719->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:20 **UDP flood** 220.213.53.6, 32768->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:20 **UDP flood** 69.156.120.200, 25897->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:20 **UDP flood** 201.50.7.251, 50881->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:17 **UDP flood** 85.73.10.157, 19791->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:16 **UDP flood** 83.172.79.37, 20304->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:16 **UDP flood** 163.24.234.14, 60473->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:16 **UDP flood** 203.78.110.90, 12484->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:15 **UDP flood** 203.218.207.110, 25787->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:15 **UDP flood** 221.221.249.206, 26205->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:14 **UDP flood** 203.218.19.192, 21190->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:13 **UDP flood** 69.246.204.180, 55398->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:13 **UDP flood** 85.56.77.250, 10418->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:12 **UDP flood** 61.177.29.229, 19443->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:11 **UDP flood** 219.95.164.104, 63376->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:10 **UDP flood** 24.215.50.97, 9824->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:09 **UDP flood** 218.187.101.36, 8511->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:09 **UDP flood** 204.16.210.60, 60861->> 68.204.223.249, 1026 (from WAN Inbound)
12/23/2006 14:12:07 **UDP flood** 220.214.152.132, 64217->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:06 **UDP flood** 193.217.130.169, 16877->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:05 **UDP flood** 217.113.225.9, 23804->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:05 **UDP flood** 88.80.96.19, 30146->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:05 **UDP flood** 189.132.211.75, 19367->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:05 **UDP flood** 59.56.1.234, 9986->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:03 **UDP flood** 61.175.218.238, 17538->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:03 **UDP flood** 82.13.89.227, 26066->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:03 **UDP flood** 70.80.57.108, 1203->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:02 **UDP flood** 86.126.160.141, 19058->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:01 **UDP flood** 81.233.48.13, 48330->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:12:01 **UDP flood** 70.100.179.99, 1501->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:59 **UDP flood** 83.23.120.43, 8767->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:59 **UDP flood** 86.49.100.130, 6881->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:59 **UDP flood** 222.70.58.31, 13888->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:58 **UDP flood** 70.20.63.197, 18943->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:55 **UDP flood** 203.87.211.121, 1317->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:31 **UDP flood** 68.252.216.244, 55815->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:25 **UDP flood** 87.194.15.137, 52732->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:11:20 **UDP flood** 87.194.15.137, 52732->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 14:10:50 **UDP flood** 192.168.2.3, 56300->> 219.128.170.93, 14873 (from WAN Outbound)
12/23/2006 13:57:54 DHCP Client: Receive Ack from 10.110.160.1, 'Lease time'=43200
12/23/2006 13:57:54 DHCP Client: Domain name = cfl.rr.com
12/23/2006 13:57:54 DHCP Client: Send Request, Request IP=xx.xxx.xxx.xxx
12/23/2006 13:56:55 **UDP Flood Stop** (from WAN Inbound)
12/23/2006 13:56:54 **UDP flood** 84.243.94.38, 32459->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:54 **UDP flood** 85.176.90.231, 21870->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:54 **UDP flood** 85.0.236.130, 18720->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:53 **UDP flood** 91.64.158.113, 7150->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:52 **UDP flood** 62.233.239.129, 18027->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 212.54.207.125, 13761->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 85.254.159.2, 17466->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 60.218.162.32, 1501->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 83.213.218.252, 25331->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 220.129.163.237, 59847->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:51 **UDP flood** 83.51.214.115, 18166->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:50 **UDP flood** 59.127.15.131, 14084->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:50 **UDP flood** 89.132.42.12, 27087->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:49 **UDP flood** 70.225.179.205, 51451->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:49 **UDP flood** 85.228.184.78, 10605->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:48 **UDP flood** 81.233.48.13, 48330->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:47 **UDP flood** 81.15.216.54, 18229->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:47 **UDP flood** 88.88.154.99, 10839->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:47 **UDP flood** 219.68.98.164, 21588->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:46 **UDP flood** 202.103.225.93, 9437->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:46 **UDP flood** 129.57.9.57, 13144->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:44 **UDP flood** 87.194.15.137, 51885->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:44 **UDP flood** 84.155.225.246, 11220->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:43 **UDP flood** 221.2.63.71, 62140->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:43 **UDP flood** 222.191.248.84, 49015->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:42 **UDP flood** 87.80.208.234, 18085->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:41 **UDP flood** 82.25.142.205, 9558->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:41 **UDP flood** 87.210.0.77, 15323->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:41 **UDP flood** 125.24.168.48, 15073->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:40 **UDP flood** 89.59.94.150, 61126->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:40 **UDP flood** 221.222.204.108, 25975->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:38 **UDP flood** 217.216.160.87, 49855->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:38 **UDP flood** 59.50.164.221, 11867->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:37 **UDP flood** 83.142.78.51, 13184->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:37 **UDP flood** 65.6.205.35, 6881->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:37 **UDP flood** 90.194.197.237, 17543->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:36 **UDP flood** 71.113.51.14, 16820->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:36 **UDP flood** 212.72.25.10, 35597->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:36 **UDP flood** 84.68.244.240, 55399->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:35 **UDP flood** 88.3.155.238, 18813->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:35 **UDP flood** 86.56.31.12, 8010->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:35 **UDP flood** 24.37.219.215, 60348->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:35 **UDP flood** 222.67.186.249, 26113->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:34 **UDP flood** 62.65.242.161, 16869->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:34 **UDP flood** 83.31.138.147, 13501->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:33 **UDP flood** 59.105.26.215, 21279->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:32 **UDP flood** 84.196.162.41, 10888->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:32 **UDP flood** 218.97.250.194, 18181->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:31 **UDP flood** 219.79.229.80, 14854->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:30 **UDP flood** 86.207.39.121, 12429->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:28 **UDP flood** 219.46.184.108, 10062->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:27 **UDP flood** 81.105.128.176, 8674->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:26 **UDP flood** 87.122.49.166, 16478->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:26 **UDP flood** 142.167.117.7, 15961->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:26 **UDP flood** 201.19.38.243, 11165->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:25 **UDP flood** 220.238.84.94, 14606->> 192.168.2.3, 56300 (from WAN Inbound)
12/23/2006 13:56:25 **UDP flood** 82.210.180.221, 9522->> 192.168.2.3, 56300 (from WAN Inbound)
log ends here i don't know what kind of information happened earlier than this for the past 2 months.
What is this "Lease Time"?
I was trying to hook up my roomates computer to my network "in which I've succedded and it says his computer is connected to mine yet i cannot access my computer or the internet via his. I'm confused and afraid of "Black-hats"
Maybe this is why my modem has soooo many dissconnects. Maybe this is why sometimes while playing a game or surfing or something my modem disconns. I have a high modem reset rate said the guy at RoadRunner Tech support.
|
| Mon Dec 25, 2006 1:51 am |
|
|
|
FriedSushi
Forum Maggott
Joined: Tue Sep 26, 2006 11:00 pm
Posts: 103
Location: Behind you with a gun.
|
I disconnect my router and connect directly to the internet via my modem, and turn on my uTorrent.
(i get incredible speed differences, as with the router nothing would download at all except for one at a time sometimes)
and i woke up to find my PC had restarted. I have no clue why it's restarted but it restareted with ZoneAlarm (which i had disabled and not running while i as connected to uTorrent until the computer restarted.
I am getting around 40 alerts from Zone Alarm a minute now saying it's blocked me from an intruder all the numbers look suspiciously like the ip's above. From random countries (france, UK, china, hong kong, california, ecttt....)
here are a handfull
59.56.208.162
82.216.100.53
217.232.56.50
24.89.112.66
222.180.212.25
202.122.192.129
142.169.164.12
c-24-10-93-201.hsd1.ca.comcast.net 24.10.93.201
89.132.44.184
Am i being ddossed? attacked? Could someone have installed somethingin my computer while it was directly connected?
My router wouldn't work last night for some reason. so that's why i connected directly.,
|
| Mon Dec 25, 2006 9:39 am |
|
|
|
Spyda
Game Server Admin
Joined: Thu Apr 29, 2004 11:00 pm
Posts: 5609
Location: Yo mama's room, Bitch!
|
Nigga stealin your interwebz!
_________________ icemaN: i was droppin wards like they were turds
|
| Mon Dec 25, 2006 1:14 pm |
|
|
|
AltheKiller
[n00b] Member
Joined: Fri Oct 20, 2006 11:00 pm
Posts: 1116
Location: Houston, TX
|
Spyda wrote: Nigga stealin your interwebz!
_________________
If we were given just one word of information in our entire history, how we'd treasure it! How we'd pore over every syllable, divining its meaning, arguing its importance; how we'd examine it and wring every lesson we could from it. Yet today we have trillions of words, tidal waves of information, and the smallest detail of every action our government and businesses take is easily available to us at the touch of a button. And yet... We ignore it, and learn nothing from it.
One day, we'll die of voluntary ignorance.
|
| Mon Dec 25, 2006 2:19 pm |
|
|
|
FriedSushi
Forum Maggott
Joined: Tue Sep 26, 2006 11:00 pm
Posts: 103
Location: Behind you with a gun.
|
Thanks for your help guys.
|
| Mon Dec 25, 2006 8:32 pm |
|
|
|
Ryan
[n00b] Member
Joined: Sat Oct 22, 2005 11:00 pm
Posts: 2436
|
Wireless?
_________________
|
| Mon Dec 25, 2006 11:13 pm |
|
|
|
G_I_Joe
[n00b] Member
Joined: Wed Sep 07, 2005 11:00 pm
Posts: 1798
Location: NJ
|
ill try to actually post something usefull...
first...disconnect your router from the net...but leave it plugged in and connected to your computer...
then go in and see if you can change its IP address, and maybe change the password just to be safe..
_________________ [URL=http://www.habamon.com/monster/extra] 
Help me raise my Habamon![/URL]
|
| Fri Dec 29, 2006 8:06 pm |
|
|
|
Tucker
n00bfest Ancient, Senior Admin
Joined: Sun Aug 07, 2005 11:00 pm
Posts: 2629
Location: Cocoa, Florida
|
Not really sure what the problem is. DOS seems possible, but I'm not sure why someone would do it to you specifically.
I know connecting directly to the modem is a bad idea since there is no firewall between you and the interwebs.
As for what GIJoe said, roadrunner (the modem) assigns you an IP address, not the router. I doubt that would change anything.
_________________R.I.P.  Stanislav "Lord_Macros" Krivosheev
The noblest of noble.
|
| Fri Dec 29, 2006 8:54 pm |
|
|
|
MrS0X
Supreme Spammer
Joined: Sat Sep 09, 2006 11:00 pm
Posts: 1335
Location: Laredo, Texas
|
i think he was suggesting the router conencted because u can see the modem actual ip in the router status screen, lease time could be tied to dhcp lease time which is your ip basicly
|
| Sat Dec 30, 2006 10:51 pm |
|
|
|
|
|
Page 1 of 1
|
[ 9 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 7 guests |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
|
|
