D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: mb on August 09, 2007, 09:35:35 PM
-
f/w v1.05 dated 2007/08/08 is available on the US download site. I am up and running with it here. Initial observations suggest that a few configuration options have been removed. Details to follow.
-
Any ideas if this addresses the disconnection issues?
EDIT...
Appears my disconnect issues were related to faulty hardware. A replacement is working fine withi 1.05.
-
I like the addition of the Black list my self.
-
The ability to set a schedule for when the radio (wireless) is enabled is pretty sweet.
Under Setup/Wireless Settings/Manual - next to the "Enable Wireless" button, there is a pull-down that defaults to "always". You can create a schedule that will set the time when the wireless is enabled.
To set a time when the wireless will be turned off (what I'm more interested in doing), just be sure that the start time in the schedule is when you want the wireless turned back on, and the end time is when to turn it off.
By the way, the 1.05 firmware also supports the new D-Link router widget (found under Yahoo! widgets).
- Cheers
-
Sweet. I want to try this my self :D
-
I was having a lot of problems with my notebook connecting to my main pc. It would drop the connection and reconnect within a few seconds. This would go on almost constantly.
I flashed the new v1.05 firmware and it hasn't done it once!! This has done the trick for me as well as adding the mentioned improvements and extra features..
I hope it helps the rest of you guys too.
laubin
-
I updated to 1.05 this weekend...
I like it. No drops, good speeds I would suggest others to update to 1.05
-
I used a throughput testing software, with the 1.02 firmware and a pure gigbit network I was seeing like 425-500 MBPS. With the 1.05 it jumped to 600-675Mbps.
Not to mention, widgets are pretty cool.
-
I just tried it. A lot faster. More stable than 1.03 but not stable enough. With 1.03, my wireless PCs disconnect very fast. With 1.05, they would often last more than 10 minutes. However, after they disconnect, there's no way they'd reconnect, not even after I reboot the router.
I'm falling back to 1.02 until D-Link fixes the bugs.
I have 3 wireless desktops all running Windows XP, 2 with D-Link G cards, one with D-Link N card.
Here's my log (I removed lots of lines about blocking some IP address like this one: Blocked incoming TCP packet from 68.142.233.74:443 to 99.246.83.248:1386 as RST:ACK received but there is no active connection):
[INFO] Sat Aug 18 15:00:28 2007 Wireless system with MAC address 000D88934974 disconnected for reason: Timeout, station left.
[INFO] Sat Aug 18 15:00:28 2007 Wireless system with MAC address 00C0A8AB3B79 disconnected for reason: Timeout, station left.
[INFO] Sat Aug 18 15:00:28 2007 Wireless system with MAC address 00195B593546 disconnected for reason: Timeout, station left.
[INFO] Sat Aug 18 14:55:29 2007 Wireless system with MAC address 001B1154983B disconnected for reason: AP maybe crash...
[INFO] Sat Aug 18 14:50:52 2007 Wireless system with MAC address 00195B593546 associated
[INFO] Sat Aug 18 14:50:19 2007 Wireless system with MAC address 00C0A8AB3B79 associated
[INFO] Sat Aug 18 14:50:05 2007 Time synchronized
[INFO] Sat Aug 18 14:42:35 2007 Requesting time from 64.7.210.145
[INFO] Sat Aug 18 14:42:35 2007 Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO] Sat Aug 18 14:42:35 2007 Starting WAN Services
[INFO] Sat Aug 18 14:42:35 2007 WAN interface speed measurement completed. Upstream speed is 542 kbps
[INFO] Sat Aug 18 14:42:28 2007 Wireless system with MAC address 000D88934974 associated
[INFO] Sat Aug 18 14:42:18 2007 Starting DHCP server
[INFO] Sat Aug 18 14:42:11 2007 Estimating speed of WAN interface
[INFO] Sat Aug 18 14:42:11 2007 WAN interface is up. Connection to Internet established with IP Address xx.xxx.xx.xxx and default gateway xx.xxx.xx.xxx
[INFO] Sat Aug 18 14:42:11 2007 Obtained IP Address using DHCP. IP address is xx.xxx.xx.xxx
[INFO] Sat Aug 18 14:42:10 2007 Bringing up WAN using DHCP
[INFO] Sat Aug 18 14:42:10 2007 WAN interface cable has been connected
[INFO] Sat Aug 18 14:42:09 2007 LAN interface is up
[INFO] Sat Aug 18 14:42:09 2007 LAN Ethernet Carrier Detected
[INFO] Sat Aug 18 14:42:09 2007 Device initialized
[WARN] Sat Aug 18 14:42:09 2007 gw_wireless_schedule init
[INFO] Sat Aug 18 14:42:09 2007 Wireless Link is up
[INFO] Sat Aug 18 14:42:08 2007 Unlock AP setup
[INFO] Sat Aug 18 14:42:08 2007 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Wed Dec 31 20:00:00 1969 Loaded configuration from non-volatile memory
-
I'd use a blacklist to block myspace.
-
I agree. It's funny to watch my roommate squirm when they can't get on that website.
;D
-
Is it just me or is v 1.05 missing the Application Gateway Layer options? How do I passthrough VPN traffic, either through PPTP or IPSEC?
The old firmware versions had options to do so, but I can't seem to find it in version 1.05. Disappointed there.
-
have any of you had any luck with an Intel wirless nic connecting in N mode to your N router?
Just curious....
-
I've tried 1.03, 1.04 and 1.05 - 1.05 was the most stable but still hangs sometimes daily and can't stay up for more than a week tops. I gave up and reinstalled my old reliable DI-634M which stays up for months. I have 4Mb DSL, static IP - no changes for 3 years so I'm surprised that the DIR-655 is so unstable.
-
Hi,
Why did you take out the WAN Port Mode! I just purchased 7 new units and updated to the new version and now found that it's gone. We need this back! Without it the 7 units will have to go back.... Basically we need the ability to use this as an AP WITHOUT using up one of the LAN ports. This is what the Bridge Mode gave us. So pleeeeeeeeeease put this back!
-
I'm a little disappointed at D-Link's quality control in firmware development. I've been with D-Link since many years ago. It always takes a long time for the firmware to be stable. Right now firmware 1.03 through 1.05 all crashes my router minutes after normal use. It couldn't hold up even under the most simple configuration: a wired desktop plus a wireless desktop using D-Link's own wireless N card, both running Windows XP. I've tried the default settings plus all the different variations I could think of. Wasted tons of time.
Sometimes I wonder if D-Link tests their firmware at all?
-
Describe what is happening when your router crashes. I've found the device to be rock solid.
-
The router simply crashes after a few minutes of normal use. Sometimes a couple of minutes, sometimes around 10 minutes. After it crashes, the wireless PC would never be able to reconnect again. The only way out is to reboot the router.
I posted a log on Aug 18 inside this thread.
It looks like a firmware issue because the router works fine with firmware 1.02.
-
Correction when I said 1.02 works fine: it's fine when I use G mode. The router crashes as well when I tried N mode.
-
I'm looking for a description of the "crash". Does it stop routing the wired connections, or is this just affecting the wireless device? Are you just loosing connectivity to the internet? What type of internet connection to you have, cable, DSL or are you already on a LAN? Does the blinking triangle light on the front remain on, blink, or is it off? What are the rest of the lights doing? Can you access it's Web GUI when it has "crashed", if so, what does the status page report? Can you access the logs after the "crash", if so, what are they reporting. Simply saying that the router crashed is not descriptive enough to help with your problem.
-
When the router crashed:
1. Wired PC works fine.
2. Router's web GUI is working, log page accessible, don't remember status page being abnormal.
3. I remember logs stopped being updated.
4. Not sure about the lights, probably not off.
5. The wireless devices won't reconnect unless I reboot the router.
6. I have a cable connection.
Also every time it "crashed", my wired PC would lose connection for a brief moment.
-
OK, so you are saying that you are loosing your wireless connection but the router is still working. How many wireless devices are losing the connection? If just one, are you sure it isn't the wireless device? Is there interference from other devices? What are you seeing both before and after the connection loss on the router's Status > Wireless web page? Have you experimented at all with the wireless configurations on the router.
-
When the router crashes, all my wireless PCs would lose connection and couldn't reconnect unless I reboot the router. I have several wireless PCs and all but one of them have D-Link cards. I tested with only one wireless PC on and the result was the same. I experimented with all the configuration settings I could think of. Wasted lots of hours on it. I didn't see anything different on the router's Status -> Wireless page when it crashed.
Since firmware 1.02 works fine, I don't think it's anything other than bugs in the later versions of firmware.
-
These are some of the changes made to the firmware after f/w v1.02
DIR-655 Firmware Version 1.03 Release Notes.
¤ Passes "Connect with Centrino" Logo Certification program.
¤ Upgrade Wireless driver to 802.11n Draft 2.0 specification.
¤ Added Bridge Mode in Internet Settings.
¤ Added support for WiFi Protected Setup Push button Config.
¤ Added Static Routing.
¤ Improved MSN whiteboard and app-sharing.
¤ Updated Dynamic DDNS UI and added support DlinkDDNS.com Service.
¤ Added "NetBIOS announcement", "Learn NetBIOS from WAN", "NetBIOS Scope", and "NetBIOS node type" settings in Network Settings.
¤ Added "L2 Isolation" setting in Advanced Wireless.
¤ Added "Enable anti-spoof checking" setting in Firewall Settings.
¤ Increased Maximum Simultaneous Connections. (Improved P2P performance)
As you can see, some changes were made to the driver and other wireless related areas. I'll bet that you can narrow this problem down to something involving the wireless drivers or settings.
-
I didn't find much to change for the wireless card. Shouldn't the router work with the default settings? I tested with a brand-new D-Link wireless-N card using the latest driver and can consistently reproduce the crash on firmware 1.03 - 1.05. Sometime I wonder how much testing D-Link does on the firmware.
Since it obviously works for a lot of people, I'm really puzzled.
-
Is it just me or is v 1.05 missing the Application Gateway Layer options? How do I passthrough VPN traffic, either through PPTP or IPSEC?
The old firmware versions had options to do so, but I can't seem to find it in version 1.05. Disappointed there.
They are indeed gone. I need to disable the SIP ALG because it's dropping packets from my ViaTalk Linksys PAP2 adapter for no good reason (Log pretty much says "ALG (SIP) has dropped packet from [vt adapter] to [vt reg server] period" with no good reason, even when it's in DMZ).
Funny thing though, in 1.04 I disabled the SIP ALG and then nothing could connect to a website using the router's DNS. Even after switching to OpenDNS and rebooting repeatedly, it just crapped out on me until I reset it to factory defaults. This is when I upgraded to 1.05, only to discover the ALG options gone :(
Other than that I have been *very* happy with this router. My old DI-624 (and all offbranded variants of the same exact hardware) was probably the biggest piece of doorstop I've ever owned. Actually, it wouldn't even work for that because the door would close every 20 seconds when the router reboots for no reason =P This DIR-655 is the polar opposite of that. You get what you pay for! The amount of connections it can handle makes it perfect for pretty much anything, and the available features on this router are definitely not being matched by the competition right now.
-
I have a really strange problem where the 655 will work for a long time, been about 2 weeks this time. Then the router will reset uncontrollably and after an amount of time of me troubleshooting it, it will stabilize. When I say reset, I mean back to factory defaults. It was doing it earlier and now it's stable again. I can't even seem to isolate the issue. I haven't tried it on all the firmware yet though.
-
Sounds like a hardware issue, what version hardware and firmware?
-
you can still configure the router to operate as a AP.
Disable the DHCP server and change the units LAN address to somthing on the subnet you are working with and then conwnect it to your network with one of the LAN ports. it works......