Date: Sun, 2 Jul 2006 14:32:24 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Robert Watson <rwatson@freebsd.org> Cc: Peter Thoenen <peter.thoenen@yahoo.com>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) Message-ID: <20060702193224.GD4915@dan.emsphone.com> In-Reply-To: <20060702182302.H80381@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 02), Robert Watson said: > On Sun, 2 Jul 2006, Fabian Keil wrote: > >The ssh man page offers: > > > >|~B Send a BREAK to the remote system (only useful for SSH > >| protocol version 2 and if the peer supports it). > > > >I am using ssh 2, but the only reaction I get is a new line. > > > >|FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) > >| > >|login: ~B If you enter ~B and actually see a ~B printed to the screen, then ssh didn't process it because you didn't hit <cr> first. So <cr>~B will tell ssh to send a break. > It sounds like your serial console server may not know how to map SSH > break signals into remote serial break signals. Try > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > > # Solaris implements a new BREAK which is initiated by a character > # sequence CR ~ ^b which is similar to a familiar pattern used on > # Sun servers by the Remote Console. > options ALT_BREAK_TO_DEBUGGER ... and if you're sshing to your terminal server, remember that ssh will eat that tilde (because you sent <cr>~ ), so you need to send <cr>~~^B to pass the right characters to FreeBSD. Or change ssh's escape character with the -e flag. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060702193224.GD4915>