Print

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

[FurryNutz]

hat ISP Service do you have? Cable or DSL?
What ISP Modem make and model do you have?
Is this wired or wireless to the router? Or both?

I recommend going back to v2.03 or v2.07 and see if the problem follows or not.
If you downgrade, do a factory reset first, then send the .bin file, then after the router is back to ready, do one more factory reset and configure from scratch.

What was loaded on the router before upgrading to v2.10?

Hi there!
Recently updated to 2.10NA Rev.B.
Have been seeing a lot of problems.  I'm having major internet slows, 10-15 second disconnects etc.
At first I thought it was the provider so I bypassed the router and used the ****py Cable modem directly and had no issues.

Did A FULL Factory reset, wipe clean, re-configured and still seeing major intermittent issues:

The issues are around: Dropped packets and the /rootDesc.xml not found, responding ERROR 404
The IPV6 is enabled Local only.
I disabled Advanced DNS
I even set the UDP and TCP firewall settings to Endpoint independent (very uncomfortable with this but desperate).
QoS is disabled.


There are about 30-40 dropped packets when I notice slow downs (skype calls especially).

Snippet of Log Entries"
info     [47148.970000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=75.176.22.240
DST=192.168.22.100 PROTO=ICMP TYPE=3 CODE=3
info     [47144.960000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=75.176.22.240 DST=192.168.22.100 PROTO=ICMP TYPE=3 CODE=3
notice   Jan 30 11:04:02    /rootDesc.xml not found, responding ERROR 404

[electric_menace]

Thanks for the prompt reply.

Time Warner (Road Runner 30/5 down/up)
UBEE3611 piece of crap.
Both - Disabled wireless and wired - been operating as a bridge mode.

I came from v.2.07

Do I need really need to downgrade or should I hold out and see if I can help figure out what is going on with 2.10.

[FurryNutz]

Thanks for the prompt reply.

Time Warner (Road Runner 30/5 down/up)
UBEE3611 piece of ****.
Both - Disabled wireless and wired - been operating as a bridge mode.
Any chance TW allows BYOM? If so, I recommend a Motorola SB 6 Series stand alone cable modem.

I came from v.2.07
Was this problem seen on v2.07?
Do I need really need to downgrade or should I hold out and see if I can help figure out what is going on with 2.10.

I ran my 655 loaded w v2.10 last week and I don't see these problems. However I don't have the same modem either. I recommend trying a different ISP modem if possible.

Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
If IPv6 is an option on the router, select Local Connection Only or Disable IPv6 options under Setup/IPv6.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
Set current Time Zone, Date and Time. Use an NTP server feature. Tools/Time.
 
Link>Wireless Installation Considerations
What wireless modes are you using? Under Setup/Wireless/Manual.
Try single mode G or N or mixed G and N?
Channel Width set for Auto 20/40Mhz or try 20Mhz only.
Try setting a manual channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear.
What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto.
What wireless devices do you have connected?
Any cordless house phones?
Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many?
Turn off WISH, and WPS under Advanced.
Try turning off Short GI, WLAN Partition,and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
Enable WMM Enable Under Advanced/Advanced Wireless.

Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Turn off all devices accept for one wired PC while testing.

Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended.

[electric_menace]

Lol Ok.
So the recommendation is spend a ton of money on new equipment and rewire your house

Is there a developer forum where we can look into this a bit deeper and see if we can debug the issue?

Thanks.

[FurryNutz]

Was this problem seen on v2.07?
What was the reason for updating to v2.10?
Have you tried using some of the suggestions offered?

Recommendations for upgrading HW is not expensive. Modems are only $100 or less and it helps save any rental fees that ISP sometimes impose on users. LAN cables are cheap as well. I upgrade my  CAT 6 patch cables for under $30 bucks.

You need to narrow down where the symptoms are coming from. Turn off ALL devices accept for 1 wired PC. Ensure 3rd party security and any other background running programs are disabled. Test with this one PC. Then graduate turning on the next one. See if the problem appears or not.

If your looking for further information, you'll need to contact DLink support, ask for level 2 or higher.

Good Luck.

[electric_menace]

It's definitely 2.10. I did not see this in 2.07.

The reason I upgraded is - it was published as official firmware - so like a good soldier I've upgraded.

Also expensive is relative depending on who you are talking to.
The rewire for me would include tearing out the walls because my house is pre-wired.

[FurryNutz]

Please review this:
FW Update Process

Cabling could be a factor on this. I would isolation the router from all other cables and go directly from the PC to the router then to the ISP modem. This will also help to see of the problem exists still. The cabling I recommend is between the ISP modem and router mostly and replacing non-inwall cabling. Inwall cabling is a different animal.

If this was not seen on v2.07, I recommend that you review the FW Update process and go back to v2.07. Theres many cases that being a good soldier can cause problems. Good rule to think about before updating, Review the FW update release notes on Dlinks main web page before updating. Look at the notes, if your note effected or seeing or having problems with what is listed in the release notes, then it's recommended to keep what is currently loaded and do not upgrade. Which brings me to say, If it works, Don't Fix it!

[electric_menace]

The cabling between the Router to the modem is CAT6. Sorry I misunderstood. I thought you were referring to the workstation to patch panel cabling.

From personal perspective - If it works, Don't fix it is a big fallacy.  That attitude hinders innovation and improvement.

Being a tech-geek I was looking to see if i can help debug the issues that are occurring from a firmware-developer perspective.

In any case thanks for your insight.

[FurryNutz]

I understand the need to always improve and move forward, however for most cases again, doing FW updates can be problematic for the average user. And taking into considerations of that and what the average user really needs and what comes in FW updates, again, look at the updates, if most users are not effected by what is in the FW updates, I don't regard taking being safe and not updating a fallacy. However for us tech geeks, of course, we gotta try it man. 

Not lot of DLink developers review the forum we believe. I think they used to years ago however since have moved on or mainly bother with what comes in officially at Customer Support. We do pass on problems to contacts we know of and they get forwarded to the correct project for review. What happens from there on out, anyones guess. We don't get much feedback from that. 

Which is why I do recommend for some users that if we can resolve it here and it seems to be something that DLink needs to be made aware of, phone contacting DLink is highly recommended to get visibility to them and make them aware of possible problems that we can't fix here at a low level.

Try some of the suggestions and see how it works out. Keep us posted.

[electric_menace]

Kept trying to play with it -- finally went back to 2.03 with 2 factory resets and have not had any problems since.

[FurryNutz]

Good to hear, Enjoy.

[FurryNutz]

Anyone willing to test the v2.10 (Beta) build on the Canada site? Not sure if this fixes the known Guest Zone issue seen on some wireless devices. Please post your results for those that do.

v2.10   06/02/2013
(Beta)

• Remove 404 feature
 • Fixed some IPv6 issues
 • Fixed mDNS issue
 • Fix Autodetect 6rd mode MTU issue.

[FurryNutz]

Premiminary test results look good. I loaded the Canadian version and Guest Zone is fixed. At least for me, testing with out any security and then with WPA2 and AES only and both MacBook Pro and iPhone 4S connected with out issue. I didn't test the router online with the ISP modem. No time.

Hope this might help others.

[nicknml]

The 2.10NA version has some uptime stability issues, mine just crashed and rebooted after an uptime of about 2 months.

[FurryNutz]

You might try the v2.10 version on the Canada site.