D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: salahx on November 04, 2011, 11:34:11 AM
-
I bought 2 of these not to long ago, to replace 2 older routers (a Zyxel and Linksys ). However so far I've run into the following 3 problems:
1) Lots of intermittent hang/stalls, especially on web pages. Turning off SPI seems to stop it. Did not occur with old router or direct connection, happens on both routers.
2) NAT TCP Timeouts? TCP connection idle for more than 60 seconds seems to timeout (so far DCC and MSN ) - a "connection reset by peer" message occurs if anything is sent after timeout period. So far no solution: Tunring off SPI, QoS, making endpoint independent doesn't help. Does nto happen directly, without router, does happen with both routers.
3) Routing screen only has "WAN" dropdown, no "LAN". I have a VPN between me and my parents networks , the VPN server is on another machine, it would be too cumbersome - and on some devices, impossible to add the route to every machine - this was the express reason I bought these (that and IPv6 support for the inevitable switch). Seems to be a UI limitation only - using Firebug was able to get this to work.
4) My ISP, Charter, now has a 6rd gateway for ipv6 connectivity (http://www.myaccount.charter.com/customers/Support.aspx?SupportArticleID=2665). However there is no 6rd config in the IPv6 menu in the router, and none of the other options seem right either. Am I missing something or is this just not supported (yet)?
-
What HW version is your router?
What FW version is currently loaded?
What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options.
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.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.
What wireless modes are you using?
Try single mode G or mixed G and N?
What security mode are you using? WEP, WPA or WPA2? Preferred is WPA-Personal. WPA2/Auto TPIK and AE
6RD is a fairly new protocol so I don't think it was implemented on the 615. Not sure if it will be.
Get ahold of Patrick533 over on the 825 forum about 6RD.
If you need some help, maybe we can use teamviewer (http://www.teamviewer.com) and review your routers settings with you.
Keep us posted.
-
Hardware version E3
Firmware 5.10
Charter / Cable - both routers
Motorola SB5120 - Stand Alone - both routers
DNS is populated
Turned off QoS - didn't help
Advanced DNS was never enabled
DNS Relay was already enabled
DHCP address were already reserved for both computers
Changed firewall settings - didn't help
Using G+N, however the computers are both wired
WPA2-AES on one router, WPA-Mixed on the other (Due to PSP 1000 series, hardware not WPA2 capable)
-
Ok, how do you have these router(s) set up? Are you using these 2 router in tandem or at different places?
What OS and web browsers are you using on the PCs?
-
They are in 2 different places, on 2 different network. They are residential gateway to the Internet. Both computers run Linux (one Gentoo, one Fedora). The 2 Linux computers are openvpn gateway between the 2 networks, each network has several devices (Windows, Macs, game systems, DVD players, printers - no smartphones or tablets yet).
All computers are browsing via Firefox usually, occasionally using IE (Windows) or Safari (Mac), some of the game systems have embedded browsers as well)
-
Are you sure the 2 Linux PCs are set for correctly for this operation?
Does normal internet work well for a PC directly connected to the router and getting internet correctly with out going thru any of the Linux Gateways?
-
Yes, they are configured correctly for this (they wre configured long before these routers were introduced)
The Internet works the same when 2 Linux PC are disabled - all the same problem above occur.
-
I would have you ensure that the cables between the ISP modem and routers are in good working condition. swap cables just to be sure. I have experiences some in box cables are not mfr'd well.
This is happening on 2 of the same routers and different networks. Possible these units could be faulty.
Can you put one of the older routers back online for a quick test to see if the problem goes away?
-
I rehooked up and configured the old router on my side of the network. There have been no disconnects or timeout on idle connections (using the same cable as I was with the DIR-615) in the last hour (which normally happen every few minutes for stalls and every 60 seconds for TCP timeouts)
-
Must say this is an odd issue. Really leaning towards the routers being bad.
I suppose as a last effort would be for someone to teamviewer.com in and take a look at the router settings with you if your interested.
-
While I was going through preparing for the end of DST, the router did support changing on dates, but while there there was one for Nov 6, there NOT one for Mar 11 (which is when DST starts in 2012).
I loaded DD-WRT to see if its some kind of hardware problem, the router works fine with it (no NAT timeouts, no stall with SPI, static route GUI) so the router itself seems OK - this just seems like a case of buggy firmware. I was hoping, by buying a brand-name router, rather than some store Brand X, I wouldn't run into this (and I've tried several, many of the firmwares are broken to the port of unusability).
Unfortunately while DD-WRT support many things (that I don't need), IPv6 and WPS support are not among them (not for this model, anyway) - which is what I wanted, so I'd rather use the factory firmware. I'd just return them to the store for a different kind of router, but they were refurbs and the return period has expired. 5.10US seems to be the latest (and so far, only) firmware version - nearly 2 years old.
-
Well you can use WRT, just know that if you want support from Dlink, you'll need to put on OEM FW. Good luck.
-
>TCP connection idle for more than 60 seconds seems to timeout
I have the same problem with my new DIR 601. The doc states that established TCP connections have a 7800 second (130 minute) idle timeout. However, any new TCP connection I establish gets killed by the DIR601 after only 60 seconds. I can verify this in the dlink's STATUS menu, INTERNET SESSIONS. This shows me the connections and the dlink's idle timer for them (which never is higher than 59 seconds even for a brand new TCP connection), and if I keep refreshing the page, I can watch it go to 0, and then the next time I try to use the application whose connection that was, it can't use the connection and has to recover. The DLINK doesn't even do the courtesy of announcing to the application that it RESET the connection. It just dumps it... which can make applications take EVEN LONGER to recover, since the application then has to try and retry to use the connection over and over until it gives up and finally either announces the problem or tries to open a brand new connection.
If I remove my dlink from the mix and connect directly to my ISPs equipment, I have no problems. (But of course no private network or firewall.) I need a properly functional router!
P.S. I support networks for a living, so 98% chance I'm not just making a user error. And the remaining 2% is mostly because I'm humble, not because I actually think I might be wrong. :)
-
What Hardware version is your router? Look at sticker under router.
What Firmware version is currently loaded? Found on routers web page under status.
What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Some things to try:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turn off ALL QoS (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
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.
What wireless modes are you using?
Try single mode G or mixed G and N?
What security mode are you using? WEP, WPA or WPA2? Preferred is WPA-Personal. WPA2/Auto TPIK and AES.
What wireless devices do you have connected?
Any cordless house phones?
Any other WiFi routers in the area?
Turn off Short GI and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
Turn off all anti virus and firewall programs on PC while testing.
Turn off all devices accept for one wired PC while testing.
>TCP connection idle for more than 60 seconds seems to timeout
I have the same problem with my new DIR 601. The doc states that established TCP connections have a 7800 second (130 minute) idle timeout. However, any new TCP connection I establish gets killed by the DIR601 after only 60 seconds. I can verify this in the dlink's STATUS menu, INTERNET SESSIONS. This shows me the connections and the dlink's idle timer for them (which never is higher than 59 seconds even for a brand new TCP connection), and if I keep refreshing the page, I can watch it go to 0, and then the next time I try to use the application whose connection that was, it can't use the connection and has to recover. The DLINK doesn't even do the courtesy of announcing to the application that it RESET the connection. It just dumps it... which can make applications take EVEN LONGER to recover, since the application then has to try and retry to use the connection over and over until it gives up and finally either announces the problem or tries to open a brand new connection.
If I remove my dlink from the mix and connect directly to my ISPs equipment, I have no problems. (But of course no private network or firewall.) I need a properly functional router!
P.S. I support networks for a living, so 98% chance I'm not just making a user error. And the remaining 2% is mostly because I'm humble, not because I actually think I might be wrong. :)
-
What Hardware version is your router? Look at sticker under router.
A1
What Firmware version is currently loaded? Found on routers web page under status.
1.02NA (and the unit claims this is current when I tell it to check)
What ISP Service do you have? Cable or DSL?
I have VeracityNetworks, it is fiber optic.
What ISP Modem do you have? Stand Alone or built in router?
I believe the unit it is a stand alone but I have very little information about it's true nature. Ethernet on my side, fiber goes out.
What ISP Modem make and model do you have?
World Wide Packets, Lightning Edge 46 (Normally I wouldn't even know this, because it's sealed in the ISP's box. But last time their tech was here he left it unlocked.)
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
N/A
Some things to try:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Done
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Done (had tried this already, but now is done again).
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
It is off. Never turned it on.
Turn on DNS Relay under Setup/Networking.
It is on.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking
Set it up this way in the first place
Ensure devices are set to auto obtain an IP address.
Done
Set Firewall settings to Endpoint Independent for TCP and UDP.
Done. (In fact I had already tried all variations of these settings, but now they are back to this).
Turn off all anti virus and firewall programs on PC while testing.
Done
What wireless modes are you using?
I am not using wireless for this, I am just using a wired PC. In fact, today I disabled the wireless completely to see if that made any difference. It did not. So the following questions become irrelevant:
Try single mode G or mixed G and N?
What security mode are you using? WEP, WPA or WPA2? Preferred is WPA-Personal. WPA2/Auto TPIK and AES.
What wireless devices do you have connected?
Any cordless house phones?
Any other WiFi routers in the area?
Turn off Short GI and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
Turn off all anti virus and firewall programs on PC while testing.
Turn off all devices accept for one wired PC while testing.
------------------------------
None of this changed the behavior in question. What I really need is someone at DLINK to pull out a 601 (or 615 as the previous poster had) and test this. It's easy. Make a new tcp connection and check the timeout in STATUS / INTERNET SESSIONS. If it is always just 60 seconds or less on established connections, then the problem is reproduced and they troubleshoot the problem there until they isolate and fix it. (I have emailed support but have not heard back. But it's only been 24 hours, so I'm giving it more time.)
-
Always go directly to the web site for FW updates. For some reason, using the routers FW update checker doesn't work or the servers are not correctly identifying whats being requested.
It's possible this could be a compatibility issue with your ISP Modem, have seen some Fiber issues with this routers. Possible FW issue to:
v1.10 is most resent. (http://www.dlink.com/products/?tab=3&pid=DIR-615&rev=DIR-615)
This router at a home or business? If at a business I would recommend getting into a different model router for business. These low end 6 Series routers are good however generally designed for mom and pop email and surfing at home.
If you really wanna, Do the FW update and follow the FW update process outlined in the FW Update sticky.
Keep us posted.
-
The 1.10 revision is for the 615 and mine is the 601. I checked the website for 601 and there, it shows 1.02NA as the current. I'm tempted to try 1.01NA and see if the problem occurs there, too. But I'm not sure if it's advisable or even possible. Thoughts?
This is a "home" implementation... but I use my home office to work from on many occasions.
My impression is that most web browsing and such opens tcp connections, uses them, then closes them, so they don't have to remain open when idle. So I can see how this problem might not manifest itself for many people. However, I rely on some applications that form a TCP connection and leave it up and often idle for a while, then wants to use them again. Having those silently "killed" by the 601 is dramatically slowing me down.
Ironically, this 601 is replacing a 7 year old ZyXel which only cost me $5 after rebate. It never gave me any problems until the day it burnt out (10 days ago). ZyXel certainly doesn't have the reputation of Dlink, and some of it's features weren't as nice... but at least it let me have idle tcp connections.
-
Opps I got my links crossed, sorry bout that.
Possible that you can down grade and see if it will let you. Not sure if it will. It might as I don't think there is a major version between these two, only minor. Can give it a go.
Follow the FW update sticky process.
I can understand the frustrations of working with this router however I'm wondering after you mention that what your doing at home and needing these services to remain open is somewhat beyond the scope and design of this router. I'm curious if something better like a DGL-4500 would serve you better. I have this router, a DIR-825, DIR-655 and a DIR-657 routers. From my experience so far, they were great for general use and gaming. I also have a roommate who VPNs into work when needed and haven't had any issues. However I'm not sure what kind of open services besides gaming that I can relate to your services that you need.
Any thing you can elate here to help us understand what you are doing with this router? What applications are you using that you need these services to be open all the time? Will help us understand some.
It's possible that there is a better fit router out there that will handle your needs and probably this one just might not be suited for your needs at this time. I would try
Maybe someone can review your router settings with you using teamviewer. (http://www.teamviewer.com)
-
Two apps which I use a lot and are effected are Novell Groupwise (email) and Novell Messenger (chat). Both of these form TCP connections to a server and then (depending on whether I'm actively used them) they may sit idle for a time. If the connection is no longer available when they want to do work again, they "stall" while trying / retrying the dead connection. Or in chat, other people may see me as "online" but then they try to reach me and I never get it. To them I'm just not responding. Those applications can recover eventually, but in the meantime I'm frequently delayed for 30 to 60 seconds. Often the whole windows desktop stalls while these are trying to recover, too.
Another example is FTP for file transfers. FTP sessions use one TCP connection for "control" (commands) and when you transfer a file, it opens a second TCP "data connection" for that purpose. If you are transfering a file which takes more than 60 seconds, the data connection is okay (as it is not idle) but the control connection gets killed by the DIR601 because it is idle until the data connection finishes its job.
While I understand that this is a "bottom line" router, this is fundamental communication. And even the router's doc claims it will allow established connections to be idle for 7800 seconds before terminating them. I'm only seeking capability for which the router is supposedly designed. Within a few days I will either have DLINK authorize a replacement or I will return it to the store and go another way.
I just reread the above. It kind sounds like I'm ranting or something. I'm not... this is just intended to relate facts and what my plans are. No hard feelings, and I thank you FN for taking time to respond.
-
Hey frustration is understood man and can relate.
Novell is pretty high end business application and I would presume that these routers would probably not fit your needs when using Novell man. Not sure if even the DGL-4500 or DIR-825 could as I've never used Novell with a home end router before. It's always been corporate business class routers for that.
I would recommend, if you have the time and if you want to, try the DGL-4500, DIR-825 or DIR-655. The only diff between the 825 and 655 is that the 655 doesn't have 5Ghz radio. The DGL-4500 has both however you can only run either or radios, not both at the same time. I currently have all 3 and enjoy them greatly. However I don't use Novell so really not sure if either one of these routers would work. I can ask some resources and see what DLink might recommend using for Novell applications. They might have something.
Let me know.
-
I've been going over the source code (Ironic that the source code is packaged in the proprietary RAR Format). Its based on a 2.6.15 kernel, which is over 5 years old. Netfilter has since been completely revamped and the source looks totally different to what it did then...
However back then the TCP timeout stuff should be in net/ipv4/netfilter/ip_conntrack_proto_tcp.c. A quick glance shows ip_ct_tcp_timeout_established is set to 5 days. Those timeout are stored in a structure array tcp_timeouts which is only reference in 1 place in that file, on line 1069. tcp_timeouts[3] is 5 days, but the one right above it ip_ct_tcp_timeout_syn_recv IS 60 seconds (which is consistent with what we've been seeing), which makes me thing there might be an off-by-one error. The router does seem to be properly transitioning states correctly (according http://192.168.0.1/internet_sessions.asp) However the state machine here is pretty complicated, i need to study it for a few hours....
This also explains why no 6rd support - 6rd support wasn't added until Linux 2.6.33.
-
Viola, I found it! Turns out it not a kernel bug at all. Back then, there's a sysctl to change the nat timeout
Took the source code, and running "strings Matrix/projects/DIR-615WW_E4/apps/rc/firewall.o" I see the folowing:
echo "2048" > /proc/sys/net/ipv4/ip_conntrack_max
echo "1024 65000" > /proc/sys/net/ipv4/ip_local_port_range
echo "65" > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
echo 50 > /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout
echo "60" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
echo 5 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close
echo 30 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait
echo 60 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait
echo 3 > /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout
echo 1 > /proc/sys/net/ipv4/conf/all/arp_ignore
The offending line is in BOLD. The documentation the router states the following Support->Status->Internet Sessions
Time Out
The number of seconds of idle time until the router considers the session terminated. The initial value of Time Out depends on the type and state of the connection.
300 seconds
UDP connections.
240 seconds
Reset or closed TCP connections. The connection does not close instantly so that lingering packets can pass or the connection can be re-established.
7800 seconds
Established TCP connections.
So it SHOULD state:
echo "7800" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
echo "300" > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
echo "240" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close
Some of those other values look suspicious as well. These are the default values:
echo -n "256" > /proc/sys/net/ipv4/ip_conntrack_max ( 1/16384 of RAM / (sizeof struct list_head) * 8 - the the dir-615, 32 MB (33554432 bytes) of ram, struct list_head is 2 pointers, on this arch, that's 8 bytes) so 33554432 / 16384 /8 * 8
echo -n "30" > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
echo -n "600" > /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout
echo -n "432000" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
echo -n "10" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close
echo -n "60" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_close_wait
echo -n "120" > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_time_wait
echo -n "30" > /proc/sys/net/ipv4/netfilter/ip_conntrack_icmp_timeout
2048 seems about right for ip_conntrack_max, no comment on the others.
-
Excellent research, salahx. By the way, I see that the strings you found also show:
echo "65" > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout
And I have noticed that most (but not all) of my udp traffic seems to result in a 65 second timeout in the same Status > Internet Sessions screen that I was watching my TCP timeouts. So that point matches up exactly with my experience, too.
I had talked with DLINK support over the phone... they were stumped and thought I had a defective unit, and offered a replacement. I had my doubts that this was a one-unit glitch (it seemed very programatic), but was willing to try anyway. However, they failed to send me the email (or maybe they failed to correct my address, which I told them was slightly off when they read it back to me). So I was not able to arrange for a replacement and eventually returned this DIR601 to the store and got a Belkin N150 instead. The Belkin doesn't have as many bells and whistles in the administration menus (no status screen showing my connections, and no way to reserve certain DHCP assignments for certain MAC addresses), but it works great with idle TCP connections. And my wireless seems faster. I've been using it a week and have only seen one problem, one time (which isn't necessarily the router's fault... not sure): It had assigned an address to one of my wired desktops, supposedly with a "forever" lease, but a day later when I woke up that desktop it had a IP conflict with another desktop which somehow had obtained the same address. So for anything where I need a truly permanent assignment, I'm configuring statically at the PC, outside of the DHCP range.