From owner-freebsd-current@freebsd.org Sun Jun 21 21:12:22 2020 Return-Path: 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 982B33344DA for ; Sun, 21 Jun 2020 21:12:22 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49qlc56t3Gz4f3F; Sun, 21 Jun 2020 21:12:21 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 05LLCKLX006978; Sun, 21 Jun 2020 14:12:20 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 05LLCKQR006977; Sun, 21 Jun 2020 14:12:20 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202006212112.05LLCKQR006977@gndrsh.dnsmgr.net> Subject: Re: ? ????? ??: vnc can't connect to socket In-Reply-To: <202006212108.05LL8STF006936@gndrsh.dnsmgr.net> To: "Rodney W. Grimes" Date: Sun, 21 Jun 2020 14:12:20 -0700 (PDT) CC: Ian Lepore , Michael Tuexen , "bergerkos@yahoo.co.uk" , "freebsd-current@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 49qlc56t3Gz4f3F X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [0.16 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.45)[-0.451]; NEURAL_HAM_LONG(-0.33)[-0.326]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.04)[0.041]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[freebsd.org,yahoo.co.uk]; SUBJECT_HAS_QUESTION(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jun 2020 21:12:22 -0000 > > On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote: > > > > On 21. Jun 2020, at 14:28, Kostya Berger > > > > wrote: > > > > > > > > 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. > > > > > > 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. > > 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! > > > > I guess, https://svnweb.freebsd.org/changeset/base/361752 is the > > > relevant commit here. > > > > > > > *BSD has always accepted 0 as a synonym for localhost (and iirc, linux > > does not). If this no longer works, it's a regression which is going > > to cause existing applications and scripts to fail. At the very least > > it deserves an entry in UPDATING. > > 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 And to add the netstat data to show what connected: tcp4 0 0 127.0.0.1.22 127.0.0.1.43135 ESTABLISHED tcp4 38 0 127.0.0.1.43135 127.0.0.1.22 ESTABLISHED Can we back this commit out, discuss it in next weeks call, and then find a way forward? > > INADDR_ANY is the wildcard listen address, but as a destination what code remapped > it to 127.0.0.1? > > We should very seriously consider restoring this behavior. > > > -- Ian > > > > > Best regards > > > Michael > > > > ?????????? ?? Yahoo ????? ??? Android > > > > > > > > ??, 21 ???. 2020 ? 9:40 Kostya Berger > > > > ???????(-?): 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 > > > > _______________________________________________ > > > > 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" > > > > > > _______________________________________________ > > > 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" > > > > > > > _______________________________________________ > > 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" > > > > > > -- > Rod Grimes 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" > -- Rod Grimes rgrimes@freebsd.org