D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: smapdi on June 10, 2008, 04:21:26 PM
-
Hey guys,
I bought a DIR-655 to replace my aging Buffalo WHR-G54S. I thought all was going well until I tried to do a bandwidth test via speakeasy.net and Verizon's own speedtest. Both show my connection as 10/5 while with the Buffalo, it was showing ~20/5 (the correct speed for my FIOS tier).
I read that it had something to do with autoneg on the WAN port not working well. I tried to manually set it to 100Mbps but that setting caused it to continuously drop the link. When set to 10Mbps or 1000Mbps the link works but I am capped at 10/5. Is there anything that I can do to fix this issue? I am running an A3 with firmware 1.11 (thinking of trying 1.11MSBetaB39)
-
I'm running an A2 version of the DIR-655 which is behind the Actiontec router that is configured as a bridge (the Actiontec that is). The WAN Port Speed is set to Auto 10/100/1000Mbps. I am paying for 15/2. The transfer rates generally run between 15/1.5 to 20/1.9 using the speed tests on BroadbandReports.com. Depending on the server location and traffic I have gotten as low as 5/0.5 and as high as 27/1.9.
Have you tried different ethernet cables?
If you want other DIR-655 settings that I use then let me know and I'll post them for you.
-
When I first bought the 655 I had it connected to the FIOS line via bridged Actiontec. My original troubleshooting steps were to remove the bridge and connect via ethernet.
I ran a new ethernet cable and connected the 655 directly with the exact same results.
If you have any settings that could effect the WAN performance I would be happy to try them out.
Thanks!
-
I am not a network guy so selections what I am listing are a "shot in the dark." I am using the 1.11 firmware.
Enable Multicast Streams - checked (I have two TiVO's on my network)
Advanced Networking:
Enable SPI - checked
Enable anti-spoof checking - checked
QOS Engine:
Enable QoS Engine: checked
Setup - Internet:
Use Unicasting - checked (I don't remember why I checked this, probably when I was trying to get my TiVO's to see each other on the network). I think the default is not checked.
I don't know if these items will help or not. I was going from memory (not reliable at my age for certain) to indicate what items I changed from their default values as I have had the DIR-655 for almost a year.
Please let me know if there are any other settings you may want.
-
Hmm....I have the same settings set (and I guess you meant Multicasting instead of unicasting :P ) yet I still have the issue..
Any other thoughts what I should be setting/not setting?
-
What hardware rev is your 655?
-
smapdi: No, it is unicasting (Setup->Internet under "Dynamic IP (DHCP) Internet Connection Type").
Lycan: He said he had A3 and I have A2 (unless I'm missing something and answered the wrong question).
smapdi: I initially thought that MAC filtering could possibly have some effect but after some testing with MAC filtering turned on with my PC's on home network (includes two DAP-1522 access points/bridges set up as bridges) I saw no degradation with internet speed tests. I'm out of ideas at this point.
-
It would appear to be a negotation issue. I'll se what can be done at the PM level.
-
DavePDX: I didn't notice the Unicasting setting under the Settings -> Internet ->DHCP (mine was always checked on)
Just as an update, I installed the Beta firmware and still no joy :'(
Lycan: I also think it's something to do with negotiation. I was thinking of upgrading my FIOS service to 20/20 symmetric but unless I can get this issue resolved that plan goes out the window...
-
It's odd. We've seen this randomly. I've seen this work and I've also seen this exact thing with the same product and the same network.
I'll see what I can dig up.
-
Hey guys,
I bought a DIR-655 to replace my aging Buffalo WHR-G54S. I thought all was going well until I tried to do a bandwidth test via speakeasy.net and Verizon's own speedtest. Both show my connection as 10/5 while with the Buffalo, it was showing ~20/5 (the correct speed for my FIOS tier).
I read that it had something to do with autoneg on the WAN port not working well. I tried to manually set it to 100Mbps but that setting caused it to continuously drop the link. When set to 10Mbps or 1000Mbps the link works but I am capped at 10/5. Is there anything that I can do to fix this issue? I am running an A3 with firmware 1.11 (thinking of trying 1.11MSBetaB39)
Hi,
I was wondering if you were able to resolve this problem. Please let us know.
Thanks!
-
Unfortunately I still have the issue. None of the settings that I have changed seemed to do anything in terms of WAN speed. I can only hope that someone within DLink can help out and/or a new firmware version comes out that addresses this (I can't be the ONLY person trying to get this thing working on FIOS).
The really frustrating thing is that my 2+ year old Buffalo router can do 20/5 with no problems whatsoever while this brand spankin' new "XTreme N" router cannot :'(
-
What state are you getting your fios in? Also, are you familiar with packet captures?
-
I live in New Jersey.
About packet captures.....I have spent more time than I care to mention analyzing tcpdump captures in ethereal/wireshark at work.
Hmmm....maybe I can put a probe on my WAN to capture what the packets being exchanged between the router and FIOS ONT are...
-
Thats what I'd like to see, the negotation between the unit and the ONT tansversal box.
Also are you getting a true public to the routers WAN?
-
I'll have to wait until the 4th or 5th to put in a probe.
And I believe I am getting the true public IP. The router sees the WAN side as 96.234.55.238 which is the same as this forum logs and as the address my dyndns forwarder resolves to.
-
Just to give you guys an update:
I hooked up an in-line sniffer between the ONT and the router and didn't see anything out of the ordinary in terms of TCP. I did notice that the ONT side ethernet negotiated 10Base-T and the router side did 100Base-TX so I decided to check with Verizon. After convincing the techs I knew what was going on, they checked the ONT remotely and said that there was some kind of misconfiguration when they switched me from MoCA to Ethernet. Once they changed their setting the connection negotiated to 100Baste-TX and my line is back at 20/5.
Thanks Lycan and DavePDX for your help.
-
Wow, thats cool. So it wasn't the router? Sweet. Also, the MoCa that you had, was that also with Verizon?
-
Wow, thats cool. So it wasn't the router? Sweet. Also, the MoCa that you had, was that also with Verizon?
Yeah, it was not the router. The MoCA connection was the only one Verizon ran to their crappy router. I got the DIR-655 for the gigabit ethernet and 802.11n so I had to run my own CAT6 cables. The only thing that Verizon had to do then is disable to MoCA and enable the ethernet which apparently they did not do so well.
-
Yeah, it was not the router. The MoCA connection was the only one Verizon ran to their crappy router. I got the DIR-655 for the gigabit ethernet and 802.11n so I had to run my own CAT6 cables. The only thing that Verizon had to do then is disable to MoCA and enable the ethernet which apparently they did not do so well.
My FiOS installer a month or so ago told me I that he had done only a couple other CAT-5 Ethernet installations in the last six months, the rest were all (MocA) cable installs. If this is typical (and I think it probably is -- they WANT to sell triple-play packages) then the folk who do the remote config don't do it often either (not an excuse by any stretch, but perhaps an explanation). It took my installer a little while to get it to work after installed and fussing with the config-folk may have been what he was battling with as well.
-
My FiOS installer a month or so ago told me I that he had done only a couple other CAT-5 Ethernet installations in the last six months, the rest were all (MocA) cable installs. If this is typical (and I think it probably is -- they WANT to sell triple-play packages) then the folk who do the remote config don't do it often either (not an excuse by any stretch, but perhaps an explanation). It took my installer a little while to get it to work after installed and fussing with the config-folk may have been what he was battling with as well.
I can definitely see that. Back when I signed up for FIOS and asked why the installer was running a coax line instead of ethernet, he said that's for when I get FIOS TV....
I hate it when companies try to force you to get more of their services.....
-
I heard that Verizon is having massive probalems with piggy-backing the TV on the Fiber lines and it's causing outages for internet serivices.
-
I heard that Verizon is having massive probalems with piggy-backing the TV on the Fiber lines and it's causing outages for internet serivices.
Strange, it's not even using the same electronics (uses a third separate wavelength of light on the same fiber as do the up-going and down-going internet digital streams). They been having optical transceiver problems or the like?
-
I can definitely see that. Back when I signed up for FIOS and asked why the installer was running a coax line instead of ethernet, he said that's for when I get FIOS TV....
I [exploitive deleted] it when companies try to force you to get more of their services.....
Actually he was easily convinced not to run coax. No real "push" at all. I explained how it was going to be twenty times more work for him to put coax to where it needed to go compared to what he had to do with CAT5. For CAT-5 he needed a short run up the side of the house and to mount a CAT-5 (RJ-45) jack near the floor of the second floor almost above where the ONT was (although that was on the inside of the garage wall). I then had CAT-5 already there to take it toward the middle of the house where the wireless router needed to be to get proper coverage and where he'd otherwise need to run coax (previous DSL setup). Plus just a few months prior we had three HD DVR's from DirecTV installed which took three installers nearly three hours to put in. FiOS TV wasn't a likely scenario for a while. :-) He also was easy to convince not to try installing stuff on or fussing with my computer. :-) An AOL person I'm not (I design telecom hardware by day). :-)