Print

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

[svg1234]

I have a DIR-825 with 2.60VT firmware (rented from Videotron).

Even though the manual says the stateful firewall should have a timeout on connections of 240 seconds or 7800 seconds, all of my connections start at a mere 120 seconds. I'm having trouble with IMAP IDLE pushing e-mails because the connections timeout so quickly (before any stay alive can be sent). A connection to the e-mail server gets opened on 143 (Videotron) or 993 (encrypted - google, e.g.), and I see the connection on the Internet Sessions page, the timeout starts at 120. When it hits 0, the connection is no longer displayed (it is not renewed), and the IMAP IDLE craps out because the server can't find the client (i.e. the connection has been closed). But it's not just on those ports or servers. ALL of my TCP sessions begin at a mere 120 seconds! Even for a home router, isn't this way too low?

Can someone please confirm that their DIR-825, on the Internet Sessions page, shows initial timeout values of greater than 120 for a TCP connection? I would love to see a picture of that screen showing higher values. Does it start at 240? Do you ever see a connection start at a timeout of 7800?

I see no way of changing the timeout value. Is it possible to force connections on certain ports to begin at a higher timeout value?

Thank you.

[FurryNutz]

You'll need to refer to Videotron for information regarding your DIR-825. Even though the HW is from DLink, Videotron coded the FW for there ISP services there and they don't use DLinks OEM FW. I presume the options and features are different between them.

[svg1234]

I understand, but all I am looking for is confirmation that *ANY* DIR-825 starts with timeout values other than 120 seconds (240 or 7800). That's all. Thank you.

[FurryNutz]

Looking at my 826L the lowest I see is 10 and the max is 238 and anything in between those two values.

[svg1234]

Well, I spoke with Videotron, but they were useless. Didn't even understand what the problem is.

So I took matters into my own hands and flashed it via the Router Recovery Mode with the latest oem firmware from dlink (2.09NAB08) just to see if it would help matters. I was very pleased to see that the timeout setting is now a whopping 24 hours (86,400). lol. Isn't that nuts? From 120 seconds to 86,400 seconds. MUCH better. Now everything works as it should.

[FurryNutz]

Enjoy.