D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: kmiller7351 on February 02, 2015, 12:54:11 AM
-
keeps resetting intermittently. firmware updated 1.23na, comcast, motorola SB6162, win 7 home premium. Worked a month ago with out glitches. Had and still have trying to update sp1 or something like that. went to windows forum and followed adjustments, started getting all types of updates after that but not that one.
As far as this goes did factory reset, unchecked other stuff, changed channels, ect.
INFO] Mon Feb 02 03:30:18 2015 Allowed configuration authentication by IP address 192.168.0.197
[INFO] Mon Feb 02 03:29:12 2015 Blocked incoming TCP connection request from 218.77.79.38:37608 to 98.221.172.192:8081
[INFO] Mon Feb 02 03:28:26 2015 Blocked incoming TCP connection request from 61.160.223.62:6000 to 98.221.172.192:1433
[INFO] Mon Feb 02 03:27:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:26:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:25:43 2015 Blocked incoming TCP connection request from 61.240.144.66:60000 to 98.221.172.192:1158
[INFO] Mon Feb 02 03:25:28 2015 Blocked incoming UDP packet from 23.95.114.90:55518 to 98.221.172.192:1900
[INFO] Mon Feb 02 03:25:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:01 2015 Blocked incoming TCP connection request from 184.105.247.208:55397 to 98.221.172.192:443
[INFO] Mon Feb 02 03:23:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:22:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:22:15 2015 Blocked incoming TCP connection request from 171.123.240.127:56068 to 98.221.172.192:23
[INFO] Mon Feb 02 03:22:12 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:21:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:20:49 2015 Blocked incoming TCP connection request from 89.46.100.26:38243 to 98.221.172.192:9064
[INFO] Mon Feb 02 03:20:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:19:57 2015 Blocked incoming ICMP error message (ICMP type 3) from 182.117.205.35 to 98.221.172.192 as there is no UDP session active between 98.221.172.192:28796 and 182.117.205.35:53
[INFO] Mon Feb 02 03:19:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:58 2015 Blocked incoming TCP packet from 74.125.226.71:80 to 98.221.172.192:35472 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:55 2015 Above message repeated 4 times
[INFO] Mon Feb 02 03:18:20 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as RST:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:11 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:06 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:06 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Above message repeated 5 times
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP connection request from 64.94.18.69:50893 to 98.221.172.192:53755
[INFO] Mon Feb 02 03:17:47 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:39 2015 Blocked outgoing TCP packet from 192.168.0.197:59995 to 64.94.18.73:12975 as PSH:ACK received but there is no active connection
[WARN] Mon Feb 02 03:17:37 2015 A network computer (iPhone) was assigned the IP address of 192.168.0.195.
[INFO] Mon Feb 02 03:17:36 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:36 2015 OFFICE-PC_Network: Wireless system with MAC address 04F7E424A647 secured and linked
[INFO] Mon Feb 02 03:17:36 2015 OFFICE-PC_Network: Wireless system with MAC address 04F7E424A647 associated
[INFO] Mon Feb 02 03:17:36 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:17:26 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:24 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:16 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:14 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:06 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:02 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[WARN] Mon Feb 02 03:16:57 2015 A network computer (008077012E00) was assigned the IP address of 192.168.0.194.
[INFO] Mon Feb 02 03:16:57 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:57 2015 Wireless link is up
[INFO] Mon Feb 02 03:16:56 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:52 2015 Firmware upgrade server wrpd.dlink.com.tw is at IP address 54.214.30.206
[INFO] Mon Feb 02 03:16:52 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:50 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:49 2015 Starting DHCP server
[INFO] Mon Feb 02 03:16:49 2015 Blocked outgoing TCP packet from 192.168.0.197:51406 to 68.87.20.10:993 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:49 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:46 2015 Obtained IP Address using DHCP. IP address is 98.221.172.192
[INFO] Mon Feb 02 03:16:46 2015 Bringing up WAN using DHCP
[INFO] Mon Feb 02 03:16:46 2015 WAN interface cable has been connected
[INFO] Mon Feb 02 03:16:46 2015 LAN interface is up
[INFO] Mon Feb 02 03:16:46 2015 LAN Ethernet Carrier Detected
[INFO] Mon Feb 02 03:16:46 2015 Device initialized
[WARN] Mon Feb 02 03:16:40 2015 Wireless schedule init
[INFO] Mon Feb 02 03:16:40 2015 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
here you go if this helps.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
Please confirm your ISP Modem model #? 6141? 6120? 6180? 6121?
- What Hardware version is your router? Look at sticker under the router case.
- What region are you located?
- Are you wired or wireless connected to the router?
- Has a Factory Reset (http://blog.dlink.com/what-is-a-reset-button-when-should-i-use-it) been performed?
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
>FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
- Was the router working before any firmware updates?
Internet Service Provider and Modem Configurations
- What ISP Modem service link speeds UP and Down do you have?
- Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended. (http://en.wikipedia.org/wiki/CAT6)
I recommend that you have your ISP check the cabling going to the ISP modem, check signal levels going to the ISP modem. For DSL or Fiber service lines, ensure that the ISP is using good working phone or cable lines to the DSL modem and that the phone lines are filtered correctly. For cable Internet, RG-6 coaxial cable is needed, not RG-59. Check for t.v. line splitters and remove them as they can introduce noise on the line and lower the signal going to the ISP modem. I recommend having the ISP service physically check the lines going from the out side to the ISP modem. Connecting to the ISP modem could result in a false positive as the signal to the modem could be just enough to that point then adding on a router, could see problems. The router operation is dependent upon getting good data flow from the ISP modem and the modem is dependent upon getting good signal from the ISP Service.
Wireless Configurations
Links>Wireless Installation Considerations (http://forums.dlink.com/index.php?topic=48327.0) and Managing Signal Congestion (http://forums.dlink.com/index.php?topic=53228.0) and Good Neighbour Policy (http://forums.dlink.com/index.php?topic=10634.0)
- Ensure the default (dlink) SSID name is changed. Ensure that different SSID names are used between each WiFi 2.4/5Ghz radios. Can be anything and not something that's already in use by any neighbouring WiFi routers. Under Setup/Wireless/Manual.
- What wireless modes are you using?
- 2.4Ghz and 5Ghz routers: Try single mode G or N or mixed G and N on 2.4Ghz and single mode N or AC on 5Ghz?
- Channel Width set for Auto 20/40Mhz or try 20Mhz only.
- Try setting a manual Channel (http://en.wikipedia.org/wiki/Wireless_channels) to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear. 13 for EU regions. Try channel 48 or 149 on 5Ghz.
- What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES (http://en.wikipedia.org/wiki/Advanced_Encryption_Standard), so you might want to try TPIK (http://en.wikipedia.org/wiki/Temporal_Key_Integrity_Protocol) only or Auto TPIK and AES.
- What wireless devices do you have connected?
- Ensure any devices with WiFi adapter drivers are updated.
- Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
- Any other WiFi routers in the area that maybe causing interferences? Link> Use InSSIDer (http://www.techspot.com/downloads/5936-inssider.html) to find out. How many? Use v3, its free.
- If you have any of these options, Try turning OFF or ON Short GI (http://www.smallnetbuilder.com/wireless/wireless-features/30969-what-do-80211ns-optional-features-mean-for-you), WLAN Partition, Extra Wireless Protection and HT 20/40 Co-existence if you have it. Also testing with HT20/40Mhz Co-existence enabled will impact results as well. I prefer to use this option OFF. Recommended settings are default. Under Advanced/Advanced Wireless.
Router Placement
Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
3-6' feet minimum safe distance between devices.
Placement on main level floor and central in the building and WELL ventilated is preferred. Not in basements or closets as building materials, or near by electronics devices could interfere or hinder good signal propagation.
http://www.smallnetbuilder.com/wireless/wireless-basics/31083-smallnetbuilders-wireless-faq-the-essentials (http://www.smallnetbuilder.com/wireless/wireless-basics/31083-smallnetbuilders-wireless-faq-the-essentials)
-
Any status on this? ???
keeps resetting intermittently. firmware updated 1.23na, comcast, motorola SB6162, win 7 home premium. Worked a month ago with out glitches. Had and still have trying to update sp1 or something like that. went to windows forum and followed adjustments, started getting all types of updates after that but not that one.
As far as this goes did factory reset, unchecked other stuff, changed channels, ect.
INFO] Mon Feb 02 03:30:18 2015 Allowed configuration authentication by IP address 192.168.0.197
[INFO] Mon Feb 02 03:29:12 2015 Blocked incoming TCP connection request from 218.77.79.38:37608 to 98.221.172.192:8081
[INFO] Mon Feb 02 03:28:26 2015 Blocked incoming TCP connection request from 61.160.223.62:6000 to 98.221.172.192:1433
[INFO] Mon Feb 02 03:27:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:26:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:25:43 2015 Blocked incoming TCP connection request from 61.240.144.66:60000 to 98.221.172.192:1158
[INFO] Mon Feb 02 03:25:28 2015 Blocked incoming UDP packet from 23.95.114.90:55518 to 98.221.172.192:1900
[INFO] Mon Feb 02 03:25:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:52 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52971 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52975 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52974 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:51 2015 Blocked incoming TCP packet from 184.29.106.122:80 to 98.221.172.192:52973 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:24:01 2015 Blocked incoming TCP connection request from 184.105.247.208:55397 to 98.221.172.192:443
[INFO] Mon Feb 02 03:23:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:22:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:22:15 2015 Blocked incoming TCP connection request from 171.123.240.127:56068 to 98.221.172.192:23
[INFO] Mon Feb 02 03:22:12 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:21:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:20:49 2015 Blocked incoming TCP connection request from 89.46.100.26:38243 to 98.221.172.192:9064
[INFO] Mon Feb 02 03:20:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:19:57 2015 Blocked incoming ICMP error message (ICMP type 3) from 182.117.205.35 to 98.221.172.192 as there is no UDP session active between 98.221.172.192:28796 and 182.117.205.35:53
[INFO] Mon Feb 02 03:19:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:58 2015 Blocked incoming TCP packet from 74.125.226.71:80 to 98.221.172.192:35472 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:55 2015 Above message repeated 4 times
[INFO] Mon Feb 02 03:18:20 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as RST:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:20 2015 Blocked incoming TCP packet from 162.150.51.138:993 to 98.221.172.192:58922 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:11 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:06 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:18:06 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Above message repeated 5 times
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP packet from 64.94.18.73:12975 to 98.221.172.192:59995 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:59 2015 Blocked incoming TCP connection request from 64.94.18.69:50893 to 98.221.172.192:53755
[INFO] Mon Feb 02 03:17:47 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:39 2015 Blocked outgoing TCP packet from 192.168.0.197:59995 to 64.94.18.73:12975 as PSH:ACK received but there is no active connection
[WARN] Mon Feb 02 03:17:37 2015 A network computer (iPhone) was assigned the IP address of 192.168.0.195.
[INFO] Mon Feb 02 03:17:36 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:36 2015 OFFICE-PC_Network: Wireless system with MAC address 04F7E424A647 secured and linked
[INFO] Mon Feb 02 03:17:36 2015 OFFICE-PC_Network: Wireless system with MAC address 04F7E424A647 associated
[INFO] Mon Feb 02 03:17:36 2015 Above message repeated 1 times
[INFO] Mon Feb 02 03:17:26 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:24 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:16 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:14 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:06 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:02 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:17:01 2015 Blocked incoming TCP packet from 162.150.51.135:993 to 98.221.172.192:60032 as PSH:ACK received but there is no active connection
[WARN] Mon Feb 02 03:16:57 2015 A network computer (008077012E00) was assigned the IP address of 192.168.0.194.
[INFO] Mon Feb 02 03:16:57 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:57 2015 Wireless link is up
[INFO] Mon Feb 02 03:16:56 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:52 2015 Firmware upgrade server wrpd.dlink.com.tw is at IP address 54.214.30.206
[INFO] Mon Feb 02 03:16:52 2015 Blocked incoming TCP packet from 173.252.79.23:443 to 98.221.172.192:60677 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:50 2015 Blocked incoming TCP packet from 74.125.22.188:5228 to 98.221.172.192:34568 as FIN:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:49 2015 Starting DHCP server
[INFO] Mon Feb 02 03:16:49 2015 Blocked outgoing TCP packet from 192.168.0.197:51406 to 68.87.20.10:993 as PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:49 2015 Blocked incoming TCP packet from 69.171.248.65:443 to 98.221.172.192:55566 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Feb 02 03:16:46 2015 Obtained IP Address using DHCP. IP address is 98.221.172.192
[INFO] Mon Feb 02 03:16:46 2015 Bringing up WAN using DHCP
[INFO] Mon Feb 02 03:16:46 2015 WAN interface cable has been connected
[INFO] Mon Feb 02 03:16:46 2015 LAN interface is up
[INFO] Mon Feb 02 03:16:46 2015 LAN Ethernet Carrier Detected
[INFO] Mon Feb 02 03:16:46 2015 Device initialized
[WARN] Mon Feb 02 03:16:40 2015 Wireless schedule init
[INFO] Mon Feb 02 03:16:40 2015 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
here you go if this helps.