From owner-freebsd-stable@FreeBSD.ORG Fri Jan 22 16:10:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1AFB10656D6; Fri, 22 Jan 2010 16:10:25 +0000 (UTC) (envelope-from dnaeon@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 129DA8FC15; Fri, 22 Jan 2010 16:10:24 +0000 (UTC) Received: by ewy26 with SMTP id 26so333134ewy.3 for ; Fri, 22 Jan 2010 08:10:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=eL41dN0L5PLt0KdWho/DEzHD6PeOg8dEwFYx/RP4k2g=; b=ozEAzEfNPjkIq3eJKHKL3oBKJRpQ4rGFqFsVpreqt4+xxSdIsHMlQ3kJ6ORFqAdus1 RYZpobm9wxzAulTryoHxFf8biFR9YbB0mvAelbMJjAWi9gMYuo0P38l9y/izZCM3YVRd cDjvq/tCq1IBJBnoMy6skW6KfesKgfs+INTB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XZXvAciriQf/ARSDOt50JtrZAB52CgJbUJhU1MWrtkoXDayFUWdn0ArdxLm4pDvfQN zPYcyJXlRRzjAYNKjFm0b1F3Y2F3WNBDqnjDGVMxTo/SUJ/XmRQ+GhlYFLsn56h59RbM MjkHtTugCdIlgFfsZ6UPPBTYNfS3jPS6CJyGw= MIME-Version: 1.0 Received: by 10.216.91.81 with SMTP id g59mr1221978wef.128.1264176623743; Fri, 22 Jan 2010 08:10:23 -0800 (PST) In-Reply-To: <20100122080223.GA6681@titania.njm.me.uk> References: <717f7a3e1001120714m37aada69gfaa35f0f9b17f435@mail.gmail.com> <44678539@bb.ipt.ru> <717f7a3e1001142234y1de7ae15x6853e3ddcab4add9@mail.gmail.com> <717f7a3e1001192246o4dce4a82q57c05ff3f41b5feb@mail.gmail.com> <20100120074611.GA405@icarus.home.lan> <717f7a3e1001210137p7884adcbxc66a4f7fff928821@mail.gmail.com> <20100122080223.GA6681@titania.njm.me.uk> Date: Fri, 22 Jan 2010 18:10:23 +0200 Message-ID: <717f7a3e1001220810s11b241b7ve9a9172c51ea531b@mail.gmail.com> From: Marin Atanasov To: Marin Atanasov , Jeremy Chadwick , freebsd-hardware@freebsd.org, freebsd-stable@freebsd.org, Ronald Klop Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Multiple serial consoles via null modem cable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2010 16:10:25 -0000 On Fri, Jan 22, 2010 at 10:02 AM, N.J. Mann wrote: > In message <717f7a3e1001210137p7884adcbxc66a4f7fff928821@mail.gmail.com>, > Marin Atanasov (dnaeon@gmail.com) wrote: > > Hello Jeremy, > > > > Now I'm a little confused :) > > > > I've made some tests with my machines and a couple of null modem cables, > and > > here's what I've got. > > > > On Wed, Jan 20, 2010 at 9:46 AM, Jeremy Chadwick > > wrote: > > > > > On Wed, Jan 20, 2010 at 08:46:48AM +0200, Marin Atanasov wrote: > > > > Hello, > > > > > > > > Using `cu' only works with COM1 for me. > > > > > > > > Currently I have two serial ports on the system, and only the first > is > > > able > > > > to make the connection - the serial consoles are enabled in /etc/tty, > but > > > as > > > > I said only COM1 is able to make the connection. > > > > > > I'm a little confused by this statement, so I'll add some clarify: > > > > > > /etc/ttys is for configuring a machine to tie getty (think login > prompt) > > > to a device (in this case, a serial port). Meaning: the device on the > > > other end of the serial cable will start seeing "login:" and so on > > > assuming you attach to the serial port there. > > > > > > For example: > > > > > > box1 COM1/ttyu0 is wired to box2 COM3/ttyu2 using a null modem cable. > > > box1 COM2/ttyu1 is wired to box2 COM4/ttyu3 using a null modem cable. > > > > > > On box1, you'd have something like this in /etc/ttys: > > > > > > ttyu0 "/usr/libexec/getty std.9600" vt100 on secure > > > ttyu1 "/usr/libexec/getty std.9600" vt100 on secure > > > > > > > Here's what I did: > > > > box1 COM1/ttyd0 -> box2 COM1/ttyd0 -> using null modem cable > > box1 COM2/ttyd1 -> box3 COM1/ttyd0 -> using null modem cable > > > > On box1 I have this in /etc/ttys: > > > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > > > > Now if I want to connect to box1 from box2 or box3 through the serial > > connection it should work, right? > > But I only can connect to box1 from box2, because box2's COM port is > > connected to box1's COM1 port. > > > > >From box2 I can get a login prompt > > box2# cu -l /dev/cuad0 -s 9600 > > Connected > > > > login: > > ) > > (host.domain) (ttyd0) > > > > login: ~ > > [EOT] > > > > But if I try to connect to box1 from box3 - no success there. > > box3# cu -l /dev/cuad0 -s 9600 > > Connected > > ~ > > [EOT] > > You need to reduce the number of unknowns, e.g. where is the problem: > box1, box3 or in between. So, swap the cables on box1 so that you now > have box1:COM1 -> box3:COM1 and box1:COM2 -> box2:COM1. Now repeat the > tests above and post your results. > > > Cheers, > Nick. > -- > > Seems I've found the issue, that I'm having - a broken null modem cable :( The last time I was using that cable it was working fine. And now that I connected a second one to the machine, it seemed that only the one connected to COM1 was actually working, and I was left with the impression from the documentation that only COM1 is able to do a serial console connection. I'm very sorry to bother you like that. I'll continue setting up the servers once I get a new null modem cable. Thanks and regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org