Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[RamGuy]

Hi,

I've got a new D-Link DIR-655 A3 to replace my somewhat defective DGL-4500!
The reason for me getting the DIR-655 is because it's way more mainstream than the DGL-4500, it's been out for a bit longer and I then hoped for a somewhat better and more stable firmware being available!

Well, I guess the perfect D-Link firmware from Ubicom is somewhat a dream never coming true?

My DIR-655 got some of the same issues I've had with my DGL-4500 since March 2008!
First of all the wireless radius seems a bit weak? When I pay twice the money for a "Draft-N v2.0" router, which D-Link brag about being so much better than the old Wireless-G standard I expect it to have better range than our old Linksys WRT54Gv5 (yeah the v5.. the one with that bad VX (not Linux) firmware with a stupid small amount of memory).. But guess what? The range / radius of the wireless has become significantly reduced? It was all the same with the DGL-4500, so don't start with "You've got your self a bad version".. This is actually my second A3 DIR-655 as well!

So a Wireless-G router for half the price of the DIR-655, and like on third of the DGL-4500 price tag is having like 50% better radius / range on the wireless? It's okay with a slightly weaker radius, but here we are talking about significant differences? In the advantage of the old and cheap Wireless-G router?!

But that isn't bothering us that much as long as we've got signal all-round the house, but sitting in the living room with only weak signal compared with our old Linksys WRT54Gv5 good / excellent signal feels kinda dull..


But that's not the major issue..
The major issue is the fact that the internet connection disappears quite often?
Like yesterday evening, I was just playing World of Warcraft and using FireFox (connected with cable, and all ports open and no firewall enabled on the router nor the computer!) and suddenly the router drops the internet connection?

Happens annoyingly often! Had somewhat the same issue with DGL-4500!
Got no idea why it happens, but the router for some reason seem to be dropping the WAN or blocking my computers internet connection every now and then?

When only running World of Warcraft it works without any issues, but when firing up FireFox the disconnections might suddenly start to pop? Downloading with FireFox might be a real pain in the ass because sometimes just downloading with FireFox makes me getting disconnected all the time? No matter what I download?

Here are a copy of my resent log? Within this time frame I lost my internet connection like 2-3 times?

[INFO] Sat Nov 22 04:57:43 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...
[INFO] Sat Nov 22 04:54:45 2008 Above message repeated 3 times
[INFO] Sat Nov 22 04:54:13 2008 Blocked outgoing TCP packet from 192.168.1.149:1551 to 74.125.77.102:80 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:54:09 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...
[INFO] Sat Nov 22 04:53:22 2008 Above message repeated 2 times
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1541 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1546 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1545 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1544 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1543 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1542 to 194.24.252.216:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:52:42 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...
[INFO] Sat Nov 22 04:52:00 2008 Above message repeated 1 times
[INFO] Sat Nov 22 04:51:57 2008 Log viewed by IP address 192.168.1.149
[INFO] Sat Nov 22 04:51:53 2008 Allowed configuration authentication by IP address 192.168.1.149
[INFO] Sat Nov 22 04:51:10 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:49 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:48 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...
[INFO] Sat Nov 22 04:50:28 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:27 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:24 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:17 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:16 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:13 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:11 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:50:09 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...
[INFO] Sat Nov 22 04:50:09 2008 Blocked outgoing TCP packet from 192.168.1.149:1552 to 74.125.100.35:80 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:55 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:55 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:54 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:53 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:53 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:52 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:52 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:46 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:44 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:43 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:42 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:42 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:38 2008 Above message repeated 2 times
[INFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:36 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:36 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:33 2008 Blocked incoming TCP packet from 74.125.77.102:80 to 192.168.0.3:1551 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:28 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:27 2008 Blocked outgoing TCP packet from 192.168.1.149:1534 to 194.24.252.223:80 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:26 2008 Blocked outgoing TCP packet from 192.168.1.149:1468 to 80.239.181.75:3724 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:24 2008 Starting DHCP server
[INFO] Sat Nov 22 04:49:24 2008 Blocked incoming TCP packet from 74.125.77.102:80 to 192.168.0.3:1551 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:20 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:20 2008 Blocked incoming TCP packet from 74.125.77.102:80 to 192.168.0.3:1551 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:20 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:19 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:18 2008 Latest firmware version 1.20 is available
[INFO] Sat Nov 22 04:49:18 2008 Blocked outgoing TCP packet from 192.168.1.149:1518 to 80.239.181.75:3724 as PSH:ACK received but there is no active connection
[INFO] Sat Nov 22 04:49:18 2008 Starting WAN Services
[INFO] Sat Nov 22 04:49:18 2008 Estimating speed of WAN interface
[INFO] Sat Nov 22 04:49:18 2008 WAN interface is up. Connection to Internet established with IP Address 192.168.0.3 and default gateway 192.168.0.1
[INFO] Sat Nov 22 04:49:18 2008 Bringing up WAN using Static IP Address
[INFO] Sat Nov 22 04:49:18 2008 WAN interface cable has been connected
[INFO] Sat Nov 22 04:49:17 2008 LAN interface is up
[INFO] Sat Nov 22 04:49:17 2008 LAN Ethernet Carrier Detected
[INFO] Sat Nov 22 04:49:16 2008 Device initialized
[WARN] Sat Nov 22 04:49:16 2008 gw_wireless_schedule init
[INFO] Sat Nov 22 04:49:16 2008 Wireless Link is up
[INFO] Sat Nov 22 04:49:15 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Thu Jan 01 01:00:00 1970 Loaded configuration from non-volatile memory

[funchords]

1.  Decreased relative signal strength does not mean decreased range or performance over an 802.11g router. The MIMO antenna selection and use methods used in your DIR-655 or DGL-4500 router (Atheros-based 3x3 MIMO) means that you'll get greater performance over larger distances without requiring signal power output. This is not only faster, but more spectrally efficient.  The DGL-4500 will be stronger in spots and weaker in spots than the DIR-655 owing to its higher-gain vertical antennas.  The antennas used by the DGL-4500 give a flatter signal (more pancake shaped) than the DIR-655 (more donut shaped).

2.  Your log is indicating "Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash..." -- that seems like a very severe entry (D-Link Tech, this should be bugged -- such an error should not have an "INFO" tag but should be "WARN" or "CRIT" instead).  You should probably update to the latest version of firmware (your log indicates you are using 1.20).  I am using v1.21 2008/10/09 and have never seen the log entry above.

Good luck.

[EddieZ]

Since FF itself does not have any interaction with the router and just uses the same TCP stack IE uses  you might want to look on your PC too if there is a buggy driver, virusscanner or firewall acting up.

The best position is different for each router. With the triple antennae you need to figure out the total placement based on the required coverage and prederred direction (up/dow/sideways). Remember that configuring the three antennae makes a big difference. If you a maths  crack you can calculate the exact angles and alignment, taking into account the 'shape' of the signal (and thus the area to cover). The  'donuts' should not overlap , and the donut is centered around the straight antenna, leaving a weak spot (hole) above the tip of the antena. So pointing the antenna directly to a receiving laptop gives a very weak signal.

[Lycan]

I highly suggest updating the firmware. Also the PC thats getting dumped like that, is it running any AV suites?

[RamGuy]

This issue has been for ages, and that "disconnected for reason: AP maybe crash..." has been popping in the log with firmware 1.11EU, 1.20EU and 1.21? All final versions..

On my computer there is no firewall whatsoever, the whole Windows Firewall process has been removed with nLite and I now run Norton AntiVirus 2009, but that entry popped even before I installed Norton?

The firewall on the router is gone, all my ports are open, no mac filtering, no extra wireless protection, the wifi protection is set to WPA2 only AES only (doesn't really matter as my comp is running through cable).

[funchords]

If a firmware change or a hard reset won't fix it, then I'd go to the "hardware failure" conclusion.  Judging by the log entry, some process is watching over the hardware and kicking it in the pants when it is not responding as expected. 

Check your warranty and get an RMA -- yours should be young enough. 

Robb

[RamGuy]

Well, now I have experienced that same issue with 2x DIR-655's and 1x DGL-4500, no matter what firmware and hardware revision I've been running that same "kicking" occurs?

[netdevil]

I am experiencing the same disconnections on my wife's laptop with my DIR-655... I'll post a log next time it occurs...

[funchords]

Well, now I have experienced that same issue with 2x DIR-655's and 1x DGL-4500, no matter what firmware and hardware revision I've been running that same "kicking" occurs?

Do you live by an airport or other high-powered radar?  Do you have any other wireless transmitters near where you are setting up the wireless router?