Print

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

[sixersclt]

Reset it back to factory config.  Did not touch a setting and not hooked to WAN.  DIR655 still chokes at 10Mbps or greater.  Still drops out then back in - over and over.

Other than the niceness o***B LAN, I'm struggling to find a reason to keep this router.  I should not have to run the streaming through a Dlink DGS2205 GB switch for the stream to flow properly.

Mod comments please?

[bananaman]

Sorry, I'm coming in late here. I had a coupla thoughts:

Doesn't the fact that you're seeing the problem on a Netgear WNT3500, a D-Link DGS-2205, and a D-Link DIR-655 suggest that they are not the problem?

Other than the Gigabit routers, NICs, and switches, the other "new" thing in your setup is the cabling.

It's possible that somewhere in your new cabling there is something flakey. Not flakey enough to affect 10/100 performance, but enough to cause Gigabit to roll back its speed.

10/100 uses 4 wires in your cabling, whereas Gigabit needs all 8 wires. If any of the extra 4 connections which Gigabit needs are flakey... bingo.

I know it is a PITA, but can you set up the streaming source, destination, and intervening network hardware somewhere where you can easily swap cables to test?

BTW, like several others who have posted, I have no >10Mbps DIR-655 Gigabit streaming problems.

[EddieZ]

It's possible that somewhere in your new cabling there is something flakey. Not flakey enough to affect 10/100 performance, but enough to cause Gigabit to roll back its speed.

10/100 uses 4 wires in your cabling, whereas Gigabit needs all 8 wires. If any of the extra 4 connections which Gigabit needs are flakey... bingo.

Very good remark. You might want to check the connector first. If it is home made, there might be a glitch....

BTW, like several others who have posted, I have no >10Mbps DIR-655 Gigabit streaming problems.

Me neither with 1Gbps network.

[sixersclt]

I got two new cat6 10 foot cables, connected the 2 pcs through the router and it does the same thing.  The sending machine does not drop off the stream.  The stream gets dropped in the router.

Run them through the GB switch and it is fine, as it has been once jumbo frames were enabled.  The streaming continues to be fine through the Gb DLink switch.  The PCs show it as Gb Lan.

I'm out of ideas.  Maybe I'll get a different DIR655.

[bluenote]

Hey sixers

This really doesn't surprise me.  I've had several dlinks and they all had really really bad glaring issues out of the box.

I've been fighting with reboots, connection drops, poor performance, and confirmed bugs for about a week now (I have mostly got them ironed out, finally).

Anyways, I'm going to cautiously suggest that you try some of the things I've tried, even though you are only having switch troubles.

The first is, I found my router to become VASTLY more stable as soon as I upgraded the firmware to 1.21B02 .  I don't have a link for you, and its not the 1.21 available on the support site, but I got the link from this forum so I'm sure with a little searching you'll find it.  If you can't, post up and I'll search it out.

I have also heard many many many people praise 1.11 as much more solid than the later firmwares as well, although I have not tried it.

The second suggestion is that you go through the router and turn OFF all enhanced functionality.  SPI, mac filtering, QOS, WISH, wireless radio, the "INFO" logging option, etc etc etc etc.  We're just testing it as a switch so we want to eliminate the possibility that a hiccup in one of these modules is going to disrupt your data stream.   

Anyways, good luck.  You may be able to find a way to 'work around' the routers limitations on the PC/nic/etc but that doesn't mean the router isn't the problem.  (as you've sortof proved already in one instance).

Cory

[Lycan]

Cory,
Your statement is biased and unfounded. Sixers hardware maybe faulty, or there could simply be an issue with the Nic's in his PC. I have an complete D-link network and it's all GIGABIT based on a DIR-655 and I have ZERO issues. So to state that you believe that it's his router based on current testing is inaccurate.

-Sixers,
Last I checked you were running jumbo frames, and this solved the issue. I was wondering if you could run one more test for me. Please purchase a GIG NIC. make sure you keep the receipt so you can return it. Install it an disable the jumbo frames on it. Tell me what happens. (also you may need two for both PC's)

If this resolves the issue, I'm going to blame the TOE in the driver for your current NIC or just bad handling of the driver in the PC.
Try this also, DPC Latency timer. Run it when your running the stream. See if the driver for your NIC is causing hangs on your system.
Also what hard drives are you using in the machine that your streaming from? please list make and model.

[bluenote]

Hi lycan

All troubleshooting is hypothesizing and testing.

It of course could be almost anything.

However, assuming that it is not the router, even though sixer has shown that in other configurations  without the router the problem goes away (in several configurations, actually) is kind of unhelpful.  I'm sorry my first statement bothered your sensibilities, I'm not trying to cause trouble I'm trying to help sixer and add a little balance to this thread.

I'm sure you can imagine how frustrating it is to have someone pointing at other equipment despite some (I'll admit, small) evidence to the contrary.  It's possible that what you've said about the NIC will be related to the problem.  It's also a logical fact that his experiments are pointing in the direction of the router at this point.  (Well, to be exact I would say it points to a fault or an incompatibility in some retail network hardware .. but for our purposes we only really care about fixing the router behaviour.)

When one ships a product (like the 655) that crashes and reboots out of the box and otherwise doesnt work in some configurations for some people for such basic things as DNS resolution, or DHCP assignment then I would think it would be more profitable to concentrate on solving the problems than squelching dissent.  Maybe I'm wrong.  Unfortunately I would also say that puts *that* equipment at the top of the list for being at fault for any other problems until evidence proves otherwise.

I hope you figure out your problem sixer!  It might be profitable to see what logging options are available on the switch (if they are different from the router), recreate the problem, and see if anything is reported.
Forcing the router/switch/NIC (if you have the option) to 100/1000/full duplex/half duplex might shed some more light on the problem.  Its kind of involved but another path might be to go down the path of etherreal  or something similar and do some logging that way.

Cory

[EddieZ]

Hi lycan

All troubleshooting is hypothesizing and testing.

It of course could be almost anything.

However, assuming that it is not the router, even though sixer has shown that in other configurations  without the router the problem goes away (in several configurations, actually) is kind of unhelpful.  I'm sorry my first statement bothered your sensibilities, I'm not trying to cause trouble I'm trying to help sixer and add a little balance to this thread.

I'm sure you can imagine how frustrating it is to have someone pointing at other equipment despite some (I'll admit, small) evidence to the contrary.  It's possible that what you've said about the NIC will be related to the problem.  It's also a logical fact that his experiments are pointing in the direction of the router at this point.  (Well, to be exact I would say it points to a fault or an incompatibility in some retail network hardware .. but for our purposes we only really care about fixing the router behaviour.)

When one ships a product (like the 655) that crashes and reboots out of the box and otherwise doesnt work in some configurations for some people for such basic things as DNS resolution, or DHCP assignment then I would think it would be more profitable to concentrate on solving the problems than squelching dissent.  Maybe I'm wrong.  Unfortunately I would also say that puts *that* equipment at the top of the list for being at fault for any other problems until evidence proves otherwise.

I hope you figure out your problem sixer!  It might be profitable to see what logging options are available on the switch (if they are different from the router), recreate the problem, and see if anything is reported.
Forcing the router/switch/NIC (if you have the option) to 100/1000/full duplex/half duplex might shed some more light on the problem.  Its kind of involved but another path might be to go down the path of etherreal  or something similar and do some logging that way.

Cory

I would believe that the DIR is causing all kinds of issues by definition if I was also hit by those. But...since none of the issues arises I do not blame the router. Even though it would seem obvious that an error that occurs only with the DIR in the loop can be blamed on the router, this is not necessarily the case. A router does much more than a switch a will therefore confront you with more general networking issues on the modem or the client PC. 

[bluenote]

Hey Eddie

I don't want to hijack this thread any further, so I'm going to sign off this tangent with this comment -

Fortunately/unfortunately we all have different equipment/configurations/requirements and received our boxes with different firmwares, etcetera.  As an example, I have a linksys VOIP adapter that simply needs DHCP info from the router, but won't get it properly with the shipped or current FW.  The beta firmware fixes this problem, and the VOIP adapter worked fine with two other routers ... so the logical assumption is, the DIR 655 was at fault.  Other factors (such as the presence of torrent traffic, for example) can also have a big impact on performance and stability (not only with Dlink routers, FYI).

And yes, a router is more than a switch.  However, when switching traffic from one inside port to another, I can't think of too many router functions that *should* be involved.  Obviously, this may or may not be the case in actuality.

Cory

[EddieZ]

Just have a look at the extras a router has compared to a switch. Those are exactly the extra things the router traffic needs to deal with. And about VOIP adapters, phew...had my share of problems with those in the past and all came down to very flakey firmware on those boxes, unpredictable SOB's 

At least the router issues are not generic, mine is really working flawlessly. No reboots, no wireless disconnects, etc.

Good luck

[sixersclt]

I ran DPC Latency timer on both ends and results are both green when hooked through the 655.  Average between 20-60 micro sec. 

I am streaming live H264 or Std Def Video/Audio, so it never goes through the hard disks.  The program streams over UDP 239.255.255.255 which shows as a multicast in the 655. 

I picked up 2 Intel Pro/1000 NICs for dirt cheap.  Once they arrive, we shall continue…

[tipstir]

I ran DPC Latency timer on both ends and results are both green when hooked through the 655.  Average between 20-60 micro sec. 

I am streaming live H264 or Std Def Video/Audio, so it never goes through the hard disks.  The program streams over UDP 239.255.255.255 which shows as a multicast in the 655. 

I picked up 2 Intel Pro/1000 NICs for dirt cheap.  Once they arrive, we shall continue…

4 systems are the NIC that are Gig all uses Realtek 3 uses Encore and one is TP-LINK (rates it 2GB) but we now how that goes. I stream over 5GB (mini series) to 7x Hauppauge MediaMVP from my HTPC. Been doing this since 2003 using onboard NiCs VIA Fast 100mpbs. Onboard NICs are not the best way to go. There have been problems reported over the years. I disabled those NICs and use the PCI ones. The PCI-E suppose to be slightly better. I also use VLC streaming over the wireless G and N to wireless laptops no problem there. Gig MPG2 which I record using SageTV then stream though recorded media to 4x HDTVs again no issues. I do find bad switches can cause jitter, shuttering, audio sync problems. I've ordered new switches I go through them like crazy. I going for business class switch for 100mbps side. the one I use now for Gig is a clone of DLINK 8-port it's just metal case 8K mac table/144KB patch buffer memory.

You should look out for Throughput in a switch. You had reported that your NIC was going from 1000mbps to 100mbps. You should replace those NIC as they have duff ports on them. Not DLINK. I had the same issue with one of the Encore. I did everything you could think of and it still did it. Bad NIC. TP-LINK was very cheap but they're ROHS gave it a try. So far no issues.