Print

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

[Celeras]

Using DGL 4300 to broadcast wireless to a laptop + DAP-1522 as a bridge for 2 PCs. At least twice a day, usually at about the same times (3pm and 9pm are when I notice the problems, relatively consistently. Not on the dot, but around those times) the net will just drop.

When the laptop is wired to the router while the wireless is down, it works fine, so its not the modem or the ISP. Just inexplicably the wireless will drop for a few minutes, its very disruptive when trying to game.

Using firmware 1.7, and the problem is unrelated to DHCP lease refresh(i have it set to keep the lease for 45 days). Log doesn't really show anything out of the ordinary.

[Reinvented]

What are your wireless settings?  And have you tried updating to 1.9 FW which is the latest?

[Celeras]

I've tryed 1.6/1.7, I was told 1.8 had security problems and 1.9 increases wireless errors/dropped packets.

DHCP
WEP encryption
Auto channel select(it goes to 11)
Transition rate: Best (Automatic)
802.11g only
Super G without turbo
100/3200/3200 beacon/threshold

[Reinvented]

Why is the thresholds so high?  Should leave them at default, or lower them if it can't maintain a connection.

Don't bother with Turbo unless you have devices that can support it.  Also, channel 11 and Turbo don't work so well.  It recommends you put it at 6.
1.9 is fine.  May produce more errors, but so what?  It'll stay connected at least.

You are always bound to get errors, simply because of the walls that it has to travel through.
Here's what you NEED to do..

-Change thresholds to 2346
-Manually set wireless channel to 11
-Update to Firmware 1.9
-Turn off Turbo Mode

If it still can't maintain a connection, then lower your thresholds to 2100, and beacon period to 80.

[Celeras]

They were set to those settings because those are the defaults that the router came with >.>;

Upon further investigation of this problem, it seems its not just the wireless that was going down. My laptop was autoconnecting to another nearby network when my router died. The router itself is actually rebooting itself all together. I confirmed this by disabling my wireless connection on my laptop, and plugging it straight into the 4300. When the wireless went down on my PC in the other room, I checked the laptop, and it was also down. When it came back up, i checked the web configuration and the uptime for the connection was under 30 seconds.

Leads me to believe that this is not a fixable problem, if the whole thing is going down and not just the wireless. Y/n?

[Reinvented]

Check logs, and see what it's saying. This will be the biggest indicator of why it's losing connection, and/or restarting.  I will say that if it's rebooting, or dropping connections, it could be because of your actual internet connection.  When the WAN drops, everything on the LAN drops...and it'll auto sense a new IP address when it comes up again.

But yes, generally if it's in  constant reboot, then you have some problems. Hard reset first to troubleshoot it.

The defaults for the router aren't 3200 at all.  It's 2346.  That's why.  Did you get this router 2nd hand from a friend?

[Celeras]

Code: [Select]

[INFO] Fri Nov 21 07:49:16 2008 Blocked incoming TCP packet from 64.12.24.72:5190 to 69.123.93.246:2772 as PSH:ACK received but there is no active connection
[INFO] Fri Nov 21 07:49:15 2008 Log viewed by IP address 192.168.0.150
[INFO] Fri Nov 21 07:49:11 2008 Allowed configuration authentication by IP address 192.168.0.150
[INFO] Fri Nov 21 07:49:01 2008 Blocked incoming TCP packet from 64.12.165.65:5190 to 69.123.93.246:2777 as ACK received but there is no active connection
[INFO] Fri Nov 21 07:48:55 2008 Blocked incoming TCP packet from 64.12.24.72:5190 to 69.123.93.246:2772 as PSH:ACK received but there is no active connection
[INFO] Fri Nov 21 07:48:40 2008 Blocked incoming TCP packet from 64.12.24.72:5190 to 69.123.93.246:2772 as ACK received but there is no active connection
[INFO] Fri Nov 21 07:48:27 2008 Blocked incoming TCP packet from 64.12.24.72:5190 to 69.123.93.246:2772 as PSH:ACK received but there is no active connection
[INFO] Fri Nov 21 07:47:59 2008 Above message repeated 5 times
[INFO] Fri Nov 21 07:47:48 2008 Blocked outgoing TCP packet from 192.168.0.123:3196 to 72.14.205.101:80 as FIN:ACK received but there is no active connection
[INFO] Fri Nov 21 07:47:48 2008 Blocked outgoing TCP packet from 192.168.0.123:3198 to 74.125.12.30:80 as FIN:ACK received but there is no active connection
[INFO] Fri Nov 21 07:47:26 2008 Allowed configuration authentication by IP address 192.168.0.150
[INFO] Fri Nov 21 07:45:39 2008 Starting WAN Services
[INFO] Fri Nov 21 07:45:39 2008 WAN interface speed measurement completed.  Upstream speed is 2165 kbps
[INFO] Fri Nov 21 07:45:18 2008 Wireless system with MAC address 0022B053A105 associated
[INFO] Fri Nov 21 07:45:07 2008 Starting DHCP server
[INFO] Fri Nov 21 07:45:00 2008 Estimating speed of WAN interface
[INFO] Fri Nov 21 07:45:00 2008 WAN interface is up. Connection to Internet established with IP Address 69.123.93.246 and default gateway 69.123.92.1
[INFO] Fri Nov 21 07:45:00 2008 Obtained IP Address using DHCP. IP address is 69.123.93.246
[INFO] Fri Nov 21 07:44:58 2008 Bringing up WAN using DHCP
[INFO] Fri Nov 21 07:44:58 2008 WAN interface cable has been connected
[INFO] Fri Nov 21 07:44:58 2008 LAN interface is up
[INFO] Fri Nov 21 07:44:58 2008 LAN Ethernet Carrier Detected
[INFO] Fri Nov 21 07:44:58 2008 Device initialized
[WARN] Fri Nov 21 07:44:58 2008 gw_wireless_schedule init
[INFO] Fri Nov 21 07:44:58 2008 Wireless Link is up
[INFO] Fri Nov 21 07:44:57 2008 Unlock AP setup
[INFO] Fri Nov 21 07:44:57 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Wed Dec 31 19:00:00 1969 Loaded configuration from non-volatile memory

That's what the log looks like after it happens, because the router is rebooting which is causing the problem. Its not going to show anything.

Its not the internet connection, because plugging into the modem works fine.

[Celeras]

Just to update for people searching through this thread for their own problems:

This problem persisted for an extended period of time. I bought a new (dlink dir-615)router, and it has since been fixed. I setup the 615 exactly the same way as I did the 4300, and didn't make any changes to the settings on the 1522(bridge). It automatically picked up the 615, and have had no problems since. The problem was the 4300, it just crapped out.

[Scaevola]

I just upgraded as well to f1.9 and It seem to be completely lock up every day or so.

Perform a power cycle and check the logs -> and everything is basically omitted from yesterday until after the restart occured!

Frustrating