Re: В ответ на: vnc can't connect to socket

On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
> > On 21. Jun 2020, at 14:28, Kostya Berger <bergerkos_at_yahoo.co.uk>
> > 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 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.

-- Ian

> Best regards
> Michael
> > Отправлено из Yahoo Почты для Android 
> > 
> > вс, 21 июн. 2020 в 9:40 Kostya Berger<bergerkos_at_yahoo.co.uk>
> > написал(-а):   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_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> > freebsd-current-unsubscribe_at_freebsd.org"
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "
> freebsd-current-unsubscribe_at_freebsd.org"
>