Closed
Bug 974263
Opened 12 years ago
Closed 12 years ago
SSH sessions between ringring and yvr1 timeout after 10 minutes
Categories
(Infrastructure & Operations Graveyard :: NetOps: Office ACL Requests, task)
Infrastructure & Operations Graveyard
NetOps: Office ACL Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: justdave, Assigned: dcurado)
Details
When sshing from ringring to pbx1.voip.yvr1, and leaving the connection idle for more than 10 minutes or so, the session hangs, requiring you to forcefully terminate your ssh session and reconnect. A longer timeout (say a couple hours) would be nice.
| Reporter | ||
Comment 1•12 years ago
|
||
Same problem with pbx1.voip.akl1
| Reporter | ||
Comment 2•12 years ago
|
||
between admin1a.private.mtv1 and admin1a.private.akl1 as well.
| Assignee | ||
Comment 3•12 years ago
|
||
dcurado@fw1.yvr1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
dcurado@fw1.akl1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
dcurado@fw1.pdx1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
dcurado@fw1.tor1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
dcurado@fw1.lon1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
dcurado@fw1.tpe1.mozilla.net# set applications application junos-ssh inactivity-timeout 86400
fw1.sfo1 was already set to: tcp port=22, appl_name=junos-ssh, service type=22, alg id=0, timeout=14400
fw1.mtv1 already set to 86400.
fw1.mtv2 set to 86400 via different bug.
fw1.par1 already set to 86400.
| Assignee | ||
Updated•12 years ago
|
Assignee: network-operations → dcurado
| Assignee | ||
Updated•12 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•12 years ago
|
||
Hopefully the above changes will resolve any issues you have with ssh timing out.
But if not, please re-open the bug and raise the priority, so we can get it sorted out.
Thanks,
Dave C.
| Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•