From owner-freebsd-questions@freebsd.org Thu Nov 8 20:07:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF5A21103847 for ; Thu, 8 Nov 2018 20:07:21 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EDD6769C4C for ; Thu, 8 Nov 2018 20:07:20 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541707632; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=WKAQ2D9GTwjpr1Zus/f3IVm0WXVS/6FzKzZwPGn9AI7iasC5+OTw22/Mq73+hpdZX1Ae1/BPk9wST iMQdZcV291kDJgHxz2lr1/ribYglKaHWwMqWo5z93VpRwbO12hwq9FRMeRg5zGMMLBtuCL21ut78bp XMQPdTFMHPUgMH9xeLSL7Fdk+JT+O56SOAbcn0BliXAWQTkWeezUHTukucSzCRl3yBo93XTBlQv82s lLiv4Icwzqq/N5q+exx3VVJ21q5YPMsMCDYfmSFQOEDdDMEa7E/c3Av6/J1mjwDqwBP/NgfAcCfjor bycFZbK1wITeLjsnJ9x7qrdBSJfHr6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=60FHaLIj37/ZJgG5ns0Db2FyVBghMJo8dpIpUxiG6M8=; b=SqsQOwpX2AOTaOE1Xi17goWxFPnQ5ZIM3g3Hubl3HdhIxJiR1N9QoinITYykkoNzsdFMzerdaTZJo Q/0FEW/nuH0jt42W3vMRUrnAB1szTcHAD5hinGZo6fxG3TzKOUf3RRGRG40FJilcmxVr8RWxCDjgEj IkTgUWyhuNmbzDmOAzJLtby4Zfx1ov/j9lDM+40EiePlAype+cgdr1L8HX9WJ6Ey477xzurtxPaggq OQZrknnftwmsM/6GFIj2Sr+IGZqVQYQZo+K2r18Nx3DPMBwVKHT5TTFsrAIwUj4E9N3ur4Vk2rHeVL ubJAgbEJ0cRN07bXmj/FvyyWCUw+PPQ== ARC-Authentication-Results: i=1; outbound1.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=60FHaLIj37/ZJgG5ns0Db2FyVBghMJo8dpIpUxiG6M8=; b=GJNmJxx5jqVPKk35l5NWuIh3yzVFGxlZjzRpDL6s9gRWRk8gFxhJMX1PtM5aryeVetp3r214EAOfj gWmM82SDGqDYS4KzSPhoTM6BCkmi27gO5JDLQfd4fFT478DTiuvzUovAnedowFaze5kZzN7OSo4GgD bFTnNdufKWCd3k/WVHtkFfWTqdaBza5Jn0q8l5K7fLqKPswrIZNGKAXAMscim3W8bzj5YFZ98s+GEC mg6bcDN7aOtdvlsoOL+eY9moRLbmnxbMa/XWgtePrYLp2fTO/OR8+onN5EPIcg9XBPE2WLxijrAtS9 LMiQV6OjTKXmTmsSBIZbRGTS955bUTg== X-MHO-RoutePath: aGlwcGll X-MHO-User: dc4d6a2b-e391-11e8-9048-075f73944867 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id dc4d6a2b-e391-11e8-9048-075f73944867; Thu, 08 Nov 2018 20:07:08 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA8K72lV086189; Thu, 8 Nov 2018 13:07:02 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1541707622.52306.134.camel@freebsd.org> Subject: Re: sudo not available after configuring ipmi serial over lan From: Ian Lepore To: Jordan Caraballo Cc: eugen@grosbein.net, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Date: Thu, 08 Nov 2018 13:07:02 -0700 In-Reply-To: References: <1541691574.52306.94.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: EDD6769C4C X-Spamd-Result: default: False [-103.95 / 200.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ALLOW_DOMAIN_WHITELIST(-100.00)[freebsd.org]; HAS_XOIP(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: mx66.freebsd.org]; DKIM_TRACE(0.00)[outbound.mailhop.org:+]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[60.211.177.67.zen.spamhaus.org : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:16509, ipnet:52.58.0.0/15, country:US]; IP_SCORE(-0.16)[asn: 16509(-0.70), country: US(-0.09)]; MID_RHS_MATCH_FROM(0.00)[]; ARC_ALLOW(-1.00)[i=1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[outbound.mailhop.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[202.109.58.52.list.dnswl.org : 127.0.20.0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2018 20:07:22 -0000 On Thu, 2018-11-08 at 12:47 -0500, Jordan Caraballo wrote: > Hi Ian, > Changing the line following line from std.115200 to 3wire.115200 > worked. > Can you explain the why? I am not entirely sure of the difference > between > 3wire and std there. > > ttyu0   "/usr/libexec/getty 3wire.115200" vt100   on          secure > > Thanks, > - Jordan > The standard setting honors the modem control lines on the serial port, so any attempt to open that serial device will block until the carrier- detect line on the port is asserted. The 3wire setting indicates that only RX, TX, and GND are connected, and modem-control signals should be ignored. An open of such a device will return immediately whether anything is actually connected to the serial port or not. A /dev/ttyN device is assumed to be a "call-in" device and has the blocking behavior by default. A /dev/cuaN device is assumed to be a "call-out" device that doesn't wait for modem carrier by blocking. Using the std vs 3wire designations in /etc/ttys causes init(1) to set termios(4) flags to implement blocking-open or immediate-open behavior without needing to change the device name as well. -- Ian > El jue., 8 nov. 2018 a las 10:39, Ian Lepore () > escribió: > > > > > On Thu, 2018-11-08 at 06:10 +0700, Eugene Grosbein wrote: > > > > > > 08.11.2018 5:56, Jordan Caraballo wrote: > > > > > > > > > > > > > > > Hi guys, > > > > > > > > After configuring ipmi serial over lan console, I am not being > > > > able > > > > to > > > > execute any command related to sudo; not even "sudo su -". I am > > > > using ttyu0 > > > > and COM1 on a Dell R530. Everything regarding receiving output > > > > and > > > > typing > > > > at the serial console is fine; the only command not working is > > > > sudo. > > > > > > > > Any ideas? Below are the configurations. > > > > > > > > /etc/ttys > > > > > > > > # Serial terminals > > > > # The 'dialup' keyword identifies dialin lines to login, > > > > fingerd > > > > etc. > > > > #ttyu0  "/usr/libexec/getty 3wire"      vt100   onifconsole > > > > secure > > > > ttyu0   "/usr/libexec/getty std.115200" > > > > vt100   on          secure > > > Use network access to perform the following: > > > > > > 1) Change "on" to "off" for ttyu0 then run "init q" to apply > > > changes. > > > 2) Replace "ttyu0" with "cuau0" within same line then run "init > > > q" > > > again. > > > > > > Then retry using console and sudo. > > The easy way to accomplish the same thing is to change std.115200 > > to > > 3wire.115200 (and then do 'init q'). > > > > -- Ian > > >