D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: BaronRon on July 21, 2010, 11:04:38 AM
-
Dear Forum,
I've never posted on here before but I'm at a complete loss with my current problem. This one has been a real doozy for me.
I used to have a Linksys WRT54GC and life was good for a time (~2 years). Then about 5 weeks ago my wireless connection started to become intermittent. I figured the old gal had finally petered out. So I bought a Linksys WRT610N to replace the old one. For a time too, order was restored (~1 month). However, I started to have the same problems again. So I returned my Linksys router and bought a brand-spanking new D-LINK DGL-4500 router thinking that If anything was going to have strong signal it would be this puppy. Unfortunately, I'm still getting the same intermittent failure. Its actually been getting worse!
I read all the forum posts across all the Google links. I've updated my firmware to 1.22NA, I've tried all the channels over the last few days I've tried 5Ghz and 2.4Ghz, I've increased and decreased my transmission strength, I have gone with WEP, WAP, and no security (only briefly). I have disconnected all cordless phones, enacted a moratorium on microwave use, and prayed to the wireless router gods for assistance. All to no avail. By the way, my wired internet connection through each router has never faltered.
I have observed many logs which show my router constantly booting up and then going down. I will paste this below. In addition, I live in a apartment building and I started to monitor the APs in the building to try to determine which channels might be less noisy. I have 26 detectable APs! I have also attached an image of a 5 minute recording. Interestingly, I observed 2 very strong signals oscillating back and forth. I have never noticed these strong signals before all my problems occurred but I don’t know if that’s just coincidence.
Please dear forum, I humbly request your guidance and wisdom.
http://yfrog.com/42wifilogj (http://yfrog.com/42wifilogj)
Log
[INFO] Tue Jul 20 22:29:51 2010 Wireless link is down
[INFO] Tue Jul 20 22:29:51 2010 Wireless restart
[INFO] Tue Jul 20 22:29:51 2010 Disconnect all stations
[INFO] Tue Jul 20 22:29:51 2010 All Wireless shut down
[INFO] Tue Jul 20 22:29:49 2010 Wireless restart
[INFO] Tue Jul 20 22:29:47 2010 Wireless link is up
[INFO] Tue Jul 20 22:29:46 2010 Log viewed by IP address 192.168.0.199
[INFO] Tue Jul 20 22:29:44 2010 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Tue Jul 20 22:29:25 2010 Wireless link is down
[INFO] Tue Jul 20 22:29:25 2010 Wireless restart
[INFO] Tue Jul 20 22:29:25 2010 Disconnect all stations
[INFO] Tue Jul 20 22:29:25 2010 All Wireless shut down
[INFO] Tue Jul 20 22:29:23 2010 Wireless restart
[INFO] Tue Jul 20 22:29:22 2010 Blocked incoming TCP connection request from 76.120.52.108:64329 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:29:21 2010 Wireless link is up
[INFO] Tue Jul 20 22:29:16 2010 Blocked incoming TCP connection request from 76.120.52.108:64329 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:29:13 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:29:10 2010 Blocked incoming UDP packet from 90.200.53.2:64719 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:28:58 2010 Wireless link is down
[INFO] Tue Jul 20 22:28:58 2010 Wireless restart
[INFO] Tue Jul 20 22:28:58 2010 Disconnect all stations
[INFO] Tue Jul 20 22:28:58 2010 All Wireless shut down
[INFO] Tue Jul 20 22:28:56 2010 Wireless restart
[INFO] Tue Jul 20 22:28:54 2010 Wireless link is up
[INFO] Tue Jul 20 22:28:31 2010 Wireless link is down
[INFO] Tue Jul 20 22:28:31 2010 Wireless restart
[INFO] Tue Jul 20 22:28:31 2010 Disconnect all stations
[INFO] Tue Jul 20 22:28:31 2010 All Wireless shut down
[INFO] Tue Jul 20 22:28:29 2010 Wireless restart
[INFO] Tue Jul 20 22:28:27 2010 Wireless link is up
[INFO] Tue Jul 20 22:28:25 2010 Blocked incoming TCP connection request from 76.120.52.108:64180 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:28:19 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:28:18 2010 Blocked incoming UDP packet from 89.230.126.212:25392 to xx.xx.x.xx:33479
[INFO] Tue Jul 20 22:28:16 2010 Blocked incoming TCP connection request from 76.120.52.108:64180 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:28:05 2010 Wireless link is down
[INFO] Tue Jul 20 22:28:05 2010 Wireless restart
[INFO] Tue Jul 20 22:28:05 2010 Disconnect all stations
[INFO] Tue Jul 20 22:28:05 2010 All Wireless shut down
[INFO] Tue Jul 20 22:28:03 2010 Wireless restart
[INFO] Tue Jul 20 22:28:01 2010 Wireless link is up
[INFO] Tue Jul 20 22:27:38 2010 Wireless link is down
[INFO] Tue Jul 20 22:27:38 2010 Wireless restart
[INFO] Tue Jul 20 22:27:38 2010 Disconnect all stations
[INFO] Tue Jul 20 22:27:38 2010 All Wireless shut down
[INFO] Tue Jul 20 22:27:36 2010 Wireless restart
[INFO] Tue Jul 20 22:27:34 2010 Wireless link is up
[INFO] Tue Jul 20 22:27:31 2010 Blocked incoming UDP packet from 123.50.44.52:12321 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:27:29 2010 Blocked incoming TCP connection request from 76.120.52.108:64041 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:27:28 2010 Blocked incoming UDP packet from 77.18.23.93:30505 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:27:23 2010 Blocked incoming TCP connection request from 76.120.52.108:64041 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:27:20 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:27:15 2010 Blocked incoming UDP packet from 119.240.75.163:26096 to xx.xx.x.xx:33479
[INFO] Tue Jul 20 22:27:12 2010 Wireless link is down
[INFO] Tue Jul 20 22:27:12 2010 Wireless restart
[INFO] Tue Jul 20 22:27:12 2010 Disconnect all stations
[INFO] Tue Jul 20 22:27:12 2010 All Wireless shut down
[INFO] Tue Jul 20 22:27:10 2010 Wireless restart
[INFO] Tue Jul 20 22:27:08 2010 Wireless link is up
[INFO] Tue Jul 20 22:26:57 2010 Blocked incoming UDP packet from 59.115.242.24:9206 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:26:50 2010 Blocked incoming UDP packet from 219.126.224.79:13558 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:26:45 2010 Wireless link is down
[INFO] Tue Jul 20 22:26:45 2010 Wireless restart
[INFO] Tue Jul 20 22:26:45 2010 Disconnect all stations
[INFO] Tue Jul 20 22:26:45 2010 All Wireless shut down
[INFO] Tue Jul 20 22:26:43 2010 Wireless restart
[INFO] Tue Jul 20 22:26:41 2010 Wireless link is up
[INFO] Tue Jul 20 22:26:34 2010 Blocked incoming TCP connection request from 76.120.52.108:63899 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:26:28 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:26:27 2010 Blocked incoming UDP packet from 89.218.82.141:10076 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:26:25 2010 Blocked incoming TCP connection request from 76.120.52.108:63899 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:26:18 2010 Wireless link is down
[INFO] Tue Jul 20 22:26:18 2010 Wireless restart
[INFO] Tue Jul 20 22:26:18 2010 Disconnect all stations
[INFO] Tue Jul 20 22:26:18 2010 All Wireless shut down
[INFO] Tue Jul 20 22:26:16 2010 Wireless restart
[INFO] Tue Jul 20 22:26:14 2010 Wireless link is up
[INFO] Tue Jul 20 22:26:03 2010 Blocked incoming UDP packet from 115.61.98.196:11252 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:55 2010 Blocked incoming UDP packet from 83.44.227.41:21246 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:52 2010 Wireless link is down
[INFO] Tue Jul 20 22:25:52 2010 Wireless restart
[INFO] Tue Jul 20 22:25:52 2010 Disconnect all stations
[INFO] Tue Jul 20 22:25:52 2010 All Wireless shut down
[INFO] Tue Jul 20 22:25:50 2010 Wireless restart
[INFO] Tue Jul 20 22:25:48 2010 Wireless link is up
[INFO] Tue Jul 20 22:25:38 2010 Blocked incoming TCP connection request from 76.120.52.108:63758 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:25:34 2010 Blocked incoming UDP packet from 95.133.221.107:63743 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:32 2010 Blocked incoming TCP connection request from 76.120.52.108:63758 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:25:29 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:25:25 2010 Wireless link is down
[INFO] Tue Jul 20 22:25:25 2010 Wireless restart
[INFO] Tue Jul 20 22:25:25 2010 Disconnect all stations
[INFO] Tue Jul 20 22:25:25 2010 All Wireless shut down
[INFO] Tue Jul 20 22:25:23 2010 Wireless restart
[INFO] Tue Jul 20 22:25:21 2010 Wireless link is up
[INFO] Tue Jul 20 22:25:15 2010 Blocked incoming UDP packet from 121.203.18.42:12132 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:06 2010 Blocked incoming UDP packet from 110.1.96.219:10741 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:03 2010 Blocked incoming UDP packet from 84.253.224.111:12646 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:25:01 2010 Blocked incoming UDP packet from 90.3.214.6:20870 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:59 2010 Blocked incoming UDP packet from 123.112.114.99:29479 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:58 2010 Wireless link is down
[INFO] Tue Jul 20 22:24:58 2010 Wireless restart
[INFO] Tue Jul 20 22:24:58 2010 Disconnect all stations
[INFO] Tue Jul 20 22:24:58 2010 All Wireless shut down
[INFO] Tue Jul 20 22:24:56 2010 Wireless restart
[INFO] Tue Jul 20 22:24:54 2010 Wireless link is up
[INFO] Tue Jul 20 22:24:46 2010 Blocked incoming UDP packet from 78.90.26.125:13774 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:41 2010 Blocked incoming TCP connection request from 76.120.52.108:63610 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:24:32 2010 Above message repeated 2 times
[INFO] Tue Jul 20 22:24:32 2010 Wireless link is down
[INFO] Tue Jul 20 22:24:31 2010 Wireless restart
[INFO] Tue Jul 20 22:24:31 2010 Disconnect all stations
[INFO] Tue Jul 20 22:24:31 2010 All Wireless shut down
[INFO] Tue Jul 20 22:24:29 2010 Wireless restart
[INFO] Tue Jul 20 22:24:27 2010 Wireless link is up
[INFO] Tue Jul 20 22:24:14 2010 Blocked incoming UDP packet from 78.35.223.187:38944 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:12 2010 Blocked incoming UDP packet from 92.62.224.7:65279 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:09 2010 Blocked incoming UDP packet from 122.175.77.68:10001 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:24:05 2010 Wireless link is down
[INFO] Tue Jul 20 22:24:05 2010 Wireless restart
[INFO] Tue Jul 20 22:24:05 2010 Disconnect all stations
[INFO] Tue Jul 20 22:24:05 2010 All Wireless shut down
[INFO] Tue Jul 20 22:24:03 2010 Wireless restart
[INFO] Tue Jul 20 22:24:01 2010 Wireless link is up
[INFO] Tue Jul 20 22:23:47 2010 Blocked incoming UDP packet from 206.212.229.139:1201 to xx.xx.x.xx:33479
[INFO] Tue Jul 20 22:23:45 2010 Blocked incoming TCP connection request from 76.120.52.108:63470 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:23:39 2010 Above message repeated 1 times
[INFO] Tue Jul 20 22:23:38 2010 Wireless link is down
[INFO] Tue Jul 20 22:23:38 2010 Wireless restart
[INFO] Tue Jul 20 22:23:38 2010 Disconnect all stations
[INFO] Tue Jul 20 22:23:38 2010 All Wireless shut down
[INFO] Tue Jul 20 22:23:36 2010 Blocked incoming TCP connection request from 76.120.52.108:63470 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:23:36 2010 Wireless restart
[INFO] Tue Jul 20 22:23:34 2010 Wireless link is up
[INFO] Tue Jul 20 22:23:24 2010 Blocked incoming UDP packet from 93.146.184.45:57541 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:23:13 2010 Blocked incoming UDP packet from 77.202.210.61:24747 to xx.xx.x.xx:33479
[INFO] Tue Jul 20 22:23:11 2010 Wireless link is down
[INFO] Tue Jul 20 22:23:11 2010 Wireless restart
[INFO] Tue Jul 20 22:23:11 2010 Disconnect all stations
[INFO] Tue Jul 20 22:23:11 2010 All Wireless shut down
[INFO] Tue Jul 20 22:23:09 2010 Wireless restart
[INFO] Tue Jul 20 22:23:09 2010 Blocked incoming UDP packet from 89.133.91.28:13511 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:23:07 2010 Wireless link is up
[INFO] Tue Jul 20 22:22:51 2010 Blocked incoming TCP connection request from 76.120.52.108:63343 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:22:49 2010 Blocked incoming UDP packet from 117.47.160.78:19254 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:22:45 2010 Blocked incoming TCP connection request from 76.120.52.108:63343 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:22:45 2010 Wireless link is down
[INFO] Tue Jul 20 22:22:45 2010 Wireless restart
[INFO] Tue Jul 20 22:22:45 2010 Disconnect all stations
[INFO] Tue Jul 20 22:22:45 2010 All Wireless shut down
[INFO] Tue Jul 20 22:22:43 2010 Wireless restart
[INFO] Tue Jul 20 22:22:42 2010 Blocked incoming TCP connection request from 76.120.52.108:63343 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:22:42 2010 Blocked incoming UDP packet from 220.215.160.109:18206 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:22:41 2010 Wireless link is up
[INFO] Tue Jul 20 22:22:38 2010 Blocked incoming UDP packet from 80.54.100.149:25468 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:22:30 2010 Blocked incoming UDP packet from 92.133.30.115:9570 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:22:18 2010 Wireless link is down
[INFO] Tue Jul 20 22:22:18 2010 Wireless restart
[INFO] Tue Jul 20 22:22:18 2010 Disconnect all stations
[INFO] Tue Jul 20 22:22:18 2010 All Wireless shut down
[INFO] Tue Jul 20 22:22:16 2010 Wireless restart
[INFO] Tue Jul 20 22:22:14 2010 Wireless link is up
[INFO] Tue Jul 20 22:22:06 2010 Blocked incoming UDP packet from 187.58.182.83:1207 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:56 2010 Blocked incoming UDP packet from 93.80.72.112:27659 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:55 2010 Blocked incoming TCP connection request from 76.120.52.108:63195 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:21:52 2010 Wireless link is down
[INFO] Tue Jul 20 22:21:52 2010 Wireless restart
[INFO] Tue Jul 20 22:21:52 2010 Disconnect all stations
[INFO] Tue Jul 20 22:21:52 2010 All Wireless shut down
[INFO] Tue Jul 20 22:21:50 2010 Wireless restart
[INFO] Tue Jul 20 22:21:49 2010 Blocked incoming TCP connection request from 76.120.52.108:63195 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:21:48 2010 Wireless link is up
[INFO] Tue Jul 20 22:21:46 2010 Blocked incoming TCP connection request from 76.120.52.108:63195 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:21:43 2010 Blocked incoming UDP packet from 89.136.107.116:25970 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:37 2010 Blocked incoming UDP packet from 77.85.123.133:23209 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:25 2010 Wireless link is down
[INFO] Tue Jul 20 22:21:25 2010 Wireless restart
[INFO] Tue Jul 20 22:21:25 2010 Disconnect all stations
[INFO] Tue Jul 20 22:21:25 2010 All Wireless shut down
[INFO] Tue Jul 20 22:21:24 2010 Blocked incoming UDP packet from 218.165.29.5:8720 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:23 2010 Wireless restart
[INFO] Tue Jul 20 22:21:21 2010 Wireless link is up
[INFO] Tue Jul 20 22:21:18 2010 Blocked incoming UDP packet from 93.51.127.58:16562 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:03 2010 Blocked incoming UDP packet from 92.249.96.41:52117 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:21:03 2010 Blocked incoming UDP packet from 58.114.87.153:24497 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:20:58 2010 Wireless link is down
[INFO] Tue Jul 20 22:20:58 2010 Wireless restart
[INFO] Tue Jul 20 22:20:58 2010 Disconnect all stations
[INFO] Tue Jul 20 22:20:58 2010 All Wireless shut down
[INFO] Tue Jul 20 22:20:57 2010 Blocked incoming TCP connection request from 76.120.52.108:63044 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:20:56 2010 Wireless restart
[INFO] Tue Jul 20 22:20:54 2010 Wireless link is up
[INFO] Tue Jul 20 22:20:51 2010 Blocked incoming TCP connection request from 76.120.52.108:63044 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:20:48 2010 Blocked incoming UDP packet from 94.28.174.205:18831 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:20:48 2010 Blocked incoming TCP connection request from 76.120.52.108:63044 to xx.xx.x.xx:11594
[INFO] Tue Jul 20 22:20:47 2010 Blocked incoming UDP packet from 209.203.56.250:2055 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:20:47 2010 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Tue Jul 20 22:20:46 2010 Blocked incoming UDP packet from 61.217.194.171:14012 to xx.xx.x.xx:26774
[INFO] Tue Jul 20 22:20:43 2010 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Tue Jul 20 22:20:39 2010 WAN interface speed measurement completed. Upstream speed is 724 kbps
[INFO] Tue Jul 20 22:20:32 2010 Wireless link is down
[INFO] Tue Jul 20 22:20:32 2010 Wireless restart
[INFO] Tue Jul 20 22:20:32 2010 Disconnect all stations
[INFO] Tue Jul 20 22:20:32 2010 All Wireless shut down
[INFO] Tue Jul 20 22:20:29 2010 Wireless restart
[INFO] Tue Jul 20 22:20:27 2010 Wireless link is up
[INFO] Tue Jul 20 22:20:05 2010 Wireless link is down
[INFO] Tue Jul 20 22:20:05 2010 Wireless restart
[INFO] Tue Jul 20 22:20:05 2010 Disconnect all stations
[INFO] Tue Jul 20 22:20:05 2010 All Wireless shut down
[INFO] Tue Jul 20 22:20:03 2010 Wireless restart
[INFO] Tue Jul 20 22:20:01 2010 Estimating speed of WAN interface
[INFO] Tue Jul 20 22:20:01 2010 PPP network up with IP Address xx.xx.x.xx
[INFO] Tue Jul 20 22:20:01 2010 Wireless link is up
[INFO] Tue Jul 20 22:20:00 2010 LCP sets local options: ACCM: 00000000, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Tue Jul 20 22:20:00 2010 LCP sets remote auth: C023
[INFO] Tue Jul 20 22:20:00 2010 LCP sets remote options: ACCM: FFFFFFFF, ACFC: 1, PFC: 0, MRU: 1492
[INFO] Tue Jul 20 22:20:00 2010 Established INTERNET PPPoE connection, session id 7108
[INFO] Tue Jul 20 22:20:00 2010 Issuing request for offer for INTERNET PPPoE Session
[INFO] Tue Jul 20 22:20:00 2010 Offer of service [any] accepted for INTERNET PPPoE Session
[INFO] Tue Jul 20 22:20:00 2010 Discovering PPPoE servers for INTERNET PPPoE Session
[INFO] Tue Jul 20 22:20:00 2010 Trying to establish INTERNET PPPoE connection
[INFO] Tue Jul 20 22:20:00 2010 Attempting to start WAN connection on-demand
[INFO] Tue Jul 20 22:19:53 2010 Starting DHCP server
[INFO] Tue Jul 20 22:19:50 2010 Bringing up WAN using PPPoE
[INFO] Tue Jul 20 22:19:50 2010 WAN interface cable has been connected
[INFO] Tue Jul 20 22:19:50 2010 LAN interface is up
[INFO] Tue Jul 20 22:19:50 2010 LAN Ethernet Carrier Detected
[INFO] Tue Jul 20 22:19:50 2010 Device initialized
[WARN] Tue Jul 20 22:19:44 2010 Wireless schedule init
[INFO] Tue Jul 20 22:19:44 2010 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
-
Looks like this is interference due to the fact that you seem to be around numerous other APs and some using the same channel. Wow, how interested. Have you tried going thru all the channels and see if you can get away from the commonly used ones? How about trying G mode only at 2.4Ghz with WPA2 and then start trying different channels. Try 11 first. Then channel 1.
I might try turning off the following as a test, WISH, WiFi Proctected Setup and Short GI. You could enable WLAN Partition and see if that does anything.
Seems like that if the linksys was having problems and the DLink is exhibiting the same problems, really feel this is interference caused.
Let us know how it goes.
-
Hi Furry,
Thanks for your reply. Unforunately, I'm still getting intermittent connections. Is there anything else I can try? Can I link routers in parallel to boost my signal?
Thanks for all your help!
-
I would do this. do a factory reset on the 4500, have only pc PC connected. Get the wireless for N mode only a 2.4Ghz, WPA2 or open for testing. Turn off all other wireless devices including any house wireless phones if you have them. Connect and see if you get any stable connections. You might have to run thru the channel as well. Are you on DSL or Cable?
-
This is driving me crazy! Nothing seems to work! Even the factory reset and n-mode only. I'm on DSL. My wired connection is flawless.
-
I'm seeing this error in my logs:
************: Wireless system with MAC address ************* disconnected for reason: Received Deauthentication
Is that normal?
-
Does your DSL modem have a router and wireless as well? It's recommended that if this is so, you have your ISP bridge and put the DSL modem into transparency and let the 4500 router so all the routing functions.
What happens if you don't use any security on the WiFi? Same thing?
I'm also concerned that this unit could be bad. I would contact DLink and see. There just could be a bad wireless section in the 4500.
-
Hi Furry,
I spoke with my neighbors and they are experience wi-fi connection troubles too at the same time as it happend to me. I'm wondering what it means if its more wide spread?
Also, take a look at my log over the last few minutes. Does that seem normal to you?
---
[INFO] Wed Jul 21 04:57:48 2010 Blocked incoming TCP connection request from 96.229.3.98:2372 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:46 2010 Blocked incoming TCP connection request from 41.174.54.156:1575 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:46 2010 Blocked incoming TCP connection request from 187.108.97.193:56408 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:45 2010 Blocked incoming TCP connection request from 88.238.44.26:4872 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:44 2010 Blocked incoming TCP connection request from 79.207.119.91:57947 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:43 2010 Blocked incoming TCP connection request from 41.174.54.156:1575 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:42 2010 Blocked incoming TCP packet from 186.44.67.168:53165 to xx.xx.x.xxx:6882 as RST received but there is no active connection
[INFO] Wed Jul 21 04:57:42 2010 Blocked incoming TCP connection request from 96.229.3.98:2372 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:42 2010 Blocked incoming UDP packet from 189.26.185.132:56249 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:40 2010 Blocked incoming TCP connection request from 187.108.97.193:56408 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:39 2010 Blocked incoming TCP connection request from 41.174.54.156:1575 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:39 2010 Blocked incoming TCP connection request from 88.238.44.26:4872 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:39 2010 Blocked incoming TCP connection request from 96.229.3.98:2372 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:38 2010 Blocked incoming TCP connection request from 79.207.119.91:57947 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:37 2010 Blocked incoming TCP connection request from 187.108.97.193:56408 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:36 2010 Blocked incoming TCP connection request from 88.238.44.26:4872 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:36 2010 Blocked incoming UDP packet from 189.26.185.132:56249 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:35 2010 Blocked incoming TCP connection request from 79.207.119.91:57947 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:31 2010 Blocked incoming UDP packet from 189.26.185.132:56249 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:31 2010 Blocked incoming TCP connection request from 86.80.128.126:58106 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:29 2010 Blocked incoming TCP connection request from 79.48.211.133:1032 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:29 2010 Blocked incoming UDP packet from 77.30.14.105:49863 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:25 2010 Blocked incoming TCP connection request from 187.108.97.193:56267 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:23 2010 Blocked incoming TCP connection request from 79.48.211.133:1032 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:23 2010 Blocked incoming TCP connection request from 200.116.155.167:58072 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:22 2010 Blocked incoming TCP connection request from 92.130.219.196:4063 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:20 2010 Blocked incoming TCP connection request from 79.48.211.133:1032 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:19 2010 Blocked incoming TCP connection request from 187.108.97.193:56267 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:18 2010 Blocked incoming TCP connection request from 200.116.155.167:58072 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:16 2010 Blocked incoming TCP connection request from 86.80.128.126:58106 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:16 2010 Blocked incoming TCP connection request from 92.130.219.196:4063 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:16 2010 Blocked incoming UDP packet from 93.141.87.15:53154 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:16 2010 Blocked incoming TCP connection request from 187.108.97.193:56267 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:16 2010 Blocked incoming TCP connection request from 109.64.8.34:3592 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:15 2010 Blocked incoming TCP connection request from 24.224.148.100:55253 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:14 2010 Blocked incoming TCP connection request from 200.116.155.167:58072 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:13 2010 Blocked incoming TCP connection request from 92.130.219.196:4063 to xx.xx.x.xxx:59228
[INFO] Wed Jul 21 04:57:12 2010 Blocked incoming TCP connection request from 86.80.128.126:58106 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:11 2010 Above message repeated 1 times
[INFO] Wed Jul 21 04:57:10 2010 Blocked incoming TCP connection request from 109.64.8.34:3592 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:10 2010 Blocked incoming TCP connection request from 74.133.135.253:1605 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:09 2010 Blocked incoming TCP connection request from 117.199.129.56:61396 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:06 2010 Blocked incoming TCP connection request from 109.64.8.34:3592 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:05 2010 Blocked incoming UDP packet from 187.27.31.227:47738 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:04 2010 Blocked incoming TCP connection request from 74.133.135.253:1605 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:04 2010 Blocked incoming TCP connection request from 74.235.90.50:54066 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:03 2010 Blocked incoming TCP connection request from 189.107.47.130:64533 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:03 2010 Blocked incoming TCP connection request from 189.12.180.8:55184 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:03 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:03 2010 Blocked incoming TCP connection request from 117.199.129.56:61396 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:02 2010 Blocked incoming TCP connection request from 24.245.75.160:60544 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:01 2010 Blocked incoming TCP connection request from 74.133.135.253:1605 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:57:00 2010 Blocked incoming TCP connection request from 117.199.129.56:61396 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:59 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:58 2010 Blocked incoming TCP connection request from 187.67.148.82:49519 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:57 2010 Blocked incoming TCP connection request from 74.235.90.50:54066 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:57 2010 Blocked incoming TCP connection request from 189.12.180.8:55184 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:57 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:57 2010 Blocked incoming UDP packet from 75.23.229.129:58360 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:56 2010 Blocked incoming TCP connection request from 24.245.75.160:60544 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:56 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:55 2010 Blocked incoming TCP connection request from 74.235.90.50:54066 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:55 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:54 2010 Blocked incoming TCP connection request from 189.12.180.8:55184 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:54 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:53 2010 Blocked incoming TCP connection request from 24.245.75.160:60544 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:53 2010 Blocked incoming TCP connection request from 217.42.164.23:54779 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:52 2010 Above message repeated 1 times
[INFO] Wed Jul 21 04:56:50 2010 Blocked incoming TCP connection request from 41.174.54.156:1402 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:48 2010 Blocked incoming TCP connection request from 117.197.145.150:54845 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:48 2010 Blocked incoming TCP connection request from 189.26.213.182:52890 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:44 2010 Blocked incoming TCP connection request from 186.44.67.168:55433 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:44 2010 Blocked incoming TCP connection request from 70.27.47.126:63061 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:43 2010 Blocked incoming TCP connection request from 117.197.145.150:54845 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:42 2010 Blocked incoming TCP connection request from 189.26.213.182:52890 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:41 2010 Blocked incoming TCP connection request from 70.27.47.126:63061 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:40 2010 Blocked incoming TCP connection request from 41.174.54.156:1402 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:40 2010 Blocked incoming TCP connection request from 117.197.145.150:54845 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:39 2010 Blocked incoming TCP connection request from 189.26.213.182:52890 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:38 2010 Blocked incoming TCP connection request from 78.162.145.13:2690 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:38 2010 Blocked incoming TCP connection request from 186.44.67.168:55433 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:38 2010 Blocked incoming TCP connection request from 41.174.54.156:1402 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:38 2010 Blocked incoming TCP packet from 71.52.163.235:54658 to xx.xx.x.xxx:6882 as RST:ACK received but there is no active connection
[INFO] Wed Jul 21 04:56:33 2010 Blocked incoming TCP connection request from 78.162.145.13:2690 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:31 2010 Blocked incoming UDP packet from 70.189.190.133:28790 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:29 2010 Blocked incoming TCP connection request from 78.162.145.13:2690 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:29 2010 Blocked incoming TCP connection request from 24.82.181.220:60217 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:25 2010 Blocked incoming UDP packet from 70.189.190.133:28790 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:25 2010 Blocked incoming TCP connection request from 41.132.192.88:51680 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:24 2010 Blocked incoming UDP packet from 124.169.109.3:61363 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:24 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:24 2010 Blocked incoming UDP packet from 41.132.163.225:23271 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:24 2010 Blocked incoming UDP packet from 188.53.28.135:61575 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:23 2010 Blocked incoming TCP connection request from 124.169.109.3:61988 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:23 2010 Blocked incoming UDP packet from 70.189.190.133:28790 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:23 2010 Blocked incoming TCP connection request from 24.82.181.220:60217 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:22 2010 Blocked incoming TCP connection request from 41.132.163.225:64670 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:21 2010 Blocked incoming UDP packet from 70.189.190.133:28790 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:20 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:20 2010 Blocked incoming TCP connection request from 24.82.181.220:60217 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:19 2010 Blocked incoming TCP connection request from 59.100.77.215:62932 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:18 2010 Blocked incoming UDP packet from 124.169.109.3:61363 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:18 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:18 2010 Blocked incoming UDP packet from 41.132.163.225:23271 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:17 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:17 2010 Blocked incoming TCP connection request from 96.229.3.98:2231 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:17 2010 Blocked incoming TCP connection request from 124.169.109.3:61988 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:17 2010 Blocked incoming TCP connection request from 41.132.163.225:64670 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:16 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:15 2010 Blocked incoming UDP packet from 124.169.109.3:61363 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:15 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:15 2010 Blocked incoming UDP packet from 41.132.163.225:23271 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:14 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:14 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:14 2010 Blocked incoming TCP connection request from 124.169.109.3:61988 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:14 2010 Blocked incoming UDP packet from 124.169.109.3:61363 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:13 2010 Blocked incoming UDP packet from 41.132.163.225:23271 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:13 2010 Blocked incoming TCP connection request from 41.132.163.225:64670 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:13 2010 Blocked incoming TCP connection request from 151.59.143.237:63288 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:13 2010 Blocked incoming TCP connection request from 59.100.77.215:62932 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:11 2010 Blocked incoming TCP connection request from 96.229.3.98:2231 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:10 2010 Blocked incoming TCP connection request from 59.100.77.215:62932 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:10 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:08 2010 Above message repeated 1 times
[INFO] Wed Jul 21 04:56:08 2010 Blocked incoming TCP connection request from 96.229.3.98:2231 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:07 2010 Blocked incoming UDP packet from 87.224.199.155:60397 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:07 2010 Blocked incoming TCP connection request from 187.4.34.112:62887 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:07 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:07 2010 Blocked incoming TCP connection request from 173.10.248.102:59514 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:07 2010 Blocked incoming UDP packet from 82.4.35.89:18650 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:06 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:06 2010 Blocked incoming TCP connection request from 74.171.117.92:50916 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:05 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:05 2010 Blocked incoming TCP connection request from 173.10.248.102:59514 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:04 2010 Blocked incoming TCP connection request from 75.69.187.146:50043 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:03 2010 Above message repeated 1 times
[INFO] Wed Jul 21 04:56:03 2010 Blocked incoming TCP connection request from 173.10.248.102:59514 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:02 2010 Above message repeated 1 times
[INFO] Wed Jul 21 04:56:01 2010 Blocked incoming TCP connection request from 187.4.34.112:62887 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:01 2010 Blocked incoming TCP connection request from 109.64.8.34:3280 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:01 2010 Blocked incoming TCP connection request from 173.10.248.102:59514 to xx.xx.x.xxx:6882
[INFO] Wed Jul 21 04:56:00 2010 Above message repeated 1 times
-
yes and no,
Yes that the 4500 is doing it's job and blocking what could be the surrounding area APs. No, this shouldn't be happening on a scale like this. Again I think this has to due with the fact of all these near by access points.
-
Thanks for your reply Furry.
I thought this was interesting. Take a look at this image http://yfrog.com/5cwifi2qj (http://yfrog.com/5cwifi2qj). These are the 3 strongest signals in my immediate area. Do you know if its normal for them to be going in and out like this? I'm going to see if I get the same ocillations with my other laptop. What could cause these ups and downs at such a constant rate?
-
only think I can think if is that there seeing the same thing or there APs are reacting to interference or someone is not managing them correctly. Hard to say. Wish I could be of more help. Anyone else care to comment on this issue?
You must live in a very populated area.
-
Hi Furry,
I went back to the Linksys WRT610N and started playing with the settings. I disabled the 2.4Ghz and only enabled the 5Ghz band. When scanned the frequencies using inSSIDer I noticed that the occilation of my signal stopped when I disabled the 2.4Ghz band. I got this nice flatline which made me think I was on the right track. Then I played with a few frequencies and I've had a stable connection for over 60 minutes. I settled on the following settings:
Wireless N only on the 5Ghz band
channel width of 40Mhz,
wide channel 159
standard channel 161 (5.805Ghz)
I made sure I disabled everything related to the 2.4Ghz. So far I haven't had any disconnects for over 1 hour. I would like to go back to my newer D-Link 4500. Do you think I can do the same thing with the D-Link? I can't remember if I had the option to completely disable the 2.4Ghz band(antenna?)
Your insight is greatly appreciated!
---update
I spoke too soon :( its down again!!!
-
Sounds like you got it working a bit better. Seems like theres more people using the 2.4Ghz band than the 5Ghz. However seems like something is still interfering even with that. Keep us posted.
-
Hey Furry,
Yes. Its funny, it takes a lot longer to lose the wireless internet than before but my laptop actually never gets disconnected. I still see it under the network icon as connected with "access: Local and Internet" and it has 5 bars. Unfortunately, when I open my web browser it waits for a response and times out. I dont know if maybe a simple setting change can fix that? To fix the problem I have to disconnect and reconnect to my router manually.
As to living in a populated area, it looks like everyone and their cat have a wireless router in this building.
-
Ya, your connected to the routers WiFi LAN side just fine, it's the WAN side of the WiFi thats seems to be having problems dealing with all of the other WiFi in the immediate area. I bet if you took the 4500 to say your parents place, which I presume they might live in a house and in a less populated a area, that the 4500 WiFi would work as expected. I think with all of the other WiFi in the area that everyone else is probably seeing the same problems.
Do you think you can talk to the building manager and see if maybe they could come up with a better system? How about asking others to share the WiFi? I presume this is a residential building? Seems like someone could come up with a better system and policy to at least help out WiFi in the building and maybe get people to share WiFi, costs and cut down on the excessive WiFi APs. Seems ridiculous here. LOL
-
Ahhhh... yet again an area so saturated with WiFi routers that having a wired network looks better and better.
I'm with Furry on parts of this. Try getting together with some of your surrounding Condo/Apartment Dwellers and see if you can set your selves up as a interdependent cooperative WiFi setup. If that does not work get with the building people and try to get it as a building wide setup. There are lots of turn key systems that can be implemented with a little savvy and some time.
It's that or wire your place. I really do not see much else, the SoHo routers are not made to take the abuse that it seems like you and your fellow dwellers are putting them through.
-
Thanks for your comments!
I will talk to some more residents and see how widespread this problem is. If I can get enough of them to complain maybe we can get the ball rolling. In the event that I can't mobilize the troops. Is there anything I can do, short of building a giant Farraday cage around my appartment, to reduce outside signals?
Also, whats the strongest SOHO wi-fi out there?
-
It's not going to be the router so much as the signal penetration. A faraday cage would help. ::) My house is aluminum framed and most radio is lost inside here.
I used to use this a lot on my old laptop to show people the saturation in their area. It is good @ seeing signals weaker than are reported by other applications. I have not used the newer version. Try it and see if you can spot a router/access point that was "hidden" it even shows routers with hidden SSIDs.
http://www.netstumbler.com/downloads/ (http://www.netstumbler.com/downloads/)
I'll have to reload this onto my new laptop and see what crap is in my area here.
Are you in a metro somewhere like NYC or Chicago?
-
Hi Corroded.
I'm in Toronto, Canada. I tried netstumbler but for some reason it says no APs detected. So I'm using inSSIDer instead. I can pick up over 30 APs in just under 5 mintues. What bothers me is that everything was fine up until a few weeks ago. Could it really be that just one more person installed a wifi and it was the straw that broke the camel's back? I didnt notice any decrease in performance up until it stopped working consistently. Do you know if we could see this effect if someone installed a commerical router in the area?
-
There is an off chance someone moved in with an old 2.4 rig of some kind that is intermittently blasting the floor(s) of your building.
I used to see radio interference from ship radar that seemed random until I placed with a passing ship and the rotational period of the radar.
Do you live near a radio station, LEO shop, or other place that may have erected some sort of tower/transmitter nearby?
Did they roll out WiMAx or city wide WiFi there recently?
Are there new cell antennae on an adjacent building in the line of site with your place?
I know there are radio disruptor devices capable of knocking down radio traffic on specific freq's as well. You can buy devices to cut off cell service in your place as easy as plugging them in...
Do you drop if you are in the same room as the router?
Wire it. Faster connection anyways.
__________
I just pulled inSSIDer and netstumbler. netstumbler does not work on my laptop. inSSIDer gives me about 13 active AP's in sight of my 4500. No interference. Some of them are commercial ones from the local WiFi DSL provider.
-
Hi Corroded,
I'm far away from shore and I haven't seen any large towers errected nearby in the last few weeks. All great ideas but I just can't connect the dots to something outside of this building. I'm not actually in the downtown core, I'm quite a bit away so we dont get a city wide WiFi out here. The other day I was getting plenty of deauthorization messages from my D4500, so I thought it was a deauth flood attack. But maybe its some sort of jamming device? How could I figure out where its coming from?
Also, my router is 4 feet away from my laptop. I may just wire it, but I would hate to think one person could spoil it for the rest of us.
Thanks for your help!
-
I would not think that either but I have seen older 2.4 phones mess up peoples wifi. Spread Spectrum is supposed to get rid of that but not always. ???
Can you find out if someone moved in about the time you started having the issue? See if they might have an older cordless phone or real old Wifi router, an "a" perhaps?
I am at a loss beyond this point.
-
Well I just did some light research and you wouldn't happen to have a Intel wireless NIC would you? Found a bunch of forums post on egghead, DSLreports, PSN, Wii Forum, etc, all with issues between D-link routers and Intel cards. Intel cards are super common though, so could mean nothing. Eitherway, heres some tips I dug up will searching.
1. Turn your off the Power Saving Protocol (PSP) on your laptop. This might also be known as setting it to CAM or Always Awake. More info here: http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm
OR (because this kills battery life)
2. Lower the Beacon Period: 192.168.0.1 > Advanced > Advanced Wireless > Beacon Period.
Default is 100. Some people have better results with a Beacon of 30 or so. Picture the beacon being like schronizing your watches before a mission. The more times you do it during a mission, the more cordinated you will be.
AND
3. Increase your DTIM: 192.168.0.1 > Advanced > Advanced Wireless > DTIM Interval
DTIM is the amount of frames a wireless client (Wireless NIC) waits before it "wakes up" to transmit or recieve data. Default is 1. If your lowering the Beacon to improve dependability, increasing your DTIM can perserve battery life.
Basically here is the deal. Theres some different technology out there to peserve battery life. The core of it to not have the laptop listening for anything when the router isn't sending, and not have the laptop sending when the router isn't listening. When all things are perfect, it works great. But its like fireflies trying to use morse code in a forest jack full of fireflies. When you have so much noise, the system can start to become inaccurate. The looser you make that power saving system, the more dependable (and better performing) it becomes, but the more battery you burn. If this is a wireless desktop or a laptop thats plugged in all the time there is no reason for PSP to be enabled.
Keep in mind this is one possibility of varible in your problem. There may be, and probably are, other parameters as well. Thats why its important to start with a router that is default and a wireless NIC with updated driver with default values. Change one thing, monitor, evaluate, change it back, repeat.
-
good post Tri :o
-
Thanks a lot Trikein! I will try out your suggets and report back!