News: This forum is now permanently frozen.
Pages: [1]
Topic: TCP timeout too soon  (Read 6901 times)
« on: March 08, 2009, 20:23:24 »
webclaus *
Posts: 4

Hi folks,

I'm experiencing a TCP timeout way sooner than my setting. I've set it to 3600 but I get timeouts after just a few minutes. Five minutes away from an ssh connection and I have to re-connect Sad

Are there other settings that can affect the timeout limit, or anything else I should be aware of?
« Reply #1 on: March 08, 2009, 22:16:12 »
Fred Grayson *****
Posts: 994

That might be your ssh server dropping the connection, not m0n0wall. See if you can enable a "keep alive" in either the server or client.

--
Google is your friend and Bob's your uncle.
« Reply #2 on: March 08, 2009, 22:22:13 »
webclaus *
Posts: 4

Well, connecting to the same servers outside my wall I never loose the connection. And I'm connecting from my good ol' laptop at all times, so I don't think this is the issue.
« Reply #3 on: March 08, 2009, 23:36:19 »
Fred Grayson *****
Posts: 994

No problems here (latest beta of m0nowall) , but then again we have KeepAlive set in our servers.

It wouldn't hurt to at least check that setting and enable it if you can.

--
Google is your friend and Bob's your uncle.
« Reply #4 on: March 09, 2009, 00:39:49 »
webclaus *
Posts: 4

You're right, it didn't hurt Smiley

However, that doesn't change anything.

I should have mentioned, that this is not just when using ssh. I have a slimserver set up streaming music and that dies too when I access it from outside my FW. I believe slimserver "streams" in the way that it sends a chunk of music and waits for you to request the next track. So, in between tracks I get disconnected.

« Reply #5 on: March 19, 2009, 19:25:09 »
adram *
Posts: 1

seeing the same problem with long running TCP connections (esp. ssh) and keepalives don't help -- I've set the timeout to 86400 (24 hours) to no avail. This started with 1.3b15 (was running 1.3b12 before and didn't experience this). Very annoying.
« Reply #6 on: March 19, 2009, 19:56:17 »
webclaus *
Posts: 4

I forget which beta version, but I also did not have this problem earlier in the beta stream.

There must be more people out there seing this?
« Reply #7 on: June 16, 2009, 02:12:50 »
swindmill *
Posts: 9

I concur. With my connection running through m0n0wall's NAT in the latest 1.3 betas my SSH connections die after a short period of time without activity.

If I run the same connection through pfSense running on the same hardware I do not experience this issue.
« Reply #8 on: July 21, 2009, 18:40:55 »
liggyman *
Posts: 8

We are experiencing the same issue.  At the very least SSH, and RDP are effected.
« Reply #9 on: August 01, 2009, 03:42:41 »
ke4pym *
Posts: 10

I think it's a problem with FreeBSD 6.x, myself.  Back in the day, before I started using m0n0, and used a stand alone FBSD box, I started noticing this issue.

As soon as m0n0 went from the 4x release to the 6x release, I immediately noticed it in my telnet and SSH connections.  I don't see it in anything else, however.
« Reply #10 on: August 02, 2009, 22:03:45 »
Manuel Kasper
Administrator
*****
Posts: 364

This bug is now being investigated here: http://forum.m0n0.ch/index.php/topic,3253.0.html
« Reply #11 on: June 08, 2010, 11:23:06 »
E *
Posts: 4

This seems to be still broken in 1.32. All my SSH connections timeout after few minutes, but without monowall they stay up just fine.
« Reply #12 on: June 08, 2010, 13:38:39 »
rpsmith ***
Posts: 113

I just used PuTTY to SSH into a remote pfSense firewall and let it set idle for over an hour. I then issued a ping command without a problem.  My local firewall is running 1.32 - Generic PC.  Looks to be working from what I can tell.

Roy...
« Reply #13 on: June 08, 2010, 15:21:47 »
E *
Posts: 4

I just used PuTTY to SSH into a remote pfSense firewall and let it set idle for over an hour. I then issued a ping command without a problem.  My local firewall is running 1.32 - Generic PC.  Looks to be working from what I can tell.

Roy...

Looks like this only happens when I'm on WLAN connection. I use WPA+WPA2 PSK with TKIP+AES/CCMP and the wlan card on my Monowall is Atheros 5212.
« Reply #14 on: June 08, 2010, 15:45:41 »
rpsmith ***
Posts: 113

Might be time to upgrade to a real hardware access point.

 Smiley

Roy...
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines