Re: sudo not available after configuring ipmi serial over lan
09.11.2018 3:26, Eric Borisch wrote: > What I find interesting is that with the 'wrong' setting, you can log still > in just fine, and run most commands, but 'sudo' alone fails as described > above. (I've had the same experience on Serial-over-IPMI, but 'su' worked > fine so I never dug into it.) > > It's an easy fix, but I'm still (academically) interested in what it is > that sudo is doing that is unique. It calls syslog() function with parameters that (for default /etc/ttys and /etc/syslog.conf) makes an attempt to write to the console that blocks. You can easily verify this using "ktrace -i sudo ..." and "kdump" after. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
What I find interesting is that with the 'wrong' setting, you can log still in just fine, and run most commands, but 'sudo' alone fails as described above. (I've had the same experience on Serial-over-IPMI, but 'su' worked fine so I never dug into it.) It's an easy fix, but I'm still (academically) interested in what it is that sudo is doing that is unique. - Eric ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
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 > > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
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 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 > -- Jordan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Update to 12.0-RELEASE schedule
The 12.0-RELEASE schedule has been updated, adding BETA4 to the schedule in order to provide additional testing for changes that fix a boot time issue, in addition to allowing more time for packages for arm and arm64 to finish building, before branching releng/12.0 and starting the RC phase of the cycle. (Note, the change for the boot time issue is not yet in stable/12.) The 12.0 schedule has been updated on the website at: https://www.freebsd.org/releases/12.0R/schedule.html Thank you in advance for your patience. Glen On behalf of: re@ signature.asc Description: PGP signature
Re: sudo not available after configuring ipmi serial over lan
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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: TP-LINK TL-WN321G
On 27 Oct 2018, at 18:43, tech-lists wrote: On 27/10/2018 18:50, Bjoern A. Zeeb wrote: ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (450mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x148f idProduct = 0x5370 This is indeed a Ralink RT5370, so run(4) as it attached. There seem to be at least 4 versions of the “TP-LINK TL-WN321G” all being Ralink chips. Earlier versions were indeed Ralink RT25xx based it seems, which is rum(4). I’ve updated the man pages to reflect this: https://svnweb.freebsd.org/changeset/base/340251 Thanks a lot for reporting, /bz ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
Hi, Am 07.11.18 um 23:56 schrieb Jordan Caraballo: > 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. > try looking into a manpage of your choice, does this work? We had similar problems here with IPMI/SOL, these could be fixed by using a 3wire getty instead of std: ttyu0 "/usr/libexec/getty 3wire.115200" vt100 on secure with kind regards, Robert Schulze ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
It hangs. No output at all. Latest testing showed that if I do: # sudo su - And hit Ctrl-C two times I get the password prompt, however, when I enter the password it ignores it ( no error message). /var/log/auth.log just records that the user executes the “su -“ command. Just to be clear, when using normal console or kvm, this works fine. On Thu, Nov 8, 2018 at 7:27 AM Ronald Klop wrote: > On Wed, 07 Nov 2018 23:56:26 +0100, 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. > > > What do you mean by 'not working'? Is there an error message? Does it > hang? Do you get logged out? > > Regards, > Ronald. > > > > > > 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 > > ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure > > ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure > > ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure > > # Dumb console > > dcons "/usr/libexec/getty std.9600" vt100 off secure > > > > /boot/loader.conf > > > > # ipmi enabled > > ipmi_load="YES" > > # ipmi configurations > > boot_multicons="YES" > > boot_serial="YES" > > # serial configurations for COM1 > > console="comconsole,vidconsole" > > comconsole_speed="115200" > > comconsole_port="0x3F8" > > hint.uart.0.flags="0x00" > > hint.uart.2.flags="0x10" > > > -- Jordan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sudo not available after configuring ipmi serial over lan
On Wed, 07 Nov 2018 23:56:26 +0100, 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. What do you mean by 'not working'? Is there an error message? Does it hang? Do you get logged out? Regards, Ronald. 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 ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure /boot/loader.conf # ipmi enabled ipmi_load="YES" # ipmi configurations boot_multicons="YES" boot_serial="YES" # serial configurations for COM1 console="comconsole,vidconsole" comconsole_speed="115200" comconsole_port="0x3F8" hint.uart.0.flags="0x00" hint.uart.2.flags="0x10" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
