Date: Mon, 22 Jun 2020 14:11:57 +0000 (UTC) From: Kostya Berger <bergerkos@yahoo.co.uk> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Michael Tuexen <tuexen@freebsd.org> Cc: Ian Lepore <ian@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: ? ????? ??: vnc can't connect to socket Message-ID: <1182799644.3507612.1592835117691@mail.yahoo.com> In-Reply-To: <3E06883E-BAB1-4E1A-AB20-06DD1F812057@freebsd.org> References: <202006212112.05LLCKQR006977@gndrsh.dnsmgr.net> <3E06883E-BAB1-4E1A-AB20-06DD1F812057@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
BTW, I was not using it purposefully. I think I used it because it was sugg= ested by TigerVNC viewer itself. The original connect dialogue, I think, ha= d that address in it. So I used it, and it worked. This is how I remember i= t. Other than that I NEVER used this wildcard address unless suggested by d= ocumentation in certain configurations. With kindest regards, Kostya Berger =20 =20 On Monday, 22 June 2020, 16:56:41 GMT+3, Michael Tuexen <tuexen@freebsd= .org> wrote: =20 =20 > On 21. Jun 2020, at 23:12, Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.n= et> wrote: >=20 >>> On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote: >>>>> On 21. Jun 2020, at 14:28, Kostya Berger <bergerkos@yahoo.co.uk> >>>>> wrote: >>>>>=20 >>>>> Ok, it turns out, it gives the previously mentioned error only if I >>>>> use VNC server string 0.0.0.0:5900 (as I always did). in my VNC >>>>> client.But when replaced with127.0.0.1:5900it connects all right. >>>>=20 >>>> I don't hink 0.0.0.0 is a valid destination address you can use in >>>> connect(). Using 127.0.0.1 should >>>> be fine. >>=20 >> I do not believe that this is a destination address when your talking >> about 0.0.0.0:5900 on the VNC server side, that is a wild card accept >> any address and if this has been broken.. it must be fixed! >>=20 >>>> I guess, https://svnweb.freebsd.org/changeset/base/361752 is the >>>> relevant commit here. >>>>=20 >>>=20 >>> *BSD has always accepted 0 as a synonym for localhost (and iirc, linux >>> does not).=C2=A0 If this no longer works, it's a regression which is go= ing >>> to cause existing applications and scripts to fail.=C2=A0 At the very l= east >>> it deserves an entry in UPDATING. >>=20 >> I am not aware of that, but can not deny it either, and just confirmed >> it to be true: >> root {1002}# telnet 0.0.0.0 22 >> Trying 0.0.0.0... >> Connected to 0.0.0.0. >> Escape character is '^]'. >> SSH-2.0-OpenSSH_7.8 FreeBSD-20180909 >=20 > And to add the netstat data to show what connected: > tcp4=C2=A0 =C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 0 127.0.0.1.22=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 127.0.0.1.43135=C2=A0 =C2=A0 =C2=A0 =C2=A0 ESTABLI= SHED > tcp4=C2=A0 =C2=A0 =C2=A0 38=C2=A0 =C2=A0 =C2=A0 0 127.0.0.1.43135=C2=A0 = =C2=A0 =C2=A0 =C2=A0 127.0.0.1.22=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ESTABLI= SHED >=20 > Can we back this commit out, discuss it in next weeks call, > and then find a way forward? >=20 >>=20 >> INADDR_ANY is the wildcard listen address, but as a destination what cod= e remapped >> it to 127.0.0.1? >>=20 >> We should very seriously consider restoring this behavior. Reallowing 0.0.0.0 is covered by https://reviews.freebsd.org/D25401 Best regards Michael >>=20 >>> -- Ian >>>=20 >>>> Best regards >>>> Michael >>>>> ?????????? ?? Yahoo ????? ??? Android=20 >>>>>=20 >>>>> ??, 21 ???. 2020 ? 9:40 Kostya Berger<bergerkos@yahoo.co.uk> >>>>> ???????(-?):=C2=A0 Hi,upgraded to 362292 via buildworld.Now I cannot >>>>> connect to my bhyve guest as I used to: neither via VNC nor via >>>>> RDP.VNC gets error: unable to connect the socket. Address family >>>>> not supported by protocol family (47). >>>>> Neither can I ping my bhyve IP (it uses a separate NIC and should >>>>> have no problems) >>>>> Internet connectivity is ok and I can ping other hosts on my >>>>> network. >>>>> In 359997 all works fine. >>>>> ?????????? ?? Yahoo ????? ??? Android=C2=A0=20 >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to " >>>>> freebsd-current-unsubscribe@freebsd.org" >>>>=20 >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to " >>>> freebsd-current-unsubscribe@freebsd.org" >>>>=20 >>>=20 >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >>>=20 >>>=20 >>=20 >> --=20 >> Rod Grimes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 rgrimes@freebsd.org >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" >>=20 >=20 > --=20 > Rod Grimes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 rgrimes@freebsd.org _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" =20 From owner-freebsd-current@freebsd.org Mon Jun 22 14:57:38 2020 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 405A434EA0F for <freebsd-current@mailman.nyi.freebsd.org>; Mon, 22 Jun 2020 14:57:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49rCFF3xq7z3Rjs for <freebsd-current@freebsd.org>; Mon, 22 Jun 2020 14:57:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x829.google.com with SMTP id i3so3320126qtq.13 for <freebsd-current@freebsd.org>; Mon, 22 Jun 2020 07:57:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Dyirvr4ZtiCs8D744ane26paI0xPkhMmgj77m2Q6Pec=; b=doND5NcPOo27yjYrzY/BOX21jXz09O2YhJhtJK8ztMTAJiA3Nnxenjm4i5wUmJolZ+ PpjtePXFBKO3QbbLu1Tj6rQQwt5wLATsF1Rrl8g9sMOHmq5GGId9C/z0lEnNfonuWH5c XfaYrzdiyVtHSvMUuACgpDD9mFC8fPxMcbQdkUEpws4tV4N6fwT4pL/WtWA8PUlAx5nZ RRRirqpwappcbgdXQqlQUT4l3RNHnPzaEGE+fby5WU5+uzr9kAJ47NGsFqZ9J+fN3a4T wV8QgqPj3S+L0aWCiAP5zwZqYKXDJsOMSFmc05a5iXMb+9dylfLt9kv52gAPS4arBpA9 PZQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Dyirvr4ZtiCs8D744ane26paI0xPkhMmgj77m2Q6Pec=; b=ptRCm4pPJkul1ju7gNBWytiFgNpNfXW9DmVYV1q2eOq+BxHrH/Bawlf+G3AZJRVkdR /JMZdHh+uGlj2FjlNPV6vIf9EW8uxh4PM6gUIVUb1A7GyAzPC6A1tOeIbPDEcLe7HfbK mu84itu+7d5neORFQghueuk71LdznV0Mqj0l3uyyne0cbOnsxfzQK5On9zoy8s0Ib4x9 lx7NvLLc+ZCshdyR+De4/SdZhgy6K+/wNo66mOj5CYsqncxpL/uVOTfXBt0yOEJiSl0z 0gwianmTH6TvCc0d4LIcHttIBcf69Q7e/UpOh7jpqtQNptepVW8gTaXDQqbQ61dlojPw kswQ== X-Gm-Message-State: AOAM531clrAkmHxhyUN5GbtsQwFnG/ypFF7OkqDDet+Qm/BDJ+6rc8Zx 0LfTIcQoCSKGk9z6dIL859XD76XLfCO4aRYCeav/baLkjKk= X-Google-Smtp-Source: ABdhPJyCAwqimxfqUhxVIxKxzJCZfuZ2emsJBRo7DihU/6IGrGpojIlIeFiyxQohuj8jE5o482p/IPo8ZAAVr7SIwss= X-Received: by 2002:aed:3386:: with SMTP id v6mr17227021qtd.187.1592837855821; Mon, 22 Jun 2020 07:57:35 -0700 (PDT) MIME-Version: 1.0 References: <20200619.052348.232031363704679601.yasu@utahime.org> <20200622.164523.492970231904065687.yasu@utahime.org> <20200622.191348.2299220192956341788.yasu@utahime.org> In-Reply-To: <20200622.191348.2299220192956341788.yasu@utahime.org> From: Warner Losh <imp@bsdimp.com> Date: Mon, 22 Jun 2020 08:57:24 -0600 Message-ID: <CANCZdfqujHd2omS6G2AP7GOYdTOBVZf_a6yZ9Zj566kmpb5m0A@mail.gmail.com> Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot To: Yasuhiro KIMURA <yasu@utahime.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> X-Rspamd-Queue-Id: 49rCFF3xq7z3Rjs X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=doND5NcP; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::829) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-2.42 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.94)[-0.940]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.992]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::829:from]; NEURAL_HAM_SHORT(-0.49)[-0.491]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/> List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 22 Jun 2020 14:57:38 -0000 On Mon, Jun 22, 2020 at 4:14 AM Yasuhiro KIMURA <yasu@utahime.org> wrote: > From: Yasuhiro KIMURA <yasu@utahime.org> > Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot > Date: Mon, 22 Jun 2020 16:45:23 +0900 (JST) > > > I tried bisect and found this problem happens with r342108 and > > after. Commit message of r342108 says as following. > > > > yasu@rolling-vm-freebsd5[1012]% LANG=C svn log -c 342108 > > ------------------------------------------------------------------------ > > r342108 | cem | 2018-12-15 14:46:04 +0900 (Sat, 15 Dec 2018) | 7 lines > > > > efirt: When present, attempt to use EFI runtime services to shutdown > > > > PR: maybe related to 233998 (inconclusive at this time) > > Submitted by: byuu <byuu AT tutanota.com> (previous version) > > Reviewed by: imp > > Differential Revision: https://reviews.freebsd.org/D18506 > > > > ------------------------------------------------------------------------ > > yasu@rolling-vm-freebsd5[1013]% > > > > Judging from it, I think it's very likely that this commit caused the > > problem. > > > > Then is there anything I can do for further investigation? > > I submitted this problem to Bugzilla. > > Bug 247474 - `shutdown -p now` fails to power off with VirtualBox UEFI boot > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247474 > Does setting the tunable hw.efi.poweroff=0 help you? Warner > --- > Yasuhiro KIMURA > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1182799644.3507612.1592835117691>