autossh 1.4g-1 is now available in Cygwin. According to the upstream changelog
at http://www.harding.motd.ca/autossh/:
"Version 1.4g most notably addresses a bug that could see an alarm signal occur
without a handler, causing autossh to exit inappropriately."
autossh is a program t
On Thu, May 31, 2018, 4:58 AM Germain Le Chapelain wrote:
>
> Hi,
>
>
> I am experiencing troubles trying to set up a reverse SSH tunnel:
>
> I have installed AutoSSH as such:
>
> cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -R
> *:5900:localhost:59
On 06/01/18 23:03, René Berber wrote:
The behavior looks normal.
Quoting from the autossh man page:
"Startup behaviour
If the ssh session fails with an exit status of 1 on the very first try,
autossh
1.' will assume that there is some problem with syntax or the connection
setup
On 6/1/2018 10:31 AM, Germain Le Chapelain :
The behavior looks normal.
Quoting from the autossh man page:
"Startup behaviour
If the ssh session fails with an exit status of 1 on the very first try,
autossh
1.' will assume that there is some problem with syntax or the connection
Hi Andrew!
Thank you so much for the prompt answer,
Hi. I'm glad someone is using autossh. I don't use it myself any more, and as a
package maintainer it's impossible for me to tell if anyone else is.
Yes, it came up first in our research to establish a reliable reverse
SSH-tun
Hi. I'm glad someone is using autossh. I don't use it myself any more, and as a
package maintainer it's impossible for me to tell if anyone else is.
> I have installed AutoSSH as such:
>
> cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -R
> *:5900:localhos
Hi,
I am experiencing troubles trying to set up a reverse SSH tunnel:
I have installed AutoSSH as such:
cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -R
*:5900:localhost:5900 s...@lanvaux.fr" -y tcpip --type auto -e
AUTOSSH_NTSERVICE=yes
Now, it works great, except
autossh 1.4f-1 is now available in Cygwin. According to the upstream changelog
at http://www.harding.motd.ca/autossh/:
"Version 1.4f incorporates a number of changes and fixes to signal handling and
exit conditions. The most notable changes are that it will exit properly when
killed
A new release of autossh is available in the Cygwin distribution. This is a new
upstream release, with a small adjustment to how poll times are chosen. See
http://www.harding.motd.ca/autossh/CHANGES for a full list of changes.
autossh is a program to start an instance of ssh and monitor it
A new version of autossh, 1.4d-1, is available in the Cygwin distribution.
This is a new upstream release, with bug fixes:
* Fixes file descriptor issues when started without standard input
available (for example, in system initialization scripts)
autossh is a program to start an instance of ssh
thing in this Windows machine.
> It uses ssh to forward some ports of its own, and
> that feature might be ipv4-only. You can turn it off by passing -M0 to
> autossh. Does that fix the problem?
>
I could try, but there is no way I can test a remote connection with V6,
local connectio
> On Fri, 12 Jul 2013, Andrew Schulman wrote:
>
> > Hi Lee. Okay, that does seem to narrow it down.
> >
> > You're right that autossh doesn't have any ipv4 options. It hasn't been
> > updated in a few years, and I think it's just not ipv6-aware
On Fri, 12 Jul 2013, Andrew Schulman wrote:
> Hi Lee. Okay, that does seem to narrow it down.
>
> You're right that autossh doesn't have any ipv4 options. It hasn't been
> updated in a few years, and I think it's just not ipv6-aware yet.
>
Looks like it may no
> debug1: Local connections to LOCALHOST:5661 forwarded to remote address
> 127.0.0.1:6661
> debug1: Local forwarding listening on ::1 port 5661.
> ^
>
>
>
> It looks like the problem is that AutoSSH is binding to IPV6, *NOT
On Fri, 12 Jul 2013, Andrew Schulman wrote:
> > Trying to debug a session, .. neither AUTOSSH_DEBUG nor AUTOSSH_LOGLEVEL:
> >
> > $ env | grep AUTO
> > AUTOSSH_DEBUG=1
> > AUTOSSH_LOGLEVEL=7
> >
> > nor -vv:
> >
> > cygrunsrv -I
> Trying to debug a session, .. neither AUTOSSH_DEBUG nor AUTOSSH_LOGLEVEL:
>
> $ env | grep AUTO
> AUTOSSH_DEBUG=1
> AUTOSSH_LOGLEVEL=7
>
> nor -vv:
>
> cygrunsrv -I AutoSSH -f "remote_link" -p /usr/bin/autossh -a " -vv \
>
> change the l
Trying to debug a session, .. neither AUTOSSH_DEBUG nor AUTOSSH_LOGLEVEL:
$ env | grep AUTO
AUTOSSH_DEBUG=1
AUTOSSH_LOGLEVEL=7
nor -vv:
cygrunsrv -I AutoSSH -f "remote_link" -p /usr/bin/autossh -a " -vv \
change the logging info always ("Host key verification filed")
realivlty quickly. I have set the AUTOSSH_DEBUG to yes but I am not
making heads or tails of the error
My main issue is that I keep getting ssh exited with error status 255;
restarting ssh
I have been using http://linux.die.net/man/1/autossh for most of my
info and I have been searching the
Le 10/11/2010 02:38, David Rothenberger a écrit :
>
> On 11/9/2010 5:26 PM, cygwin.20.gyur...@spamgourmet.com wrote:
>> How Can I do autossh connection with any computer which is off, but
>> sometime coming to power on?
>> I used this:
>> cygrunsrv -I AutoSSH -n
Thank you, you could solve it my problem. ;-)
2010/11/10 David Rothenberger - daver...@acm.org
> On 11/9/2010 5:26 PM, cygwin.20.gyurman wrote:
>> How Can I do autossh connection with any computer which is off, but
>> sometime coming to power on?
>> I used this:
>> cy
On 11/9/2010 5:26 PM, cygwin.20.gyur...@spamgourmet.com wrote:
> How Can I do autossh connection with any computer which is off, but
> sometime coming to power on?
> I used this:
> cygrunsrv -I AutoSSH -n -O -u name -w pass -p /usr/bin/autossh -a "-M
> $port -R 5903:localhost:2
How Can I do autossh connection with any computer which is off, but
sometime coming to power on?
I used this:
cygrunsrv -I AutoSSH -n -O -u name -w pass -p /usr/bin/autossh -a "-M
$port -R 5903:localhost:22 n...@192.168.1.102" -e
"AUTOSSH_NTSERVICE=yes AUTOSSH_GATETIME=0"
But
d to create /etc/ssh/ssh_known_hosts and make it writeable by
SYSTEM.
Or /etc/ssh_known_hosts? Since it appears that you have all of your ssh configs
in /etc instead of /etc/ssh. That is unusual, although I don't think it should
cause any problems for autossh.
> The autossh command line
I am trying to create an autossh service that establishes a reverse
ssh connection to an openssh server runing on the local lan. The
server will eventually migrate off the lan and I have no control over
the firewall which is why I'm testing this setup first. I've run into
several probl
Am Sonntag 04 Oktober 2009 schrieb Julio Costa:
> Hi,
>
> On Sun, Oct 4, 2009 at 17:57, Matthias Meyer wrote:
> > Hi,
> >
> > I've running port forwarding in WindowsXP as well as Windows Vista by
using
> > autossh, running as a service, installed by cygrunsr
Hi,
On Sun, Oct 4, 2009 at 17:57, Matthias Meyer wrote:
> Hi,
>
> I've running port forwarding in WindowsXP as well as Windows Vista by using
> autossh, running as a service, installed by cygrunsrv.
>
> cygrunsrv -I service-tunnel -f "secure tunnel for service"
Hi,
I've running port forwarding in WindowsXP as well as Windows Vista by using
autossh, running as a service, installed by cygrunsrv.
cygrunsrv -I service-tunnel -f "secure tunnel for service" \
-n -t auto -y tcpip -O -u $priv_user -w $priv_pwd -p /bin/nice \
>
>> > I have problems running autossh via cygrunsrv on WIN2003:
>> >
>> > /bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -g2CN -R
>> > 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12" -e
>> > AUTOSSH_NTSER
> > Hm, I'm surprised to hear that. I haven't run autossh as a service in a
> > while,
> > but when I did it worked very reliably for me. Can you tell me anything
> > more
> > about how or why it fails to start?
>
> No, sorry, there's n
Andrew Schulman wrote:
> Hm, I'm surprised to hear that. I haven't run autossh as a service in a
> while,
> but when I did it worked very reliably for me. Can you tell me anything more
> about how or why it fails to start?
No, sorry, there's no useful information
> > I have problems running autossh via cygrunsrv on WIN2003:
> >
> > /bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -g2CN -R
> > 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12" -e
> > AUTOSSH_NTSERVICE=yes -y tcpip --t
hooner wrote:
> I have problems running autossh via cygrunsrv on WIN2003:
>
> /bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -g2CN -R
> 20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12" -e
> AUTOSSH_NTSERVICE=yes -y tcpip --type auto
&g
I have problems running autossh via cygrunsrv on WIN2003:
/bin/cygrunsrv.exe -I AutoSSH -p /bin/autossh -a "-M 2 -g2CN -R
20120:localhost:3389 -i /etc/key-rsa -p 20012 u...@192.168.100.12" -e
AUTOSSH_NTSERVICE=yes -y tcpip --type auto
As soon as I start the service (net start a
A new version of the autossh package is available in the Cygwin
distribution. autossh is a program to start an instance of ssh and
monitor it, restarting it as necessary should it die or stop passing
traffic. autossh monitors connections by sending data to an echo server
or through a loop of
A new version of the autossh package is available in the Cygwin
distribution. autossh is a program to start an instance of ssh and
monitor it, restarting it if it should die or stop passing traffic.
Changes in version 1.4a-1:
* New upstream release: bug fixes.
Andrew E. Schulman
A new version of the autossh package is available in the Cygwin
distribution. autossh is a program to start an instance of ssh and
monitor it, restarting it if it should die or stop passing traffic.
Changes in version 1.4-1:
* New upstream release: bug fixes.
Andrew E. Schulman
> > $ AUTOSSH_FIRST_POLL=5 AUTOSSH_POLL=5 AUTOSSH_DEBUG=yes autossh -M 3
> > -N dessent.net
> > autossh: PID 3204: short poll time: adjusting net timeouts to 2500
> > autossh: PID 3204: checking for grace period, tries = 0
> > autossh: PID 3204: starting ssh (
t before 1.5.20, I reverted all event
> handling for accept and connect and returned to using select again, as
> it was implemented until 1.5.18.
Thanks for the quick fix, and I can confirm that autossh is functioning
fine again now. It's always unfortunate when something has to be
re
On Jun 23 20:19, Brian Dessent wrote:
>
> I'm not sure if it is due to changes in openssh, or changes in Cygwin,
> but the current autossh package fails to work. Instead of detecting
> that the connection is alive, it seems to continuously timeout and
> recycle the ssh
I'm not sure if it is due to changes in openssh, or changes in Cygwin,
but the current autossh package fails to work. Instead of detecting
that the connection is alive, it seems to continuously timeout and
recycle the ssh process. Here is a representative testcase:
$ AUTOSSH_FIRST_P
A new version of the autossh package is available in the Cygwin
distribution. autossh is a program to start an instance of ssh and
monitor it, restarting it if it should die or stop passing traffic.
Changes in version 1.3-2:
* Clarify the documentation for running autossh as an NT system
A new version of the autossh package is available in the Cygwin
distribution.
Changes in version 1.3-1:
* New upstream release:
- You can now use a remote echo server, instead of a loop of port
forwardings, to monitor the ssh connection. See the man page for details.
- Several bug fixes
Original Message
>From: Christopher Faylor
>Sent: 16 March 2005 19:21
> On Wed, Mar 16, 2005 at 06:06:20PM -, Dave Korn wrote:
>> [EMAIL PROTECTED] /gnu/glibc-2.3.4/resolv> cat -n gethnamaddr.c
>> [snip!] 103
>> 104 static struct hostent host;
>> 105 static cha
On Wed, Mar 16, 2005 at 08:45:09PM +0100, [EMAIL PROTECTED] wrote:
>A new version of the autossh package is available in the Cygwin
>distribution.
>
>Changes in version 1.2g-5:
>* Fix heap corruption and segfaults caused by free()ing static memory.
Just to state it really clea
A new version of the autossh package is available in the Cygwin
distribution.
Changes in version 1.2g-5:
* Fix heap corruption and segfaults caused by free()ing static memory.
Andrew E. Schulman
***
To update your installation
On Wed, Mar 16, 2005 at 06:06:20PM -, Dave Korn wrote:
>Original Message
>>From: Andrew Schulman
>>Sent: 16 March 2005 17:08
>
>
>> Would the job be easier in my case, where I have a repeatable crash? I
>> provided strace output in the earlier thread
> Generally speaking, it is whoever mallocs memory that has the
> responsibility for freeing it. If your app mallocs it, your app should free
> it; if the library mallocs it, the library should free it.
>
> In some cases, the ownership of a bit of memory (or any other resource)
> may be trans
> GOK why it works on glibc-based systems, but I guess it must, or the
> problem would surely have cropped up before. Hm..
Simple: that part of the code is contained in an #ifdef HAVE_NO_ADDRINFO
... #endif block, and so is only built on systems without a getaddrinfo
() function. That
Original Message
>From: Andrew Schulman
>Sent: 16 March 2005 17:44
> OK. (hangs head) I have to take the blame for this, because as it
> happens I contributed that bit of code. Forgive my simplicity on this
> point, but it seemed like good memory heigene-- free up the memory that
> getho
> The problem is that autossh is freeing the return value of
> gethostbyname(). I can't find any reference which says that is a
> acceptable thing to do. It certainly screws up cygwin, and I can't
> think of any way to avoid having it screw up cygwin. Maybe it won'
Original Message
>From: Andrew Schulman
>Sent: 16 March 2005 17:08
> Would the job be easier in my case, where I have a repeatable crash? I
> provided strace output in the earlier thread about my autossh problems,
> but haven't tried using any debug builds of c
ked "funny" and I couldn't figure out how cygwin could get
> in the state indicated by the stack trace. Well, heap corruption is what
> caused the funniness.
>
> The problem is that autossh is freeing the return value of
> gethostbyname(). I can't find any referenc
hread either.
Would the job be easier in my case, where I have a repeatable crash? I
provided strace output in the earlier thread about my autossh problems,
but haven't tried using any debug builds of cygwin1.dll. I'm not
conversant with debuggers, but I have used gdb before and could
On Tue, Mar 15, 2005 at 08:20:28PM -0800, David Rothenberger wrote:
>I've been having some problems with autossh crashing with 1.5.13 and
>later snapshots. These problems did not occur with 1.5.12. (The problem
>may be related to the one reported by Andrew Schulman in
><http
Original Message
>From: David Rothenberger
>Sent: 16 March 2005 04:20
> Andrew. It has crashed twice in the few weeks and I've captured stack
> traces for each. I was running a debugging copy of the Cygwin DLL (built
> myself from CVS) in each case and I've run addr2line on each stack
> tr
I've been having some problems with autossh crashing with 1.5.13 and
later snapshots. These problems did not occur with 1.5.12. (The problem
may be related to the one reported by Andrew Schulman in
<http://sourceware.org/ml/cygwin/2005-03/msg00410.html>.)
autossh doesn't relia
A new version of the autossh package is available in the Cygwin
distribution.
Changes in version 1.2g-4:
* Changed to generic build script method for package building.
* Combined all Cygwin-specific docs (README.Cygwin, NEWS.Cygwin,
autossh.README) into autossh.README.
To update your
A new version of the autossh package is available in the Cygwin
distribution.
Changes in version 1.2g-2:
* Expanded /usr/share/doc/autossh/README.Cygwin, to describe the NT
service mode and how to use it with cygrunsrv.
To update your installation, click on the "Install Cygwin now&quo
The package 'autossh' is now available in the Cygwin distribution.
autossh is a program to start an instance of ssh and monitor it,
restarting
it as necessary should it die or stop passing traffic. autossh monitors
connections by sending data through a loop of port forwardings, an
Has anyone had any success in building autossh for cygwin? I have
version 1.2f. When I try to compile it with any of the provided
Makefiles, I get a boatload of errors:
$ make -f Makefile.linux
gcc -Wall -D"SSH_PATH=\"/usr/bin/ssh\"" -D"VER=\"1.2f\""
60 matches
Mail list logo
