persistent TCP under unreliable wireless AP

kaichen · 09-28-2004

I am running XP connected to a wireless AP via DHCP. When the link goes
down due to transient wireless outage, the network icon gives me "network
cable unplugged" message. But the connection usually goes up again
quickly (e.g. after 5-30 seconds).

The problem is that my TCP connections (e.g. ssh) are all lost after the
outage. The scenario goes like this:
1) The TCP session is connected. Netstat shows that it is "ESTABLISHED".
2) When the link is down, after a few seconds, the TCP connection drops with an error message like "connection to server lost". Netstat shows that the TCP
session is gone.
3) After the link is up again, DHCP gives me back the old IP. However, the
previous TCP connection cannot resume, and it has to be re-started again,
which is very annoying.

I am looking for a solution to keep the TCP connection persistent after a
transient wireless link outage. Is there any registry in XP that can do
this?

Thanks in advance for any pointers.

-KC

beakmyn · 09-28-2004

Although I'm no expert. I have three opinions on the matter.
1. Would a static IP address be better?
2. This may be built security mechanism to ssh to prevent someone from hijacking your connection
3. Because the connection dropped the server side of your TCP connection isn't going to hold a connection open if there's nothing on the other end.

Chris · 09-28-2004

Quote:

Originally Posted by beakmyn

Although I'm no expert. I have three opinions on the matter.
1. Would a static IP address be better?
2. This may be built security mechanism to ssh to prevent someone from hijacking your connection
3. Because the connection dropped the server side of your TCP connection isn't going to hold a connection open if there's nothing on the other end.

1. Static IP isn't going to matter.
2. Not really a security mechanism, just how TCP/IP works.
3. Yep. The connection is broken when the link goes down and has to be re established. There is no workaround.

09-28-2004	#1 (permalink)
kaichen Registered Member Join Date: Sep 2004 Posts: 1	persistent TCP under unreliable wireless AP I am running XP connected to a wireless AP via DHCP. When the link goes down due to transient wireless outage, the network icon gives me "network cable unplugged" message. But the connection usually goes up again quickly (e.g. after 5-30 seconds). The problem is that my TCP connections (e.g. ssh) are all lost after the outage. The scenario goes like this: 1) The TCP session is connected. Netstat shows that it is "ESTABLISHED". 2) When the link is down, after a few seconds, the TCP connection drops with an error message like "connection to server lost". Netstat shows that the TCP session is gone. 3) After the link is up again, DHCP gives me back the old IP. However, the previous TCP connection cannot resume, and it has to be re-started again, which is very annoying. I am looking for a solution to keep the TCP connection persistent after a transient wireless link outage. Is there any registry in XP that can do this? Thanks in advance for any pointers. -KC

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

09-28-2004	#2 (permalink)
beakmyn root\.workspace\.garbage. Join Date: Aug 2003 Posts: 4,796	Although I'm no expert. I have three opinions on the matter. 1. Would a static IP address be better? 2. This may be built security mechanism to ssh to prevent someone from hijacking your connection 3. Because the connection dropped the server side of your TCP connection isn't going to hold a connection open if there's nothing on the other end.