Fun 404 page.

I clicked on a link in a c. '99 Linux article, and wound up here:
http://www.ibiblio.org/LDP

I especially enjoy the Unix(6) translation.

-Ken

Re: Fun 404 page.

On Mon, Apr 4, 2011 at 10:40 AM, Ken D'Ambrosio <ken@...> wrote:
> I clicked on a link in a c. '99 Linux article, and wound up here:
> http://www.ibiblio.org/LDP
>
> I especially enjoy the Unix(6) translation.
>
> -Ken

Also the Zombie, and Wookie...

--

-- 
John Abreau / Executive Director, Boston Linux & Unix
AIM abreauj / JABBER jabr@... / YAHOO abreauj / SKYPE zusa_it_mgr
Email jabr@... / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

Re: Fun 404 page.

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@...
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

ssh reverse tunnel issue

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@...
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: ssh reverse tunnel issue

It doesn't seem like you're dropping connections but I generally setup
ssh stanzas in my .ssh/config file and use ServerAliveInterval.  Maybe
that will help keep things active.

Host some_host
	Port <some_port>
	Hostname <some_server_ip>
	ServerAliveInterval 240

Hope that helps.

Andy

On Tue, Apr 05, 2011 at 05:40:59PM -0400, David Ohlemacher wrote:
> Hi all,
> 
> I am having a bothersome issue with ssh (maybe) and was wondering if anyone
> has an idea what the problem might be.
> 
> I am running a reverse ssh tunnel from the west coast to a middle machine in
> Nashua, NH.   I need to run some machines on the left coast for some
> embedded dev with hardware there.  My machine and the west coast machines
> are behind firewalls, hence the need for the rev tunnel. The middle machine
> is not behind a router firewall.
> 
> >From the west coast machine to the middle machine:
> 
> ssh -X -C -R  <tunnel port>:localhost:22   <user> <at> <middle machine>
> // using X, and compression (not sure if the compression helps or not)
> 
> I then ssh to middle machine:
> 
> ssh -X -C <user> <at> <middle machine>
> 
> and from the middle machine to the west coast:
> 
> ssh -X -C  <user> <at> <west coast machine> -p <tunnel port>
> 
> Issue:   It mostly works fine.  I can open X apps, vim, etc.   But I get
> momentary freezes.   They last 10 seconds to over a minute.  After, I can
> continue my work.    5 or 10 minutes later, it happens again.
> 
> I don't think it is the Internet because during freezes not all the windows
> do it.    While one window is frozen, I can use 'talk' over the same tunnel
> to talk to another developer on the west coast.
> 
> Any ideas?
> 
> Thanks,
> -d

> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss@...
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

--

-- 
Andy

KoreLogic Security
603.465.3236 (Office)
603.340.2498 (Mobile)
http://www.korelogic.com
GnuPG Fingerprint: 688A 79EC B1E5 5748 CE87  1F20 2C45 60E7 0583 23B6

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@...
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: ssh reverse tunnel issue

<shotsInTheDark>

 - Try increasingly more verbose invocations up to -vvv.

 - You might modify things to eliminate a hop thus:

       WestCoast% ssh -X -R 2222:localhost:22 middleMachine`

   ...and then connect thru the middleMachine thus:

       EastCoast% ssh -X -p 2222 middleMachine

   ...though if this fixes (or exacerbates) your problem we'd
   have to scratch our heads to figure out what we've learned.

</shotsInTheDark>

Re: ssh reverse tunnel issue

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@...
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: ssh reverse tunnel issue

David Ohlemacher <ohlemacher <at> gmail.com> writes:

> Thanks.
>
> I have already added to /etc/ssh_config
>
> ServerAliveInterval 240
> ClientAliveInterval 240
>
> on all machines.
>
> I'll try it wo compression.   I really couldn't tell the difference, but maybe
> that is it.

I'd think that the double-compression may be interfering with each
other.  Personally I never use compression with SSH and I never notice
an issue (except, I suppose, with X -- but I don't often run X over
long-distance ssh connections).

> -d
>
> On Tue, Apr 5, 2011 at 6:04 PM, Seth Cohn <sethcohn <at> gmail.com> wrote:
>
>     Agreed, turn on keep alive, turn off compression.  You want the tunnel to
>     be fast, not byteslim.

-derek

--

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord <at> MIT.EDU                        PGP key available

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss <at> mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: ssh reverse tunnel issue

Since the primary complaint is that the connection "freezes"
for as long as a minute I'm gonna predict that this will turn
out not to be compression-related.  Yes, unnecessary/redundant
compression can reduce throughput but the effect would be
(approx) constant rather than intermittent and I can't imagine
it bogging things down for a solid minute.  This smells more
like a scheduling problem or maybe some transient network failure.

Re: ssh reverse tunnel issue

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@...
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/