From kaz@kobe1995.net  Thu Oct 12 08:39:34 2000
Return-Path: <kaz@kobe1995.net>
Received: from ns.kobe1995.net (211.12.126.15.user.dt.il24.net [211.12.126.15])
	by hub.freebsd.org (Postfix) with ESMTP id 9D5F937B502
	for <freebsd-gnats-submit@freebsd.org>; Thu, 12 Oct 2000 08:39:28 -0700 (PDT)
Received: from mako.kobe1995.net (root@mako [192.168.0.2]) by ns.kobe1995.net (8.8.8/3.4Wbeta6-primary) with ESMTP id AAA25664; Fri, 13 Oct 2000 00:39:20 +0900 (JST)
Received: (from kaz@localhost) by mako.kobe1995.net (8.9.3/3.4Wbeta6-glove) id AAA99625; Fri, 13 Oct 2000 00:39:19 +0900 (JST)
Message-Id: <200010121539.AAA99625@mako.kobe1995.net>
Date: Fri, 13 Oct 2000 00:39:19 +0900 (JST)
From: NAKAMURA Kazushi <kaz@kobe1995.net>
Reply-To: kaz@kobe1995.net
To: FreeBSD-gnats-submit@freebsd.org
Cc: kaz@ns.kobe1995.net
Subject: Can't serial line login via cross-cable
X-Send-Pr-Version: 3.2

>Number:         21935
>Category:       conf
>Synopsis:       Can't serial line login via cross-cable
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 12 08:40:03 PDT 2000
>Closed-Date:    Sun Oct 15 13:15:19 PDT 2000
>Last-Modified:  Sun Oct 15 13:17:25 PDT 2000
>Originator:     NAKAMURA Kazushi
>Release:        FreeBSD 3.3-RELEASE i386
>Organization:
PC shop LABBIT
>Environment:

	I'm try to login FreeBSD box from Windows PC via RS-232C cross-cable.

>Description:

	But can't login or connect. Terminal Emulator on Windows dos'nt echo
	anything. Of cource, the "login:" message also does'nt appear.

>How-To-Repeat:
>Fix:
	
--- /etc/ttys~	Fri Oct 13 00:25:08 2000
+++ /etc/ttys	Fri Oct 13 00:24:47 2000
@@ -42,8 +42,8 @@
 ttyv8	"/usr/X11R6/bin/xdm -nodaemon"	xterm	off secure
 # Serial terminals
 # The 'dialup' keyword identifies dialin lines to login, fingerd etc.
-ttyd0	"/usr/libexec/getty std.9600"	vt100	on secure
-ttyd1	"/usr/libexec/getty std.9600"	vt100	on secure
+cuaa0	"/usr/libexec/getty std.9600"	vt100	on secure
+cuaa1	"/usr/libexec/getty std.9600"	vt100	on secure
 ttyd2	"/usr/libexec/getty std.9600"	dialup	off secure
 ttyd3	"/usr/libexec/getty std.9600"	dialup	off secure
 # Pseudo terminals

And "kill -1 1". Then it appear "login:" message on the Windows terminal.

>Release-Note:
>Audit-Trail:

From: Brian Somers <brian@Awfulhak.org>
To: kaz@kobe1995.net
Cc: FreeBSD-gnats-submit@freebsd.org, kaz@ns.kobe1995.net,
	brian@freebsd.org
Subject: Re: conf/21935: Can't serial line login via cross-cable 
Date: Fri, 13 Oct 2000 14:59:34 +0100

 > 
 > >Number:         21935
 > >Category:       conf
 > >Synopsis:       Can't serial line login via cross-cable
 [.....]
 > -ttyd0	"/usr/libexec/getty std.9600"	vt100	on secure
 > -ttyd1	"/usr/libexec/getty std.9600"	vt100	on secure
 > +cuaa0	"/usr/libexec/getty std.9600"	vt100	on secure
 > +cuaa1	"/usr/libexec/getty std.9600"	vt100	on secure
 
 Your cross-cable is mis-wired.  It should have CD (and CTS) on one 
 side wired to DTR on the other etc.  This is a problem with most 
 ``laplink'' cables.
 
 Your fix is quite appropriate.  The ttyd devices will block on open 
 'till carrier is available - which will never happen.
 
 I'll close the PR when I get a 
  chance....
 -- 
 Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
       <http://www.Awfulhak.org>                   <brian@[uk.]OpenBSD.org>
 Don't _EVER_ lose your sense of humour !
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: brian 
State-Changed-When: Sun Oct 15 13:15:19 PDT 2000 
State-Changed-Why:  
I believe the cross cable is miswired - unless you have a 
CD <-> CTS/DTR wiring, you must use cuaa*. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21935 
>Unformatted:
