[Equipment] Sagem F@st 1704 Short Idle Timeout
For the longest time, I used a 2-wire 2701HG which suddenly died on me (all it wants to do is reboot over and over and over again and factory reset does not work) so I called up Windstream and they were nice enough to send me a new modem.
This new modem is a Sagem F@st 1704.
Ever since I got this new modem, I noticed that it appears to have an absurdly short idle timeout on connections.
For example, there's a telnet program that I use to access an online server. Before the new router, I could leave a connection idle for nearly ten minutes before I'd lose the connection.
After the SAGEM router, this can happen in as little as *30 seconds*!
I have a NETGEAR WNR3500L in behind the Sagem Router, so I'd like to give all of the NAT/DHCP/etc to the Netgear and use the Sagem as a Modem-Only, but I'm not too keen on setting Quick Bridge Mode (which would not allow me to access the firmware, what happens when I need to reboot it, and re-log onto my DSL service?) and I've read other posts where people have had trouble keeping their sagem router in bridge mode.
Is there any other ways I can get this to work?
30 seconds is a ridiculously short idle timeout; it is causing serious issues in some of my online apps (Diablo 3, telnet games, IRC, etc) and I don't want to go modifying my windows registry (the one game doesn't like you using Keep Alives as it is).
You should be able to set your idle times in your Netgear Router.
Normally this setting is just under "Internet Setup" in the Netgear router just below your (PPPoE user and pass).
Keep in mind that Some people want to bridge there modems and let the router manage all of the network,But the only problem with that is when you do that you must set up the network correctly in the route itself.
If you want less problem's i would recommend that you fully bridged your modem,and set up the router by entering your PPPoE user and pass.
|reply to Agni |
said by Agni :The default is no idle timeout
I noticed that it appears to have an absurdly short idle timeout on connections
I'm thinking that people are misunderstanding what I'm talking about, I should have explained it better.
I'm not talking about the timeout on the entire internet connection, I'm talking about idle timeouts on data connections.
For example, I could open a telnet window to, say, IRC or a MU*. Two of them work better. In window #1, I'd connect up, and log on, say, Alias #1.
In Window #2, I'd connect up, and log on, say, Alias #2.
I'd let one of them, let's say Alias #2 idle in a place/time where I'd be receiving no data whatsoever and in Alias #1's window, I'd be sure to send data (and of course receive its echo) to keep the connection open.
With the 2-Wire 2701HG, it would take between 10-15 minutes before Alias #2's window would stop receiving data (but yet Telnet doesn't tell me I got disconnected). This takes some testing (waiting 10 minutes then sending a message to Alias #2 and see if I receive it).
With the Sagem F@st 1704, [u]this happens within 30 seconds[/u].
It took a long time for me to figure out what is causing this, but in the end it has to do with NAT, modem/router combos having an extremely small amount of RAM (and they have to keep purging their routing tables to make room for new data connections).
The only work-around for this problem, is modifying your TCPKeepAlive in Windows Registry, something I'm not too keen on doing for multiple reasons (some people don't like you constantly pinging their servers, especially not every 30 seconds).
There are no places to modify timeouts at least not those having to do with Data Connections anywhere in either of the devices. This is something that appears to be hard-coded and limited by how much RAM they put in these devices, unless I'm just blind and I missed it somewhere.
You are correct I did not understand
If you still have the 2wire replacing it's power supply may stop it from rebooting
No dice there unfortunately. I tried moving it to another outlet entirely, tried holding in the reset button, tried making sure there was no wireless activity anywhere near the house, even tried borrowing someone else's AC adapter.
I do, however, have an old Speedstream 4200 or two lying about.
Are those still viable? I was told a long time ago when they gave me the 2-Wire, that they aren't very good, but in the time it took them to send me the Sagem, the Speedstream seemed to work OK.
The 4200 does have it's limitations, however it should still perform the majority functions you need it to. If you would like please send us a PM with your account number and we can send out a new modem to you.
We're here to help! email@example.com