Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-08-07
02:44 AM
2011-08-07
02:44 AM
N150 WNR1000v3 and ssh
I have just replaced a computer running NAT software with a N150:
Hardware Version WNR1000v3
Firmware Version V1.0.2.28_52.0.60
GUI Language Version V1.0.2.28_2.1.10.1
It seems to work fine save for one issue. Whenever I leave an ssh session idle for some time (30 minutes or so), I am unable to resume my work and after a while, the connection breaks. Is there anything i can do so that my connections wont break? I am very certain that this behaviour is caused by the router as i never came across it when i used my old setup. Both ssh sessions from wired and wireless connected computers are affected. The machines that i ssh into are out of my control so any sollutions involving reconfiguring them wont work.
Hardware Version WNR1000v3
Firmware Version V1.0.2.28_52.0.60
GUI Language Version V1.0.2.28_2.1.10.1
It seems to work fine save for one issue. Whenever I leave an ssh session idle for some time (30 minutes or so), I am unable to resume my work and after a while, the connection breaks. Is there anything i can do so that my connections wont break? I am very certain that this behaviour is caused by the router as i never came across it when i used my old setup. Both ssh sessions from wired and wireless connected computers are affected. The machines that i ssh into are out of my control so any sollutions involving reconfiguring them wont work.
Message 1 of 2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-08-17
08:31 AM
2011-08-17
08:31 AM
Re: N150 WNR1000v3 and ssh
BUMP
Seriously. This must be possible to solve somehow. It is indeed very annoying to come back to, say, an editing session only to realize that the connection is broken and the file has to be recovered.
Seriously. This must be possible to solve somehow. It is indeed very annoying to come back to, say, an editing session only to realize that the connection is broken and the file has to be recovered.
Message 2 of 2