7;t recall having this problem. the only thing i
remember explicitly having to do is tell sshd to bind to the jail's
IP.
-g
On 12/01/07, Andras GELANYI <[EMAIL PROTECTED]> wrote:
Do you know how can I initaite a SSH connection from within a jail?
I always get the "Host key ver
Do you know how can I initaite a SSH connection from within a jail?
I always get the "Host key verification failed." message. Starting the
ssh session with -v it seems that the problem is with tty allocation.
debug1: read_passphrase: can't open /dev/tty: Device busy
The jail has de
Do you know how can I initaite a SSH connection from within a jail?
I always get the "Host key verification failed." message. Starting the
ssh session with -v it seems that the problem is with tty allocation.
debug1: read_passphrase: can't open /dev/tty: Device busy
The jail ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I swore I had it saved here somewhere, but can't seem to find it in my
mailboxes :(
I have an HP Proliant DL360 G4p server (well, a few, actually), that allow for
getting a remote console via ssh ... I have DDB/KDB enabled on the server, just
like
[EMAIL PROTECTED] wrote:
>> While doing a backup on an HP Ultrium LTO1 tape, my ssh connection
>> froze, and since then, I'm not able to use the tape device anymore.
>
> Presumably there is another instance of dump or whatever is
> still running; try to kill -INT or ki
On Sep 27, 2006, at 5:25 PM, Philippe Lang wrote:
While doing a backup on an HP Ultrium LTO1 tape, my ssh connection
froze, and since then, I'm not able to use the tape device anymore.
Presumably there is another instance of dump or whatever is still
running; try to kill -INT or kill
Hi,
While doing a backup on an HP Ultrium LTO1 tape, my ssh connection froze, and
since then, I'm not able to use the tape device anymore.
xeon# mt -f /dev/nsa0 rewind
mt: /dev/nsa0: Device busy
xeon# dump -0uaL -f /dev/nsa0 /dev/da0s1a
DUMP: Date of this level 0 dump: Wed Sep 27 23:
Hi,
I've just wanted to tell you, that I've solved the problem by not
letting the script run under control of the daemon tools but via a
self written perl script.
Now, the problem not being able to access TTY no longer exists.
Bye,
S.Wagler
S. Wagler wrote:
Hi,
I'm currently using FreeBS
Hi,
yes, devfs is mounted.
I've tried to connect from within the jail via telnet to the SSH port
of the foreign host, which opens the connection successfully and
shows the version number. So, the connection was established
correctly and I think the problem with the pseudo TTY device is more
On Jul 21, 2006, at 5:19 PM, S. Wagler wrote:
Hi,
I'm currently using FreeBSD 6.1-RELEASE with a bunch of jails. In
one of them I need to connect to the outside world via SSH which
does not work properly.
When logging in to (!) the jail via SSH, everything works properly:
I can connect
Hi,
I'm currently using FreeBSD 6.1-RELEASE with a bunch of jails. In one
of them I need to connect to the outside world via SSH which does not
work properly.
When logging in to (!) the jail via SSH, everything works properly: I
can connect from "inside" the jail to the outside via SSH, but
HI Nelis
Thank you
I added it but can't help
for the secureCRT: the error messages:
Unable to authenicate using of any authenicate method
for the putty: suddenly disconnect when the login is
idle about 2 minutes
This hasn't happened in freebsd 5.2.1 and 4.0 but this
problem also had in 5.3 R2
et same message
>> [ssh: connect to host 192.168.0.5 port 22: Permission denied] when the
>> freebsd box is switched on or OFF!!
>>
>> I guess I will have to try mac lists for a solution.
>>
>> pota
>
> I use OS X (I'm actually on a OS X ssh connection at
ed on or OFF!!
>
> I guess I will have to try mac lists for a solution.
>
> pota
I use OS X (I'm actually on a OS X ssh connection at the moment), not
currently to a FreeBSD machine, but when I did I had no specific SSH
interoperability problems. OS X uses OpenSSH in fairly stan
On 21/9/04 1:33 pm, "Lowell Gilbert"
<[EMAIL PROTECTED]> wrote:
> Pota Kalima <[EMAIL PROTECTED]> writes:
>
>> Thanks for all your responses. I must add that I am not a programmer, so all
>> that the verbose stuff did not mean much too. I bit the bullet and started
>> afresh - re-installed 5.2.1.
Pota Kalima <[EMAIL PROTECTED]> writes:
> Thanks for all your responses. I must add that I am not a programmer, so all
> that the verbose stuff did not mean much too. I bit the bullet and started
> afresh - re-installed 5.2.1.
>
> I find that I could ssh to the machine itself, okay - as KeS sugge
> -Original Message-
> From: Pota Kalima [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 20, 2004 12:54 PM
> To: Lowell Gilbert; Kevin Stevens
> Cc: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> Subject: Re: Ssh connection
>
>
> Thanks for all y
Thanks for all your responses. I must add that I am not a programmer, so all
that the verbose stuff did not mean much too. I bit the bullet and started
afresh - re-installed 5.2.1.
I find that I could ssh to the machine itself, okay - as KeS suggested. The
process ends with the machine connecting
On 19 Sep 2004 20:32:15 -0400, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Kevin Stevens <[EMAIL PROTECTED]> writes:
>
> > On Sep 19, 2004, at 10:17, Pota Kalima wrote:
> >
> > > On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
> > >>
> > >> What happens if you try to ssh to the mach
Kevin Stevens <[EMAIL PROTECTED]> writes:
> On Sep 19, 2004, at 10:17, Pota Kalima wrote:
>
> > On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
> >>
> >> What happens if you try to ssh to the machine from itself?
> >>
> >> KeS
> >>
> >
> > Tried to ssh to machine itself and got the
Pota Kalima wrote:
On 19/9/04 6:24 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
On Sep 19, 2004, at 10:17, Pota Kalima wrote:
On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
What happens if you try to ssh to the machine from itself?
KeS
Tried to ssh to machine itself and got the
On 19/9/04 6:24 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
>
> On Sep 19, 2004, at 10:17, Pota Kalima wrote:
>
>> On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
>>>
>>> What happens if you try to ssh to the machine from itself?
>>>
>>> KeS
>>>
>>
>> Tried to ssh to machin
On Sep 19, 2004, at 10:17, Pota Kalima wrote:
On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
What happens if you try to ssh to the machine from itself?
KeS
Tried to ssh to machine itself and got the following:
$ Ssh 192.168.0.5
The authenticity of host '192.168.0.5 (192.168.0.5)' ca
On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
>
> On Sep 19, 2004, at 05:28, Pota Kalima wrote:
>
>> I am having trouble connecting TO my base machine which runs release
>> 5.2.1
>> from 2 other machines (Mac OS X, and Windoz). I can connect to the OS X
>> machine FROM this base
On Sep 19, 2004, at 05:28, Pota Kalima wrote:
I am having trouble connecting TO my base machine which runs release
5.2.1
from 2 other machines (Mac OS X, and Windoz). I can connect to the OS X
machine FROM this base machine as well as from the windoz machine.
What happens if you try to ssh to the
On Sep 19, 2004, at 05:28, Pota Kalima wrote:
I am having trouble connecting TO my base machine which runs release
5.2.1
from 2 other machines (Mac OS X, and Windoz). I can connect to the OS X
machine FROM this base machine as well as from the windoz machine.
What happens if you try to ssh to the
Are you running a firewall?
On Sep 19, 2004, at 8:28 AM, Pota Kalima wrote:
I am having trouble connecting TO my base machine which runs release
5.2.1
from 2 other machines (Mac OS X, and Windoz). I can connect to the OS X
machine FROM this base machine as well as from the windoz machine.
When at
I am having trouble connecting TO my base machine which runs release 5.2.1
from 2 other machines (Mac OS X, and Windoz). I can connect to the OS X
machine FROM this base machine as well as from the windoz machine.
When attempting connection from OS X I get the following message:
Yes Master? ssh -
- Original Message -
From: "Joshua Lokken" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 5:19 PM
Subject: Re: ssh Connection refused
> * Kevin D. Kinsey, DaleCo, S.P. <[EMAIL PROTECTED]> [2004-04-13 07:52]:
> > RazorOnF
> >Cc: <[EMAIL PROTECTED]>
> >Sent: Tuesday, April 13, 2004 4:19 AM
> >Subject: Re: ssh Connection refused
> >
>
> I guess anything is somewhat possible. I'm just
> looking for the most likely stuff first ...
>
> Can you "ssh [EMA
I guess anything is somewhat possible. I'm just
looking for the most likely stuff first ...
Can you "ssh [EMAIL PROTECTED]" ?
Another thingy you can try:
if you logged in from console (if possible) can you telnet to
localhost 22 ? (or whatever ip the sshd is listening on).
Hope this helps as well
razor.
- Original Message -
From: "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
To: "RazorOnFreeBSD" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 4:38 PM
Subject: Re: ssh Connection refused
> RazorOnFreeBSD wro
RazorOnFreeBSD wrote:
- Original Message -
From: "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
To: "RazorOnFreeBSD" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 4:19 AM
Subject: Re: ssh Connection refused
Thank
- Original Message -
From: "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
To: "RazorOnFreeBSD" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 4:19 AM
Subject: Re: ssh Connection refused
> RazorOnFreeBSD wrote
RazorOnFreeBSD wrote:
I have a firewall and it's running.
But the outputs for the command "ps -auxv | grep sshd" are :
root93 0.00.430082176??Is6:19PM0:00.16
/usr/sbin/sshd
root1680.00.0336 204 v0R+ 6:58PM0:00.01
grep sshd
I d
<[EMAIL PROTECTED]>
Sent: Tuesday, April 13, 2004 1:55 AM
Subject: Re: ssh Connection refused
> RazorOnFreeBSD wrote:
>
> >Hi everyone,
> >
> >I just had an electricity problem ... my freebsd server
> >lost the power and shutted down without being requested.
>
RazorOnFreeBSD wrote:
Hi everyone,
I just had an electricity problem ... my freebsd server
lost the power and shutted down without being requested.
So far everything looks good on the system, except for sshd
When the kernel boot up it is one of the daemons started,
it is clearly written. Ex
Hi everyone,
I just had an electricity problem ... my freebsd server lost the power and shutted
down without being requested.
So far everything looks good on the system, except for sshd
When the kernel boot up it is one of the daemons started, it is clearly written.
Except that it's not anym
On Tue, 17 Jun 2003, [iso-8859-1] haifa touati wrote:
> Hi all, I tried to ssh to a remote machine from a FreeBSD 4.5 machine,
> but I received "... connection refused" message. However I succeeded to
> connect to this machine from Windows. Are there any specifics settings
> to fix this? Thanks
Hi all,
I tried to ssh to a remote machine from a FreeBSD 4.5 machine, but I received "...
connection refused" message. However I succeeded to connect to this machine from
Windows. Are there any specifics settings to fix this?
Thanks in advance,
Haïfa.
-
Do You
at sysadmin say first
Thanks
Goodwin
- Original Message -
From: "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
To: "Goodwin Lawlor" <[EMAIL PROTECTED]>; "FreeBSD List"
<[EMAIL PROTECTED]>
Sent: Thursday, October 10, 2002 8:10 PM
Subject: Re:
Hi
I've just installed FreeBSD4.5 on machine attached to a college network. I
can connect to the machine using ssh from another machine on the network.
When I try to connect using ssh from home via an ISP (using PuTTY on winxp)
I get "connection timed out". I can connect from home using telnet tho
42 matches
Mail list logo
