Print

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

[Geck]

I am having a recurring problem with tcp sessions timing out / getting reset.  I'm using the DIR-655 with PPPoE on a Qwest DSL line.  Everything appears to be working fine (including my ipv6 tunnel) except for this issue where my long running ssh & database connections are being reset after a period of time.  Currently have 2.03NA loaded, tried using 2.07NA but couldn't get ipv6 working correctly with the newer version.  The couple other routers I've use (Buffalo & Airport) didn't have this issue.  Anyone else experience this, and/or have a fix for this issue?

[FurryNutz]

Welcome!
What region are you located?
Are you wired or wireless connected to the router?


Some things to try:
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
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking.

Ensure that ALWAYS ON is enabled under Setup/Internet/Manual/Connection Type

[Geck]

Qwest DSL in the Southwest using transparent bridging to the DIR-655 configured with PPPoE.

I'm using a wired connection with a static ip address, so no dhcp or wifi.  My static ip address on the lan is separate from any dhcp ranges.  These are all disabled, QoS, Advanced DNS, SPI, Wan traffic shaping, WISH.  These are enabled, UpnP, Multicast.  PPPoE set to Always On.

I did not use the "Endpoint Independent" setting, since the manual specifies it has a 5 minute idle time-out setting.  I used "Address Restricted" instead.

Everything is working fine except for this one issue with tcp connections being reset after being idle for a few minutes.  Unfortunately when running database queries that take time to complete, the session gets dropped before the query finishes.

[FurryNutz]

Have you tried using DHCP and reserving the IP addresses ON the router and set your devices to automatic obtain IP addressing?

What happens if you turn OFF uPnP?

I might contact DLink 2nd level support and see if there is any more information. IF they tell you to update to v2.07, tell them that v2.07 breaks a few things and is not recommended. You could try it however I don't think it would make any difference. You can go back to v2.03 from v2.07.

Let us know how it goes.

[Geck]

I did try 2.07NA but it broke my IPv6 over IPv4 tunnel setup so I went back to 2.03NA which IPv6 works fine on.

[FurryNutz]

Ok, was wondering about that, something else to add to the list of items v2.07 breaks.  
Curious, what applications, if any, are you using for this database connection and I presume this is connecting to a different site or remote location?

I'd get a hold of DLink and ask and see whats the deal with the timeout.

Keep us posted on how it goes.

[Geck]

One is an ssh client, the other is a mysql client from my local Redhat linux box to several remote Redhat linux box in different locations.  The Buffalotech router I replaced would reset any idle tcp connections after 24 hours.  The DIR-655 idle timeout is much shorter, yet I don't see anywhere I can adjust that and I've already disabled the stuff, like the firewall, that would typically have an idle timer reset.

[FurryNutz]

I would ask DLink support about this. I'm wondering if your client SW could be configured in anyway to hold the connection? Might be some settings there as well. DLink routers don't usually have any sort of idle timeout settings.